#066 · Developer Utilities Developer Tool

User Agent Parser

Analyze User-Agent strings without external libraries and export browser, operating system, device, engine, bot, and WebView results.

Developer Input

One User-Agent per line

Detection Summary

Batch statistics

How to use this developer tool

  1. Paste one or more User-Agent strings.
  2. Select JSON or CSV output.
  3. Run the parser.
  4. Review detection confidence and unknown fields.

What this developer tool does

Applies ordered pattern matching so Chromium-derived browsers are identified before generic Chrome rules.

Split lines → bot/in-app/WebView checks → browser rules → OS rules → device/model rules → confidence output.

User-Agent strings can be modified and should be treated as hints rather than verified identity.

Example

Android Chrome Mobile string with model SM-S918N.

Tips for better output

  • Check Edge, Opera, and Samsung Internet before generic Chrome.
  • Use Client Hints when available.
  • Keep Unknown rather than guessing unsupported models.

FAQ

How do I detect the browser from a User-Agent string?

The parser applies ordered browser patterns and returns the first specific match.

How do I identify mobile devices using User-Agent text?

Mobile, Tablet, iPad, and related tokens are used to estimate device type.

How do I detect Android WebView and in-app browsers?

The parser checks WebView markers and Facebook or Instagram tokens.

How do I check whether a User-Agent belongs to a bot?

Common bot, crawler, spider, and indexing tokens are flagged.

Why does a User-Agent parser return an unknown device model?

Many User-Agent strings omit or obscure model details, so the parser avoids unsupported guesses.

Supported formats and output

Single or batch User-Agent input. Output is JSON or CSV.