Chrome is about to ship updates twice as fast. Starting with Chrome 153 on September 8, 2026, Google confirmed it is moving the browser to a two-week release cycle, cutting the wait time in half from the four-week cadence Chrome has followed since 2021. The change applies to desktop, Android, and iOS alike, and it means new features, fixes, and web platform capabilities reach your browser in roughly half the time they used to. Most people will not notice until an extension behaves differently or a website changes without warning. Developers testing against Chrome get considerably less runway before the next version lands.
TL;DR: Chrome moves from a four-week release cycle to a two-week one starting with Chrome 153 on September 8, 2026, according to Google’s own announcement. The change covers desktop, Android, and iOS, though Extended Stable keeps its existing eight-week schedule for enterprise users. Smaller, more frequent releases are meant to reduce the disruption of any single update. Regular users get new capabilities sooner, but developers and testers get less lead time to catch problems before each version ships.
What actually changes with Chrome 153
Chrome 153 is the first version to ship under the new two-week cadence, landing as a stable release on September 8, 2026. Under the old four-week schedule, that same version would not have reached stable until September 22.
Google laid out the shift in a post on the Chrome for Developers blog, published back in March 2026 and now taking effect. The company already added weekly security patches in 2023 and introduced an early stable release to catch problems before the wider rollout. The two-week cycle builds on both of those changes rather than replacing them.
| Stage | Old schedule (M153) | New schedule (M153) |
|---|---|---|
| Branch cut | Aug 24 | Aug 17 |
| Beta promotion | Aug 26 | Aug 19 |
| Stable cut | Sep 8 | Aug 25 |
| Early stable release | Sep 9 | Aug 26 |
| Stable release | Sep 22 | Sep 8 |
The same acceleration is already visible in how extensions have had to adapt. Chrome’s move to Manifest V3 forced ad blockers to rework how they filter content, and the uBlock Origin Manifest V3 changes from earlier this year show how quickly those transitions can outpace extension developers.
Why Google is moving to a two-week release cycle now
Google says the web platform itself is moving too fast for a monthly release to keep pace. In its own words, the goal is to make sure “developers and users have immediate access to the latest performance improvements, fixes and new capabilities.”
Smaller releases are also easier to debug. When something breaks in a four-week release, engineers have to isolate the cause from a much larger batch of changes. A two-week window narrows that search considerably, at least in theory.
Two weeks between releases leaves less room for a bug to sit unnoticed before the next version arrives to either fix it or compound it.
What does not change: enterprise and Chromebook users
Extended Stable keeps its existing eight-week cycle, unchanged by any of this. That option exists for enterprise administrators and Chromium embedders who need more time to test updates before deploying them across an organization.
Chromebooks are also getting a slower on-ramp. Google says the latest Chrome releases will roll out to Chromebooks only after dedicated platform testing, with more details on managed device updates to come. The Dev and Canary channels are not affected by the change at all.
A faster release cadence does raise the stakes for catching device-specific problems before they ship widely, the kind of issue that locked some Android tablet owners out of Chrome earlier this year after a routine update went wrong.
What this means for your next Chrome update
Your Chrome version number is going to climb faster than it used to. Checking Settings, then About Chrome, will show a new milestone roughly every two weeks instead of every four, even if most of those updates are incremental rather than dramatic.
Websites and extensions you rely on could also shift behavior with less warning between changes. If you like testing new capabilities before they reach everyone else, this is a reasonable moment to look at which Chrome flags are worth enabling on the beta channel, where new features typically surface three weeks ahead of stable.
None of this requires you to do anything differently today. Chrome will keep updating itself in the background the same way it always has. The only real difference is how often that background update happens, and how quickly the browser you open tomorrow might look slightly different from the one you closed tonight.
