Free browser tool

User-Agent parser

Estimate browser, operating system, and device type from a User-Agent string.

Input and settings

How to use it

Turn a User-Agent string into a quick estimate of browser, OS, device class and whether it looks like a bot. It is useful for first-pass log/support triage, not for proving the identity of a device or user.

  1. Paste a User-Agent or use the button to insert this browser’s UA.
  2. Run the parser and review browser/version, OS, device class and Bot status.
  3. For important decisions, combine the result with other logs or client information.
Browsers recognized
Edge / Opera / Chrome / Firefox / Safari
OS families
Windows / Android / iOS / macOS / Linux and others
Device class
smartphone / tablet / desktop or unknown
Bot heuristic
looks for common bot/crawler keywords

Summarize a long access-log UA as something like Chrome / Android / Smartphone

Instead of reading every token in a long string, the result separates a few useful fields for a quick support or analytics investigation.

User-Agent strings can be spoofed or deliberately reduced by browsers. Windows 10 and 11 may also look the same in a traditional UA. Do not use this output alone for authentication, fraud decisions or exact device identification.

The parser recognizes common browser signatures

It checks familiar Edge, Opera, Chrome, Firefox and Safari patterns and reports Other when the simple rules do not recognize the string.

Windows 10 and 11 are not reliably separable here

Modern Windows browsers commonly expose Windows NT 10.0 for both, so the result intentionally groups them as Windows 10/11.

Device class is also a heuristic

Tokens such as Mobile, iPhone, Android and iPad guide the phone/tablet classification. Desktop mode and unusual browsers can make the label differ from the physical hardware.

Bot detection is not a complete crawler database

The result looks for common words such as bot, crawler and spider. A disguised or new automated client may still be reported as non-bot.

Use it as a starting point for support analysis

After summarizing the UA, use browser version details, client hints, viewport information and server logs when the investigation requires more certainty.