The Chrome two-week release cycle is now live. Since Chrome 153 landed on September 8, 2026, Google ships a new major Chrome version every 14 days instead of every four weeks. For you, that means smaller updates, features arriving sooner, and one habit worth keeping: relaunch Chrome when it asks.
Here are the numbers that matter before we get into the details.
- Starts with Chrome 153 on September 8, 2026.
- A new stable version every two weeks, on desktop, Android and iOS.
- Weekly security patches keep flowing between versions.
- Enterprise Extended Stable stays on its eight-week schedule.
If you only skim, the takeaway is simple: nothing breaks, and Chrome just moves faster.
How the Chrome two-week release cycle works
Google first announced the change in March. According to 9to5Google, Chrome had shipped a major version every four weeks since 2021, and added a weekly security update in 2023. The new plan cuts the major-version gap in half.
The idea is to shorten the wait between a feature being finished and you actually using it. Per Phoronix, smaller releases should also cause less disruption and make bugs easier to track down after launch.
Each version still spends time in beta first. 9to5Google reports that a beta ships three weeks before its stable release, so the testing window shrinks but does not disappear.
The new Chrome release schedule at a glance
Two-week steps make the calendar easy to predict. The first three rows below come from reporting on the actual rollout; the last two follow the same pattern and could still shift.
| Chrome version | Stable date | Status |
|---|---|---|
| Chrome 153 | September 8, 2026 | Shipped, first on the new cycle |
| Chrome 154 | September 22, 2026 | Shipped |
| Chrome 155 | October 6, 2026 | Shipped |
| Chrome 156 | About October 20, 2026 | Projected (beta since September 30) |
| Chrome 157 | About November 3, 2026 | Projected from the two-week pattern |
Why this matters: you can now guess when the next Chrome version lands without checking a calendar. If a feature appears in beta, it is usually only a few weeks from reaching you.
You can see how recent versions looked in our guides to Chrome 155 and its JPEG XL support and the Chrome 154 HTTP warning. Those two shipped just 14 days apart.
What the new schedule changes for you day to day
For most people, very little. Chrome still updates itself in the background, and you still get a “Relaunch” button when an update is ready. The difference is that the button may show up a little more often, with fewer changes inside each update.
Here is the old and new setup side by side.
| What | Before | Now |
|---|---|---|
| Major version | Every 4 weeks | Every 2 weeks |
| Security patches | Weekly | Weekly (unchanged) |
| Size of each update | Bigger batch of changes | Smaller batch of changes |
| Enterprise Extended Stable | 8 weeks | 8 weeks (unchanged) |
Smaller batches also help when something goes wrong. If a site looks off after an update, there are fewer suspects, and Google can fix it faster.
The change covers Chrome on desktop, Android and iOS, according to 9to5Google. The Dev and Canary channels, which developers use to test early builds, stay as they are.
One tip: a Chrome tab that has been open for days will not pick up an update until you relaunch. If you notice the green, yellow or red update arrow in the top corner, that is Chrome telling you to restart.
What IT admins and extension developers should know
Work and school computers are the group that could feel this most. 9to5Google says the eight-week Extended Stable channel for enterprise customers and Chromium embedders is unchanged, so managed fleets do not have to move at double speed.
On Chromebooks, Google says the latest releases will roll out after dedicated platform testing. Chrome Unboxed adds that ChromeOS will skip odd version numbers to stay in sync while keeping its four-week hardware cadence.
Extension makers get a calmer story than you might expect. According to Chrome Unboxed, Manifest V3 extensions should not be disrupted, and Chrome 153 adds a native chrome.publicSuffix API. Manifest V2 is already gone after the Chrome Web Store clean-up on August 31, per the same report. If you use Edge instead, see our post on the Edge Manifest V2 shutdown.
Frequently Asked Questions
How often does Chrome update now?
A new major version arrives every two weeks, and security fixes still arrive weekly. Chrome downloads them in the background.
Do I need to do anything for the Chrome two-week release cycle?
No. Keep automatic updates on and relaunch Chrome when you see the update arrow. You can check manually at Settings, then About Chrome.
Will Chrome 156 arrive on October 20?
That is the date the two-week pattern points to, and the beta has been out since September 30. Google can still adjust a date, so treat it as likely rather than guaranteed.
Does this affect work or school computers?
Usually not directly. The Extended Stable channel stays on an eight-week cycle, and your IT team picks which channel your device follows.
Our verdict: faster is fine, as long as you restart
This is a good change for regular users. Smaller updates are easier on you and easier for Google to fix, and the weekly security patches mean you were never waiting a month for safety anyway. The only real cost is more restarts, so make a habit of relaunching Chrome once a week and let the rest happen on its own.
Leave a Reply