User-Agent Parser
Read a User-Agent string and see which browser, engine, operating system and kind of device it describes.
Examples
Files are processed in your browser and are never uploaded to a server.
How to use
Free to use with no sign-up, no install and no usage limit.
Paste a User-Agent string from a log and it is broken into browser, engine, operating system and device. The button below fills in the string your own browser is sending right now.
These strings are almost unreadable on purpose. Thirty years of compatibility theatre are stacked in them: Chrome calls itself Mozilla, KHTML and Safari, all in the same line, so that old server-side checks keep working.
That stacking is why order matters more than pattern matching. Edge, Opera, Samsung Internet and Whale all carry Chrome/ in their string, so a parser that looks for Chrome first reports every one of them as Chrome.
Safari is the other trap. The number after Safari/ is a build number, not the version — the version lives in Version/. Reading the wrong one turns Safari 17.6 into Safari 605.
Android tells you the device kind by whether Mobile appears: with it a phone, without it a tablet. That is Google’s own rule, and it is the only signal in the string.
Treat any of this as a hint, not a fact. A User-Agent is sent by the client and can say anything at all, so never make a security decision from it.
Nothing you paste is sent to a server. The string is parsed inside your browser.