About this tool
Breaks a User-Agent string into the fields developers actually care about: which browser it is and what version, which rendering engine that browser uses, the operating system and version, and whether it's identifying as a desktop, mobile, or tablet device. The page opens prefilled with your own browser's real User-Agent string.
How to use the User Agent Parser
- Paste a User-Agent string from a log file, bug report, or another browser.
- Click "Parse" to see the breakdown.
- Or click "Use my browser's UA" to re-check your own.
Common use cases
- Figuring out what browser and OS a support ticket or log line actually came from
- Checking whether a User-Agent string you're about to send from a script or scraper looks legitimate
- Confirming which rendering engine (Blink, Gecko, WebKit) a browser uses before debugging a CSS or JS quirk
Worked example
A User-Agent like Mozilla/5.0 (iPhone; CPU iPhone OS 17_5 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) CriOS/126.0.6478.54 Mobile/15E148 Safari/604.1 parses to browser Chrome (iOS) version 126, but engine WebKit rather than Blink — because Apple requires every iOS browser to use its WebKit engine under the hood, so "Chrome" on an iPhone isn't running the same rendering engine as Chrome everywhere else. Getting that distinction right is exactly the kind of detail a naive parser misses.
Things to watch out for
This parser works by pattern-matching known tokens in the string, the same approach every free User-Agent parser uses — it isn't backed by a maintained device database, so a very new or unusual browser, or a deliberately spoofed User-Agent, may parse incompletely or misleadingly. Treat the result as a strong hint about what a client claims to be, not verified fact — any script can send any User-Agent string it wants.
Frequently asked questions
It only parses whatever text is in the box. The page starts prefilled with your actual navigator.userAgent value, but from then on it's just pattern-matching against the string you give it — nothing is verified against your browser's real behavior.
Because Apple requires every browser on iOS, including Chrome, to use the system WebKit engine rather than its own — so even though it identifies as Chrome, it isn't running Chrome's usual Blink engine underneath.
Yes, easily — any browser, script, or command-line tool can send whatever User-Agent string it likes. This tool tells you what a string claims, not whether that claim is genuine.