User Agent Parser
Paste any User-Agent string and see the browser, operating system and device type it reports — parsed instantly in your browser.
🔒 Processed locally in your browser
Loading…
How to use
- Paste a User-Agent string into the box, or click "Use my User-Agent" to fill in the one your own browser sends.
- Read the detected browser, operating system and device type below — they update live as you type.
- Anything the parser can't identify with confidence is reported as "Unknown" instead of being guessed at.
- Click Reset to clear the box and analyse another string.
Features
- Detects browser name and version, including Chromium-based browsers such as Edge, Opera and Samsung Internet that hide behind Chrome and Safari tokens
- Identifies Windows, macOS, iOS, Android, ChromeOS and Linux, mapping Windows NT numbers to their marketing versions
- Classifies the device as desktop, mobile, tablet or bot/crawler
- One click fills in the User-Agent your own browser is currently sending
- Runs entirely in your browser — nothing is uploaded, logged or stored
Frequently asked questions
What is a User-Agent string?
It's a short line of text your browser sends with every HTTP request, in the User-Agent header, describing itself: the browser and version, the rendering engine, and usually the operating system and platform. Sites have historically read it to serve different markup, redirect to a mobile site, count visitors by platform, or warn about unsupported browsers. It's an informal convention rather than a strict standard, which is why the strings look like such a jumble of legacy tokens.
How accurate is this parser?
It's best-effort, and deliberately so. There is no specification browsers must follow, so parsing means matching well-known patterns. Every Chromium browser ships "Chrome" and "Safari" tokens for backwards compatibility, so Edge, Opera and Samsung Internet are checked before the generic Chrome and Safari rules. When a string doesn't clearly match anything, the tool reports "Unknown" rather than inventing an answer.
Why does my iPad show up as a Mac, or my Chrome version look rounded off?
Both are the browsers' own doing. Since iPadOS 13, Safari on iPad requests desktop sites by default and sends a Mac-style User-Agent, so it genuinely reports itself as macOS. Chrome's User-Agent Reduction, meanwhile, freezes parts of the string and reduces the version to its major number with zeros after it, so minor and build numbers are no longer meaningful. The parser reports what the string says; it can't recover detail the browser removed.
Can I use the User-Agent to identify or block someone?
No. A User-Agent is just a request header, and anyone can set it to anything — a one-line command, a developer-tools toggle or a browser extension is enough. Treat this tool as a diagnostic aid for reading a string someone gave you or debugging your own requests, never as an identity or security check. For real access decisions, use authentication.
What should I use instead of sniffing the User-Agent?
For deciding whether a capability exists, use feature detection — test for the API or CSS property you actually need, so your code keeps working on browsers that didn't exist when you wrote it. When you genuinely need platform information, User-Agent Client Hints give structured, permission-aware values instead of one ambiguous string. Everything here runs locally in your browser: the string you paste is never uploaded, logged or stored.