User-Agent Parser
Every browser introduces itself to every website with a user-agent string — a long, cryptic line that names the browser, its version, the operating system, and the device.
Paste any user-agent string to decode it into browser, version, operating system, rendering engine and device type. Your own browser's user agent is loaded by default.
Detected Browser
How It Works
A user-agent string is a single line of text a browser sends with every request. A typical Chrome string — Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36 — packs in the platform (Windows 10, 64-bit), the engine (AppleWebKit/Blink), and the browser and version (Chrome 120). This parser reads the string in the right order: it checks for Edge and Opera first, because both also contain the word "Chrome", then Chrome, then Firefox, then Safari — which is identified by "Version/" plus "Safari" and the absence of "Chrome".
The operating system comes from the platform token in brackets: "Windows NT 10.0" is Windows 10/11, "Macintosh" is macOS, "iPhone" or "iPad" is iOS/iPadOS, "Android" is Android, "Linux" is Linux, and "CrOS" is ChromeOS. Device type follows from the same tokens: iPhone and Android phones are mobile, iPad and Android tablets are tablets, and everything else is a desktop. The rendering engine is derived from the browser: Blink for Chrome, Edge and Opera; WebKit for Safari; Gecko for Firefox.
User-agent strings can be spoofed, and modern browsers are freezing parts of them for privacy (Chrome's User-Agent Reduction, for example, caps version detail), so treat the result as the browser's self-description — usually accurate, never guaranteed. Parsing runs entirely in your browser; nothing is uploaded.
Worked Example
Parsing Mozilla/5.0 (iPhone; CPU iPhone OS 17_2 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/17.2 Mobile/15E148 Safari/604.1 gives: browser Safari 17.2, operating system iOS 17.2, device Mobile, engine WebKit. The "Version/17.2" token carries the Safari version (the "Safari/604.1" token is the engine build, not the browser version), and "iPhone" marks it as a mobile device.
How to Use This Tool
Your own user agent is already loaded — click Parse User Agent to see it decoded, or paste any other UA string.
- Use your own UA or paste one. The box starts with your browser's real user-agent string. Replace it with any UA string from a log file, a bug report, or a device you are testing.
- Parse it. The headline shows the browser and version; the table shows the operating system and version, the device type, the rendering engine, and whether the device is a bot or crawler.
- Try a sample. The Try a Sample button loads an iPhone Safari user agent so you can see a mobile result without finding one yourself.
Reset reloads your own browser's user agent.
Tips and Practical Advice
User-agent parsing is a diagnostic tool, not a detection system — a few cautions keep it honest.
- Do not build features on UA sniffing. Browsers change their strings, users spoof them, and Chrome is actively reducing the detail they carry. Use feature detection (does the browser support this API?) for behaviour, and UA parsing only for analytics and debugging. To tell crawlers which parts of your site they may visit, use a robots.txt generator.
- Edge and Opera contain "Chrome". Both are Chromium-based, so their UA strings include Chrome tokens. A parser that checks for Chrome first will misidentify them — this one checks Edge and Opera first for exactly that reason.
- Safari's version is in "Version/", not "Safari/". The Safari/ token is the WebKit build number (604.1), which barely changes. The real Safari version comes from the Version/ token — 17.2 in the example above.
- Bots announce themselves. Most legitimate crawlers (Googlebot, Bingbot) say so in their UA string. This parser flags common bot tokens, which is useful when a strange UA shows up in your logs. The UA string names the browser, not the network — to work out the network a device sits on, use an IP subnet calculator.
Reading a User-Agent String, Token by Token
A user-agent string looks like gibberish until you read it token by token. Take the Chrome example from this page — Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36 — and it breaks into six pieces. Mozilla/5.0 is a compatibility fossil: every major browser starts with it, a leftover from the 1990s, when sites checked for Mozilla and turned other browsers away. The bracketed platform token, Windows NT 10.0; Win64; x64, names the operating system and architecture — Windows 10 or 11, 64-bit. AppleWebKit/537.36 names the rendering engine family, and (KHTML, like Gecko) is another fossil, claiming kinship with two older engines. Chrome/120.0.0.0 is the real browser and version. And the trailing Safari/537.36 is there for compatibility too: early sites served their best pages to Safari, so Chrome claimed to be Safari as well.
That history explains the two traps parsers have to avoid. First, the string names several browsers, and only one is real: the true browser is the last specific token — Chrome, Edge or Opera — while Mozilla and Safari are claims every Chromium browser makes. Second, the version is not always where you expect it: in a Safari string the real version lives in the Version/ token, while the Safari/ token is the WebKit build number, which barely changes between releases.
Some things a user-agent string cannot tell you at all. Windows 10 and Windows 11 both report Windows NT 10.0 — Microsoft kept the token unchanged for compatibility, so the two are indistinguishable from the string alone. And the detail in these strings is shrinking: Chrome's User-Agent Reduction freezes version numbers and platform detail, and the replacement is User-Agent Client Hints, an API (navigator.userAgentData) that lets a site request specific details — browser, version, platform, mobile or desktop — instead of reading them from a single string. Parsers will keep working, but the strings they parse will carry less and less.
Two practical uses remain. The first is debugging: when a user reports a bug, their UA string tells you the browser, version and device in one line, which is often enough to reproduce the problem. The second is log analysis: most legitimate crawlers — Googlebot, Bingbot and others — announce themselves in their UA string, so a strange entry in your logs is often a bot identifying itself rather than a browser you have never heard of. To tell crawlers which parts of your site they may visit, use a robots.txt generator. Just remember the caveat: anyone can send any string they like, so treat a parsed result as the browser's self-description — usually accurate, never proof.
Sources: No external data is used on this page — all processing runs in your browser on the text you enter. Last reviewed: 21 November 2026.
Frequently Asked Questions
What is a user-agent string?
A user-agent string is a line of text your browser sends to every website, naming the browser, its version, the operating system, and the device — for example, 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) ... Chrome/120.0.0.0 Safari/537.36'.
Why does my user agent say Mozilla when I use Chrome?
For historical compatibility. Every major browser starts its user-agent string with 'Mozilla/5.0' — a leftover from the 1990s browser wars, when sites checked for Mozilla and turned others away. The real browser is named later in the string.
Can a user-agent string be faked?
Yes — anyone can send any user-agent string they like, and browsers and extensions can change it. Treat parsed results as the browser's self-description: usually accurate, never proof of the real browser or device.
What is my user agent?
This page loads your browser's real user-agent string automatically — it is in the box above. Click Parse User Agent to see it decoded into browser, version, operating system, engine and device type.
Can I tell Windows 10 from Windows 11 in a user-agent string?
No. Both report 'Windows NT 10.0' — Microsoft kept the token unchanged for compatibility when Windows 11 launched, so the two versions are indistinguishable from the user-agent string alone.
What are User-Agent Client Hints?
A newer API (navigator.userAgentData) that lets a website request specific browser details — browser, version, platform, mobile or desktop — on demand. It is the replacement for user-agent strings as Chrome freezes the detail they carry under User-Agent Reduction.
Last updated: