Paste a User-Agent string to parse it.
Help
About this tool
Paste a User-Agent string — or keep the one your browser sends, which is filled in automatically — and read back its browser name and version, rendering engine (Blink, Gecko, WebKit, Trident), operating system and version, device type (desktop, mobile, tablet or bot) and CPU architecture. Detection runs against a rule table built into the page, so every field is resolved locally in your browser: nothing is uploaded and the tool keeps working offline. Unknown or malformed strings simply show unknown instead of failing, and each field can be copied with one click.
How to use
- Open the tool: the input is prefilled with your own browser's User-Agent so you can try it right away.
- Paste a different User-Agent string (for example from a server log) over the prefilled value if you want to inspect another client.
- Read the parsed fields below — browser, rendering engine, operating system, device type and CPU — and click Copy next to any field to copy its value.
What is a User-Agent?
A User-Agent (UA) is the string a client sends in the User-Agent HTTP header to identify itself to a server. It typically bundles a token for the browser or app and its version, the rendering engine, the operating system and often the device model, for example Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36. Servers use it to tailor content, serve the right assets and gather analytics.
Why is the User-Agent becoming less reliable?
Browsers deliberately reduce the information in the UA. Chrome froze the minor and build numbers and now reports the OS as a coarse value, Safari often reports a simplified version, and every browser keeps a long tail of tokens only for legacy compatibility. The successor, Client Hints (Sec-CH-UA), lets sites request the details they actually need instead of reading them from the UA — but it is opt-in and not universal. The result is a string that is increasingly generic and increasingly easy to spoof, so treat any single field as a hint rather than a fact.
How accurate is the parsing?
Parsing is heuristic. It works by matching regular expressions against a string that is not standardized, so an unfamiliar client, a spoofed UA or a new device may be classified as unknown or mapped to a close but not exact match. Tokens such as Safari and Chrome also appear in many other browsers' strings, which is why detection checks derived browsers like Edge, Opera and Samsung Internet before the engines they are built on. For anything critical, combine the UA with Client Hints, feature detection or your own telemetry.
Is my data uploaded anywhere?
No. The rule table ships with the page and all parsing happens locally in your browser. The User-Agent you paste never leaves your device, is not sent to a server and is not stored, so the tool works offline and is safe to use with sensitive values.