User agent parser

Decode user agent strings

Every browser and bot sends a user agent string with its requests, something like Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/130.0.0.0 Safari/537.36. It's meant to describe the software making the request, but it's notoriously confusing: nearly every browser claims to be "Mozilla" for historical reasons.

Paste a user agent and this parser pulls out the useful parts: the browser, the operating system and the device type (desktop, mobile or tablet).

Developers and support teams use it to understand bug reports, read server logs and analytics, and check what devices visitors are using.

How to use the user agent parser

1. Copy the user agent string from your logs, analytics or a bug report.
2. Paste it into the user agent field.
3. Submit to parse.
4. Read the browser, operating system and device type.

Examples

Desktop Chrome

Input:

Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/130.0.0.0 Safari/537.36

Output: Browser: Chrome 130 · OS: Windows 10 · Device: desktop

The string also says Safari and Mozilla for compatibility, but the parser identifies Chrome.

iPhone Safari

Input:

Mozilla/5.0 (iPhone; CPU iPhone OS 18_0 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/18.0 Mobile/15E148 Safari/604.1

Output: Browser: Safari 18.0 · OS: iOS 18.0 · Device: mobile

Android Chrome

Input:

Mozilla/5.0 (Linux; Android 14; Pixel 8) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/130.0.0.0 Mobile Safari/537.36

Output: Browser: Chrome 130 · OS: Android 14 · Device: mobile

Googlebot

Input:

Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)

Output: Browser: Googlebot 2.1 · Device: bot

No operating system is reported for crawlers.

Common uses

• Understanding which browser and device a bug report came from.
• Reading raw web server or CDN logs.
• Identifying bots and crawlers (for example Googlebot or Bingbot).
• Checking compatibility for apps and email templates.
• Testing that your own user agent detection works.

Tips and things to know

• User agents can be faked, so don't rely on them for security decisions. Verify search engine bots with a reverse DNS check using the reverse IP lookup.
• Chrome and other browsers have reduced the detail in user agents for privacy, so versions and device models may be less specific.
• For feature support, test for the feature in code rather than guessing from the user agent.
• Check the headers a server returns with the HTTP headers lookup, or locate an IP with the IP lookup.

Edge cases and limitations

• Windows 11 browsers still send "Windows NT 10.0", so they're shown as Windows 10. The user agent string alone can't tell them apart.
• Chrome reports a frozen version like 130.0.0.0, so minor version numbers aren't real.
• Anyone can fake a user agent. A string claiming to be Googlebot isn't proof it's Google; check with a reverse IP lookup.

Frequently asked questions

What is a user agent?

A text string a browser or app sends with requests that identifies its software, version and platform.

Why does every user agent start with Mozilla?

For historical compatibility. Early websites served advanced pages only to Netscape (Mozilla), so other browsers copied the prefix.

How do I find my user agent?

Your browser's developer tools show it, and many sites display it. You can copy it and paste it here.

Can a user agent tell me the exact phone model?

Sometimes on Android, but modern privacy changes and iOS hide many details.

Related tools

• URL parser: Parse details from any URLs.
• IP Lookup: Get approximate IP details.
• HTTP headers lookup: Get all the HTTP headers that an URL returns for a typical GET request.
• Reverse IP Lookup: Take an IP and try to look for the domain/host associated with it.
• JSON validator & beautifier: Validate JSON content and make it looks good.