User Agent Parser

Processed 100% locally in your browser111 characters · 6 segments
Quick-Test User Agent Presets
Detection SummaryBrowser

This User-Agent belongs to Google Chrome 131.0.0.0 running on Windows 10 / 11 (Desktop), powered by the Blink 131.0.0.0 rendering engine.

Browser / Client

Google Chrome

v131.0.0.0 · Google LLC

Rendering Engine

Blink

Build 131.0.0.0

Operating System

Windows 10 / 11

x86_64 (64-bit)

Device Profile

Desktop

PC · Windows Desktop / Laptop

Privacy & User-Agent Reduction Notice
  • Windows 10 and Windows 11 both report 'Windows NT 10.0' in the standard User-Agent header. Use Sec-CH-UA-Platform-Version Client Hints to distinguish Windows 11.
  • Browser version uses Chromium User-Agent Reduction (Chrome/131.0.0.0), masking minor, branch, and patch build numbers as 0.0.0.

Interactive User-Agent Token Breakdown

Click any segment token below to inspect why browsers include it in the raw string.

6 tokens
Token #1:Mozilla/5.0(Legacy Mozilla Prefix)

Historical Netscape compatibility token sent by nearly all browsers since the late 1990s so legacy servers do not block them.

Browser & Client Specifications

Browser Name
Google Chrome
Full Version
131.0.0.0
Major Release
131
Client Type
Browser
Developer
Google LLC
Layout Engine
Blink (131.0.0.0)

Platform & Hardware Profile

Operating System
Windows
OS Version
10 / 11
Platform Token
Windows NT 10.0
CPU Architecture
x86_64 (64-bit)
Device Category
Desktop
Brand / Model
PC · Windows Desktop / Laptop

Behavior & Client Matrix

Mobile DeviceNo
Tablet Form FactorNo
Desktop EnvironmentYes
Bot / Search CrawlerNo
Embedded In-App WebViewNo
UA-Reduced / Frozen OSYes
64-Bit ArchitectureYes

How to Parse User Agent Strings & Decode Browser Tokens

Raw user agent strings are messy on purpose. Every time a browser or crawler requests a page, it sends an HTTP User-Agent header (defined in IETF RFC 9110). Over the last twenty years, browser makers kept tacking on old competitor names so websites would not block them. That is why a single Chrome request claims to be Mozilla, AppleWebKit, KHTML, Gecko, and Safari all in the same line. This user agent parser strips away those compatibility decoys and pulls out the real browser build, rendering engine, OS, and hardware type.

Matching order matters when you parse user agent logs from Nginx, Apache, or Cloudflare. Microsoft Edge (Edg/), Opera (OPR/), and Samsung Internet (SamsungBrowser/) are all built on Chromium, so they still carry the Chrome/ and Safari/ tokens inside their strings. Googlebot Smartphone does the same thing and disguises itself as mobile Chrome on Android so sites hand over their mobile layout. Our user agent analyzer checks for bots, CLI tools like cURL, and in-app WebViews (Instagram, Facebook, WeChat) first before matching standard browsers.

You will also notice capped version numbers in newer browsers. Under W3C User-Agent Client Hints (Sec-CH-UA) and Chromium User-Agent Reduction, browsers lock macOS at 10_15_7, report both Windows 10 and Windows 11 as Windows NT 10.0, and hide Android phone models behind Android 10; K. Whenever you run a user agent lookup here, the tool flags those frozen tokens so you do not waste time chasing a wrong OS version in a bug report. To check live viewport dimensions or cookie settings on your own machine, open What Is My Browser or inspect raw server responses with the HTTP Headers Checker.

Anatomy of an HTTP User-Agent String

How each token in a raw user agent string maps to browser, engine, OS, and crawler details.

UA String TokenPartWhy It Is In the String
Mozilla/5.0Legacy PrefixLeftover token from the 1990s Netscape era. Almost every browser still sends it so old server scripts do not block the request.
(Windows NT 10.0; Win64; x64)System CommentShows the operating system kernel, 64-bit subsystem, and CPU architecture.
AppleWebKit/537.36 (KHTML, like Gecko)Rendering EnginePoints to WebKit or Blink layout support. Chromium browsers hardcode 537.36 here.
Chrome/131.0.0.0 Safari/537.36Browser BuildGives the actual browser name and major release, followed by a dummy Safari token for site compatibility.
Mobile / SM-S928B / iPhoneDevice TokenFlags mobile touch screens and shows the phone model on unreduced Android or iOS strings.
(compatible; Googlebot/2.1; +http://...)Bot SignatureIdentifies search crawlers, AI scrapers (GPTBot, ClaudeBot), and chat link expanders.
Straightforward answers on how to parse user agent strings, spot crawlers, and read frozen OS versions.

Frequently Asked Questions About User Agent Parsing

Paste any raw HTTP User-Agent line into the box at the top of the page, or click Use My User Agent to load your current browser. This user agent parser online breaks the string down into browser version, rendering engine, OS, device type, and bot flags right away.
Back in the late 1990s, websites checked for the word Mozilla before sending modern stylesheets and frames. Browsers like Chrome, Safari, Edge, and Firefox started putting Mozilla/5.0 at the start of their strings so they would not get stuck with broken plain-text pages, and the habit stuck.
When you open this page, it reads window.navigator.userAgent from your browser automatically. If you also want to test your screen resolution, WebGL support, or cookie settings, check our What Is My Browser tool.
Microsoft stopped bumping the kernel number in the User-Agent header after Windows 10. Both Windows 10 and Windows 11 send Windows NT 10.0 so older websites do not misread the version, and Apple did the exact same thing by freezing macOS strings at 10_15_7.
Chrome used Apple's WebKit engine before forking it into Blink in Chrome 28. It keeps AppleWebKit/537.36 and Safari/537.36 in the header so mobile sites looking for Safari still serve the right layout. A good user agent decoder checks for Edge, Opera, and Chrome tokens first before assuming a visitor is on Safari.
Legitimate crawlers put their name and a help URL inside parentheses, like Googlebot/2.1, bingbot/2.0, GPTBot/1.2, or ClaudeBot. Since anyone can type a fake bot name into a script, server admins confirm real crawlers by running a reverse DNS lookup on the request IP.
To cut down on browser fingerprinting, Chromium browsers now zero out minor build numbers (like Chrome/131.0.0.0) and replace real Android phone models with a generic Android 10; K token. Sites that still need the exact device model or Windows 11 build have to request Sec-CH-UA Client Hints headers from the browser.
Yes, easily. It is just a plain-text HTTP header. Anyone can change it in browser DevTools, install a switcher extension, or pass the -A flag in cURL. Use parsed user agent data for debugging layouts or traffic logs, never as a security check.
Similar Tools
What Is My Browser
HTTP Headers Checker
Robots.txt Validator
Disclaimer
User-Agent strings are self-reported HTTP headers that can be modified by browser extensions, privacy settings, or custom scripts. Parsed results run locally in your browser and are never logged or transmitted to any server.