Paste a user-agent string and get the browser, rendering engine, operating system and device type. Your own is filled in to start with, which is what most people came for. The ordering is the part that separates a working parser from a broken one: Chrome's string contains the word Safari, Edge's contains both Chrome and Safari, and every Chromium fork keeps the lot while appending its own name, so the checks have to run most-specific-first or every Edge visitor gets logged as Chrome. Just as useful is what the string cannot tell you, which is stated rather than guessed at — Windows 11 is indistinguishable from Windows 10, Safari freezes its macOS version at 10.15.7, and every iOS browser is WebKit underneath. And all of it is self-reported, so treat it as a hint about a visitor, never as proof.
| Question | Answer |
|---|---|
| Windows 10 or 11? | Indistinguishable — both send NT 10.0 |
| Which macOS? | Safari freezes it at 10.15.7 |
| Engine on iOS? | Always WebKit, whatever the browser is called |
| Is the string truthful? | No — trivially changed, treat as a hint |
| Screen size or memory? | Not in the string at all |
No. The string is parsed in your browser. When you use your own, it comes from navigator.userAgent locally and is not transmitted.
Not for anything that matters. It is self-reported and takes one line to change — a developer tool, an extension or a curl flag will set it to whatever you like. Use it for analytics and for reproducing bugs, never as a security control or to gate access to a feature. Feature detection is the correct tool for deciding what a browser can do.
Because Windows 11 sends Windows NT 10.0, exactly as Windows 10 does. Microsoft kept it unchanged so that sites checking the version would not break. The two cannot be told apart from the user-agent string at all; the User-Agent Client Hints API can distinguish them, with the user's permission.
Safari froze the macOS version it reports at 10.15.7 with Catalina and has not moved it since, for the same compatibility reasons. Every newer macOS reports the same number in Safari, so your actual version is not in the string.
Because it is. Apple requires every browser on iOS to use the system WebKit engine, so Chrome, Firefox and Edge on an iPhone are all Safari's engine with a different interface. Reporting Blink there would be inaccurate.
The most popular one is dual-licensed under AGPL, which is not a licence this site can take on. The ordering rules that make a parser correct are short enough to implement directly and are covered by tests.
User-agent strings are a thirty-year pile of lies that browsers tell to get past other browsers' sniffing, and parsing them is entirely a matter of checking in the right order. Chrome's string contains Safari, Edge's contains both Chrome and Safari, Opera's contains all three, and every Chromium fork adds its own token at the end while keeping the rest. So the tests here run most-specific-first: Edge before Chrome, Chrome before Safari, and the Chromium forks before Chrome. Get the order wrong and every Edge user is reported as Chrome, which is exactly the bug in most naive parsers. Several facts simply cannot be recovered from the string, and rather than guess, they are reported as caveats. Windows 11 sends the same NT 10.0 as Windows 10, because changing it would have broken sites, so the two are indistinguishable. Safari on macOS has frozen its version at 10.15.7 since Catalina for the same reason. Every browser on iOS is required to use WebKit, so Chrome on an iPhone is Safari's engine wearing a different name, and reporting it as Blink would be wrong. Most significantly, the whole string is self-reported and trivially changed — a developer tool, an extension or one line of curl sets it to anything — so it is a hint about a visitor, never a fact, and must never be a security control. Parsing runs in your browser with no dependency on any external library.