User-Agent Parser
Break down any User-Agent string into the browser, engine, operating system and device it describes — or analyse your own. Everything is parsed locally in your browser; nothing is ever transmitted.
About the User-Agent parser
Every time your browser asks a web server for a page, it introduces itself with a User-Agent header — a compact line of text describing the browser, its version, the rendering engine, and the operating system and device you are on. Servers use it to send mobile layouts to phones, offer the right download, or gather analytics. This tool reverse-engineers that line into plain, readable fields.
Parsing is done with a set of pattern rules that check for known markers in a sensible order: brand tokens like Edg/, OPR/, SamsungBrowser/, CriOS/ and FxiOS/ are tested before the generic Chrome/ and Safari/ tokens, because many browsers pretend to be Chrome or Safari for compatibility. The operating system is read from tokens such as Windows NT 10.0, Mac OS X, Android and iPhone OS, and the device type is inferred from words like Mobile, iPad and Tablet.
The string you paste and your own navigator.userAgent are analysed entirely in JavaScript on this page. No User-Agent is uploaded, logged or stored anywhere. Turn off your connection and the parser keeps working.
Why User-Agents lie
A User-Agent is trivial to change — browsers ship developer tools that spoof it, and privacy features increasingly freeze the string to a generic value. Modern iPads even report themselves as desktop Macs. So the results here are a best-effort interpretation of common patterns, not a guarantee. The same string is also one of many signals used in browser fingerprinting, and understanding what your browser reveals is part of knowing what someone can learn about you online.
Want to see everything your own browser exposes, not just the User-Agent? Try the Browser & Device Info tool, or find your public address with What Is My IP.
Frequently asked questions
What is a User-Agent string?
A User-Agent is a line of text your browser sends with every web request. It advertises the browser name and version, the rendering engine, and the operating system and device, so servers can adapt content. This tool decodes that line into readable fields.
Does this tool send my User-Agent anywhere?
No. All parsing happens with JavaScript inside your own browser. The string you paste, and your own navigator.userAgent, are never uploaded, logged or stored. You can disconnect from the internet and the parser still works.
Why can a User-Agent be inaccurate?
User-Agent strings are freely editable and often spoofed. Many browsers also freeze or reduce the values for privacy, and iPadOS reports itself as a Mac. Treat the result as a best-effort guess based on common patterns, not proof of a device.
What is a rendering engine?
The engine is the component that turns HTML and CSS into pixels. Blink powers Chrome, Edge, Opera and most others; WebKit powers Safari and every browser on iOS; Gecko powers Firefox. Two browsers can share one engine yet behave differently.
Want the theory? Read the guides → · Visit the zoo →