Download 101.0.4951.54 from the Chrome Stable for macOS
Download Google Chrome 101.0.4951.54 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 101.0.4951.54
Google Chrome 101.0.4951.54 is available here as part of the macOS Stable archive. Use this release page when you want the exact version, the current package details, and quick access to the correct installer.
hwb() color notation
Described in an article by Stefan Judis as a "color notation for humans", hwb() specifies color according to hue, whiteness, and blackness. As with other color notations, an optional alpha component specifies opacity.
This method of specifying color is now well-supported, with Firefox supporting it from version 96, and Safari from version 15.
Fetch Priority
Fetch Priority gives you a way to hint to the browser which order resources should be downloaded in, by using the fetchpriority attribute. This accepts values of "high", "low", and "auto".
"high": You consider the resource a high priority and want the browser to prioritize it as long as the browser's heuristics don't prevent that from happening."low": You consider the resource a low priority and want the browser to deprioritize it if its heuristics permit."auto": This is the default value that lets the browser decide the appropriate priority.
In the example below, a low priority image is indicated with fetchpriority="low".
Read more about the various use cases in Optimize resource loading with the Fetch Priority API.
Also in this release
There is a new method of forget() for USBDevice objects. This enables the forgetting of a device that previously had permission granted. For example, if this is an application used on a shared computer with many devices.
Also for Web USB, a fix to support [SameObject] for related attributes within USBDevice. The specification change can be found in a PR to the draft spec.
Dedicated workers loaded from a secure (HTTPS) origin, yet instantiated by insecure (non-HTTPS) contexts, are no longer considered secure. This means that inside such worker contexts: - self.isSecureContext is now false. - self.caches and self.storageFoundation are no longer available.
The popup argument for window.open() now evaluates to true, following a recent change to the spec for parsing this argument. Previously, when popup was set equal to true, window.open() was interpreted to mean false. This change makes boolean features easier to use and understand.
Official source: Official Chrome update
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.