User-Agent Parser

About this tool

Browsers pack a surprising amount of history into the User-Agent header — Chrome's string claims to be 'like Gecko', Edge's string claims to be Chrome, and Safari's version number lives in a completely different token than its WebKit build number. This tool applies the same ordered heuristics real-world lightweight parsers use to untangle that: check the most specific tokens first, fall back to the generic ones.

How to use

1. Paste a User-Agent string, or use your own browser's — pre-filled below.
2. Read off the parsed browser, engine, OS, and device type.

When to use this tool

• Debugging a bug report that only includes a raw User-Agent string.
• Checking what a specific User-Agent string actually identifies as.
• Understanding why a User-Agent-based redirect or feature check misfired.

Tips

• User-Agent strings can be freely spoofed by the client — never treat this as a security check, only as a hint for analytics or graceful degradation.
• Modern Chrome increasingly "freezes" its UA string and exposes more detail via Client Hints instead — parsing UA alone is a shrinking picture.

Limitations

• Uses ordered heuristics like every lightweight UA parser, not a maintained device database — exotic or deliberately spoofed strings can misclassify.

FAQ

How accurate is this?

It covers the common browsers and OSes well, using the same class of regex heuristics as most lightweight parsers. Exotic, embedded, or deliberately spoofed User-Agents can still be misclassified.

Is my User-Agent string sent anywhere?

No. Parsing happens entirely in your browser.

Related tools

• CIDR / Subnet CalculatorCompute network, broadcast, netmask and usable host range from CIDR.
• Regex TesterTest a regular expression live, with matches and capture groups.
• JSON FormatterFormat, validate and minify JSON with precise error reporting.