a build branded Google Chrome lists the Google voices Google's build ships
A build claiming the Google Chrome brand on Windows or macOS lists at least one Google network voice. N/A for Chromium-branded and other vendors' builds, non-Chromium engines, Linux, and when no voice list arrives at all (severity: warn).
What a detector infers
Google's branded Chrome ships a component extension that registers a set of remote speech voices — "Google US English", "Google Deutsch", "Google 日本語" and so on, all with localService false — beside the operating system's own voices. Measured on Chrome 153 on Windows 11: 25 voices, 19 of them Google's, headed or headless, on a fresh profile.
The same Chrome launched by an automation framework lists only the 6 Windows voices, because the framework's default --disable-component-extensions-with-background-pages switches the extension off. Edge lists its own online voices and no Google ones, and a bare Chromium lists only the OS voices — but neither claims the Google Chrome brand, so both are exempt.
A build that DOES claim the brand while listing no Google voice is describing a Chrome that does not exist, or a real Chrome launched with an automation framework's defaults. Same brand gate as the Widevine and licensed-codec rows: keyed on the UA-CH brand the build asserts about itself, not on the UA string.
How to resolve it
Run Google's build without the switch that disables its component extensions (in Playwright, add --disable-component-extensions-with-background-pages to ignoreDefaultArgs), or drop the Google Chrome brand and report as Chromium, which is what a de-Googled build honestly is.
Nearby checks in Navigator identity
- the host voice roster represents the language the browser claims
locale-vs-voice-coherenceThe voice roster is installed at the operating-system level and the language preference is set in the browser, so the two are genuinely… - eval.toString().length matches the engine (V8 = 33)
etslThe string a JS engine returns for a native function's source is an implementation detail, and its length differs per engine… - navigator.productSub === 20030107 (Chromium)
product-subnavigator.productSub is a frozen legacy constant, not a live value: Chrome, Safari and Opera return "20030107" while Firefox returns… - a build branded Google Chrome carries Google's Widevine CDM
widevine-vs-chrome-brandingThe ClearKey row in this suite deliberately refuses to score Widevine, and for the question it asked that is correct: "does a… - a build branded Google Chrome decodes the codecs Google licenses
licensed-codecs-vs-chrome-brandingH.264 and AAC are patent-encumbered. Google licenses them for its branded Chrome; a Chromium compiled without the proprietary_codecs flag… - a Firefox user-agent reports the Gecko productSub constant 20100101
gecko-productsub-hardcodenavigator.productSub is a constant compiled into the engine, and the two families disagree: every Gecko build hardcodes it to "20100101"… - no other engine's properties exist on this one, even holding undefined
legacy-engine-props-absentThere is a difference between a property that returns undefined and a property that does not exist, and only one of them is what a real… - navigator.deviceMemory is a power-of-two spec value
device-memory-boundsnavigator.deviceMemory does not report actual RAM — the spec requires the UA to quantise it to a coarse power-of-two rung before exposing…
Clearcote is a browser built for fingerprint coherence
It is a Chromium fork, maintained by the same people who wrote this reference. It ships as a compiled browser rather than as a stealth script injected into someone else's — which is a description of how it is built, and is not an argument about how it behaves on this check.
This audit takes no position on how Clearcote scores on Navigator identity checks, on this one, or anywhere else. It has no baseline corpus of other people's fingerprints to rank you against and no vendor scoreboard — nearly every check is self-referential, asking one browser the same question through two independent APIs and reporting whether both answers can be true at once. It runs identically on any browser, including ours. Run it on yours and read the result yourself.
See the other checks in Navigator identity — the family google-voices-vs-chrome-branding belongs to.