Chrome 156 Early Stable: what home users should do

Google started the next Chrome major train for a small percentage of Stable users on October 7, 2026. That is not the same story as yesterday’s “everyone should be on Chrome 155” note. Early Stable is a staged peek at Chrome 156. Most home PCs should still land on Chrome 155 first.

We already covered Google’s broad Stable jump to Chrome 155.0.8059.39/.40 (October 6, 2026). Read that first if chrome://version is still on 154.x. This article is only about what Early Stable 156 means when Google offers it, and what to do if you do not see it yet.

What Google shipped on October 7

Google’s Early Stable Update for Desktop (Wednesday, October 7, 2026) says the Stable channel was updated to:

Windows / Mac: 156.0.8078.12 or 156.0.8078.13
Scope: early Stable release to a small percentage of users

The same day’s Chrome for Android Update says Google released Chrome 156 (156.0.8078.25) for Android to a small percentage of users, with availability on Google Play over the next few days. That Android note describes stability and performance improvements and points readers at Google’s early Stable release details.

This is still the Stable channel, not Beta, Dev, or Canary. Early Stable means Google starts a new major Stable train with a limited cohort before the wider rollout. Chromium’s release channels overview still treats Stable as the everyday channel for most people. Early Stable is how Google begins that Stable train for a slice of machines.

What you should run today

If chrome://version shows 155.0.8059.39 or .40 (Linux .39): you are on the October 6 security train. Stay there unless Google already offered 156 on your machine. Do not sideload a random Chrome 156 installer from a third-party site to “catch up.”

If chrome://version shows 156.0.8078.12/.13 (desktop) or 156.0.8078.25 (Android): you are in the Early Stable cohort. That is normal for a small percentage of users. Fully quit and relaunch after the update so the new build is actually running, then keep an eye on crashes or extension weirdness for a day.

If you are still on 154.x: ignore the 156 headline for a minute. Install Chrome 155 from About Google Chrome first (our Chrome 155 guide). Early Stable 156 is not a substitute for missing last week’s Critical fixes.

Linux Stable was named in the October 6 Chrome 155 note. The October 7 Early Stable desktop note names Windows and Mac only. Do not invent a Linux Early Stable version that Google did not publish in that post.

How to check on a home PC or Mac

Open Google Chrome.
Open About Google Chrome (Menu → Help → About Google Chrome on Windows/Linux, or Chrome → About Google Chrome on Mac).
Let it finish checking. Relaunch if asked.
Type chrome://version and read the first version line.
Decide using the three cases above. Do not panic if you are still on 155 while a friend already sees 156. That is how a small-percentage Early Stable rollout looks.

Android Chrome

Open the Google Play store and check for a Chrome update.
If Play offers a build and after install Chrome reports 156.0.8078.25, you are in the early Android Stable slice Google described on October 7.
If Play still offers 155.0.8059.39 (or you already have it), that remains the right security target for most Android Chrome users right now.
Open Chrome once after any update so the new build launches.

A desktop Early Stable offer does not update your phone. A Play update does not update your PC.

Do this / don’t do that

Confirm chrome://version after every update prompt.
Prefer the version Google actually offers your machine through Stable or Play.
File a bug with Google if Early Stable 156 breaks a site or extension you rely on (the Early Stable posts ask for bug reports).

Don’t

Do not treat “Chrome 156 exists” as proof that 155 is obsolete for everyone. Early Stable is a small percentage by design.
Do not download unofficial Chrome 156 packages to force the version number.
Do not leave old Chrome windows open after an update and assume you are protected.
Do not confuse Early Stable with switching to the Beta channel on purpose.

Bottom line

On October 7, 2026, Google started Early Stable for Chrome 156.0.8078.12/.13 on Windows and Mac (desktop note) and Chrome 156.0.8078.25 for a small share of Android users (Android note). Most home users should still finish the Chrome 155.0.8059.39 security update if they have not. If Stable already moved you to 156, relaunch and verify. If it did not, stay on 155 until Google offers the next train to you.

Image: Google Chrome official update page art (google.com/chrome/update).