User Agent Parser
Parse any User-Agent string to identify the browser, operating system, and device type.
How to Use
- Your current browser's User-Agent is shown automatically — or paste a different one to analyze.
- View the parsed breakdown: browser, version, OS, device type, and engine.
- Use this to debug device-specific issues or verify analytics data.
When to Use This
- Working out which browser and version produced a crash report, when all the ticket contains is the raw string pasted in.
- Separating bot traffic from real visitors in a sample of server logs, since crawler strings carry a recognizable token.
- Confirming what a device actually reports before writing a conditional that depends on it, rather than trusting a table found online.
- Checking what your own browser sends, as a reference point when a colleague's string looks unusual in comparison.
Frequently Asked Questions
About This Tool
The User-Agent string is a fossil record of browser politics. Almost every browser still opens with Mozilla/5.0 because servers once sniffed for it, Chrome carries Safari and AppleWebKit tokens for the same reason, and Edge appends Edg precisely because spelling out Edge broke older sniffing code. Browsers are now freezing and trimming these strings, and the detail they used to carry is moving to Client Hints headers that a site has to ask for.
This parser is an ordered list of regular expressions, checked most specific first so that Edge and Opera are not mistaken for Chrome. It maps Windows NT version numbers onto marketing names, pulls Android and iOS versions from their usual positions, classifies the device as desktop, tablet, mobile or bot, and infers Gecko, Blink, WebKit or Trident from the tokens present. Your own browser's string is filled in when the page loads.
Notes & Limits
- Brave appears in the pattern list but Brave deliberately reports itself as Chrome, so it will almost never be identified as Brave here.
- Windows NT 10.0 covers both Windows 10 and Windows 11, which cannot be told apart from the string, so they are shown together.
- Safari on macOS has reported 10.15.7 since Catalina regardless of the real version, so the macOS version shown is often not the one installed.
- Only the string is read. navigator.userAgentData and the Sec-CH-UA Client Hints headers, which carry better data on Chromium, are never consulted.