Browser
—
Version —
Free network tool
See the UA your browser sends, compare HTTP vs JavaScript, read Client Hints, and paste any string to decode browser, OS and device.
Paste any UA from logs or pick an example. Decode updates the cards below instantly.
Quick examples
Showing: Your live browser
Browser
—
Version —
Core engine
—
Layout engine
Device type
—
Classified from UA tokens
Platform / OS
—
Version —
Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; [email protected])
Checking navigator.userAgentData…
A user agent is a short text string your browser (or bot, script, or app) sends so servers know how to format pages. It appears as the HTTP User-Agent header and in JavaScript as navigator.userAgent.
Modern browsers are freezing parts of that string and moving detail into Client Hints. This page shows both so you can see what sites actually receive.
Legacy servers sniffed for “Mozilla” to send modern HTML. Other browsers copied the prefix. It remains for compatibility even though it no longer identifies Netscape.
Normally both match. Extensions, anti-detect browsers, or reverse proxies can change one side. This page flags that mismatch so you notice spoofing or privacy tools.
Chromium browsers expose navigator.userAgentData. High-entropy fields include architecture and platformVersion. Windows 11 still reports Windows NT 10.0 in the classic UA; platformVersion 13+ means Windows 11 when hints are available.
Googlebot, Bingbot, ClaudeBot, curl and similar clients advertise themselves. Paste a log line into the decoder to classify it. Never trust UA alone for security — verify official bots with reverse DNS when needed.
Parsing runs in your browser. The HTTP UA is whatever your request already sent to our server (like any website). We do not create an account from this tool. See the Privacy Policy for logs.
A user agent (UA) string is a short text your browser sends so servers know roughly which browser and operating system you use. It appears in the HTTP User-Agent header and in JavaScript as navigator.userAgent.
Open this page — your live UA is shown at the top. You can also check developer tools → Network → request headers, or type navigator.userAgent in the browser console.
Historical compatibility. Early browsers pretended to be Mozilla so servers would send modern pages. The prefix stuck even though today’s browsers are not Mozilla.
Yes via extensions or developer tools, but many sites also use Client Hints and fingerprinting. Spoofing the UA alone rarely makes you anonymous.
User-Agent Client Hints are structured fields (brands, platform, architecture) that replace bits of the frozen UA string. Chrome-based browsers expose them via navigator.userAgentData.
The classic UA still says Windows NT 10.0 on Windows 11. Client Hints platformVersion 13 or higher indicates Windows 11. This page checks both when available.
A UA alone is shared by millions of users, so it is a weak identifier. Combined with IP, cookies and fingerprint signals it still helps profiling. Reducing uniqueness helps but is not complete privacy.
Crawlers such as Googlebot or curl send distinctive UA strings. Sites use them for analytics and access control. This tool flags common bot patterns when you paste a UA.
Look for the browser token (Chrome/, Firefox/, Version/…Safari/), the OS token (Windows NT, Android, Mac OS X), and optional device hints. This page parses those fields for you.
Changing your own UA for testing is generally fine. Using spoofing to bypass terms, commit fraud, or evade security controls can violate laws or site rules. Prefer honest testing accounts.