HTTP User-Agent String Parser & Client Inspector
Parse browser, operating system, rendering engine, device model, and CPU architecture from any User-Agent string. Decode historical compatibility tokens and inspect live client hardware hints in-browser with zero server tracking.
User-Agent input is empty
Enter or paste any User-Agent string above, click "My Browser UA" to inspect your current browser, or pick any sample preset above.
Anatomy of HTTP User-Agent Strings
Why do HTTP User-Agent strings contain so many deceptive and redundant tokens?
The Netscape & Mozilla Era
Netscape Navigator was code-named Mozilla. When webmasters created modern frames and JavaScript tables, they routed them exclusively to browsers starting with Mozilla/. When Microsoft introduced Internet Explorer, it prepended Mozilla/4.0 (compatible; MSIE...) so servers wouldn't break.
WebKit, Chrome & Safari
Apple created WebKit for Safari and added KHTML, like Gecko so Gecko-optimized websites rendered cleanly. Later, Google created Chrome and included both AppleWebKit and Safari tokens to inherit website compatibility.
Client Hints (Sec-CH-UA)
Because full User-Agent strings provide passive browser fingerprinting attack vectors, Chromium and WebKit are transitioning to User-Agent Reduction. Web servers now receive condensed OS strings and can selectively request granular details via Sec-CH-UA HTTP headers.
Frequently Asked Questions
Common questions about HTTP User-Agents, bot detection, and browser client privacy.