User-Agent Parser
Parse any user agent string into browser, engine, OS, device, and CPU details.
About the User-Agent Parser
Every HTTP request a browser makes carries a user agent header, a dense string describing the browser, its engine, and the operating system it runs on. They are useful for debugging and analytics and nearly impossible to read by eye, because decades of compatibility hacks mean every browser pretends to be several others. Safari claims to be Mozilla. Chrome claims to be Safari. Edge claims to be Chrome claiming to be Safari claiming to be Mozilla.
This tool parses any user agent string into a clean table: browser name and version, rendering engine, operating system, device vendor and model, and CPU architecture. Paste a string from your server logs, an error report, or a support ticket, or click Use mine to parse the browser you are in right now.
Typical uses: confirming which browser version a bug report came from, checking what a crawler or bot identifies as, working out whether traffic in your logs is mobile or desktop, and verifying what your own application sends.
Parsing happens entirely in your browser with the ua-parser-js library. Log lines and user agent strings, which can be personally identifying in combination with other data, never leave your machine.
Reach developers and designers who use these tools every day. Privacy-first, no trackers.
Frequently asked questions
Why do all user agents start with Mozilla/5.0?
History. In the 1990s servers sent better pages to Netscape (Mozilla), so other browsers started claiming to be Mozilla to get them. Every browser since has kept the prefix for compatibility. It means nothing today.
Can I rely on user agent parsing for feature detection?
No. User agents are routinely spoofed and browsers are reducing the information they contain. Use feature detection in code instead. User agent parsing is for understanding logs and reports, not for deciding what code to run.
Why does the parser show no device vendor for desktop browsers?
Desktop user agents do not include hardware vendor information. Vendor and model appear mostly for mobile devices, where the user agent often names the phone, like SM-G991B for a Samsung Galaxy S21.
What is the difference between the browser and the engine?
The engine renders pages; the browser is the product around it. Chrome, Edge, Opera, and Brave all use the Blink engine. Safari uses WebKit. Firefox uses Gecko. Bugs often track the engine rather than the browser.
Is my log data uploaded anywhere?
No. Parsing runs locally in your browser. Nothing you paste here is transmitted, stored, or logged.