Skip to content
en es

User Agent Parser

Paste a user-agent string to see the browser, rendering engine, operating system, device and CPU. The page starts with your own user agent and also shows the User-Agent Client Hints your browser offers.

Runs in your browser — nothing is uploaded.

The page starts with your own user agent.

Samples

Result

Looks like a bot

Client Hints of this browser

Reported by your browser through navigator.userAgentData, not parsed from the string above.

This browser does not support User-Agent Client Hints (Chrome, Edge and other Chromium browsers do).

Only the basic hints were available: the detailed ones were refused.

How to use it

  1. Your own user agent is filled in. Paste another one or pick a sample to parse it.
  2. Read the browser, engine, operating system, device and CPU.
  3. Below, see the Client Hints your browser reports about itself.

Frequently asked questions

Why do all user agents start with Mozilla/5.0?

For historical compatibility: browsers have copied each other’s strings for decades so that sites would not block them. Chrome even says “like Gecko” and “Safari”. That is why parsing needs a library with many rules.

Can a user agent be trusted?

No. Clients can send anything they like, and bots often pretend to be browsers. Use it for statistics and hints, never for security decisions.

What are Client Hints?

A newer way for Chromium-based browsers to describe themselves (navigator.userAgentData). Chrome and Edge are reducing the detail in the classic string, so details such as the exact OS version or CPU architecture are only available through hints. Firefox and Safari do not provide them.

Is anything sent to a server?

No. The string is parsed in your browser with an open-source library, and your own user agent is read locally.

Why is the device unknown?

Desktop browsers usually do not report a device. Phones and tablets usually do, but many only say “Android” or hide the model on purpose.