User-Agent String Parser

Parse any User-Agent string into browser, engine, operating system, device type, vendor/model and CPU, and detect search and AI crawlers. Runs locally.

Pre-filled with the User-Agent of your current browser. Paste any other string to analyze it.

Parsed locally with ua-parser-js. User-Agent strings can be spoofed and modern browsers reduce the details they send (User-Agent Client Hints), so treat the result as a hint, not proof.

What is User Agent Parser?

This tool decodes a User-Agent string into readable parts: browser and version, rendering engine, operating system and version, device type, vendor and model, CPU architecture, and whether it is a bot or AI crawler. The field starts with your own browser's User-Agent.

How to use User Agent Parser

  1. Use the pre-filled value, or paste any User-Agent from logs or analytics.
  2. Read the parsed fields in the table.
  3. Click "Use my browser's User-Agent" to reset to your own.
  4. Copy the result as JSON if you need it elsewhere.

Example

Input
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36
Output
Browser Chrome 124.0.0.0 · engine Blink 124.0.0.0 · OS Windows 10 · CPU amd64 · bot: no

When to use User Agent Parser

Use it to make sense of User-Agent strings in server logs, bug reports or analytics. Do not rely on it for security decisions: User-Agents are trivially spoofed, and Chromium browsers now freeze parts of the string (User-Agent reduction), so OS versions such as Windows 11 appear as Windows 10.

How User Agent Parser works

Parsing uses the open-source ua-parser-js library (v2) with its crawler, bot, fetcher, library and CLI extensions, loaded in your browser. It matches the string against regular expressions for thousands of browsers, devices and bots. Desktop browsers usually report no device type, which is shown as "desktop or not specified".

Common Use Cases

  • Identify which browser and OS a bug reporter used.
  • Recognise Googlebot, Bingbot or GPTBot in access logs.
  • Check whether traffic comes from mobile phones or tablets.
  • Inspect the User-Agent sent by a tool such as curl or an HTTP library.

FAQs

Why does Windows 11 show as Windows 10?

Browsers keep "Windows NT 10.0" in the User-Agent for compatibility. The real version is only available through User-Agent Client Hints.

Can it tell if a request is really from Googlebot?

It can tell that the string claims to be Googlebot. To verify, do a reverse DNS lookup of the IP and check that it resolves back to googlebot.com or google.com.

Is my User-Agent sent anywhere?

No. Parsing runs entirely in your browser.

Good next steps

Cron Expression Parser
Paste a cron expression to validate it, read it in plain language and list the next 10 run times in any time zone. Supports seconds fields and @daily macros.

Explore more categories

CRC
Cyclic Redundancy Check algorithms for error detection
MD
Message Digest algorithms (MD2, MD4, MD5)
SHA-1
Secure Hash Algorithm 1 - 160-bit hash function
SHA-2
Secure Hash Algorithm 2 family (SHA-224, SHA-256, SHA-384, SHA-512)