ToolSphere

User Agent Parser

More tools

Parse user agent strings to identify web browser, layout engine, operating system, and device type. Inspect client details or parse your current browser.

User agent parser

On this browser only

Give feedback

Did this tool help?

Tell us what worked, what didn’t, or what you’d like next.

Opens Google Forms in a new tab with this tool’s name filled in. No sign-in or email required. Feedback is optional.

About User Agent Parser

Why User-Agent Strings Are a Historical Mess

A User-Agent string identifies the browser, engine, and operating system making an HTTP request — but its actual format is a well-known historical accident: nearly every modern browser's User-Agent string contains the word "Mozilla" for backward-compatibility reasons dating back to the 1990s browser wars, even though most of them aren't Mozilla-based at all. Parsing a User-Agent string correctly means recognizing these historical quirks and layered compatibility tokens, not just reading it literally.

This is exactly why naive User-Agent parsing (simple substring matching) frequently misidentifies browsers — many browsers include other browsers' names in their own User-Agent string for compatibility purposes (Edge includes "Chrome" and "Safari" tokens, for instance), so correctly identifying the actual browser requires checking tokens in a specific priority order, not just checking whether a name appears anywhere in the string.

User-Agent strings are also increasingly considered a fingerprinting/privacy concern, which is part of why some browsers are moving toward "User-Agent reduction" — deliberately returning less detailed information than they used to, trading some server-side compatibility logic for reduced tracking surface.

Frequently asked questions

Why does almost every browser's User-Agent string contain "Mozilla"?

A historical artifact from 1990s browser compatibility — early servers checked for "Mozilla" to serve enhanced content, and subsequent browsers kept including the token for backward compatibility, even though most aren't Mozilla-based today.

Why does simple substring matching often misidentify browsers?

Many browsers include other browsers' name tokens in their own User-Agent string for compatibility purposes — Edge's string contains both "Chrome" and "Safari" tokens, so correctly identifying the actual browser requires checking tokens in a specific priority order, not just presence.

Why are some browsers reducing the detail in their User-Agent strings?

User-Agent details can contribute to browser fingerprinting, a privacy concern — some browsers now deliberately return less granular information than they historically did, trading server-side compatibility detail for reduced tracking surface.

Have a suggestion for User Agent Parser?Share your feedback ↗