UA Client Hints, low entropy
Browser brand list, mobile flag and OS name that Chromium sends by default.
In one line
Can see your browser brand, whether it is mobile, and your OS name
Browser brand list, mobile flag and OS name that Chromium sends by default.
Three coarse hints (Sec-CH-UA, Sec-CH-UA-Mobile, Sec-CH-UA-Platform) replace most of the old User-Agent. They split the audience into mobile vs desktop and Windows vs macOS vs Android with almost no tracking power.
What it can and can't do
What the user does: Nothing. Chromium sends this with every request
It can
- See your browser brand list
- See a yes or no for mobile
- See whether you use Windows, macOS, Android, or Linux
- Split visitors into big groups, such as mobile and desktop
It cannot
- See exact versions or device models
- Work in Firefox, Safari, or on iPhone
- Tell you apart from many other visitors
- See your name, location, or accounts
How it differs between platforms: Chromium browsers send them. Firefox and Safari send the old user agent text instead.
Browser support
| Browser | Status | First version | Released | Note |
|---|---|---|---|---|
| Chrome | Supported | 90 | 2021-04-13 | None |
| Edge | Supported | 90 | 2021-04-15 | None |
| Firefox | Not supported | Not available | Not listed | None |
| Safari | Not supported | Not available | Not listed | None |
| Safari on iPhone | Not supported | Not available | Not listed | None |
| Chrome on Android | Supported | 90 | 2021-04-13 | None |
| Samsung Internet | Supported | 15.0 | 2021-08-13 | None |
How a site asks for it
| API | navigator.userAgentData.brands, .mobile, .platform; headers Sec-CH-UA, Sec-CH-UA-Mobile, Sec-CH-UA-Platform |
| Browser compat keys | api.Navigator.userAgentDataapi.NavigatorUAData.brandsapi.NavigatorUAData.mobileapi.NavigatorUAData.platform |
| How access is granted | none |
| What the user sees | None |
| Needs a secure context (HTTPS) | Yes |
| Needs a user gesture | No |
| How long it lasts | read fresh on every page load; nothing stored |
| How to take it back | none needed (no grant) |
| Inside an iframe | Readable from cross-origin iframes too (same values) |
Typical flow
- Page script reads the value
- No prompt is shown
Data you get
Shape: object
How often: static per session
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
brands | list | None | 3 or so brand+version pairs incl. one randomized GREASE brand like Not A;Brand | major version only |
mobile | boolean | None | true or false | Not listed |
platform | enum | None | Windows, macOS, Linux, Android, Chrome OS, iOS(n/a), Unknown | Not listed |
Technical limits
- Chromium family only (Chrome, Edge, Opera, Brave)
- HTTPS or localhost only
- Brand list order and GREASE token are randomized per version to stop sniffing
The story
What it is
Three basic facts sent by default: browser brand, phone or not, and operating system name.
For you
You never see these. They ride along with every page request, in the background. They let a site know if you are on a phone or a computer so it shows the right version.
For makers
These replace most of the old user agent. They give just enough to serve mobile or desktop pages and basic OS fixes. They are coarse, so they carry less tracking value.
Where you see it
| Type | Example | Apps |
|---|---|---|
| shopping | A shop sends a mobile layout to phones and a full layout to desktops from the very first request. | None named |
| games | A game portal picks the mobile or desktop version of a browser game before the page loads. | Poki |
| media | A news site routes phones to a lightweight version of an article. | None named |
| video | A video site chooses a mobile player on phones and a full player on computers. | YouTube |
| analytics | A traffic dashboard splits visits into mobile and desktop and Windows, Mac and Android. | Google Analytics |
| security | A bot tool compares the brand list with other signals and flags a fake Chrome. | Cloudflare |
Risks
- Very coarse
- Still splits audiences
What the platform says
- Google: User-Agent Client Hints. Chrome sends a short default set and lets sites ask for more, as part of reducing the old user agent.
Good uses and abuse
Legitimate uses
- Pick download for OS
- Mobile layout
Known abuse
- Baseline for fingerprint combos
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 1 of 5 | How revealing the data is |
| Utility | 4 of 5 | How useful it is to honest apps |
| Friction | 0 of 5 | How much the user has to do |
| Fingerprint bits | 2 | Rough identifying entropy, when known |
History
- 2021-03, Chrome 89: Sec-CH-UA, Mobile, Platform sent by default on HTTPS
- 2022-10, Chrome 107: UA string reduction completes the shift of detail to hints
Related capabilities
Related
- UA Client Hints, high entropy. Can see detailed device and browser versions, but only if the site asks
Sources
- Chrome developers: UA Client Hints
- MDN NavigatorUAData
- fingerprintjs source: user_agent_data
- Browser Fingerprinting: A Survey, Laperdrix et al.
How well checked: Checked against real behavior.