About
Paste a User-Agent from a log line and get the browser, operating system, and device type it describes. There is also a button for your own, which is the quick answer when a support request asks what you are running.
How to use
Paste the string, or use your current browser's. The result is a reading of the text, so a spoofed or trimmed UA is reported exactly as written.
A claim, not a fingerprint
The User-Agent is a header the client chooses to send. Anyone can change it, automated tools routinely do, and browsers have been trimming what they include for privacy reasons. Reading one tells you what the request said about itself, which is genuinely useful for reproducing a bug and close to worthless as an identity check.
Reading a line out of a log
The pattern to look for is the last recognisable product token, since the string is largely a stack of compatibility claims. Chrome announces Safari, Edge announces Chrome, and an embedded webview announces whichever app is hosting it. When a user reports that a page fails only for them, the app or webview part of the string is usually the difference that matters.
When two parsers disagree
Every parser is a pile of patterns maintained by someone, and the piles differ. New browser versions land before rules are updated, reduced strings drop details that rules expected, and bots imitate browsers deliberately. Where a decision depends on the answer, verify with something more reliable than the header, because building logic on User-Agent parsing tends to age badly.
FAQ
How accurate is the result?
It is as accurate as the string. A User-Agent is self reported and can be edited freely, so this reads a claim rather than detecting hardware.
Why does my analytics dashboard say something different?
Every parser carries its own rule set, and they disagree at the edges. Bots, embedded webviews, and reduced strings from modern browsers are where the disagreement concentrates.
Is the string sent anywhere?
No. Parsing happens in the page.
Why do so many strings start with Mozilla/5.0?
Historical compatibility. Browsers began claiming to be Mozilla decades ago to get past server checks, and the prefix stayed even though nothing depends on it now.
Related tools
- Developer and text tools
- What Is My IP
The public IP our server sees for your connection.
- HTTP Header Checker
Read the response headers a URL returns.
- JSON Formatter
Format, minify and check JSON in the browser.
- URL Encoder and Decoder
Percent encode or decode text, locally.
- Unix Timestamp Converter
Convert between epoch timestamps and dates.
- Cookie Converter
Convert between HTTP, JSON and Netscape cookies.