Chrome Cuts Its Release Cycle to Two Weeks

Chrome 153 reached the stable channel on Sept. 8, 2026, the first release under a two-week release cycle that replaces the four-week schedule Chrome had used since 2021. Chrome 154 is due 14 days later, on Sept. 22, according to 9to5Google's report on the switch.

Senior Technical Program Manager Ben Mason and Distinguished Engineer and Senior Director Deepak Ravichandran, in a joint post covered by PYMNTS, said the point is to shrink what security researchers call the N-day gap: the window after a fix lands in Chrome's public, open-source codebase but before it reaches every user's machine, during which an attacker can read the fix, reverse-engineer the bug it patches, and build an exploit before most people have updated. "Shrinking the window between landing a fix in the public codebase and delivering it to end users keeps the 'N-day' patch gap as small as possible, helping us protect against fast-moving threats," the pair wrote, per PYMNTS.

Stable and Beta double their pace; Extended Stable does not

The change only touches two of Chrome's release channels. Dev and Canary already ship continuously and are unaffected. Extended Stable, the slower track Google recommends for enterprise fleets and Chromebooks, keeps its eight-week cadence.

Channel	Cadence before Sept. 8, 2026	Cadence now
Stable	Every 4 weeks	Every 2 weeks
Beta	Every 4 weeks	Every 2 weeks
Extended Stable	Every 8 weeks	Every 8 weeks
Dev / Canary	Continuous	Continuous

Applied across a full year, the arithmetic behind that change is stark: a 4-week cycle produces 13 stable releases annually, and a 2-week cycle produces 26.

The volume of bugs is part of the reason, not just the speed

PYMNTS reports Google's own framing points to rising patch volume as well as attacker speed, citing "automated AI discovery tools and community bug reports" as sources generating more fixes than the old four-week cycle could ship promptly. Google's developer blog adds that a smaller scope per release should also make it easier to isolate which change caused a regression, since fewer commits land between any two stable builds. Google's post does not say how many CVEs or bugs Chrome fixes in an average release, so the size of that volume increase is not quantified in either source.

Chrome's cadence has changed before

This is not the first time Google has sped up the schedule. 9to5Google notes Chrome ran on a six-week cycle before 2021, when it first moved to four weeks, the same cadence that just gave way to two. The platform's history of exploited bugs is part of why the pace matters to more than developers: The Terminal has covered two V8 engine flaws patched within days of each other on the previous, slower cycle, including a second exploited V8 bug Chrome shipped a fix for in four days. Google's own handling of goto-link redirects showed the same pattern of shipping a change and adjusting it in near-real time once developers reported side effects. Neither Google's post nor either outlet covering it says whether Chrome's extension review process or enterprise policy update tools will move to the same two-week rhythm.