⚡ BreezyTools Pro — Ad-free experience across all 200+ tools. Less than a coffee a month → Learn More

User Agent Parser

Decode any User-Agent string into browser, OS, engine, and device.

Browser: —
Version: —
Engine: —
OS: —
Device: —

How to use the user agent parser

Paste a User-Agent string, for example from a server log, an analytics export, or a bug report. Or click Use My User Agent to load the one your current browser sends. The results update as you type and show the browser name and version, rendering engine, operating system, and device type. Parsing happens entirely in your browser.

Anatomy of a user agent string

Here is a typical string from Microsoft Edge on Windows:

Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36 Edg/120.0.0.0
  • Mozilla/5.0: a legacy token that almost every browser sends for compatibility. It tells you nothing about the actual browser.
  • (Windows NT 10.0; Win64; x64): the platform, meaning the operating system and CPU architecture.
  • AppleWebKit/537.36 (KHTML, like Gecko): engine tokens. Blink-based browsers kept the WebKit token after Blink split from WebKit in 2013.
  • Chrome/120.0.0.0 Safari/537.36: compatibility tokens, so sites that check for Chrome or Safari still work.
  • Edg/120.0.0.0: the token that actually identifies Edge.

The parser reports this string as Edge 120.0.0.0, Blink engine, Windows 10/11, Desktop.

Why detection order matters

Because browsers copy each other's tokens, a parser has to check the most specific token first. Edge's string contains "Chrome" and "Safari", and Chrome's contains "Safari". This tool checks for Edge (Edg/, EdgA/, EdgiOS/), then Opera (OPR/), Samsung Internet, Firefox (Firefox/ or FxiOS/ on iPhone and iPad), Chrome (Chrome/ or CriOS/), and finally Safari, which it identifies by the Version/ token. A Gecko/ token means the Gecko engine (Firefox). On iPhone and iPad every browser is reported as WebKit, because Apple requires all iOS browsers to use it. Elsewhere, a WebKit token together with "Chrome" means Blink, and WebKit alone means Safari's WebKit. iOS is checked before macOS, because iPhone strings also contain "like Mac OS X". Browsers outside these families show up as the family whose tokens they copy, or as Unknown.

What user agent strings can't tell you

  • Exact versions on Chromium browsers. Under User-Agent Reduction, Chrome and the Chromium browsers that follow it send frozen values: minor versions are always 0.0.0, and Android strings show a generic Android 10; K instead of the real version and device model.
  • Windows 10 vs. 11, and the real macOS version. Both Windows versions send Windows NT 10.0. Major Mac browsers report macOS as 10.15 no matter which version is installed.
  • iPads. Since iPadOS 13, Safari on iPad requests desktop websites by default and sends a Mac-style string, so many iPads look like Mac desktops.
  • Bots. Any client can send any string. Strings containing bot, crawler, or spider (such as Googlebot and bingbot) are shown with the device type Bot, but crawlers can also copy a normal browser's string, and impostors can claim to be Googlebot. Confirm real crawlers with a reverse DNS lookup.

User-Agent Client Hints

Chromium-based browsers also send Sec-CH-UA, Sec-CH-UA-Mobile, and Sec-CH-UA-Platform request headers with low-detail brand, mobile, and platform information. A server can request more, such as the full version, platform version, or device model, with the Accept-CH response header. Scripts can call navigator.userAgentData.getHighEntropyValues(). Don't assume every browser sends client hints. This tool parses classic User-Agent strings only.

When to parse user agents

Parsing user agents is useful for reading server logs, triaging bug reports, segmenting analytics, and writing bot or firewall rules. For front-end code, use feature detection instead, such as checking 'share' in navigator or using CSS @supports. Feature detection keeps working when browsers change their strings.

Frequently Asked Questions

What is a user agent string?

It's a line of text your browser sends in the User-Agent header of every request, and scripts can read it as navigator.userAgent. It names the browser, rendering engine, and platform so servers can adapt their responses or log who visited.

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

For historical compatibility. Early websites served advanced features only to browsers that claimed to be Mozilla, and later ones checked for WebKit or Safari. Each new browser copied the tokens it needed to avoid being blocked, and the habit stuck.

Can I tell Windows 10 from Windows 11 with a user agent?

No. Both send Windows NT 10.0, which is why this tool shows "Windows 10/11". In Chromium browsers, the Sec-CH-UA-Platform-Version client hint can tell them apart: a major version of 13 or higher means Windows 11.

How accurate is the device type?

It's a heuristic. Strings containing iPad or Tablet count as tablets, and so do Android strings without the Mobile token, which is how Android tablets identify themselves. Strings with Mobile, iPhone, or iPod count as mobile, crawler strings count as Bot, and everything else counts as desktop. iPads in desktop mode send a Mac string, so they show as desktop.

Can a user agent be faked?

Yes. Browser developer tools, extensions, scripts, and bots can send any string. Treat parsed results as a hint, and never rely on the user agent for security decisions.

Is my user agent sent anywhere by this tool?

No. The Use My User Agent button reads it locally, and parsing happens in your browser. Every website you visit already receives this string in the request header anyway.

Love using BreezyTools?

Go Pro for an ad-free experience, priority features, and support independent development — for less than a coffee a month.

Upgrade to Pro →