User-Agent Parser
Extract browser name and version, rendering engine, operating system, device category, bot status, and CPU architecture from any HTTP User-Agent string.
Private by architecture:
All processing is 100% client-side memory. Your data never leaves this browser tab.
User-Agent string
0 charsHTTP Header
Parsed summary
Detected tokens
Ready
About This Tool
Deconstructs HTTP User-Agent strings into structured fields: Browser (name + version), Rendering Engine (Blink, WebKit, Gecko, Trident), Operating System (Windows, macOS, iOS, iPadOS, Android, Linux, ChromeOS), Device Category (desktop, mobile, tablet, bot, CLI), and CPU architecture hints.
Includes a one-click button to inspect your own current browser navigator.userAgent alongside presets for mobile Safari, Edge, Googlebot, and cURL.
Key Features
- Priority-aware browser detection: Correctly distinguishes Edge, Opera, Vivaldi, Samsung Internet, and Chrome on iOS from generic Chrome and Safari tokens.
- Bot & CLI recognition: Identifies search and AI crawlers (Googlebot, Bingbot, GPTBot, ClaudeBot, Applebot) as well as CLI clients (cURL, Wget, HTTPX, Postman).
- One-click "Use my browser UA": Load your active browser navigator.userAgent string immediately or export the parsed fields as JSON.
- Token breakdown: Lists every product/version token and parenthetical system comment inside the User-Agent string.
Frequently Asked Questions
Why do almost all browsers begin their User-Agent with "Mozilla/5.0" and end with "Safari/537.36"?
Decades of server-side User-Agent sniffing caused websites to serve broken pages unless "Mozilla/5.0", "AppleWebKit", "KHTML, like Gecko", and "Safari" appeared in the string. Modern browsers keep those historical compatibility tokens and append their real identifier (such as Edg/ or OPR/) at the end.
Why does macOS on Apple Silicon still say "Intel Mac OS X 10_15_7"?
Under User-Agent Reduction, Safari, Chrome, and Firefox froze the macOS version and architecture token in the User-Agent header to reduce passive fingerprinting.
Is my User-Agent logged when I use this page?
No. Parsing runs entirely in your browser tab.
