User Agent Parser & Display

Parse any user-agent string and display the browser, engine, OS, device and bot details instantly. Colour-coded UA anatomy, headless/automation detection, live Client Hints, inspect your own UA, and export JSON — free, private, runs in your browser.

Paste any user-agent string and this parser breaks it down into plain language — the browser and its version, the rendering engine (Blink, WebKit, Gecko), the operating system, the device type, vendor and model, and whether the visitor is a bot or crawler. It also auto-detects and displays the user-agent your own browser is sending right now, so you can see exactly what servers learn about you on every request.

Share
Category
Developer Tools
Includes
8 features
Access
Free · No sign-up
Privacy
Runs in your browser
User Agent Parser & Display

Calibrating User Agent Parser......

Please wait a moment

How to use

How to use User Agent Parser & Display

  1. 01

    Paste a user-agent string

    Drop any UA string into the box — from a log file, a support ticket, or an analytics report. You can also click 'Use my browser' to load the exact UA your current browser sends, or pick a sample from the presets menu.

  2. 02

    Read the parsed breakdown

    The tool instantly shows the browser, version, rendering engine, operating system, device type, vendor, model and CPU architecture in clean cards, plus a full field-by-field table you can copy.

  3. 03

    Check for bots & crawlers

    If the string belongs to a bot or search crawler (Googlebot, Bingbot, and more), a clear banner flags it so you can tell human traffic from automated requests at a glance.

  4. 04

    Copy or export

    Copy any single field with one click, grab the entire breakdown as formatted JSON, or review your live browser environment (platform, language, screen, and privacy signals) — all locally, nothing uploaded.

Use cases

Common use cases

  • Debug why a website serves different content to a specific browser or device.
  • Investigate suspicious traffic by decoding the user-agent in your server logs.
  • Confirm whether an incoming request is a real visitor or a crawler/bot.
  • Show support or QA exactly which browser and OS a bug was reported on.
  • Teach or learn how browsers identify themselves to web servers.
  • Validate the user-agent your own app or script is sending on each request.
Overview

What a user-agent string actually tells you

Every time a browser, crawler, or app requests a web page it sends a User-Agent (UA) header — a single line of text that identifies the software, its version, the operating system, and often the device. Servers read this string to decide which HTML, CSS, or JavaScript to send, which is why the same URL can look different on a phone and a desktop. A user-agent parser turns that cryptic string into structured, human-readable facts instead of a wall of characters.

How the parser breaks a UA down

Modern user-agent strings bundle several layers: the browser (Chrome, Safari, Firefox, Edge…) and its version, the rendering engine that powers it (Blink, WebKit, Gecko), the operating system (Windows, macOS, iOS, Android, Linux), and — on phones and tablets — the device vendor and model. This tool runs the well-maintained ua-parser-js engine entirely in your browser to extract each layer, so you get a clean card for the browser, engine, OS, and device without uploading anything.

Spotting bots and search crawlers

Not every UA comes from a person. Search engines send crawlers like Googlebot and Bingbot, and countless other bots scan the web for indexing, monitoring, or spam. This parser flags crawler and bot user-agents immediately, so you can separate automated traffic from real visitors — useful for analytics, rate limiting, and security triage. Because detection runs locally, you can check a suspicious string without sending it anywhere.

See exactly what your browser broadcasts

Beyond parsing pasted strings, the tool reads the user-agent your own browser is sending right now and pairs it with live environment details — platform, language, screen size, CPU threads, and privacy signals like Do Not Track. It's a quick, privacy-focused way to understand the digital fingerprint you expose on every request, and a reminder of why client-side, no-upload tools keep that information on your machine.

Features
01
Parse any user-agent string in real time
02
Browser, version, engine & OS breakdown
03
Device type, vendor & model detection
04
Colour-coded raw UA anatomy highlighter
05
Bot, crawler & headless/automation detection
06
Live Client Hints (navigator.userAgentData) + high-entropy values
07
Auto-detects and displays your own UA & environment
08
Copy any field or export the full JSON
FAQ

Frequently asked questions

What is a user-agent string?+

A user-agent string is a line of text your browser or app sends in the 'User-Agent' HTTP header on every request. It identifies the software (e.g. Chrome 124), the rendering engine, the operating system (e.g. Windows 11), and sometimes the device model, so the server knows how to format the response.

How do I parse a user-agent string online for free?+

Paste the user-agent string into this tool and it immediately breaks it into browser, version, engine, OS, device type, vendor, model, and CPU architecture. No signup and nothing is uploaded — the parsing happens entirely in your browser.

Can this tool detect bots and crawlers?+

Yes. It flags user-agents belonging to known bots and search crawlers such as Googlebot and Bingbot with a clear banner, so you can tell automated traffic apart from real visitors at a glance.

How do I see my own user-agent?+

Click 'Use my browser' and the tool loads the exact user-agent your current browser sends, then displays the parsed browser, OS, device, and engine details plus your live environment (platform, language, screen, and more).

Can it detect headless or automated browsers?+

Yes. Alongside search-crawler detection, the parser flags headless and automation clients — HeadlessChrome, PhantomJS, Electron, Puppeteer, Playwright and Selenium — with a distinct banner, which is useful for filtering bot traffic out of analytics and for QA.

What are Client Hints and does this show them?+

Client Hints (navigator.userAgentData) are the modern, structured replacement for the User-Agent string in Chromium browsers. When your browser supports them, the tool displays the low-entropy brands, mobile flag and platform, then requests high-entropy values like platform version, CPU architecture, bitness and the full browser version.

Is my user-agent data uploaded to a server?+

No. All parsing runs locally in your browser using client-side JavaScript. The string you paste — and the environment details read from your device — never leave your machine.

Why does the same website look different on my phone and laptop?+

Because your browser sends a different user-agent on each device, servers use it to pick a mobile or desktop layout, adjust features, or serve device-specific code. Parsing the UA reveals exactly which browser and OS each device is reporting.