Skip to main content
DataLeaked
Back to blog

Client Hints explained: the new way browsers identify you

User-Agent Client Hints (UA-CH) are replacing the User-Agent string as the way sites learn about your browser and device. Here is how they work, what they expose, and how to control them.

Published: 2 min read

Why Client Hints exist

The User-Agent string grew into a long, frozen, high-entropy identifier that sites used for tracking. Client Hints are a structured replacement: the browser sends a small set of low-entropy hints by default, and sites must explicitly request more detailed ones.

The goal is to reduce passive fingerprinting while still letting sites adapt to device capabilities. In practice, the rollout is gradual and the privacy benefit depends on browser defaults and site behavior.

Client Hints are delivered via HTTP headers (Sec-CH-UA, Sec-CH-UA-Platform, etc.) and a JavaScript API (navigator.userAgentData).

What is sent by default

By default, browsers send a brand list, platform, and mobile flag. These are low-entropy but still identifying, especially the brand list which can reveal browser family and approximate version.

High-entropy hints (platform version, architecture, model, bitness, full version list) require the site to opt in via Accept-CH headers or JavaScript calls, and the browser may prompt or gate them.

The reduction in entropy is real but modest. A determined tracker can still request high-entropy hints, and many sites do.

  • Sec-CH-UA: brand and major version (e.g., Chrome 120)
  • Sec-CH-UA-Mobile: ?0 or ?1
  • Sec-CH-UA-Platform: Windows, macOS, Android, etc.
  • High-entropy (on request): platform version, architecture, model, bitness, full version list

How to check what your browser sends

Run the browser details analysis on this site. It reads navigator.userAgentData and reports both the low-entropy and (where available) high-entropy values.

Compare the reported values with your User-Agent string. Notice how Client Hints can expose platform version even when the User-Agent is frozen.

Test in multiple browsers: Chromium-based browsers support Client Hints fully; Firefox and Safari have different levels of support.

Controlling Client Hints

You cannot fully disable Client Hints in most browsers, but you can limit them. Brave reduces or randomizes hints. Firefox has partial support. Extensions can strip Accept-CH requests.

Freezing the User-Agent (as Chrome has done) reduces one signal, but Client Hints reintroduce some of it through a structured channel.

The most effective control is using a browser with strong fingerprinting protection, which tends to normalize or reduce both signals.

What this site measures

Our browser tool collects Client Hints where available and reports them as measured values. Where the API is missing, we label it unavailable rather than guessing.