Download 139.0.7258.154 from the Chrome Stable for Windows 32-bit
Download Google Chrome 139.0.7258.154 with the branch, platform, release date, and file size shown clearly on the same page.
What users usually want to know first
What changed in Chrome 139.0.7258.154
Google Chrome 139.0.7258.154 is available here as part of the Windows 32-bit Stable archive. Use this release page when you want the exact version, the current package details, and quick access to the correct installer.
Stable release date: August 5th, 2025
Unless otherwise noted, the following changes apply to Chrome 139 stable channel release for Android, ChromeOS, Linux, macOS, and Windows.
CSS and UI
Short-circuiting var() and attr()
When the fallback is not taken, var() and attr() functions evaluate without looking for cycles in that fallback.
Support font-feature-settings descriptor in @font-face rule
This feature supports the string-based syntax for font-feature-settings as defined in CSS Fonts Level 4. Invalid or unrecognized feature tags will be ignored per specification. No binary or non-standard forms are supported.
As OpenType fonts become more widely adopted, this enhancement will improve typographic control, reduce redundancy, and support a more scalable, modern approach to web design.
Related technical references: ChromeStatus.com entry · Spec
CSS custom functions
Custom functions are similar to custom properties, but instead of returning a single, fixed value, they return values based on other custom properties, parameters, and conditionals.
Related technical references: ChromeStatus.com entry · Spec
Continue running transitions when switching to initial transition value
When the transition related properties change, they are only supposed to affect newly started transitions. This means that if you change the transition properties, unless you also change the properties which have active transition animations, those transition animations will continue with the previously specified duration and easing.
Chrome incorrectly canceled transitions when the transition property was set to none, even though it doesn't cancel them if you only change the transition-duration. This change makes Chrome consistent with Safari and Firefox, allowing active transitions to continue running, until their property value changes triggering a new transition update.
Related technical references: ChromeStatus.com entry · Spec
Corner shaping ( corner-shape , superellipse , squircle )
Enable styling corners, on top of the existing border-radius, by expressing the shape and curvature of the corner as a superellipse.
This allows shapes like squircles, notches, and scoops, and animating between them.
Related technical references: ChromeStatus.com entry · Spec
Add font-width property and descriptor and make font-stretch a legacy alias
Support async attribute for SVG <script> element
The SVGScriptElement interface in SVG 2.0 introduces the async attribute, similar to the HTMLScriptElement. This attribute allows scripts to be executed asynchronously, improving the performance and responsiveness of web applications that use SVG.
Related technical references: ChromeStatus.com entry · Spec
The request-close invoker command
Dialog elements can be closed through a variety of mechanisms, sometimes developers want to have the ability to prevent closure. To achieve this dialogs fire a cancel event. Originally this was only fired via a close request (for example, an ESC key press), recently a requestClose() JavaScript function was added which also fires the cancel event.
The request-close command brings that new ability to the declarative invoker commands API.
Related technical references: ChromeStatus.com entry · Spec
Scroll anchoring priority candidate fix
Changes the scroll anchoring algorithm. Instead of selecting the priority candidate as the anchor, choose the candidate as the scope or root of the regular anchor selection algorithm which will select the deepest onscreen element as the anchor.
Device
WebXR depth sensing performance improvements
Exposes several new mechanisms to customize the behavior of the depth sensing feature within a WebXR session, with the goal of improving the performance of the generation or consumption of the depth buffer.
The key mechanisms exposed are: the ability to request the raw or smooth depth buffer, the ability to request that the runtime stop or resume providing the depth buffer, and the ability to expose a depth buffer that does not align with the user's view exactly, so that the user agent does not need to perform unnecessary re-projections every frame.
Related technical references: ChromeStatus.com entry · Spec
DOM
Allow more characters in JavaScript DOM APIs
The HTML parser has always (or for a long time) allowed elements and attributes to have a wide variety of valid characters and names, but the JavaScript DOM APIs to create the same elements and attributes are more strict and don't match the parser.
This change relaxes the validation of the javascript DOM APIs to match the HTML parser.
Related technical references: ChromeStatus.com entry · Spec
Graphics
WebGPU: 3D texture support for BC and ASTC compressed formats
The texture-compression-bc-sliced-3d and texture-compression-astc-sliced-3d WebGPU features add respectively 3D texture support for BC and ASTC compressed formats.
Related technical references: ChromeStatus.com entry · Spec
Secure Payment Confirmation (SPC)
The securePaymentConfirmationAvailability API
This is a JavaScript API to provide an easier way to check if the Secure Payment Confirmation (SPC) feature is available. With this API, the only way to determine SPC's availability was to create a PaymentRequest with the required parameters, which is clunky and difficult in the case where a developer wants to check for SPC before starting to process a payment.
Related technical references: ChromeStatus.com entry · Spec
Secure Payment Confirmation: Browser Bound Keys
Adds an additional cryptographic signature over Secure Payment Confirmation assertions and credential creation. The corresponding private key is not synced across devices. This helps web developers meet requirements for device binding for payment transactions.
Related technical references: ChromeStatus.com entry · Spec
On-device AI
On-device Web Speech API
This feature adds on-device speech recognition support to the Web Speech API, allowing websites to ensure that neither audio nor transcribed speech are sent to a third-party service for processing.
Websites can query the availability of on-device speech recognition for specific languages, prompt users to install the necessary resources for on-device speech recognition, and choose between on-device or cloud-based speech recognition as needed.
Related technical references: ChromeStatus.com entry · Spec
Navigation
Clear window name for cross-site navigations that switches browsing context group
Clears the value of the window.name property when navigation switches browsing context groups, to avoid leaking information that could be used as a tracking vector.
Related technical references: ChromeStatus.com entry · Spec
Network
Reduce fingerprinting in Accept-Language header information
Reduces the amount of information the Accept-Language header value string exposes in HTTP requests and in navigator.languages. Instead of sending a full list of the user's preferred languages on every HTTP request using the Accept-Language header, Chrome only sends the user's most preferred language.
Related technical references: ChromeStatus.com entry
Randomize TCP port allocation on Windows
This launch enables TCP port randomization on versions of Windows (2020 or later) where we don't expect to see issues with re-use of prior ports occurring too fast (causing rejection due to timeouts on port re-use). The rapid port re-use issue arises from the Birthday problem, where the probability of randomly re-picking a port already seen rapidly converges with 100% for each new port chosen when compared to port re-use in a sequential model.
Related technical references: ChromeStatus.com entry
Performance
Faster background freezing on Android
Shortens the time to freezing background pages (and associated workers) from five minutes to one minute on Android.
Related technical references: ChromeStatus.com entry
Security
Fire error event for Content Security Policy (CSP) blocked worker
Makes Chrome conform to the specification, checking the CSP during fetch and firing the error event asynchronously instead of throwing exception when script runs "new Worker(url)" or "new SharedWorker(url)".
Related technical references: ChromeStatus.com entry · Spec
WebRTC
Audio level for RTC encoded frames
This feature exposes to the web the audio level of an encoded frame transmitted using RTCPeerConnection and exposed using WebRTC encoded transform.
Related technical references: ChromeStatus.com entry · Spec
Web APIs
Web app scope extensions
Adds a scope_extensions web app manifest field that enables web apps to extend their scope to other origins.
This allows sites that control multiple subdomains and top level domains to be presented as a single web app.
Requires listed origins to confirm association with the web app using a .well-known/web-app-origin-association configuration file.
Related technical references: ChromeStatus.com entry · Spec
Specification-compliant JSON MIME type detection
Chrome now recognizes all valid JSON MIME types as defined by the WHATWG mimesniff specification. This includes any MIME type whose subtype ends with +json, in addition to application/json and text/json. This change ensures that web APIs and features relying on JSON detection behave consistently with the web platform standard and other browsers.
This page highlights the release changes most relevant to users. The official source below contains the full technical detail.
Official source: Chrome 139 Release Notes
Installation notes
After downloading the package, confirm that the branch and platform match your device before launching the installer or extracting the archive. If you only need a standard everyday browser, Stable is usually the safest choice. If you are testing new behavior, Beta, Dev, and Canary are better fits.
Related release pages
For newer or older builds in the same branch, open the category archive linked above. For different platforms, use the related desktop archives in the sidebar.
Frequently asked questions
These FAQ blocks help the page read like a complete release article instead of a download stub, which is better for trust and better for SEO.
Should I use this release or stay on Stable?
If you just want the safest everyday browsing experience, Stable is usually the right default. Preview branches are better for testing, compatibility checks, and early feature access.
Why show exact version numbers so prominently?
Because exact-version queries are common in English search behavior, especially for QA teams, enterprise users, and people trying to reproduce a bug or environment.
Why keep a full article around the download buttons?
A stronger page body gives users context and gives Google clearer signals about what the release page actually covers.
Where should older releases live?
Older versions belong in the category archive page, with this article template handling exact-version landing pages one release at a time.