Chrome moves to a two-week release cycle

The Chrome for Developers blog by Ben Mason and Deepak Ravichandran, published 8 September 2026, says Chrome is shifting Stable from a four-week to a two-week release cycle. The change starts with Chrome 153 on Desktop, Android, and iOS.

This is a Chrome engineering blog announcing a shipping-cadence change. It is not a CVE advisory, not a forced enterprise policy, and not a dump of new browser features beyond the cadence itself.

Chrome 154 Beta is already available. Chrome 154 Stable is scheduled for September 22.

Google frames the faster cadence as a security move. The post says AI discovery tools and community bug reports raise patch volume, and shorter cycles shrink the N-day window between a public fix and the user getting it. That is Google's argument, not an independent security rating of every peer browser. The same post names Microsoft, Mozilla, and Brave as already on a roughly two-week cadence.

TechCrunch covered the same shipping change as AI raising the security patch load.

For enterprise admins, the blog calls two-week Stable the most secure choice for most users. Organizations that cannot take a two-week cycle keep Extended Stable. Extended Stable still gets weekly security backports. Major feature updates stay on eight-week milestones, with Chrome 156 and Chrome 160 given as examples.

The post also notes Chrome pioneered "Release Early, Release Often" in 2010 and moved to four-week cycles in 2021.

Browser and AI-adjacent context on Techpresso includes Firefox for iOS adding a built-in ad blocker, OpenAI's private safety processing for ZDR, ChatGPT in Apple Messages on Mac, and US agencies on China AI distillation.

If you manage Chrome fleets, decide now whether most users move to two-week Stable (Chrome 153 onward) or stay on Extended Stable with eight-week feature milestones, and update your test and deploy pipelines before Chrome 154 Stable on September 22.