About User-Agent strings
The User-Agent header identifies the browser, rendering engine, OS and device making a request. This parser uses heuristics covering the major browsers and platforms. Parsing happens locally in your browser.
User-Agent Parser
Parse a User-Agent string into browser, engine, operating system and device.
Frequently asked questions
What does the parser extract?
It breaks a User-Agent string into the browser and version, the rendering engine, the operating system and the device type, so you can quickly make sense of an otherwise cryptic string from your logs.
Why do User-Agent strings look so messy?
For historical compatibility, browsers include tokens from older browsers (like 'Mozilla' and 'Safari') even when they are not that browser, which is why the raw string is hard to read without parsing.
Is my User-Agent sent anywhere?
No. Parsing is heuristic and runs in your browser; the tool can even auto-fill your own User-Agent for inspection without transmitting it.