User Agent Parser
Paste any User-Agent string to break it down into browser, rendering engine, operating system, device type and CPU — live. Detects hundreds of bots and crawlers, parse your own browser's UA with one click, and copy any field or pipe the result as JSON. Runs entirely in your browser.
About this ToolHow it works, benefits & use casesTap to collapse
Drop in any User-Agent string and this parser breaks it into the pieces you care about: the browser name and version, the rendering engine (Blink, WebKit, Gecko…), the operating system and its version, the device type, vendor and model, and the CPU architecture when the UA reports one. It updates live as you type or paste, so you can experiment with variations. It also recognises hundreds of bots and crawlers and flags them with a warning banner, which is handy when you are sifting through access logs. A "Use my browser" button parses your own UA instantly, and a row of sample strings lets you compare common clients. Every field is individually copyable, and the complete parse exports as JSON to feed into other tools. Nothing is uploaded — the parsing happens entirely in your browser.
How to Use
- 1Paste a User-Agent string into the input box, or click "Use my browser" to parse your own.
- 2Or pick one of the sample strings to see how a common client is detected.
- 3Read the breakdown cards — Browser, Engine, OS, Device, and CPU when present.
- 4Watch for the amber banner that appears when the string is recognised as a bot or crawler.
- 5Click any card to copy that field, or copy/download/pipe the full result as JSON.
Key Benefits
- Splits a UA into browser, engine, OS, device, and CPU architecture
- Detects browser and OS version numbers, not just names
- Recognises hundreds of bots and crawlers with a clear warning flag
- One-click "Use my browser" parses your own navigator.userAgent
- Built-in sample strings for quick comparison across clients
- Each field is individually copyable
- Exports the full parse as JSON for piping into other tools
Common Use Cases
- Investigating which clients hit an endpoint by parsing UA strings from access logs
- Distinguishing real users from bots and crawlers in traffic analysis
- Verifying the device and OS reported by a problematic client during a bug report
- Building or testing UA-based feature gating and analytics segmentation
- Checking what your own browser advertises before reporting an issue
Paste a UA string, pick a sample, or use your own browser's.
Paste a User-Agent string above to break it down.
Was this tool helpful?
Share Your Experience
Help others discover this tool!
Related tools
- JSON FormatterFormat and validate JSON with syntax highlighting
- JSON to TypeScriptGenerate TypeScript interfaces from JSON
- HTTP Header ParserParse and analyze HTTP headers
- Unused CSS DetectorFind CSS selectors never matched by your HTML, see how many bytes you can save, and get cleaned CSS - with a safelist for dynamic classes
- Chrome Extension Manifest GeneratorBuild a valid manifest.json (V3 or V2) with a permission picker, a live install-warning preview that mirrors Chrome’s consent dialog, validation, and a runnable starter-project ZIP
- Words to NumberConvert written words to numbers
It reports the browser name and version, the rendering engine and its version, the operating system and version, the device type, vendor and model, and — when the string includes it — the CPU architecture. Fields that the UA does not contain are simply omitted.
The parser matches the string against a large set of known bot and crawler signatures. When a match is found it shows an amber banner naming the bot, which is useful for separating automated traffic from real users when reviewing logs.