User-Agent Parser
Detect browser, engine, OS, and device from any user-agent string.
100% in your browser — nothing uploadedPaste a user-agent string — from a server log, an analytics report, or a bug ticket — and see what it identifies: browser and version, rendering engine, operating system, and device type. A hand-written rule table checks signatures in the order that actually works: bots first (crawlers embed real browser tokens), Edge and Opera before Chrome, and Chrome before Safari, because every Chromium fork keeps both "Chrome" and "Safari" in its string.
It’s built for support engineers triaging "works on my machine" tickets, developers reading access logs, and anyone curious what their own browser sends — there’s a "use mine" button for that. Parsing happens entirely in this page’s JavaScript: no lookup API, no database call, nothing leaves your device, so it’s safe to paste user agents straight from production logs.
FAQ
Why do all user-agent strings start with Mozilla/5.0?
Historical compatibility. Early websites served better pages to Netscape ("Mozilla"), so every later browser claimed to be it — and then to be each other. That’s why detection order matters: Edge and Opera include "Chrome" in their strings, and everything Chromium-based includes "Safari".
Why does the OS show "Windows 10 / 11"?
Windows 11 still reports "Windows NT 10.0" in the user agent, so the two are indistinguishable from the string alone. Only User-Agent Client Hints (Sec-CH-UA-Platform-Version) can tell them apart, and those are sent as separate headers, not in the UA string.
How accurate is user-agent parsing?
Best-effort, and getting less precise by design. Modern browsers freeze or reduce their strings — Safari has reported macOS 10.15.7 for years, and Chrome trims OS details — while Client Hints replace them. Strings can also be spoofed freely, so treat the result as a strong hint, not proof.