Download 119.0.6045.105 from the Chrome Stable for Windows 32-bit
Download Google Chrome 119.0.6045.105 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 119.0.6045.105
Google Chrome 119.0.6045.105 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.
Cookies expiration date.
Since Chrome 104 newly created cookies or those updated with an expiration date have had that date capped at no more than 400 days in the future. This same limit will now be retroactively applied to cookies already in storage.
The expiration dates of these cookies will be capped at no more than 400 days after the first time Chrome 119+ starts up and does a one time database migration. The impact of this change will not be felt by users until at least 400 days after Chrome 119 is released, and then only for existing cookies that have not been updated in that period.
You can read more about the expiration date recommendation and here is a friendly reminder that third party cookies will be deprecated in the near future and a guide to prepare for the deprecation.
CSS updates
For CSS we have three updates:
Number one: the new :user-invalid and :user-valid pseudo-classes that represent an element with incorrect or correct input, respectively, but only after the user has significantly interacted with it. They are similar to the :valid and :invalid, pseudo-classes but with the added constraint that the new pseudo-classes only match after the user has interacted with the element.
Number two: the relative color syntax allows developers to define colors by modifying the parameters of other colors.
For example: oklab(from magenta calc(l * 0.8) a b); results in an Oklab magenta that is 80% lighter.
And number three: clip-path now supports more values.
The clip-path property creates a clipping region that sets what part of an element should be shown. Parts that are inside the region are shown, while those outside are hidden.
Now you can use <geometry-box> values to control the clip's reference box, making clip-path easier to use. These box values can be used alongside basic shapes (for example, clip-path: circle(50%) margin-box), or they can be used alone to clip to the specified box (for example,clip-path: content-box).
You can also use the functions xywh() and rect() that make it easier to specify rectangular or rounded-rectangular clips.
Correction: A previous version of this article referred to improvements for Fenced Frames. These changes are now shipping in Chrome 120.
And more!
Of course there’s plenty more.
WebSQLis fully removed as of Chrome 119. A reverse origin trial allows developers to continue to use WebSQL until Chrome 123.- Now the
monitorTypeSurfacesoption can be used to prevent the user from sharing an entire screen, withgetDisplayMedia() - There’s an origin trial that adds a
fullscreenwindowFeatures parameter to thewindow.open()JavaScript API to allow the caller to open a popup directly to full-screen.
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.