User-Agent Parser: What the String Can and Cannot Tell You
Short answer: paste a User-Agent string into the User-Agent Parser to see the browser, rendering engine, operating system, device type and any bot indicator. Every result also says how it was determined: stated, inferred, a placeholder or not determinable. That last part matters, because a User-Agent is a claim sent by the client, not a measurement.
The Basis column
- Stated: the string says it directly.
- Inferred: worked out from other tokens by a rule that can be wrong.
- Placeholder: the browser vendor reports a fixed value, so it is probably not real.
- Not determinable: nothing in the string answers it.
What the string cannot tell you
- Anyone can send anything. Browsers, scripts and privacy tools can set any value, and many browsers deliberately report less than they used to.
- Chrome and Edge report only the major version. The remaining numbers are fixed at 0. On Android, newer Chrome versions send a fixed OS version and a generic device model.
- Windows 10 and Windows 11 look the same. Both report
Windows NT 10.0. - macOS browsers report a fixed
10.15.x. An iPad in desktop mode sends the same string as a Mac. - Chrome-based browsers such as Brave and Arc send the same string as Chrome, so a Chrome token does not prove Google Chrome. Chrome, Edge and Firefox on iPhone and iPad all use WebKit.
- Device type is certain for iPhone and iPad, a rule of thumb for Android (phones include a
Mobiletoken, tablets do not) and an inference from the operating system for desktops.
Bots
Bots are recognised by name only, and anyone can send "Googlebot". To confirm a real search crawler, check the request's IP address against the operator's published ranges or use reverse DNS. The absence of a bot name never proves the client is a person. For network ranges, see the CIDR cheat sheet.
An example
Chrome/141.0.0.0 on Windows NT 10.0; Win64; x64 gives: browser Chrome 141, engine Blink, OS Windows, 64-bit, device desktop. The tool adds honest notes, such as that current Chrome versions report only the major number and that Windows 10 and 11 cannot be told apart.
Product tokens and comments
The tool also lists each product token with its version and the comments in parentheses, and shows control characters as [U+XXXX] so hidden characters are visible. For invisible text in other places, see hidden Unicode characters.
How to use the User-Agent Parser
- Open the User-Agent Parser.
- Paste a string, pick an example, or use this browser's own.
- Read the results and the Basis column.
- Copy or download the results as text or JSON for logs, tests and bug reports.
Limits to know
- It applies fixed rules to the text you give it. No device database, no lookups, no server contact.
- It cannot use User-Agent Client Hints, which are separate HTTP headers that Chromium browsers send and which are more reliable than the string.
- Treat the output as a hint, never as proof.
Frequently asked questions
Can I tell Windows 10 from Windows 11 by User-Agent?
No. Both report Windows NT 10.0.
Does "Chrome" in the string mean Google Chrome? Not necessarily; other Chromium browsers send the same token.
How do I know if a Googlebot request is real? Check the IP address against the published ranges or use reverse DNS.
Why does Chrome show .0.0.0?
It reports only the major version.
Is my string uploaded? No.