Download 120.0.6099.109 from the Chrome Stable for Windows 64-bit
Download Google Chrome 120.0.6099.109 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 120.0.6099.109
Google Chrome 120.0.6099.109 is available here as part of the Windows 64-bit Stable archive. Use this release page when you want the exact version, the current package details, and quick access to the correct installer.
CloseWatcher API.
An important feature of modal or popup components is that they are easy to close,with a consistent mechanism for doing so. Those mechanisms are called close requests, they are typically the ESC key on desktop platforms, and the back gesture or button on Android.
Web developers had no good way to handle close requests for their own components. This is especially problematic on Android devices, where providing the simple closing behavior for the back gesture is quite complex.
Chrome 120 brings the solution with CloseWatcher, a new API for directly listening and responding to close requests. It also includes upgrades to <dialog> and popover="" to use the new close request framework, so that they respond to the Android back button.
Checkout the CloseWatcher API demo to give it a try.
<details> name attribute
The name attribute for the <details> element makes it easy to implement the accordion pattern using a sequence of <details> HTML elements.
Multiple <details> elements that have the same name form a group. With this setup at most one element in that group can be opened at once.
Here is an example with a group that shares the name cookies:
Permission policy violation reports
Permissions policy violation reports are now available, these reports integrate the Permissions policy API that allows developers to control the browser features available to a page, its iframes, and subresources, by declaring a set of policies for the browser to enforce with the Reporting API. The Reporting API provides a generic reporting mechanism for web applications to use to make reports available based on several platform features.
This Permissions Policy API and Reporting API integration allows web developers to configure endpoints, to which permissions policy violation reports will be sent, allowing site owners to see when disallowed features are being requested for their pages in the field.
Controlling browser features with Permissions Policy includes more implementation details.
And more!
Of course there's plenty more.
- The relaxed CSS nesting implementation allows nested style rules to begin with an element, rather than being wrapped with
is()or requiring an ampersand in front. - With the
enterpictureinpictureaction in the Media Session API, websites can register an action handler which can be used to open a Picture-in-Picture or Document Picture-in-Picture window. - And a reminder that Chrome is working towards deprecating third party cookies. In January an experiment begins that could affect your website, so it's important that you check Preparing for the end of third-party cookies for auditing and mitigating steps.
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.