User Agent String Parser
Parse Any User Agent String Into Readable Fields
Need to use User Agent String Parser right now?
Paste in any user agent string — your own or one found in a server log — and get it broken into clearly labeled fields instead of one dense unreadable line.
Your browser's user agent
Detecting...
Features
- Runs entirely in your browser
- Privacy-first — your data is never uploaded
- Real-time, instant results
- 100% free, no sign-up required
- Works on desktop, tablet, and mobile
- No installation needed
Who uses this tool?
About User Agent String Parser
Every browser identifies itself to websites with a User-Agent string — a dense, often confusing line of text packed with browser name, version, rendering engine, and operating system information. Websites use it (imperfectly) to decide which features to serve or how to render a page, and it's a common source of confusion when debugging browser-specific bugs.
This tool detects and clearly breaks down your own browser's user agent automatically, showing the browser name and version, rendering engine (Blink, Gecko, or WebKit), operating system, and device type in a readable format instead of the raw string. You can also paste in any arbitrary user agent string — from a bug report, a server log, or a different browser — to parse it the same way.
User agent strings are famously messy for historical reasons: nearly every browser's user agent includes the word 'Mozilla' regardless of what browser it actually is, a legacy from the 1990s browser wars that stuck around for compatibility reasons. Parsing them reliably means checking for more specific tokens (like 'Edg/' for Microsoft Edge) before falling back to broader ones.
This is useful for debugging browser-specific bugs reported by users, understanding what a mysterious user agent string in a server log actually represents, testing how your own site's user-agent detection logic behaves, and general curiosity about what your browser reveals about your setup.
How it works
- Your user agent is detected automatically. No input needed — it reads directly from your browser.
- Or paste any user agent string. Parse a UA string from a bug report, log file, or another browser.
- View the breakdown. Browser, engine, OS, and device type are shown clearly.
Examples
Parsing a Chrome on Windows user agent
Input
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36
Output
Browser: Chrome 120.0.0.0, Engine: Blink, OS: Windows 10/11, Device: Desktop