User-agent reduction explained
User-agent reduction is Chrome's effort to freeze and trim the legacy user-agent string, removing fine-grained OS and full-version detail. The information is not gone; it moves to opt-in User-Agent Client Hints. This page explains what reduction changed and how detection should migrate to Client Hints.
What reduction changed
User-agent reduction is Chrome's program to reduce the entropy in the legacy user-agent string. It freezes parts of the string and coarsens others — for example trimming the minor version to zeros and reducing fine-grained OS detail — so the raw UA exposes less passively identifiable information.
The goal is twofold: cut passive fingerprinting surface, and reduce the brittleness of sites that sniff the UA for exact versions. The reduction has been rolled out progressively rather than all at once.
- Freezes and coarsens parts of the legacy UA string
- Trims fine-grained version and OS detail
- Aims to reduce passive fingerprinting and UA-sniffing brittleness
Where the detail went: Client Hints
The detail removed from the raw string did not vanish — it moved to User-Agent Client Hints, the Sec-CH-UA family of headers, which a site requests when it has a genuine need. This shifts browser information from an always-broadcast string to an opt-in, request-based model.
The migration path is clear: stop depending on the raw UA for precise version or platform data, match on stable patterns for coarse classification, and use Client Hints where fine detail is actually required. See the Client Hints entry for the request model.
How it appears in analytics and logs
Frozen or coarsened detail in a Chrome user agent is the intended result of UA reduction, not a fault. Precise version or platform data is meant to come from Client Hints, not the raw string.
Diagnostic use case
Understand exactly what UA reduction froze or removed, so detection and analytics migrate to Client Hints rather than depending on detail the raw string no longer carries.
What WebmasterID can help detect
WebmasterID classifies clients from server-side signals robust to UA reduction, so a frozen or trimmed user-agent string does not degrade browser or automation categorisation.
Common mistakes
- Expecting the raw user agent to keep exposing full version and OS detail.
- Treating frozen or zeroed version components as a bug rather than reduction.
- Failing to migrate version-dependent logic to Client Hints.
Privacy and accuracy notes
UA reduction was motivated partly by reducing passive fingerprinting from the always-broadcast user-agent string. WebmasterID stores coarse categories, not fingerprintable raw detail from real visitors.
Related pages
- User-Agent Client Hints
User-Agent Client Hints are HTTP headers (the Sec-CH-UA family) that let a site request specific browser, platform, and version detail rather than reading it all from one passive string. They underpin UA reduction: the raw user agent is shrinking, and finer detail moves to opt-in hints. This page explains the model.
- Chrome user agent and its quirks
Chrome's user-agent string is full of historical artefacts: it claims AppleWebKit and Safari for compatibility even though Chrome uses the Blink engine. Google has also reduced the detail Chrome exposes in the UA, moving fine-grained information into User-Agent Client Hints. This page explains the pattern and the quirks.
- Privacy-first analytics
Analytics that rely on coarse categories, not fingerprintable detail.
Sources and verification notes
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.