User Agent Parser navigator

What this tool does

The User-Agent header is sent by a browser with every request and describes the browser and version, the operating system, and the rendering engine. Servers have historically used it to decide whether to serve a mobile layout or whether a feature is supported.

The problem is that the string is historically messy. A Chrome User-Agent mentions Mozilla, AppleWebKit, KHTML, and Safari all at once, because browsers began embedding each other names to pass compatibility checks and the practice never went away. Reading one by eye is therefore awkward.

This tool parses the string and separates browser, version, operating system, engine, device type, and bot indicators. You can inspect the current browser directly or paste a User-Agent taken from a log.

When to use it

Use it to identify the device behind an entry in an access log, to reproduce a bug reported only on a particular browser, to distinguish crawler traffic from real users, or to summarise the environment details in a support ticket.

Input and output examples

Notes and limitations

User-Agent strings are trivially forged. Developer tools and extensions can change them, and automation tools set them arbitrarily, so a User-Agent must never be the basis for a security or access control decision. Browsers are also reducing the detail exposed for privacy reasons, so precise version and device information may be absent. Detect features directly rather than inferring support from the User-Agent.

Frequently asked questions