Chrome moves to a two-week release cycle

Google is putting Chrome on a two-week release cycle, starting with Chrome 153 on Desktop, Android, and iOS.

The Chrome for Developers blog laid out the shift on 8 September 2026. Stable had been on a four-week cadence. The post is a shipping-schedule change, not a CVE and not a dump of new browser features.

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 change as AI raising the security patch load.

For most users, the blog calls two-week Stable the most secure choice. 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.

Chrome pioneered "Release Early, Release Often" in 2010 and moved to four-week cycles in 2021. Two weeks is the new default. The eight-week feature train is the escape hatch.

Browser shops are tightening other defaults too. Firefox for iOS just added a built-in ad blocker. Chrome's bet is that a shorter Stable cycle is the security feature.

Some offers on this page may be paid placements or contain affiliate links.