What the user-agent string shows now#
Chrome's user-agent reduction freezes the minor, build and patch numbers at zero and keeps only the major version. We loaded a page in Playwright's Chromium build, Chrome for Testing 153.0.8010.12, and read both sources:
navigator.userAgent ... HeadlessChrome/153.0.0.0 Safari/537.36
fullVersionList (Chromium) 153.0.8010.12
The same reduction applies to the User-Agent request header. A bug fixed in 153.0.8010.40 and present in 153.0.8010.12 is invisible in both. Chrome: User-Agent reduction
Where the full version still is#
| Source | How | Notes |
|---|---|---|
chrome://version | Type it in the address bar | Full version, channel, OS, the profile path and command-line flags. Also shows Variations, Chrome's field-trial state. |
| Settings > About Chrome | Menu | Full version and whether an update is waiting for a restart |
| User-Agent Client Hints | navigator.userAgentData.getHighEntropyValues(['fullVersionList', 'platformVersion']) in the Console | Chromium-based browsers only. Secure contexts only. |
edge://version, brave://version and similar | Address bar | Chromium-based browsers keep a version page under their own scheme |
Firefox: about:support | Address bar | Version, build ID and the update channel |
| Safari: Safari > About Safari | Menu | Safari version and WebKit build |
MDN: NavigatorUAData.getHighEntropyValues()
Ask for chrome://version as a pasted block. It answers several follow-up questions at once: the exact build, the channel (Stable, Beta, Dev, Canary), the OS build and any command-line flags an IT policy or a launcher added.
An update waiting for a restart#
Chrome downloads updates in the background and applies them on restart. A browser that has been open for weeks can be several versions behind what is installed. About Chrome shows a Relaunch button when that is the case. Record the version that is running, which is the one chrome://version reports, not the one installed.
Collect it in your own app#
If your application collects bug reports, capture the full version automatically, from the source that has it:
const ua = navigator.userAgentData;
const details = ua
? await ua.getHighEntropyValues(['fullVersionList', 'platform', 'platformVersion', 'mobile'])
: { userAgent: navigator.userAgent }; // Firefox and Safari: the UA string is the best available
Send both, and label which is which. A server-side log of the User-Agent header alone has only the major version for Chrome.
Worked example: a fix that had not reached one user#
This example is fictional. A team fixed a CSS rendering workaround for a Chrome bug that Chrome itself fixed in a patch release. A user still sees the broken layout. Their report says "Chrome 153".
The developer asks for chrome://version. It shows 153.0.8010.12 and a Relaunch button had been waiting in About Chrome for nine days. The Chrome fix shipped in a later 153 patch. Both the user-agent string and the developer's own 153 looked the same; the full version separated them. The team kept their workaround for one more release and added the full version to their bug report form.
Questions#
Does Firefox reduce its user-agent string too?
Firefox's user-agent string carries the major version, such as Firefox/140.0, and does not implement User-Agent Client Hints. about:support gives the build ID.
What are Variations in chrome://version?
Chrome enables some features for a share of users as field trials. Two copies of the same Chrome version can run with different features on. The Variations list is the evidence. A bug that only some users of one version see may be a trial.
Is the full version enough to reproduce?
It tells the maintainer which build to install. Install the reporter's exact Chrome version covers getting that build.
Return to reproducing what someone else saw for the other layers a replay needs.