Version article

Download 123.0.6312.122 from the Chrome Stable for Windows 32-bit

Download Google Chrome 123.0.6312.122 with the branch, platform, release date, and file size shown clearly on the same page.

Stable Windows 32-bit Published 2024-04-11
Version 123.0.6312.122
Release date 2024-04-11
Platform Windows 32-bit
File size 129.06MB
Quick facts

What users usually want to know first

Branch Stable
Clicks

What changed in Chrome 123.0.6312.122

Google Chrome 123.0.6312.122 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.

light-dark() CSS function.

The light-dark() function in CSS lets you create colors that adapt to a user's preference for light or dark mode. Use the light-dark() function to specify two different color values within a single CSS property.

The browser will automatically choose the appropriate color based on the element's computed color-scheme value. For example, with the following CSS:

  • If the user selected a light theme, the element will have a lime background.
  • If the user selected a dark theme, the element will have a green background.

Long Animation Frames API.

The Long Animation Frames API is available to help you find the causes for main-thread congestion which is often the cause for bad INP (Interaction to Next Paint)—a Core Web Vital that measures a website's responsiveness.

The new API is an enhanced version of the Long Tasks API, which provides a better understanding of slow user interface updates. The Long Animation Frames API lets you measure blocking work. It measures the tasks together with the following rendering update and adds information such as long running scripts, rendering time, and time spent in forced layout and style, known as layout thrashing.

Collecting and analyzing this information lets you identify and troubleshoot performance bottlenecks. You can capture long frames with the following code.

Service worker Static Routing API.

Using service workers you can make websites work offline and create caching strategies that can provide a performance boost.

However, there can be a performance cost when a page is loaded for the first time in a while and the controlling service worker isn't running in that moment. Since all fetches need to happen through the service worker, the browser has to wait for the service worker to start up and run to know what content to load.

With the Service Worker Static Routing API, at install time, you can declare paths to always be served from the network. When a controlled URL is later loaded, the browser can start fetching resources from those paths before the service worker has finished starting. This removes the service worker from the URLs that you know don't need a service worker.

And more!

Of course there's plenty more.

  • You can offer customized pages based on where the user navigated from with the NavigationActivation interface.
  • Chrome now has support for Zstandard (zstd). This Content-Encoding helps load pages faster and use less bandwidth, and spend less time, CPU, and power on compression on servers, resulting in reduced server costs.
  • The notRestoredReasons API for bfcache is rolling out from Chrome 123. This allows site-owners to collect reasons in the field as to why the bfcache was unable to be used. Site owners can use this to improve usage of the bfcache which allows faster history navigations.
  • The picture-in-picture value for display-mode lets you write specific CSS rules that only apply when the web app is shown in picture-in-picture mode. For example:

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.