Skip to content
Chrome 157 → 158

Chrome 158: what changed for fingerprinting and automation

Chrome 158 changes what a page can observe in 21 places, measured on the stable builds of both versions. A server sees the same TLS handshake, HTTP/2 settings and header order as on 157 in a fresh profile; only the version strings and the GREASE brand change, unless the page uses an XSL stylesheet, which 158 no longer fetches. Scripts see XSLTProcessor gone, the Web Install API, unload handlers off by default, seven media-state pseudo-classes and several V8 changes.

Pim
Pim · Clearcote Research
· Updated
Stable release
November 17, 2026
Measured on (Linux x64)
157.0.8103.50 → 158.0.8127.36
Source read at
157.0.8103.77 → 158.0.8127.36
V8
15.7.112.40 → 15.8.62.31

Key takeaways

  • XSLT is off by default: XSLTProcessor is gone from window, and an XML document with an xml-stylesheet processing instruction is shown untransformed, without fetching the stylesheet.
  • New on desktop: navigator.install(), the <install> element (HTMLInstallElement) and the web-app-installation permission, which navigator.permissions.query() now answers with prompt.
  • unload handlers stop running by default: document.featurePolicy.allowsFeature('unload') reads false, and focus-without-user-activation joins the feature list.
  • New CSS a stylesheet test sees at once: :playing, :paused and five more media-state pseudo-classes, ::highlight(*) and flow-start. V8 15.8 fills in error-message arguments and adds two early errors.
  • A server sees the same JA4, JA3N and HTTP/2 fingerprint as on 152 to 157. The new GREASE brand is Not.A/Brand version 24, listed second, between Chromium and Google Chrome.

Every check, both versions, and your browser

29 one-line checks across 21 changes. The strip shows where they are; the table shows what each returns on Chrome 157 and Chrome 158. Run them in this browser to see which version its engine matches.

Chrome 157 → Chrome 158 · 29 checks

Run the checks to see which Chrome version this browser's engine matches.

Where the changes are. Select a surface to filter the rows.

CheckChrome 157Chrome 158This browser
Client Hints
New GREASE brand and brand order in User-Agent Client Hintsnavigator.userAgentData.brands.map((b) => `${b.brand};v=${b.version}`).join(', ')"Not-A.Brand;v=99, Google Chrome;v=157, Chromium;v=157""Chromium;v=158, Not.A/Brand;v=24, Google Chrome;v=158"–
JavaScript and DOM
XSLT is off by default: XSLTProcessor is gone and XSL stylesheets are not appliedtypeof XSLTProcessor"function""undefined"–
Web Install API and the <install> element ship on desktoptypeof HTMLInstallElement"undefined""function"n/a
Web Install API and the <install> element ship on desktoptypeof navigator.install"undefined""function"n/a
Web Install API and the <install> element ship on desktop'oninstallresult' in windowfalsetruen/a
Two new permissions-policy features: focus-without-user-activation and web-app-installationdocument.featurePolicy.features().includes('focus-without-user-activation')falsetrue–
Two new permissions-policy features: focus-without-user-activation and web-app-installationdocument.featurePolicy.features().includes('web-app-installation')falsetruen/a
Long Animation Frame entries report style and layout time'styleDuration' in PerformanceLongAnimationFrameTiming.prototypefalsetrue–
Long Animation Frame entries report style and layout time'forcedLayoutDuration' in PerformanceScriptTiming.prototypefalsetrue–
Resource timing names the service-worker router source'workerMatchedRouterSource' in PerformanceResourceTiming.prototypefalsetrue–
Resource timing names the service-worker router source'workerFinalRouterSource' in PerformanceResourceTiming.prototypefalsetrue–
SVG textPath side attribute'side' in SVGTextPathElement.prototypefalsetrue–
WebTransport draining and anticipated concurrent incoming streams'draining' in WebTransport.prototypefalsetrue–
WebTransport draining and anticipated concurrent incoming streams'anticipatedConcurrentIncomingBidirectionalStreams' in WebTransport.prototypefalsetrue–
V8 error messages fill in their arguments: Atomics, Intl and Object.fromEntries(() => { try { Atomics.load(new Int32Array(4), 10); } catch (e) { return e.message; } })()"Invalid atomic access index""Invalid atomic access index: 10"–
V8 error messages fill in their arguments: Atomics, Intl and Object.fromEntries(() => { try { Intl.NumberFormat.prototype.resolvedOptions.call({}); } catch (e) { return e.message; } })()"Method UnwrapNumberFormat called on incompatible receiver undefined""Method UnwrapNumberFormat called on incompatible receiver #<Object>"–
V8 error messages fill in their arguments: Atomics, Intl and Object.fromEntries(() => { try { Object.fromEntries(null); } catch (e) { return e.message; } })()"undefined is not iterable""null is not iterable"–
Assigning to a call in strict code is an early SyntaxError(() => { try { new Function('"use strict"; if (0) f() = 1;'); return 'ok'; } catch (e) { return e.name; } })()"ok""SyntaxError"–
RegExp: \p{ASCII} with the v and i flags matches the Kelvin sign and the long snew RegExp('\\p{ASCII}', 'vi').test('K')falsetrue–
Parsing and rendering
unload handlers stop running by default: the unload permissions policy defaults to nonedocument.featurePolicy.allowsFeature('unload')truefalsen/a
NodeIterator moves its reference correctly when the reference subtree is removed(() => { const r = document.createElement('div'); r.innerHTML = '<a></a><b><i></i></b>'; const it = document.createNodeIterator(r); it.nextNode(); it.nextNode(); it.nextNode(); it.previousNode(); r.lastChild.remove(); return it.referenceNode.nodeName + ',' + it.pointerBeforeReferenceNode; })()"B,true""A,false"–
elementsFromPoint() includes inline ancestors of positioned inline children(() => { const d = document.body.appendChild(document.createElement('div')); d.style.cssText = 'position:fixed;left:0;top:0;z-index:2147483647'; d.innerHTML = '<span id="cc158a"><span style="position:relative">Text</span></span>'; const r = d.querySelector('[style]').getBoundingClientRect(); const hit = document.elementsFromPoint(r.left + 1, r.top + r.height / 2).some((e) => e.id === 'cc158a'); d.remove(); return hit; })()falsetrue–
CSS
CSS media-state pseudo-classes: :playing, :paused, :seeking, :buffering, :stalled, :muted, :volume-lockedCSS.supports('selector(:playing)')falsetrue–
CSS ::highlight(*) matches every custom highlightCSS.supports('selector(::highlight(*))')falsetrue–
CSS flow-start and flow-end alignment keywordsCSS.supports('align-self', 'flow-start')falsetrue–
Web Animations: an easing on a keyframe without the property no longer applies to it(() => { const e = document.body.appendChild(document.createElement('div')); e.style.left = '100px'; const a = e.animate([{ easing: 'steps(2, start)' }, { left: '200px' }], 1e3); a.pause(); a.currentTime = 0; const v = getComputedStyle(e).left; e.remove(); return v; })()"150px""100px"–
Media and GPU
OfflineAudioContext gains close() and incremental rendering'close' in OfflineAudioContext.prototypefalsetrue–
WebGL 2 exposes WEBGL_shader_pixel_local_storagedocument.createElement('canvas').getContext('webgl2').getSupportedExtensions().includes('WEBGL_shader_pixel_local_storage')falsetruen/a
Intl and time zones
Intl.NumberFormat rejects decimal strings and BigInts longer than 999,000 characters(() => { try { return new Intl.NumberFormat('en').format('1.' + '0'.repeat(1e6)); } catch (e) { return e.name; } })()"1""TypeError"–

A tinted cell differs from the version before it. Values are as the DevTools console prints them. Checks that need a debugger attached are not run live.

TLS, HTTP/2 and request headers in Chrome 158

TLS ClientHello
Identical to Chrome 157 in a fresh profile: JA4 t13d1517h2_8daaf6152771_cb7bf5808d99 and JA3N bd4930bd9b000ee684830e44bab76fdf, measured three times on each build against two independent TLS echo services. In the source the only TLS change removes the kill switch for signature-algorithm GREASE, which was already on in 157. The root store goes to version 43 by dropping one root that has no trust-anchor ID, so the advertised list is unchanged.
HTTP/2
Identical to Chrome 157: Akamai fingerprint 1:65536;2:0;4:6291456;6:262144|15663105|0|m,a,s,p, the same HEADERS priority and pseudo-header order m,a,s,p.
Request headers
The same names in the same order on all 21 request types we measured, and the same values apart from the version: User-Agent, Sec-CH-UA (new GREASE brand, second), Sec-CH-UA-Full-Version and Sec-CH-UA-Full-Version-List. One request a server can miss: a document with an XSL stylesheet no longer requests the stylesheet (read in the source, not measured).

Compare your own browser's handshake with these in the JA4 fingerprint checker.

Chrome 158 User-Agent strings and Client Hints

PlatformUser-Agent
WindowsMozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/158.0.0.0 Safari/537.36
macOSMozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/158.0.0.0 Safari/537.36
LinuxMozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/158.0.0.0 Safari/537.36
AndroidMozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/158.0.0.0 Mobile Safari/537.36
Headless (Linux)Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) HeadlessChrome/158.0.0.0 Safari/537.36

The Linux and headless strings were measured on 158.0.8127.36; the string does not change within a major. The others follow Chromium's reduced User-Agent format (user_agent_utils.cc): only the major version is real, the rest is frozen, and the platform part is fixed per operating system.

Sec-CH-UA (the low-entropy brand list sent with every request):

"Chromium";v="158", "Not.A/Brand";v="24", "Google Chrome";v="158"

The Chrome user agent page has these for the current version and every recent one; what is my user agent shows your own.

User-Agent and Client Hints

high impactMeasured on both builds

New GREASE brand and brand order in User-Agent Client Hints

The fake GREASE brand and the order of the brand list are computed from the major version. On 158 the brand is Not.A/Brand version 24, listed second, between Chromium (now first) and Google Chrome. Sent on every request in Sec-CH-UA and returned by navigator.userAgentData.brands in windows and workers.

navigator.userAgentData.brands.map((b) => `${b.brand};v=${b.version}`).join(', ')
Chrome 157
"Not-A.Brand;v=99, Google Chrome;v=157, Chromium;v=157"
Chrome 158
"Chromium;v=158, Not.A/Brand;v=24, Google Chrome;v=158"

Why it matters: A version number changed by hand, with the previous brand list left in place, produces a combination no real Chrome sends. The algorithm is unchanged; only its input is.

JavaScript and Web APIs

high impactMeasured on both builds

Web Install API and the <install> element ship on desktop

navigator.install() (secure contexts), the HTMLInstallElement interface behind <install>, the InstallResultEvent interface and an oninstallresult event handler on window, Document, HTMLElement, SVGElement and MathMLElement are enabled on desktop. They stay off on Android, iOS and Fuchsia. The web-app-installation permissions-policy feature and permission name come with them.

typeof HTMLInstallElement
Chrome 157
"undefined"
Chrome 158
"function"
  • typeof navigator.install"undefined"→ "function"
  • 'oninstallresult' in windowfalse→ true

Why it matters: Two new interfaces and a new event-handler property on every element prototype and on the global object: they change the global property list and the property counts of common prototypes. Desktop only, so the live column skips it.

medium impactMeasured on both builds

Two new permissions-policy features: focus-without-user-activation and web-app-installation

document.featurePolicy.features() gains focus-without-user-activation on every platform (an embedder can now deny programmatic focus from a frame that has no user activation) and web-app-installation on desktop. They are the only changes to Chrome's stable permissions-policy feature list.

document.featurePolicy.features().includes('focus-without-user-activation')
Chrome 157
false
Chrome 158
true
  • document.featurePolicy.features().includes('web-app-installation')false→ true

Why it matters: The feature list is an ordered array that scripts hash as a whole; two entries are inserted in alphabetical position, so both the length and the order change.

medium impactMeasured on both builds

V8 error messages fill in their arguments: Atomics, Intl and Object.fromEntries

V8 15.8 removes the fallback that printed undefined for a missing message argument and passes the real one. Atomics index errors now include the index; Intl.NumberFormat methods called on the wrong object name the receiver instead of undefined; Object.fromEntries(null) says null instead of undefined. Other affected templates: DataView length, the Uint8Array base64 and hex methods, and the ToIndex error Invalid value %: not (convertible to) a safe integer.

(() => { try { Atomics.load(new Int32Array(4), 10); } catch (e) { return e.message; } })()
Chrome 157
"Invalid atomic access index"
Chrome 158
"Invalid atomic access index: 10"
  • (() => { try { Intl.NumberFormat.prototype.resolvedOptions.call({}); } catch (e) { return e.message; } })()"Method UnwrapNumberFormat called on incompatible receiver undefined"→ "Method UnwrapNumberFormat called on incompatible receiver #<Object>"
  • (() => { try { Object.fromEntries(null); } catch (e) { return e.message; } })()"undefined is not iterable"→ "null is not iterable"

Why it matters: Error message text is a common engine-version probe: deterministic, synchronous, the same in every realm and on every platform.

low impactMeasured on both builds

Long Animation Frame entries report style and layout time

PerformanceLongAnimationFrameTiming gains styleDuration and layoutDuration, and PerformanceScriptTiming gains forcedStyleDuration and forcedLayoutDuration. They also appear in each entry's toJSON().

'styleDuration' in PerformanceLongAnimationFrameTiming.prototype
Chrome 157
false
Chrome 158
true
  • 'forcedLayoutDuration' in PerformanceScriptTiming.prototypefalse→ true

Why it matters: Four new getters on performance-timing prototypes; serialised entries grow by those keys.

low impactMeasured on both builds

Resource timing names the service-worker router source

PerformanceResourceTiming (and so PerformanceNavigationTiming) gains workerMatchedRouterSource and workerFinalRouterSource, the spec names for the existing workerMatchedSourceType and workerFinalSourceType, which stay. Both read as an empty string unless a service worker's static router handled the request, and both appear in each entry's toJSON(). This one landed late in the branch: the 158 beta (158.0.8127.18) did not have it, stable 158.0.8127.36 does.

'workerMatchedRouterSource' in PerformanceResourceTiming.prototype
Chrome 157
false
Chrome 158
true
  • 'workerFinalRouterSource' in PerformanceResourceTiming.prototypefalse→ true

Why it matters: Two new getters on a performance-timing prototype; a serialised navigation or resource entry grows by those two keys.

low impactMeasured on both builds

WebTransport draining and anticipated concurrent incoming streams

WebTransport gains a draining promise and the anticipatedConcurrentIncomingBidirectionalStreams and anticipatedConcurrentIncomingUnidirectionalStreams attributes, in windows, dedicated workers and shared workers (secure contexts).

'draining' in WebTransport.prototype
Chrome 157
false
Chrome 158
true
  • 'anticipatedConcurrentIncomingBidirectionalStreams' in WebTransport.prototypefalse→ true

Why it matters: New members on a prototype that worker-side scripts can also read, so window and worker listings both change.

low impactMeasured on both builds

Assigning to a call in strict code is an early SyntaxError

f() = 1, f()++ and for (f() of ...) stay a runtime ReferenceError in sloppy code for web compatibility, but in strict code V8 now rejects them when the script is parsed, as the specification requires. A strict script that merely contains such a line, even in a branch that never runs, no longer compiles.

(() => { try { new Function('"use strict"; if (0) f() = 1;'); return 'ok'; } catch (e) { return e.name; } })()
Chrome 157
"ok"
Chrome 158
"SyntaxError"

Why it matters: A parse-time difference: a script either compiles or not, before any line of it runs.

low impactMeasured on both builds

RegExp: \p{ASCII} with the v and i flags matches the Kelvin sign and the long s

In /vi mode V8 now closes \p{ASCII} over simple case folding, so U+212A KELVIN SIGN (folds to k) and U+017F LATIN SMALL LETTER LONG S (folds to s) match it, and the complement \P{ASCII} no longer does.

new RegExp('\\p{ASCII}', 'vi').test('K')
Chrome 157
false
Chrome 158
true

Why it matters: A one-line, deterministic engine probe.

Removed or deprecated

high impactMeasured on both builds

XSLT is off by default: XSLTProcessor is gone and XSL stylesheets are not applied

The XSLT runtime feature loses its stable status, so its base feature is off by default. XSLTProcessor disappears from window, the only interface removed from Chrome's stable interface listing between 157 and 158. An XML document with <?xml-stylesheet type="text/xsl" href="..."?> is no longer transformed, and the stylesheet is not requested: the processing instruction is dropped before its href is read, with the console message "XSLTProcessor and XSLT Processing Instructions have been removed in this browser". XSLT can still be turned back on per site by the deprecation trial and per device by enterprise policy.

typeof XSLTProcessor
Chrome 157
"function"
Chrome 158
"undefined"

Why it matters: A one-word check that separates 157 from 158 on every platform, with no permission and no page setup. A server that serves XML with an XSL stylesheet also sees the difference: 157 fetches the .xsl file, 158 does not. Pages that still use XSLT behave differently, and checks written for earlier versions that call new XSLTProcessor() now throw.

Parsing and rendering behaviour

high impactMeasured on both builds

unload handlers stop running by default: the unload permissions policy defaults to none

DeprecateUnload and DeprecateUnloadByBucket are on by default with a rollout of 100 %, so on every http and https page the unload permissions-policy feature defaults to none. unload event listeners are no longer called (pagehide, visibilitychange and beforeunload are unaffected). A page or frame can still opt back in with Permissions-Policy: unload=(self).

document.featurePolicy.allowsFeature('unload')
Chrome 157
true
Chrome 158
false

Why it matters: Changes what a page can observe at navigation and what a server receives: beacons and requests sent from unload handlers stop arriving. The Chromium commit says the server-side rollout was about to reach 100 % on stable, so many 157 profiles already behave like 158; the live column skips it.

low impactMeasured on both builds

NodeIterator moves its reference correctly when the reference subtree is removed

When the pointer is before the reference node and the removed subtree has children but no following node inside the root, 157 left the reference on the removed node. 158 follows the DOM specification and moves it to the preceding node with the pointer after it.

(() => { const r = document.createElement('div'); r.innerHTML = '<a></a><b><i></i></b>'; const it = document.createNodeIterator(r); it.nextNode(); it.nextNode(); it.nextNode(); it.previousNode(); r.lastChild.remove(); return it.referenceNode.nodeName + ',' + it.pointerBeforeReferenceNode; })()
Chrome 157
"B,true"
Chrome 158
"A,false"

Why it matters: A pure DOM computation with no layout, so it is the same on every platform.

low impactMeasured on both builds

elementsFromPoint() includes inline ancestors of positioned inline children

For <span id=a><span style="position:relative">Text</span></span>, document.elementsFromPoint() on the text now lists #a as well as the inner span, as WebKit and CSSOM View do. Single-point hit tests and event targets are unchanged.

(() => { const d = document.body.appendChild(document.createElement('div')); d.style.cssText = 'position:fixed;left:0;top:0;z-index:2147483647'; d.innerHTML = '<span id="cc158a"><span style="position:relative">Text</span></span>'; const r = d.querySelector('[style]').getBoundingClientRect(); const hit = document.elementsFromPoint(r.left + 1, r.top + r.height / 2).some((e) => e.id === 'cc158a'); d.remove(); return hit; })()
Chrome 157
false
Chrome 158
true

Why it matters: List-based hit testing is used by scripts that inspect what is under a point; the list is one element longer here.

CSS

medium impactMeasured on both builds

CSS media-state pseudo-classes: :playing, :paused, :seeking, :buffering, :stalled, :muted, :volume-locked

Seven pseudo-classes that match <audio> and <video> by playback state are enabled. Selectors that use them parse on 158 and are dropped as invalid on 157.

CSS.supports('selector(:playing)')
Chrome 157
false
Chrome 158
true

Why it matters: A selector support test, synchronous and side-effect free, on every platform.

low impactMeasured on both builds

CSS flow-start and flow-end alignment keywords

flow-start and flow-end are accepted as self-alignment and default-alignment values (align-self, align-items, justify-self, justify-items), as aliases of flex-start and flex-end.

CSS.supports('align-self', 'flow-start')
Chrome 157
false
Chrome 158
true

Why it matters: A new keyword in a property every engine parses; support tests and the CSSOM see it.

low impactMeasured on both builds

Web Animations: an easing on a keyframe without the property no longer applies to it

Per the Web Animations specification, keyframes that do not set a property are dropped before that property's intervals are built, so the synthetic (neutral) keyframe at offset 0 now uses the default linear easing instead of the easing written on the offset-0 keyframe. This matches Firefox and Safari.

(() => { const e = document.body.appendChild(document.createElement('div')); e.style.left = '100px'; const a = e.animate([{ easing: 'steps(2, start)' }, { left: '200px' }], 1e3); a.pause(); a.currentTime = 0; const v = getComputedStyle(e).left; e.remove(); return v; })()
Chrome 157
"150px"
Chrome 158
"100px"

Why it matters: A computed style read with no timing dependence (the animation is paused at 0). The values are the ones Chromium's own tests asserted before and after the change.

Media and codecs

medium impactMeasured on both builds

OfflineAudioContext gains close() and incremental rendering

OfflineAudioContext.prototype.close() is exposed, and startRendering() gains an overload that takes a chunk size so the graph can be rendered incrementally.

'close' in OfflineAudioContext.prototype
Chrome 157
false
Chrome 158
true

Why it matters: OfflineAudioContext is the usual starting point of audio fingerprinting scripts; a new own method changes its prototype's property list.

WebGL and WebGPU

low impactMeasured on both builds

WebGL 2 exposes WEBGL_shader_pixel_local_storage

The WEBGL_shader_pixel_local_storage extension appears in getSupportedExtensions() of a WebGL 2 context: Chrome 157 offered it only with WebGL draft extensions enabled, Chrome 158 whenever the ANGLE backend supports it. Measured with the SwiftShader software renderer of a headless Linux build; on a real GPU it depends on the driver.

document.createElement('canvas').getContext('webgl2').getSupportedExtensions().includes('WEBGL_shader_pixel_local_storage')
Chrome 157
false
Chrome 158
true

Why it matters: The WebGL extension list is a classic fingerprint input, so it grows by one name where the GPU supports it. The live column skips it because the answer depends on the GPU.

Intl, time zones and locale

low impactMeasured on both builds

Intl.NumberFormat rejects decimal strings and BigInts longer than 999,000 characters

Before handing a decimal string or a BigInt to ICU, V8 now throws a TypeError (Internal error. Icu error.) when its string form is longer than 999,000 characters. 157 formats such input. A temporary limit until fixes land in ICU.

(() => { try { return new Intl.NumberFormat('en').format('1.' + '0'.repeat(1e6)); } catch (e) { return e.name; } })()
Chrome 157
"1"
Chrome 158
"TypeError"

Why it matters: Independent of locale and operating system; Chrome's ICU data is the same at both tags, so the difference is V8's own check.

What the docs claim that the source does not show

Release notes and Chrome Platform Status describe intent; the source at the release tag is what shipped. These entries differ, so a version check built on the docs alone would be wrong.

  • Chrome Platform Status (milestone 158, enabled by default): WebTransport reliability attributes (<code>WebTransport.reliability</code> and <code>WebTransport.supportsReliableOnly</code>).

    Not a 157-to-158 difference: the WebTransportReliability flag is already stable at 157.0.8103.77, and both members are in 157's stable interface listing.

  • Chrome Platform Status (milestone 158, enabled by default): object-fit and object-position apply to SVG documents in <code>&lt;object&gt;</code> and <code>&lt;embed&gt;</code>.

    The SVGEmbeddedAsReplacedElement flag that implements it is still experimental at 158.0.8127.36, so stable 158 keeps stretching embedded SVG documents as 157 does.

  • Chrome Platform Status (milestone 158): XSLT removal listed as a stepped rollout.

    In the source XSLT is simply off by default from 158: the XSLT flag has no status, so XSLTProcessor is not exposed and XSL processing instructions are ignored. It comes back only through the deprecation trial, the enterprise policy, or a server-side configuration.

  • Chrome Platform Status (milestone 158, enabled by default): Source Specific Multicast for the Direct Sockets API.

    Enabled in the source, but Direct Sockets are available only to Isolated Web Apps, so an ordinary web page sees no difference.

Reproduce these results

  1. 1. Get both versions

    Use Google Chrome's own Linux packages of the two exact versions. Google keeps every version in its package pool:

    bash
    curl -sSO https://dl.google.com/linux/chrome/deb/pool/main/g/google-chrome-stable/google-chrome-stable_157.0.8103.50-1_amd64.deb
    curl -sSO https://dl.google.com/linux/chrome/deb/pool/main/g/google-chrome-stable/google-chrome-stable_158.0.8127.36-1_amd64.deb
    for f in google-chrome-*.deb; do dpkg -x "$f" "${f%.deb}"; done
  2. 2. Start each one clean

    A new profile directory per run and no automation flags. A fresh profile has not applied Google's field-trial configuration yet, which is the state these values describe.

    bash
    ./google-chrome-stable_158.0.8127.36-1_amd64/opt/google/chrome/chrome --user-data-dir="$(mktemp -d)" --no-first-run https://example.com
  3. 3. Run the checks

    Press "Run the checks in this browser" at the top of this page, or paste the script below into the DevTools console on any https:// page. Some checks are asynchronous; the script awaits them.

  4. 4. Check the network side

    Open tls.peet.ws or tls.browserleaks.com in each version and compare the JA4 and HTTP/2 fingerprints and the request headers with the values above. They are the same on 157 and 158 in a fresh profile.

  5. 5. Find a change in the source yourself

    Blink's test expectations record the page-visible surface of each release; the runtime feature list records what is on by default:

    bash
    git diff 157.0.8103.77 158.0.8127.36 -- third_party/blink/web_tests/virtual/stable/webexposed/
    git diff 157.0.8103.77 158.0.8127.36 -- third_party/blink/renderer/platform/runtime_enabled_features.json5

The whole check list as one script

Paste it into the DevTools console on Chrome 157 and on Chrome 158: it prints every check on this page with the value your browser returns.

chrome-158-probe.js
// Chrome 157 vs 158: paste into the DevTools console on any https:// page and press Enter.
// Each line prints "<change>  <check> = <value>". Expected values: clearcotelabs.com/chrome-releases/158
(async () => {
  const checks = [
    ["grease-brand", () => navigator.userAgentData.brands.map((b) => `${b.brand};v=${b.version}`).join(', ')],
    ["xslt-removed", () => typeof XSLTProcessor],
    ["web-install", () => typeof HTMLInstallElement],
    ["web-install", () => typeof navigator.install],
    ["web-install", () => 'oninstallresult' in window],
    ["permissions-policy-features", () => document.featurePolicy.features().includes('focus-without-user-activation')],
    ["permissions-policy-features", () => document.featurePolicy.features().includes('web-app-installation')],
    ["unload-deprecated", () => document.featurePolicy.allowsFeature('unload')],
    ["css-media-element-pseudos", () => CSS.supports('selector(:playing)')],
    ["css-highlight-universal", () => CSS.supports('selector(::highlight(*))')],
    ["css-flow-start-end", () => CSS.supports('align-self', 'flow-start')],
    ["offline-audio-context-close", () => 'close' in OfflineAudioContext.prototype],
    ["loaf-style-layout-duration", () => 'styleDuration' in PerformanceLongAnimationFrameTiming.prototype],
    ["loaf-style-layout-duration", () => 'forcedLayoutDuration' in PerformanceScriptTiming.prototype],
    ["sw-router-source-timing", () => 'workerMatchedRouterSource' in PerformanceResourceTiming.prototype],
    ["sw-router-source-timing", () => 'workerFinalRouterSource' in PerformanceResourceTiming.prototype],
    ["svg-textpath-side", () => 'side' in SVGTextPathElement.prototype],
    ["webtransport-draining-streams", () => 'draining' in WebTransport.prototype],
    ["webtransport-draining-streams", () => 'anticipatedConcurrentIncomingBidirectionalStreams' in WebTransport.prototype],
    ["v8-error-message-arguments", () => (() => { try { Atomics.load(new Int32Array(4), 10); } catch (e) { return e.message; } })()],
    ["v8-error-message-arguments", () => (() => { try { Intl.NumberFormat.prototype.resolvedOptions.call({}); } catch (e) { return e.message; } })()],
    ["v8-error-message-arguments", () => (() => { try { Object.fromEntries(null); } catch (e) { return e.message; } })()],
    ["strict-call-assignment-early-error", () => (() => { try { new Function('"use strict"; if (0) f() = 1;'); return 'ok'; } catch (e) { return e.name; } })()],
    ["regexp-vi-ascii-casefold", () => new RegExp('\\p{ASCII}', 'vi').test('K')],
    ["intl-numberformat-long-input", () => (() => { try { return new Intl.NumberFormat('en').format('1.' + '0'.repeat(1e6)); } catch (e) { return e.name; } })()],
    ["nodeiterator-removal", () => (() => { const r = document.createElement('div'); r.innerHTML = '<a></a><b><i></i></b>'; const it = document.createNodeIterator(r); it.nextNode(); it.nextNode(); it.nextNode(); it.previousNode(); r.lastChild.remove(); return it.referenceNode.nodeName + ',' + it.pointerBeforeReferenceNode; })()],
    ["neutral-keyframe-easing", () => (() => { const e = document.body.appendChild(document.createElement('div')); e.style.left = '100px'; const a = e.animate([{ easing: 'steps(2, start)' }, { left: '200px' }], 1e3); a.pause(); a.currentTime = 0; const v = getComputedStyle(e).left; e.remove(); return v; })()],
    ["elementsfrompoint-culled-inline", () => (() => { const d = document.body.appendChild(document.createElement('div')); d.style.cssText = 'position:fixed;left:0;top:0;z-index:2147483647'; d.innerHTML = '<span id="cc158a"><span style="position:relative">Text</span></span>'; const r = d.querySelector('[style]').getBoundingClientRect(); const hit = document.elementsFromPoint(r.left + 1, r.top + r.height / 2).some((e) => e.id === 'cc158a'); d.remove(); return hit; })()],
    ["webgl-pixel-local-storage", () => document.createElement('canvas').getContext('webgl2').getSupportedExtensions().includes('WEBGL_shader_pixel_local_storage')],
  ];
  const out = [];
  for (const [id, f] of checks) {
    let v;
    try { v = await f(); } catch (e) { v = "throws " + e.name; }
    const expr = f.toString().replace(/^\(\)\s*=>\s*/, "");
    out.push(id.padEnd(28) + expr + " = " + (typeof v === "string" ? JSON.stringify(v) : String(v)));
  }
  console.log(out.join("\n"));
})();

FAQ

When is Chrome 158 released?

Chrome 158 reached the stable channel on November 17, 2026, after an early-stable rollout to a small share of Windows and macOS users from November 4. The current stable builds are 158.0.8127.37 on Windows and macOS and 158.0.8127.36 on Linux, the build measured on this page.

What is the Chrome 158 user agent string?

On Windows: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/158.0.0.0 Safari/537.36. Only the major version changes; the full version travels in Client Hints. The table above lists every platform.

What is the Sec-CH-UA header in Chrome 158?

"Chromium";v="158", "Not.A/Brand";v="24", "Google Chrome";v="158", measured on 158.0.8127.36. Both the fake GREASE brand and the order change with every major.

Did Chrome 158 change the TLS (JA3/JA4) or HTTP/2 fingerprint?

No: JA4 t13d1517h2_8daaf6152771_cb7bf5808d99 and the same HTTP/2 settings in a fresh profile, as on 152 to 157. See the network section.

How can a website tell Chrome 157 from Chrome 158?

The quickest lines are typeof XSLTProcessor, document.createElement('install').constructor.name and CSS.supports('selector(:playing)'). None of them needs a permission.

Is XSLT really gone in Chrome 158?

Off by default: the XSLT runtime feature is no longer enabled, so XSLTProcessor is undefined and XSL stylesheets are neither fetched nor applied. Google's field-trial configuration and enterprise policy can still turn it back on for some users, so a Chrome 158 that still has it is possible.

Did Chrome 158 change anything for automation?

Not in what a page sees: navigator.webdriver and the headless User-Agent format are unchanged. Read in the source: in headless mode a popup no longer opens about:blank first, and the DevTools protocol limits returnByValue results and restricts some methods for untrusted clients.

Clearcote runs Chromium 157, with all 260 patches carried forward.

Clearcote puts this into practice

An open-source Chromium with fingerprint control compiled into the engine. A drop-in for Playwright & Puppeteer.

  • 260engine patches
  • 38,417lines added
  • 349Chromium files changed
  • 365checks per build

Engine numbers are for the Pro build; the free open build is a smaller, public patch set.

Free for one browser: GitHub, a card check or a company Google account. Never charged.