Skip to content

User Agent Parser

Break a user agent string into browser, engine, operating system and device.

Quick Tool Overview

The User Agent Parser untangles thirty years of compatibility claims into the real browser, engine, operating system and device — checking the most specific token first, which is what naive detection gets wrong.

What it does
Parses a user agent string into its real components
You give it
A user agent string
You get back
Browser, version, engine, OS and device class
Best for
Reading server logs and analytics data
Developer Tools Free, unlimited use No sign-up Runs in your browser

About the User Agent Parser

A user agent string is an accumulation of thirty years of compatibility lies. Every browser claims to be Mozilla, most claim to be Safari, and Chromium-based browsers append their real identity at the end and hope you read it backwards.

This untangles it: the actual browser and version, the rendering engine, the operating system and its version, and the device class. The ordering matters and is handled correctly — Edge is checked before Chrome, and Chrome before Safari, because each claims to be the next. Crawlers and scripts get their own treatment, with Googlebot, the AI crawlers, link-preview fetchers, curl and headless automation all identified by name.

Key features of the User Agent Parser

Checks in the right order

Edge before Chrome, Chrome before Safari — because each claims to be the next, and getting the order wrong misattributes every Edge user.

Bots identified by name

Googlebot, the AI crawlers, link-preview fetchers, curl, Postman and headless Chrome are each named rather than reported as an unknown browser.

Windows versions decoded

Windows NT 10.0 becomes "10 or 11", because Microsoft never changed the token — which is a genuine limitation worth knowing.

Device class inferred

Desktop, mobile, tablet or TV, worked out from the combination of tokens rather than a single keyword.

Honest about reliability

A user agent is a header anyone can set, and the page says so rather than presenting it as fact.

How to use the User Agent Parser

  1. 1

    Paste a user agent

    From a server log, an analytics report or a request header.

  2. 2

    Read the breakdown

    Browser, version, engine, operating system and device class.

  3. 3

    Check for bots

    Crawlers and scripts are named rather than being reported as an unknown browser.

  4. 4

    Compare several

    Parse a list at once when you are working through a log.

Frequently asked questions

Because of a browser war in the 1990s. Netscape called itself Mozilla, servers checked for it before serving frames, and every subsequent browser copied the claim to avoid being downgraded. It has been meaningless for decades.

Reviews of the User Agent Parser

What people who use the User Agent Parser think of it. Reviews come from visitors and are posted as written.

No ratings yet

Yours would be the first.

  • 5 0 reviews rated 5 stars
  • 4 0 reviews rated 4 stars
  • 3 0 reviews rated 3 stars
  • 2 0 reviews rated 2 stars
  • 1 0 reviews rated 1 star

Write a review

Used this tool? Your rating helps the next person decide.

Your rating

Plain text only — links, email addresses and HTML are not accepted. Your name and review are shown publicly; nothing else is collected. See the privacy policy.

0 reviews

Newest first

No reviews yet

Be the first to rate the User Agent Parser. It takes half a minute and no account.

Write the first review

More developer tools