User Agent Parser
Paste a User-Agent string and the parser reads off the browser and version, the rendering engine, the operating system and the device type (desktop, mobile, tablet or bot), plus the notable tokens in it. The example, a Chrome-on-Windows string, parses as Chrome 131.0.0.0 on the Blink engine, running Windows 10 or 11, on a desktop device. That is a best guess, not a fact: a UA string is whatever the client chooses to send, and Chromium now freezes its OS version (Windows NT 10.0, macOS 10_15_7, Android 10 with the model “K”) and zeroes the rest of the Chrome version. Everything is parsed on your device and nothing is sent anywhere.
Updated Runs in your browser: nothing you enter is uploadedHow this tool works
Parsed on this device. Your own User-Agent is read only when you press the button. Nothing is uploaded or saved; the site only records that the tool was used.
Best guess: Chrome 131.0.0.0 on Windows 10 or 11, desktop.
Parsed result
- Browser
- Chrome 131.0.0.0
- Rendering engine
- Blink 131.0.0.0
- Operating system
- Windows 10 or 11
- Device type
- Desktop
This string shows Chromium’s reduced values (a frozen OS version, an Android model of “K” or a Chrome version of major.0.0.0), so the real OS version, device model and full browser version are not in it.
Notable tokens
Mozilla/5.0A legacy compatibility token that nearly every browser sends; it says nothing about the browser.KHTML, like GeckoAnother legacy claim, kept so sites that sniff for Gecko or KHTML still serve a modern page.AppleWebKit/537.36Frozen at 537.36 in every Chromium browser; it is not the Chrome version.Safari/537.36Chromium browsers still say "Safari" and keep this number fixed, so "Safari" in a UA does not mean Safari.Win64; x6464-bit Windows on an x64 processor (an ARM PC can also send this).Windows NT 10.0Windows 10 and Windows 11 both send NT 10.0, so it cannot tell them apart.Chrome/131.0.0.0Chromium reduces the version to major.0.0.0; the full version is only available through User-Agent Client Hints.
Example User-Agent strings and how they parse
| Example | User-Agent string | Browser | Engine | OS | Device |
|---|---|---|---|---|---|
| Chrome on Windows | Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36 | Chrome 131.0.0.0 | Blink 131.0.0.0 | Windows 10 or 11 | Desktop |
| Edge on Windows | Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36 Edg/131.0.0.0 | Edge 131.0.0.0 | Blink 131.0.0.0 | Windows 10 or 11 | Desktop |
| Firefox on Windows | Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:133.0) Gecko/20100101 Firefox/133.0 | Firefox 133.0 | Gecko 133.0 | Windows 10 or 11 | Desktop |
| Safari on macOS | Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/17.6 Safari/605.1.15 | Safari 17.6 | WebKit 605.1.15 | macOS 10.15.7 | Desktop |
| Chrome on macOS | Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36 | Chrome 131.0.0.0 | Blink 131.0.0.0 | macOS 10.15.7 | Desktop |
| Firefox on Linux | Mozilla/5.0 (X11; Linux x86_64; rv:133.0) Gecko/20100101 Firefox/133.0 | Firefox 133.0 | Gecko 133.0 | Linux | Desktop |
| Chrome on ChromeOS | Mozilla/5.0 (X11; CrOS x86_64 14541.0.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36 | Chrome 131.0.0.0 | Blink 131.0.0.0 | ChromeOS 14541.0.0 | Desktop |
| Safari on iPhone | Mozilla/5.0 (iPhone; CPU iPhone OS 17_6 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/17.6 Mobile/15E148 Safari/604.1 | Safari 17.6 | WebKit 605.1.15 | iOS 17.6 | Mobile |
| Safari on iPad (iPadOS 12) | Mozilla/5.0 (iPad; CPU OS 12_5_7 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/12.1.2 Mobile/15E148 Safari/604.1 | Safari 12.1.2 | WebKit 605.1.15 | iOS 12.5.7 | Tablet |
| Chrome on Android phone | Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Mobile Safari/537.36 | Chrome 131.0.0.0 | Blink 131.0.0.0 | Android 10 | Mobile |
| Chrome on Android tablet | Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36 | Chrome 131.0.0.0 | Blink 131.0.0.0 | Android 10 | Tablet |
| Samsung Internet on Android | Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) SamsungBrowser/26.0 Chrome/122.0.0.0 Mobile Safari/537.36 | Samsung Internet 26.0 | Blink 122.0.0.0 | Android 10 | Mobile |
| Opera on Windows | Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36 OPR/115.0.0.0 | Opera 115.0.0.0 | Blink 131.0.0.0 | Windows 10 or 11 | Desktop |
| Googlebot | Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html) | Googlebot 2.1 | Unknown | Unknown | Bot |
| Bingbot | Mozilla/5.0 (compatible; bingbot/2.0; +http://www.bing.com/bingbot.htm) | Bingbot 2.0 | Unknown | Unknown | Bot |
Values Chromium freezes (UA reduction)
| Part | Frozen token | Parsed as | What it hides |
|---|---|---|---|
| Windows | Windows NT 10.0 | Windows 10 or 11 | Windows 10 and Windows 11 look the same; the CPU part is fixed at "Win64; x64". |
| macOS | Intel Mac OS X 10_15_7 | macOS 10.15.7 | Chrome, Firefox and Safari report 10.15.7 whatever the macOS release, and Apple Silicon Macs still say "Intel". |
| Android | Android 10; K | Android 10 | The real Android version is hidden and the model is the placeholder "K". |
| Chrome version | Chrome/131.0.0.0 | Chrome 131.0.0.0 | Only the major version (131) is real; the minor, build and patch parts are zeros. |
How to parse a User-Agent string
- Paste the string. Replace the example with a User-Agent from a server log, a bug report or an HTTP header. Or press “Use my browser’s User-Agent” to fill in the one your own browser sends.
- Read the result. The browser and version, rendering engine, OS and version and device type appear as you type.
- Check the notable tokens. Each legacy or frozen token in the string is listed with what it means, such as “Safari/537.36” in a Chrome string.
- Treat it as a guess. If a note says the string is reduced, the real OS version and device model are not in it. Use User-Agent Client Hints or feature detection when you need them.
Frequently asked questions
- What is a User-Agent string?
- It is a line of text a browser or other HTTP client sends in the User-Agent request header, and that scripts can read as navigator.userAgent. It was meant to say which browser, version and operating system is asking, but it grew into a pile of legacy tokens: nearly every browser starts with “Mozilla/5.0”.
- Why does my Chrome say Safari, Mozilla and Gecko?
- For history. Sites once served better pages to Mozilla, then to Gecko, then to Safari, so each new browser added the older names to be treated well. A Chromium UA therefore contains “Mozilla/5.0”, “AppleWebKit/537.36”, “KHTML, like Gecko” and “Safari/537.36”. Only the Chrome/ (or Edg/, OPR/ and similar) token says what it is.
- What is User-Agent reduction?
- Chromium is cutting the detail in the UA string to reduce passive fingerprinting. Since Chrome 107 on desktop the OS version and CPU are fixed (Windows reports NT 10.0, macOS 10_15_7), and since Chrome 110 on Android the version is fixed at 10 and the model at “K”. The Chrome version keeps its major number, and the rest is 0.0.0. The structure of the string stays the same.
- Why does Windows 11 show as Windows NT 10.0?
- Windows 11 still reports NT 10.0 in the User-Agent, and Chromium froze that value, so a UA cannot tell Windows 10 from 11. The parser says “Windows 10 or 11”. User-Agent Client Hints (Sec-CH-UA-Platform-Version) can tell them apart in Chromium browsers, if the site asks.
- How reliable is the result?
- It is a best guess. The string can be changed by the user, an extension, a privacy setting or a proxy, many browsers imitate each other, and Chromium hides real versions. Brave, for example, does not say Brave. MDN advises against relying on UA sniffing for behaviour; use feature detection where you can.
- How does it tell phone, tablet and desktop apart?
- By tokens. “iPhone” or “Mobile” means mobile, “iPad” means tablet, and an Android string without “Mobile” is treated as a tablet, which is Google’s own convention. Everything else with a known OS is desktop. A modern iPad sends a Mac UA like desktop Safari, so it shows as a Mac desktop here.
- Which bots does it recognise?
- Googlebot (including the smartphone crawler, which has a Chrome-like string with the Googlebot token at the end), Bingbot and other common crawlers such as DuckDuckBot, Baiduspider, YandexBot and Applebot, plus any string that contains “crawler”, “spider” or a name ending in “bot”. They show as device type “Bot”. A bot can claim to be anything, so a Googlebot UA does not prove the visitor is Google; check the IP address with a reverse DNS lookup.
- Is my User-Agent sent anywhere?
- No. The string is parsed by JavaScript on this page and is never uploaded, stored or sent to analytics. Your own browser’s string is read only when you press the button. The site records only that the tool was used.
- Is there a length limit?
- Yes: the parser reads the first 1,000 characters. Real User-Agent strings are well under 400. The limit, and rules that never backtrack, keep a huge paste from slowing the page.
How it works
The text is trimmed and cut to 1,000 characters. Each rule then looks for a token with a plain substring search and reads the version that follows with a character scan, so the work is linear in the input and never backtracks. Crawlers are checked first, then the browser, most specific token first: Edg/, EdgA/ and EdgiOS/ before Opera (OPR/), Samsung Internet, Vivaldi, Firefox (including FxiOS/), Chrome (including CriOS/), Internet Explorer and finally Safari, which needs its Version/ token because Chromium strings also contain “Safari/”. The engine follows from the browser: Blink for Chromium browsers, Gecko for Firefox, WebKit for Safari and for every browser on iOS, EdgeHTML, Trident and Presto for the old ones. The OS comes from Windows NT, Android, iPhone or iPad, CrOS, Mac OS X and Linux or X11 tokens, in that order, with Windows NT numbers mapped to release names and underscores in versions turned into dots. The device is a bot, a tablet (iPad, “tablet”, Kindle or Android without “Mobile”), a mobile (iPhone, Android with “Mobile”) or a desktop. Chromium’s UA reduction freezes the Windows NT, macOS and Android values and zeroes the Chrome minor version, so the parse reports those frozen values as sent and notes them. The page itself is static: the example is a fixed string and nothing depends on the build time or your browser. The result is a best guess from a string the client controls.
Sources
More free tools
- URL ParserSplit a URL into protocol, host (punycode and Unicode), port, path and an editable query table. Strip tracking parameters and resolve relative links.
- HTTP Status Code LookupLook up any HTTP status code or phrase: its meaning, class, defining RFC section, default cacheability, and common causes and fixes. Filterable IANA table.
- Robots.txt Generator and TesterBuild a robots.txt with per-crawler rules, wildcards and sitemaps, then test any URL path against it as RFC 9309 says a crawler must. Runs in your browser.
- JWT DecoderDecode a JWT to its header and payload, read exp, iat and nbf as UTC times, spot expired or alg none tokens, and check HMAC signatures. Runs locally.
- JavaScript Key Code FinderPress any key to see event.key, event.code, the legacy keyCode and which, location and modifiers, plus a copy-ready JavaScript snippet. Common keys table.
- Network Ports ReferenceSearch common TCP and UDP port numbers by number, range or service name: 22 SSH, 443 HTTPS, 3306 MySQL and more, with secure variants and IANA status.
More: Web, URLs, images and networkAll developer toolsAll toolsHome & DIY calculators