UA Client Hints, high entropy
Detailed device and browser versions a site can request with Accept-CH or a JavaScript call.
In one line
Can see detailed device and browser versions, but only if the site asks
Detailed device and browser versions a site can request with Accept-CH or a JavaScript call.
Returns exact OS version, CPU, bitness, device model and full browser version. Not sent unless the site asks. The browser can decline, but Chrome currently answers without a prompt.
What it can and can't do
What the user does: Nothing. The site asks and Chromium answers without a prompt
It can
- Get your exact OS version, chip, and 32 or 64 bit
- Get the Android phone model
- Get your full browser version
- Use the detail to serve the right app or ad
It cannot
- Work in Firefox, Safari, or on iPhone
- Get anything until the site asks for it
- See your name, location, or accounts
- See an iPhone model
How it differs between platforms: Chromium browsers answer without a prompt. Firefox and Safari do not offer these hints.
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 | 23.0 | 2023-10-18 | None |
How a site asks for it
| API | navigator.userAgentData.getHighEntropyValues([...]); Accept-CH response header then Sec-CH-UA-* request headers |
| Browser compat keys | api.NavigatorUAData.getHighEntropyValues |
| 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 |
|---|---|---|---|---|
platformVersion | string | None | e.g. 15.1.0 (macOS), 13.0.0 or higher for Windows 11 | Not listed |
architecture | enum | None | x86, arm, empty string | Not listed |
bitness | enum | bits | 32, 64 | Not listed |
model | string | None | Android model such as Pixel 8, else empty | Not listed |
fullVersionList | list | None | brand and full version, e.g. 142.0.7444.60 | 4-part version |
uaFullVersion | string | None | deprecated | Not listed |
wow64 | boolean | None | 32-bit browser on 64-bit Windows | Not listed |
formFactors | list | None | Desktop, Mobile, Tablet, XR, Automotive, EInk, Watch | Not listed |
Technical limits
- Chromium only
- Site must ask: header needs Accept-CH, JS call per hint
- Delegation to third parties needs Permissions-Policy
- Spec lets browsers refuse or lie; Chrome does not prompt today
The story
What it is
Detailed device and browser facts, like exact OS version and model, that a site can ask for.
For you
You never see it. If a site asks, Chrome can hand over exact versions, chip type and device model. In return you get the right installer, the right layout or fewer bugs.
For makers
The older user agent gave out everything. With hints, sites must ask, which gives the browser a chance to say no. Ad tech and fraud teams still ask for many hints, since together they are a rich device profile.
Where you see it
| Type | Example | Apps |
|---|---|---|
| developer | A download page asks for CPU type and OS version to give the right installer. | Zoom, Slack |
| games | A browser game asks for model and platform version to choose graphics settings that work on that device. | None named |
| ads | An ad exchange asks for full device details so bidders can target by model and OS version. | Google Ad Manager |
| security | A bank asks for the full browser version to check it against known fakes. | None named |
| analytics | A product team logs device model and OS version to prioritise fixes. | Sentry |
| media | A streaming site asks for platform version to pick the right DRM level. | Netflix |
| enterprise | An IT dashboard reads exact versions to find outdated work laptops. | None named |
Risks
- Rich device profile
- Many sites ask for everything
What the platform says
- Google: User-Agent Client Hints. Chrome says sites should ask for only the detail they need, instead of getting everything by default.
Good uses and abuse
Legitimate uses
- Serve correct 64-bit installer
- Debug crashes by exact version
- Windows 11 detection
Known abuse
- Precise device fingerprint without any prompt
- Targeting by exact model on Android
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 2 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 | 5 | Rough identifying entropy, when known |
A real example: LinkedIn
user_agent_data source is part of mainstream fingerprint libraries; LinkedIn's list is mostly legacy navigator.* fields (not confirmed for getHighEntropyValues).
History
- 2021-03, Chrome 89: getHighEntropyValues shipped
- 2021-05, Chrome 90: wow64 hint added
- 2022-10, Chrome 107: Becomes the only way to get OS minor version, arch, model after UA reduction
Related capabilities
Related
- Client Hint: platform version. Can tell your exact Windows or macOS version when it asks
- Client Hint: device model. Can see the model name of your Android phone or tablet when it asks
- Client Hint: form factors. Can tell if you use a desktop, phone, tablet, watch, or car screen
Sources
- Chrome developers: UA Client Hints
- MDN getHighEntropyValues
- WICG UA Client Hints
- CreepJS (abrahamjuliot)
How well checked: Checked against real behavior.