User Agent Parser
Your browser’s user agent is shown and parsed below — or paste any UA string to break it down live.
Paste a user agent string above to see it parsed.
User agent strings are unreliable by design: browsers freeze and reduce them (Windows 11 reports NT 10.0, macOS is pinned at 10.15.7), and any client can spoof one. Treat this as a best-effort reading, not proof.
Parsed on your device — nothing is sent anywhere.
How it works
- Open the page and your own browser’s user agent string loads into the box automatically, already parsed into browser, version, operating system, device type and engine.
- To analyze a different string — from a server log, an analytics report or a bug ticket — paste it into the box and the breakdown updates as you type.
- Click Copy raw UA to put the current string on your clipboard, or Use my browser’s UA to switch back to your own.
Frequently asked questions
- How does this tool detect the browser and operating system?
- It runs a set of regular-expression heuristics over the string, checking distinctive tokens in a specific order — Edg/ before Chrome/, OPR/ before Safari — because most browsers include their competitors’ tokens for compatibility. The Windows NT number, Android version and iPhone OS token identify the operating system, and mobile or tablet markers set the device type.
- Why does my Windows 11 machine show as Windows 10 / 11?
- Every browser on Windows 10 and 11 sends the same frozen token, Windows NT 10.0, so the user agent alone genuinely cannot tell the two apart. The same applies to macOS, where Safari and Chrome have frozen the version at 10_15_7 regardless of the real release. Sites that need the true version must ask for it via User-Agent Client Hints instead.
- Why does a Chrome user agent mention Mozilla, AppleWebKit and Safari?
- Decades of servers sniffing for specific tokens forced each new browser to impersonate the ones before it, so those legacy tokens are kept purely for compatibility. Chrome claims Mozilla/5.0 and Safari/537.36, Edge adds Chrome on top of that, and Opera adds both. That layering is exactly why parsers must check the most specific token first.
- Is the user agent string I paste sent to a server?
- No. The parsing is a few regular expressions executed in your browser tab, with no network requests at all — you can confirm this in the network panel of your developer tools. That makes it safe to paste user agents from server logs or support tickets, which can be personally identifying data under privacy rules like the GDPR.
- Can I rely on user agent parsing in production code?
- Treat the result as a hint, not a fact. UA strings are trivially spoofed, browsers are actively freezing and reducing them, and Chrome now sends a reduced string that hides minor versions and device models. For adapting site behavior, feature detection and CSS media queries are far more robust; keep UA parsing for analytics, log analysis and debugging.
About this tool
This tool takes a user agent string — the identification header your browser sends with every request — and breaks it down into the parts people actually want: browser name and version, operating system, device type and rendering engine. On load it reads your own browser’s string via navigator.userAgent and parses it immediately, so you can see at a glance what your browser tells every website you visit. Paste any other string into the box and the breakdown updates live with each keystroke.
Parsing happens entirely on your device. The detection logic is a chain of regular-expression heuristics applied in careful order, because user agents are layered with compatibility tokens: a real Edge string also contains Chrome, AppleWebKit, Safari and Mozilla, so the parser must match Edg/ before falling through to Chrome/ and only then to Safari. Operating systems come from tokens like Windows NT 10.0, Android 14 or iPhone OS 17_5, and device type from mobile and tablet markers plus a check for common crawler names. Nothing is uploaded, which matters when the strings come from server logs that count as personal data.
Typical uses: decoding user agents found in access logs or analytics exports, confirming what a customer’s browser reported in a support ticket, checking what your own device sends after an update, and testing how a spoofed or automated client identifies itself. QA engineers use it to verify that emulated devices in testing tools present plausible strings.
One honest caveat — user agents are unreliable by design and getting more so. Windows 11 is indistinguishable from Windows 10, macOS versions are frozen at 10.15.7, and Chrome’s UA reduction strips minor versions and device models. When the string and reality disagree, trust reality: use this output for investigation and reporting, and use feature detection or Client Hints when code needs to make decisions.