User Agent Parser
Find out what a User-Agent string really says. Paste one, or start with your own, and see the browser, engine, operating system, device and any bot, which parts modern browsers freeze, and what your browser reveals through Client Hints.
How to Use
- The box starts with your own browser’s User-Agent. Paste any other one from a server log, a bug report or a request header.
- Or pick a preset: real strings for Chrome, Safari, Edge and Firefox, Android and iPhone, and for Googlebot, bingbot, GPTBot, curl and python-requests. The message under the buttons names each one’s source.
- Read the result: browser, operating system, device type and whether it is a bot. The diagram colours each part of the string by what it does.
- Show Work goes through every part and says which ones are frozen by User-Agent reduction and where the hidden details went.
- Press Show my Client Hints to see what your own browser reveals through navigator.userAgentData, such as its full version and whether Windows is 10 or 11.
- Click any result to copy it. Parse puts the string into the address bar so you can share a link to it.
Worked Example
Microsoft Edge on Windows (MDN’s example): Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/143.0.0.0 Safari/537.36 Edg/143.0.0.0. It splits into 7 parts: 5 products and 2 comments. Edg/143.0.0.0 makes it Edge 143; the parser looks for it before Chrome/, which Edge also sends. The engine is Blink. Windows NT 10.0; Win64; x64 means 64-bit Windows 10 or 11, and it is one of the fixed values Chrome-based browsers send after User-Agent reduction. 143.0.0.0 shows only the major version.
Googlebot Smartphone (Google’s documented string, 193 characters) says Android 6.0.1 on a Nexus 5X and contains Mobile Safari, yet it is a search-engine crawler: the Googlebot/2.1 token in its last comment decides. Because anyone can copy the string, a log entry is Google’s only if the IP address passes the reverse-and-forward DNS check Google describes.
The common mistake: reading Windows NT 10.0 as Windows 10. A Windows 11 PC sends exactly the same Windows NT 10.0, so a string alone can only say “Windows 10 or 11”. The answer is in the Sec-CH-UA-Platform-Version client hint: a value of 13.0.0 or more is Windows 11, 1.0.0 to 10.0.0 is Windows 10 (Microsoft Learn). Likewise Safari/537.36 in a Chrome string does not mean Safari, and Android 10; K does not mean Android 10.
Show Work
How User-Agent Strings Are Built
product = token [ "/" product-version ]
From User-Agent to Client Hints
HTTP/1.0 (RFC 1945, May 1996) defined the User-Agent header for statistics, tracing protocol violations and tailoring responses to a client’s limits; its example was CERN-LineMode/2.15 libwww/2.17b3. Browsers soon began copying each other’s tokens so that sites would not turn them away, which is why the strings grew so long. Today’s definition, RFC 9110 (June 2022), asks senders not to include needlessly fine-grained detail, because long strings help fingerprint users, and discourages borrowing other products’ tokens to claim compatibility.
Chrome acted on that with User-Agent reduction. Chrome 101 began sending 0.0.0 after the major version (rolled out to all users by June 2022), Chrome 107 fixed the desktop platform values (fully rolled out in February 2023), and Chrome 110 did the same on Android (May 2023). Firefox had already capped the macOS version it reports at 10.15 from Firefox 87. The details that left the string are offered through User-Agent Client Hints, a Web Incubator Community Group draft: three low-entropy headers on every HTTPS request, the rest only when a site asks with Accept-CH.
About This Parser
This parser splits a User-Agent string into its products and comments the way RFC 9110 defines them, then names the browser (checking Edge, Opera, Samsung Internet and others before Chrome, and Chrome before Safari), the engine (every iPhone and iPad browser is WebKit), the operating system, the device type, the architecture the string admits to, any in-app browser, and about 50 bot, crawler, script and headless-browser signatures. It flags the parts that User-Agent reduction or Firefox has frozen, and shows your own browser’s Client Hints when you ask. Pattern matching is only as good as the string: a client can send anything, so treat the result as a claim, not proof.
It is for developers reading bug reports and logs, IT staff checking what reached a server, and anyone curious what their browser tells every website. Everything runs in your browser; nothing you paste is sent anywhere.
Sources: RFC 9110 §10.1.5 and RFC 1945; Chromium, User-Agent Reduction; WICG User-Agent Client Hints; MDN’s User-Agent, Firefox user agent string and User-Agent Client Hints API pages; Microsoft Learn, Detect Windows 11 using User-Agent Client Hints; Google, common crawlers and verifying Google’s requests; the Bing Webmaster Blog; OpenAI’s crawler page; the curl manual; and the requests source.
Related tools: HTTP(S) Check, IP Lookup, and PCAP File Analyzer.
Frequently Asked Questions
Why does every browser say Mozilla/5.0, and Chrome say Safari?
For compatibility. Sites once sent their best pages only to strings they recognised, so new browsers copied older browsers’ tokens: almost every browser still starts with Mozilla/5.0 (MDN), and Chrome ends with Safari/537.36. RFC 9110 now discourages using another product’s tokens to claim compatibility, but the old tokens stay so that nothing breaks. Edge adds Edg/, Opera OPR/, so a parser must look for those before Chrome/.
What is User-Agent reduction?
Chrome cut the detail in its string to make users harder to fingerprint. From Chrome 101 (2022) the version reads like 143.0.0.0, with only the major number real; from Chrome 107 on desktop and 110 on Android the platform became a fixed value, such as Windows NT 10.0; Win64; x64 or Linux; Android 10; K. So an Android 16 Pixel 9 now reports Android 10 and model K (MDN). The hidden details moved to Client Hints.
How can I tell Windows 11 from Windows 10?
Not from the User-Agent: Windows 11 still says Windows NT 10.0. Microsoft documents the Sec-CH-UA-Platform-Version client hint instead: 13.0.0 and above is Windows 11, 1.0.0 to 10.0.0 is Windows 10. Press Show my Client Hints in a Chromium browser (Chrome, Edge, Opera) to see your value; Firefox and Safari do not provide it.
What are User-Agent Client Hints?
HTTP headers defined by the WICG User-Agent Client Hints draft. Three low-entropy ones, Sec-CH-UA (brands and major versions), Sec-CH-UA-Mobile and Sec-CH-UA-Platform, go with every HTTPS request. The rest (full version list, platform version, model, architecture, bitness, WoW64, form factors) are sent only after the server asks with an Accept-CH header; JavaScript reads them with navigator.userAgentData.getHighEntropyValues(). They are sent over HTTPS only, and MDN lists no support in Firefox or Safari.
Is a request that says Googlebot really from Google?
Not necessarily: anyone can send that text, including the 193-character Googlebot Smartphone string in the presets. Google says to run a reverse DNS lookup on the IP address, check that the name ends in googlebot.com, google.com or googleusercontent.com, then run a forward lookup on that name and check that it returns the same IP. The W.X.Y.Z in Google’s documented string stands for the Chrome version the crawler currently uses.
How do I use the User Agent Parser?
Simply type your numbers and read the result, which refreshes the instant you change something. There is nothing to submit and nothing to wait for.
Is it free? Does it work without internet?
Yes to both. It is free with no sign-up, and once the page has loaded it keeps working even with no internet.
Where does my data go?
Nowhere — every calculation runs on your own device. Nothing you enter is uploaded, logged, or stored.
Common Use Cases
Bug report triage
A report with Chrome/143.0.0.0 and Windows NT 10.0; Win64; x64 tells you Chrome 143 on 64-bit Windows 10 or 11, but not the exact build: ask the user for it, or read Sec-CH-UA-Full-Version-List.
Log analysis
Separate people from bots: bingbot/2.0 and Googlebot/2.1 are search crawlers, GPTBot/1.4 is an AI crawler, curl/8.23.0 and python-requests/2.34.2 are scripts, and HeadlessChrome means automation.
Privacy check
Chrome’s 111-character Windows string carries only a few real facts: the browser, its major version, 64-bit Windows and the engine. Everything else is fixed text, the same on every Windows PC running Chrome.
Mobile testing
Every Chrome on Android now says Android 10 and model K, so a model-specific bug cannot be matched from the User-Agent. The model is in Sec-CH-UA-Model, sent only when the server asks for it.
Feature gating
Microsoft and MDN both recommend feature detection over browser detection. If you must branch, test Edg/ and OPR/ before Chrome/, and Chrome/ before Safari/.
Last updated: