User-Agent Parser

The User-Agent Parser reads a browser's User-Agent string and breaks it down into browser name and version, rendering engine, operating system, and device type — turning a dense, hard-to-read string like 'Mozilla/5.0 (iPhone; CPU iPhone OS 17_4...)' into a clean, labeled summary.

It's used constantly for debugging a browser-specific bug report by confirming exactly which browser, version and OS combination the reporter was using, checking analytics or server logs to understand what device sent a particular request, verifying that a User-Agent your own application sends (for an API client or bot) parses the way you intend, and satisfying simple curiosity about what a given User-Agent string actually claims to be.

Parsing recognizes the major browser engines (Blink/Chromium, WebKit, Gecko) and their downstream browsers (Chrome, Edge, Safari, Firefox and many others), common operating systems (Windows, macOS, iOS, Android, Linux and their versions), and device type (desktop, mobile, tablet) along with vendor and model when the string includes that detail, which mobile Safari and Android WebView User-Agents typically do.

User-Agent strings are self-reported by the browser and not cryptographically verified in any way — a browser (or a script using `fetch` or `curl`) can claim to be anything, so this tool reports what the string says, not a guaranteed fact about the actual client. That said, for legitimate debugging and log analysis, it reflects exactly what a real visitor's browser sent, which is why server logs and analytics platforms still parse User-Agent strings as a practical (if imperfect) signal despite this limitation. Parsing happens entirely client-side; no User-Agent string you paste here is logged or transmitted, so it's safe to paste a string copied straight out of a private server log while debugging.