Skip to content

User Agent Parser

Break a user-agent string into browser, engine, OS and device.

Paste a User-Agent string to parse it.

About the User Agent Parser

Break a User-Agent string into the browser, version, rendering engine, operating system and device type. These strings are deliberately misleading for historical reasons — nearly every browser claims to be Mozilla, and every Chromium browser also claims to be Chrome and Safari.

How to use it

  1. 1 Paste a User-Agent string, or use the one your own browser is sending.
  2. 2 The parsed browser, engine, OS and device appear immediately.
  3. 3 Check the bot flag when analysing server logs.
  4. 4 Compare several strings to see how the same browser reports itself on different platforms.

What it does

  • Browser and version, resolving the overlapping brand tokens correctly
  • Rendering engine: Blink, WebKit, Gecko or Trident
  • Operating system and version
  • Device class: desktop, mobile, tablet or bot
  • Bot and crawler detection

Frequently asked questions

Why does Chrome's user agent mention Safari and Mozilla?

Compatibility theatre accumulated over thirty years. Sites used to sniff for 'Mozilla' to serve modern HTML, then for 'Safari' to serve WebKit-friendly code, so each new browser added the previous tokens to avoid being downgraded. The result is that brand order matters enormously when parsing — Edge must be checked before Chrome, and Chrome before Safari, or everything looks like Safari.

Can I trust the user agent?

No. It is a client-supplied string that anyone can set to anything, and browsers now deliberately freeze or reduce it to limit fingerprinting. Use it for analytics and rough troubleshooting; never for security decisions, and prefer feature detection over browser detection for functionality.

What is replacing the user agent?

User-Agent Client Hints — a set of Sec-CH-UA headers that expose brand and platform separately, with high-entropy details only when a site explicitly requests them. Chromium browsers already send them, but the classic string is not going away for a long time.

How reliable is the bot detection?

It matches the well-known crawlers that identify themselves honestly — Googlebot, Bingbot and similar. Bots that want to hide simply send a normal browser string, so a negative result proves nothing.

Is my user agent sent anywhere?

No. Parsing runs in your browser on whatever text you paste.