🕵️ User Agent Parser
Paste a user-agent string to see the browser, engine, OS, device type, and CPU architecture.
Samples:
Paste a user-agent string above or pick a sample to see the breakdown.
Breakdown
🔍 Raw token list
Every Token/Version pair the parser extracted from the string, in source order.
| Token | Version |
|---|
No Token/Version pairs found.
📖 Detection notes
Browser priority
| Edg / EdgA / EdgiOS | Edge (checked before Chrome) |
| SamsungBrowser | Samsung Internet |
| OPR / Opera | Opera |
| FxiOS / Firefox | Firefox |
| CriOS / Chrome | Chrome |
| Version + Safari | Safari (after the above) |
| MSIE / Trident rv: | Internet Explorer |
| bot / crawl / spider | generic bot fallback |
Windows NT → marketing
| NT 10.0 | Windows 10/11 |
| NT 6.3 | Windows 8.1 |
| NT 6.2 | Windows 8 |
| NT 6.1 | Windows 7 |
| NT 6.0 | Windows Vista |
| NT 5.1 / 5.2 | Windows XP |
About the User Agent Parser
Every HTTP request from a browser includes a User-Agent header — a single string identifying the browser, OS, and device. This tool breaks one down into the structured fields most analytics and server-side detection use: browser family + version, layout engine, OS + marketing name, device type, and CPU architecture.
How to use
- The textarea starts with your own browser's UA — edit or replace it to test others.
- Pick a sample chip for a representative UA from a different platform.
- Read the breakdown card; expand Raw token list to see every parsed
Token/Versionpair. - Paste a server log line directly — anything around the UA gets ignored.
Common use cases
- Reproducing a bug report — "which browser version was the user on?"
- Spot-checking server logs to tell humans from bots.
- Sanity-checking what your analytics dashboard parsed.
- Learning how spoofing works — note how Chrome's UA still includes "Safari" and "Mozilla".
Tips & caveats
- UA strings are advisory — every modern browser pretends to be several others for backwards compatibility.
- Windows 10 and 11 share
NT 10.0; this tool labels them "Windows 10/11". - iOS UAs say
Mac OS X; iPad UAs since iPadOS 13 default to a desktop Safari UA. - For production detection prefer feature detection or UA Client Hints (
Sec-CH-UA-*) over UA parsing.