Client Hints (Accept-CH, Critical-CH)
Servers ask the browser for extra device details through request headers.
In one line
Can ask your browser for extra device details such as model, OS version and screen
Servers ask the browser for extra device details through request headers.
A server sends Accept-CH to receive hints such as Sec-CH-UA-Platform-Version, Arch, Bitness, Model, Device-Memory, DPR and Viewport-Width. Critical-CH forces a retry with them. Chromium only; Firefox and Safari do not send them.
What it can and can't do
What the user does: Nothing. It happens when a page loads and the site asks for hints
It can
- Ask for details such as platform version, device model, memory and screen width
- Tailor images and pages to your device
- Make your browser retry the request with those details on sites that require them
It cannot
- Get these details from Firefox or Safari, which do not send them
- Get details the browser does not offer; it sends only what the site asks for
- Know who you are from them alone
How it differs between platforms: Only Chromium browsers (Chrome, Edge, Samsung Internet) send them. Firefox and Safari do not.
Browser support
| Browser | Status | First version | Released | Note |
|---|---|---|---|---|
| Chrome | Supported | 46 | 2015-10-13 | None |
| Edge | Supported | 79 | 2020-01-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 | 46 | 2015-10-14 | None |
| Samsung Internet | Supported | 5.0 | 2016-12-15 | None |
How a site asks for it
| API | Accept-CH and Critical-CH response headers; Sec-CH-* request headers |
| Browser compat keys | http.headers.Accept-CH |
| How access is granted | none |
| What the user sees | Not listed |
| Needs a secure context (HTTPS) | No |
| Needs a user gesture | No |
| How long it lasts | Not listed |
| How to take it back | Not listed |
| Inside an iframe | Not listed |
Typical flow
- Server returns Accept-CH
- Browser adds hints on later requests
- Critical-CH triggers a same-load retry
Data you get
What comes back: One header per hint
Shape: list
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
Sec-CH-UA-Model | string | None | device model or empty | exact (mobile) |
Sec-CH-UA-Platform-Version | string | None | OS version | exact |
Technical limits
- High entropy hints only sent after server opt-in and to first party by default
- Third parties need Permissions-Policy delegation
The story
What it is
The server can ask your browser for extra details about your device with each request.
For you
You never see it. When a site asks, your browser quietly sends things like your device model, system version, screen density and memory size. The site then sends the right image size or layout.
For makers
Makers use hints to send the right images, files and layout for each device, which makes pages faster. Fraud and ad systems also use the detail as a fingerprint input, so what a server asks for matters.
Where you see it
| Type | Example | Apps |
|---|---|---|
| games | A browser game site picks the right graphics quality and download size for a weak phone or a strong gaming laptop. | Poki, CrazyGames |
| games | A cloud gaming site reads device and screen details to choose the stream resolution and controls. | GeForce NOW, Xbox Cloud Gaming |
| media | A streaming site picks video quality and app layout for your TV, phone or laptop. | Netflix, YouTube |
| shopping | A store sends smaller images to a low memory phone so the page loads fast. | Amazon |
| ads | An ad system reads device model and system version to match ads to phone models. | None named |
| security | A fraud tool checks that hints agree with the browser claim, and a mismatch reveals a spoofed device. | None named |
| analytics | A product team counts visitors by exact device model and system version. | Google Analytics |
Risks
- Reveals device model
- Used for fingerprinting
What the platform says
- Google Chrome: User-Agent Client Hints. Chrome pitches it as a more private, structured replacement for the old user agent string, where sites ask for the details they need.
Good uses and abuse
Legitimate uses
- Responsive delivery, correct downloads
Known abuse
- Gets precise OS and device model without JS
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 | 3 | Rough identifying entropy, when known |
History
- 2021-03, Chrome 89: UA Client Hints on by default
- 2022-03, Chrome 100: Critical-CH shipped
- 2023-06, Chrome 110: User-Agent reduction completes on Android and desktop
Related capabilities
Related
- Sec-CH-UA low entropy hints and reduced User-Agent. Can see your browser brand, major version, phone or computer type, and system in Chromium browsers
- Network Information API and Save-Data. Can see a rough guess of your connection type, speed and data saver setting
Sources
How well checked: Based on official documentation.