Client Hint: form factors
Device class list: Desktop, Mobile, Tablet, XR, Automotive, EInk, Watch.
In one line
Can tell if you use a desktop, phone, tablet, watch, or car screen
Device class list: Desktop, Mobile, Tablet, XR, Automotive, EInk, Watch.
Newer replacement for guessing from the mobile flag and screen size. Lets a site serve car, e-reader, VR or tablet layouts. Some users report more than one factor.
What it can and can't do
What the user does: Nothing. The site asks and Chromium answers without a prompt
It can
- See device types such as Desktop, Mobile, Tablet, Watch, XR, or Automotive
- Show a layout that fits an e-reader, car, or headset
- Fit the page to your device without guessing from screen size
- Learn about more than one type if your device reports it
It cannot
- Work in Firefox, Safari, or on iPhone
- See your exact device model
- Get an answer until the site asks for it
- Be sure; some devices report oddly
How it differs between platforms: Chromium browsers answer. Firefox and Safari do not.
Browser support
| Browser | Status | First version | Released | Note |
|---|---|---|---|---|
| Chrome | Supported | 90 | 2021-04-13 | Approximate version; origin trial earlier |
| 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 | getHighEntropyValues(['formFactors']); Sec-CH-UA-Form-Factors |
| 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 |
|---|---|---|---|---|
formFactors | list | None | Automotive, Desktop, EInk, Mobile, Tablet, Watch, XR (combinable) | Not listed |
Technical limits
- Chromium only
- High entropy, so must be requested
The story
What it is
Tells a site what kind of device you use: desktop, phone, tablet, headset, car, e-reader or watch.
For you
You never see the question. What you see is a page that fits your device: a big touch layout on a car screen, or a simpler page on an e-reader. It helps pages look right without guessing from screen size.
For makers
The old method guessed from screen size and a mobile flag. A direct list of device types lets sites serve the right layout and the right controls. Some devices report more than one type, which also makes a handy signal.
Where you see it
| Type | Example | Apps |
|---|---|---|
| automotive | A web app in a car's browser shows large buttons and voice prompts instead of tiny links. | None named |
| ar-vr | A WebXR site detects a headset and offers its 3D room instead of a flat page. | None named |
| games | A browser game offers touch buttons on tablets and keyboard hints on desktops. | None named |
| media | A streaming site serves a simple high-contrast layout to an e-ink reader with no video. | None named |
| shopping | A web shop shows tablet layouts with bigger product photos and fewer columns. | None named |
| accessibility | A news site offers a text-first page on slow e-readers. | None named |
Risks
- Hardware group clue
- Multiple answers give a more unique ID
What the platform says
- Google: User-Agent Client Hints. Chrome offers sites a standard way to ask about the device when they need it.
Good uses and abuse
Legitimate uses
- Car and e-ink layouts
Known abuse
- Device cohorting
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 1 of 5 | How revealing the data is |
| Utility | 3 of 5 | How useful it is to honest apps |
| Friction | 0 of 5 | How much the user has to do |
| Fingerprint bits | 1.5 | Rough identifying entropy, when known |
History
- 2024-05, Chrome 125: Form-Factors hint reached stable (approximate)
Related capabilities
Related
- UA Client Hints, high entropy. Can see detailed device and browser versions, but only if the site asks
Sources
How well checked: Inferred from related behavior.