Skip to Content
Platform.Ontology

Client Hint: form factors

Device class list: Desktop, Mobile, Tablet, XR, Automotive, EInk, Watch.

Gets silentlyDevice detailsClient HintsWeb browsersWhen the page loadsWhile you use it

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

BrowserStatusFirst versionReleasedNote
ChromeSupported902021-04-13Approximate version; origin trial earlier
EdgeSupported902021-04-15None
FirefoxNot supportedNot availableNot listedNone
SafariNot supportedNot availableNot listedNone
Safari on iPhoneNot supportedNot availableNot listedNone
Chrome on AndroidSupported902021-04-13None
Samsung InternetSupported23.02023-10-18None

How a site asks for it

APIgetHighEntropyValues(['formFactors']); Sec-CH-UA-Form-Factors
Browser compat keysapi.NavigatorUAData.getHighEntropyValues
How access is grantednone
What the user seesNone
Needs a secure context (HTTPS)Yes
Needs a user gestureNo
How long it lastsread fresh on every page load; nothing stored
How to take it backnone needed (no grant)
Inside an iframeReadable from cross-origin iframes too (same values)

Typical flow

  1. Page script reads the value
  2. No prompt is shown

Data you get

Shape: object
How often: static per session

FieldTypeUnitRangePrecision
formFactorslistNoneAutomotive, 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

TypeExampleApps
automotiveA web app in a car's browser shows large buttons and voice prompts instead of tiny links.None named
ar-vrA WebXR site detects a headset and offers its 3D room instead of a flat page.None named
gamesA browser game offers touch buttons on tablets and keyboard hints on desktops.None named
mediaA streaming site serves a simple high-contrast layout to an e-ink reader with no video.None named
shoppingA web shop shows tablet layouts with bigger product photos and fewer columns.None named
accessibilityA 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

Good uses and abuse

Legitimate uses

  • Car and e-ink layouts

Known abuse

  • Device cohorting

Scores

ScoreValueMeaning
Sensitivity1 of 5How revealing the data is
Utility3 of 5How useful it is to honest apps
Friction0 of 5How much the user has to do
Fingerprint bits1.5Rough identifying entropy, when known

History

  • 2024-05, Chrome 125: Form-Factors hint reached stable (approximate)

Sources

How well checked: Inferred from related behavior.

On this page