User-Agent and Client Hints Explainer

Inspect your browser user-agent and available hints, or enter another bounded example.

On-device No sign-up Free to use

Inspect input controls

Showing an example. Edit to see your own.

?

Available low-entropy Client Hints are filled from this browser when supported. You can replace them with header-name: value lines. No extra high-entropy request or website lookup is made.

Processed in your browser. Your inputs stay on this device.

Result

Showing an example.

Interpret a recorded Chrome 130 header sample without treating it as a current browser or verified device identity.

Browser heuristic: Chrome 130.0.0.0. Platform token: Windows NT 10.0, which does not distinguish Windows 10 from 11. The supplied sec-ch-ua declares Chromium 130 and sec-ch-ua-mobile declares ?0. These are pasted claims, not verified device identity.

Loading the tool. Your result will appear here.

https://usefreetools.net/user-agent-client-hints-explainer · 20 November 2026

Was this helpful?

How to use User-Agent and Client Hints Explainer

  1. The page fills your current browser’s User-Agent and any available low-entropy brand, mobile and platform hints. Reset fills those local values again.
  2. To inspect a recorded request instead, replace the fields with its User-Agent and Sec-CH-UA header-name: value lines. Either input may be left empty when the other contains a value.
  3. Read the token estimates, declared hint values and uncertainty notes. Download user-agent-observations.json to keep the observations.

Example: User-Agent and Client Hints Explainer

Interpret a recorded Chrome 130 header sample without treating it as a current browser or verified device identity.

You add
User-Agent string: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/130.0.0.0 Safari/537.36; Client Hint headers (optional): Sec-CH-UA: "Chromium";v="130", "Not_A Brand";v="24" Sec-CH-UA-Mobile: ?0 Sec-CH-UA-Platform: "Windows"
You get
Browser heuristic: Chrome 130.0.0.0. Platform token: Windows NT 10.0, which does not distinguish Windows 10 from 11. The supplied sec-ch-ua declares Chromium 130 and sec-ch-ua-mobile declares ?0. These are pasted claims, not verified device identity.

Options

Browser values or recorded headers
The initial fields use navigator.userAgent and already available low-entropy navigator.userAgentData values where supported. You can replace them with other recorded claims. The page does not call getHighEntropyValues(), fetch a website or request extra Client Hint headers.
Hint forms
Brand lists use quoted Brand;v="version" entries. Mobile and WoW64 hints use ?0 or ?1. Supported platform, architecture, bitness, model and full-version hints use quoted strings. Unknown Sec-CH-UA hint names remain uninterpreted; repeated names and malformed supported forms are refused.
Heuristic observations
Browser and platform estimates come from recognizable tokens, not authenticated identity. Compatibility brands, reduced strings and GREASE decoy brands can appear together. A Windows NT 10.0 token does not distinguish Windows 10 from Windows 11.

Supported inputs and limits

  • Each input is limited to 8,192 UTF-16 units.
  • Supported brand lists accept at most 20 entries.
  • Pasted or locally available claims can be reduced, forged or inconsistent.
  • The tool does not establish a precise operating system, device identity, automation status or actual feature support.
  • No additional high-entropy hint request or website lookup occurs.

Where your input is processed

This tool does not upload your inputs. See the limits for anything saved on your device.

Disagreement needs investigation

Reduced user-agent strings, compatibility tokens and supplied hints can describe different levels of detail. A conflict does not by itself establish fraud or a specific operating system. Keep the original request context when diagnosing a compatibility issue and test the actual feature you need instead of using this output as verified identity.

Questions about User-Agent and Client Hints Explainer

Is a user-agent a verified browser identity?

No. It is supplied text and can be forged or reduced.

Are hints requested from my device?

The page reads the User-Agent and already available low-entropy hints from your browser to fill the fields. It does not request high-entropy values or contact a website for headers. Replace the fields when you want to inspect a different request.

What does an unknown token mean?

It has not been mapped by this bounded heuristic; retain the original value for review.

Page updated · Project managed by Tony Hines · Report a problem with User-Agent and Client Hints Explainer