User Agent Parser

Paste a user-agent string from a log file, analytics export or bug report and see which browser, version, rendering engine, operating system, device type and CPU architecture it describes. A button also loads the string your own browser sends. Parsing uses the open-source UAParser.js library and happens entirely on this page.

URL & HTTP Runs in your browser

Parse a User-Agent String

JavaScript is required. This tool runs in your browser, so please enable JavaScript to use it. The instructions below are still available.

How to Use the User Agent Parser

Paste a user-agent string, or press Use my browser's user agent.
Read the parsed browser, engine, operating system and device details.
Check the notes for known limits of user-agent strings.

About This Tool

Developers reading server logs or bug reports, QA testers recording test environments, and analysts checking unusual traffic.

Input: User-agent string · Output: Browser, engine, OS and device.

Features and Limitations

Features

Recognises hundreds of browsers, engines, operating systems and devices via UAParser.js 1.0.
Flags strings that look like bots or command-line tools.
Explains frozen values, such as Windows 10 and 11 sharing one token.
Nothing is sent anywhere; the string is parsed in your browser.

Limitations

User-agent strings can be changed by the user or software, so they are not proof of the real browser or device.
Modern browsers reduce the detail they send: Chrome reports a fixed Android model and OS versions, and Windows 11 appears as Windows 10.
Device models are only known when the string includes them.
Results are computed in your browser; nothing you enter is sent to a server.

Example

The sample string is parsed as Mobile Safari 17.5 on iOS 17.5, WebKit 605.1.15, device type mobile, vendor Apple, model iPhone.

Frequently Asked Questions

Why does my Windows 11 PC show as Windows 10?

Browsers froze the Windows token at “Windows NT 10.0”, so Windows 10 and 11 send the same string. Sites that need the real version use User-Agent Client Hints.

Why do all browsers start with Mozilla/5.0?

For historical compatibility. Early websites checked for “Mozilla”, so every browser kept the prefix, and the string grew with tokens from other browsers.

Should I use user-agent sniffing on my site?

Prefer feature detection (checking whether an API exists) over browser detection. User-agent parsing is best kept for analytics, logs and debugging.

Is the user-agent string personal data?

On its own it identifies software, not a person, but combined with other signals it adds to browser fingerprinting.