Why does my Windows 11 PC show Windows 10?

Browsers froze the Windows version in the user agent at "Windows NT 10.0". Chrome and Edge reveal Windows 11 only through client hints: a platformVersion of 13.0.0 or higher means Windows 11, and the tool shows it under Client hints.

Can a user agent be faked?

Yes. Any client can send any User-Agent, and browser developer tools can change it in two clicks. Treat it as a hint, and verify important crawlers with a reverse DNS lookup of their IP address.

How do I recognise Googlebot's user agent?

Googlebot's strings contain "Googlebot/2.1" together with a current Chrome version, in a desktop and a smartphone form. Other Google crawlers use tokens such as Googlebot-Image, AdsBot-Google, Storebot-Google and Google-InspectionTool.

What are User-Agent Client Hints?

A newer mechanism in Chromium browsers that sends brand, platform and mobile flags by default and lets sites request more detail — platform version, architecture, model and full version — through Sec-CH-UA headers or navigator.userAgentData.

Why is the device type empty for my laptop?

Desktop browsers do not include a device token, so the parser leaves type, vendor and model blank; the tool labels such strings as desktop. Phones, tablets, TVs and consoles name themselves.

Can I parse many user agents at once?

Yes. Switch to Bulk, paste up to 5,000 strings, one per line, and download the result as CSV or JSON.

Is the user agent I paste uploaded?

No. The parser library runs in your browser and no string is sent to a server.

User Agent Parser: What Is My User Agent?

Read any User-Agent string, starting with your own

This user agent parser breaks a User-Agent header into the browser and its version, the rendering engine, the operating system, the device type, vendor and model, and the CPU architecture. It opens on your own browser's string, shows the more precise User-Agent Client Hints where your browser offers them, flags search engines, AI crawlers, link previewers and HTTP libraries, and parses thousands of strings from a log at once with CSV or JSON export. Parsing runs locally in your browser; nothing you paste is sent anywhere.

How to parse a user agent

1Look at the result for your own browser, which is loaded on arrival, or paste any User-Agent string into the box.
2Pick an entry from Samples to compare common browsers and crawlers such as iPhone Safari, Android Chrome, Googlebot and GPTBot.
3Read the browser, engine, operating system, device and CPU cards. A highlighted banner appears when the string belongs to a bot or an HTTP client.
4Switch to Bulk, paste one user agent per line — from an access log, for example — and download the parsed table as CSV or JSON.

What a User-Agent string contains

Every HTTP request carries a User-Agent header that names the software making it. A typical browser string such as Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/130.0.0.0 Safari/537.36 is mostly history: "Mozilla/5.0" is sent by every modern browser, Chrome claims to be Safari and "like Gecko" for compatibility, and only a few tokens actually identify it.

A parser therefore works from a large table of patterns that know which token matters for which product — Edg/ means Edge even though the string also says Chrome and Safari, Version/ holds Safari's real version, and SamsungBrowser/ beats the Chrome token next to it. This tool uses the widely used open-source ua-parser-js library for that table.

The fields explained

Browser: The client application and its full and major version, for example Chrome 130 or Mobile Safari 18.1. In-app browsers such as Facebook's or Instagram's are recognised too.
Engine: The rendering engine that lays out the page: Blink (Chrome, Edge, Opera, Samsung Internet), WebKit (Safari and every iOS browser) or Gecko (Firefox).
Operating system: Windows, macOS, iOS, Android, Linux, ChromeOS and others, with a version where the string gives one.
Device: The type — mobile, tablet, smart TV, console, wearable, XR or embedded — plus vendor and model where present. A string with no device token is a desktop or laptop.
CPU: The processor architecture, such as amd64, arm64 or ia32, when the string reveals it.

Why your user agent may look wrong

Browsers have deliberately frozen parts of the string to reduce fingerprinting. Chrome and Edge report Windows 10 as Windows NT 10.0 even on Windows 11, report macOS as 10_15_7 whatever the real version, and send a minor version of 0.0.0. Safari on an iPad asks for the desktop site and reports itself as a Mac. Firefox caps the reported macOS version as well.

The precise values now come from User-Agent Client Hints. In Chromium browsers a page can ask navigator.userAgentData.getHighEntropyValues() for the platform version (13.0.0 or higher means Windows 11), the CPU architecture and bitness, the device model and the full version list. The tool shows them under your own result when your browser provides them; Safari and Firefox do not implement client hints.

Detecting bots and crawlers

Beyond browsers, the parser recognises well over a hundred non-human clients: search engines (Googlebot and its image, news and ads variants, Bingbot, DuckDuckBot, YandexBot, Baiduspider, Applebot), AI crawlers and assistants (GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, PerplexityBot, CCBot, Bytespider, Google-Extended, meta-externalagent), link previewers (facebookexternalhit, Twitterbot, Slackbot, Discordbot), SEO tools (AhrefsBot, SemrushBot), uptime monitors and HTTP libraries such as curl, python-requests and Go's http client.

A User-Agent can be set to anything, so a match is a claim, not proof. To confirm that a request really came from Googlebot or Bingbot, do a reverse DNS lookup on the IP and a forward lookup on the result, or compare it with the IP ranges the operator publishes. To decide what crawlers may fetch, write rules in a robots.txt.

Parsing user agents from logs

Bulk mode accepts up to 5,000 distinct strings, one per line; duplicates and blank lines are dropped. Export the table as CSV for a spreadsheet or JSON for a script. For server-side work, the same parsing is available as ua-parser-js on npm, and equivalents exist for Python (ua-parser), Go and PHP.

Prefer feature detection over user-agent sniffing when deciding what a browser can do: test for the API you need. User agents are best used for analytics, debugging a report from a specific device, and recognising crawlers.

Frequently asked questions

What is my user agent?: It is shown in the box at the top of the tool when the page loads, with the browser, OS and device it describes underneath. Your browser sends the same string in the User-Agent header of every request.
Why does my Windows 11 PC show Windows 10?: Browsers froze the Windows version in the user agent at "Windows NT 10.0". Chrome and Edge reveal Windows 11 only through client hints: a platformVersion of 13.0.0 or higher means Windows 11, and the tool shows it under Client hints.
Can a user agent be faked?: Yes. Any client can send any User-Agent, and browser developer tools can change it in two clicks. Treat it as a hint, and verify important crawlers with a reverse DNS lookup of their IP address.
How do I recognise Googlebot's user agent?: Googlebot's strings contain "Googlebot/2.1" together with a current Chrome version, in a desktop and a smartphone form. Other Google crawlers use tokens such as Googlebot-Image, AdsBot-Google, Storebot-Google and Google-InspectionTool.
What are User-Agent Client Hints?: A newer mechanism in Chromium browsers that sends brand, platform and mobile flags by default and lets sites request more detail — platform version, architecture, model and full version — through Sec-CH-UA headers or navigator.userAgentData.
Why is the device type empty for my laptop?: Desktop browsers do not include a device token, so the parser leaves type, vendor and model blank; the tool labels such strings as desktop. Phones, tablets, TVs and consoles name themselves.
Can I parse many user agents at once?: Yes. Switch to Bulk, paste up to 5,000 strings, one per line, and download the result as CSV or JSON.
Is the user agent I paste uploaded?: No. The parser library runs in your browser and no string is sent to a server.