User Agent Parser

Run this tool

Input or start condition: The low-risk current browser or connection check loads automatically.

Accepted input or signal: No manual input.

Possible output: The current browser's User-Agent string and its recognizable browser name and major or full version token.; Rendering-engine, operating-system, platform, vendor, and broad desktop, mobile, or tablet hints.

Key limitation: Chromium-based browsers share many tokens, so the order of product tokens matters when distinguishing Edge, Opera, Samsung Internet, and Chrome.

What this checks

• The current browser's User-Agent string and its recognizable browser name and major or full version token.
• Rendering-engine, operating-system, platform, vendor, and broad desktop, mobile, or tablet hints.
• Whether privacy reduction or an unrecognized client leaves any field as Unknown.

How to interpret results

• Browser, engine, and operating-system values describe compatibility signals, not a verified device identity.
• A Mobile or Tablet result is inferred from tokens in the user agent and can differ from the physical form factor.
• Unknown is preferable to guessing when a browser omits, freezes, or generalizes a value.

Common issues

• Chromium-based browsers share many tokens, so the order of product tokens matters when distinguishing Edge, Opera, Samsung Internet, and Chrome.
• Modern privacy protections deliberately reduce user-agent detail; client hints may provide different information only when a site requests them.

How to read a parsed user agent

Start with the browser and engine rows. The browser row reflects a recognizable product token and version, while the engine row identifies the rendering family used for compatibility decisions. The operating-system and device rows are broader classifications derived from the same string.

Treat every field as a hint. User agents were designed for content negotiation and compatibility, and their inherited tokens can be misleading when used as a precise inventory of a person's device.

User agent reduction and privacy

Browsers increasingly freeze or generalize identifying fields to reduce passive fingerprinting. That can make two different devices expose similar strings, or cause an exact operating-system version to appear as a generic family.

For troubleshooting, compare this local parse with the HTTP Headers Check. A difference can show whether the request path omitted or changed a header, but it still should not be treated as proof of identity.

Privacy note

Parsing runs locally in your browser. The displayed user-agent and platform values are not submitted by this tool.

Frequently Asked Questions

What can a user agent string reveal?

A user agent can indicate a browser family and version, rendering engine, operating-system family, and broad device class. These are compatibility hints, not proof of a person's identity or exact hardware model.

Why can a parsed user agent be incomplete or wrong?

Browsers preserve old compatibility tokens, reduce identifying detail, and sometimes report frozen or generalized versions. The parser therefore labels only signals present in the current browser and uses Unknown when a value cannot be inferred safely.

Does this user agent parser send my string to a server?

No. This page reads and parses the current browser's user agent locally. Use the HTTP Headers Check separately if you want to see the safe request-header subset received by the site.