About useragent.in

What this is

Three things, really. A detector that shows your own user agent parsed into every field it contains. A parser that does the same for any string you paste in. And a database of 27,613 user agent strings covering desktop browsers, phones, tablets, televisions, consoles, wearables, in-app browsers, crawlers and HTTP libraries.

Why it exists

Most user agent tools show you the raw string and stop, or bury a two-line result under advertising. If you are debugging why a layout breaks on one specific Android build, or writing a bot filter, or assembling a device matrix for cross-browser testing, you need the parsed detail — the engine, the form factor, whether it is a webview, whether the string has been frozen — and you need realistic strings to test against.

How the detection works

Everything runs client-side. The parser is a single JavaScript file with no dependencies that matches against an ordered set of rules — bots first, then Chromium forks, then mainstream browsers, then engines, platforms, devices and CPU. On Chromium browsers it additionally calls navigator.userAgentData.getHighEntropyValues() and merges Client Hints over the string result, which is how it can resolve Windows 11 and real Android device models despite both being frozen out of the user agent.

The parser is validated against every string in the database on each build. As of this build it resolves a browser, platform and device type for 100% of them.

Privacy

Your user agent is never transmitted to us. There is no account, no tracking pixel, and no analytics that records what you parse. The privacy page spells out exactly what is and is not collected.

Using the parser yourself

The parser file is free to use in your own projects, commercially or otherwise:

<script src="https://useragent.in/assets/js/ua-parser.js"></script>
<script>
  const r = UAParser.parse(navigator.userAgent);
</script>

The dataset is equally open — each category is a JSON file under /assets/data/. See the API page for both.

Corrections

User agent detection is never finished — new devices ship, browsers change their strings, and crawlers appear. If you find a string this site parses incorrectly, or a device class it misses entirely, please send it over. Concrete examples of wrong output are the most useful thing you can send.