User agent parser

Handy when reading server logs or chasing a bug that only shows up on one browser.

Loading the tool…

Processing and privacy: The result is calculated inside your browser and your data is not sent to any server.

How to use it

  1. Enter user agent string.
  2. The result appears straight away and updates as you edit.
  3. Copy the result, or copy a link that keeps the same values to share it.

How it is calculated

It looks for known tokens in a set order: Edg, OPR, SamsungBrowser, Firefox, Chrome, then Safari, because most browsers also mention Chrome and Safari. The OS comes from Windows NT, Android, iPhone OS or Mac OS X.

Example

Result: Browser or client: Chrome 120.0.0.0; Operating system: Windows 10 or 11; Device type: Desktop.

Limits and caveats

  • Basic rule-based parsing, and any client can fake its user agent.
  • Windows 11 sends Windows NT 10.0 like Windows 10, and recent iPads and macOS send frozen version numbers, so exact versions cannot be told apart.

Questions about this tool

Why does the Edge user agent mention Chrome and Safari?

For compatibility with old sites, which is why the tool checks specific tokens like Edg before Chrome.

Why does an iPad show up as a Mac?

Safari on iPadOS 13 and later sends a desktop user agent by default, so the string alone cannot tell.

Is the user agent enough to verify Googlebot?

No, it can be faked. Verify with a reverse DNS lookup of the IP, as Google recommends.