User Agent Parser
How to use
Reads a browser User-Agent string and tells you the browser, version, operating system, rendering engine and device type behind it. Defaults to your own browser, or paste any User-Agent string to inspect it.
User Agent String
Parsed Details
- Identifying the exact browser and version behind a bug reported in server logs
- Checking what device type or OS a visitor's User-Agent claims to be
- Confirming your own browser's reported User-Agent while testing device-specific behavior
- Investigating an unfamiliar User-Agent string flagged in analytics or access logs
Why every browser claims to be several others
A modern user agent string is a fossil record of compatibility workarounds. Chrome on Windows identifies itself as Mozilla, then as AppleWebKit, then as KHTML "like Gecko", then as Chrome, then as Safari. Each of those was added so that servers sniffing for a competitor would serve the good version of a page. Netscape used "Mozilla"; Internet Explorer claimed to be Mozilla to receive frames-capable pages; Safari claimed WebKit lineage; Chrome claimed Safari. None of it can be removed now, because somewhere a server still checks for each token.
That history is why parsing a user agent string is guesswork rather than lookup, and why the results should be treated as a hint. The string is set by the client and can be anything at all: privacy tools rotate it, bots imitate browsers, and enterprise software appends its own tokens. It is fine for analytics aggregates and for logging. It is not fine as a security control or as the basis for serving different functionality, because anything relying on it can be trivially told whatever it wants to hear.
The direction of travel is toward less information, not more. Browsers have been freezing and reducing user agent strings for years, and Chrome's Client Hints replace the guessing game with an explicit request: the server asks for the specific facts it needs and the browser decides what to reveal. For feature decisions, the correct approach has always been to test for the capability rather than infer it from an identity: the string tells you what a client claims to be, and feature detection tells you what it can actually do.
Free and private. Everything runs on your own device, with no account and no uploads.
A User-Agent string looks like gibberish but actually encodes browser, OS and device details. This tool reads it and tells you exactly what browser, version, engine and device it represents.
It is commonly used for debugging browser-specific issues, analyzing server logs, or checking what a particular device reports itself as.
Yes, browsers allow overriding the User-Agent string, so it should not be treated as a fully reliable source of truth for security purposes.
Yes, device type (mobile, tablet, desktop) is included in the parsed breakdown where the string indicates it.
- 1
Start with your own browser
Your current User-Agent is shown by default.
- 2
Or paste any User-Agent string
Inspect a string from server logs or another device.
- 3
View the breakdown
See browser, version, OS, rendering engine and device type.
- ·Don't rely on User-Agent parsing alone for security decisions, the string can be freely spoofed by the client.
- ·When debugging a browser-specific bug, compare the parsed engine (not just browser name) since some browsers share the same underlying engine.
- ·Older or unusual User-Agent strings from bots and crawlers may parse incompletely, treat missing fields as expected in those cases.