Google will speed Chrome stable releases from four weeks to two

Google will move the Chrome browser’s stable release cadence from a four-week cycle to a two-week cycle, starting in September and beginning with Chrome 153 on September 8, 2026. The company said the change is intended to give developers and users faster access to performance improvements, fixes and new capabilities.

The accelerated schedule applies to desktop, Android and iOS. Beta releases will also shift to the faster cadence, with each Chrome Beta shipping three weeks before the corresponding stable version so developers can test upcoming changes. Dev and Canary channels are unchanged, and Google will keep its Extended Stable channel for enterprise admins and Chromium embedders on an eight-week schedule. Google also noted Chromebooks will retain extended release options for admins who need slower updates.

Google framed the change as an evolution of its release process. "Building on our history of adapting our release process to match the demands of a modern web, Chrome is moving to a two-week release cycle," the company wrote. It added the move aims to "ensure developers and users have immediate access to the latest performance improvements, fixes, and new capabilities." Google also said that, thanks to recent internal process enhancements, it is confident the shift "will maintain our high standards for stability."

Under the new cadence, individual updates are expected to be smaller in scope, which Google says should minimize disruption and simplify post-release debugging. Practical schedule shifts already mapped by Google show stable milestones moving into a tighter rhythm: after Chrome 153 on September 8, 2026, the next stable milestone is set two weeks later on September 22, illustrating the new biweekly spacing between stable releases.

The company has been progressively changing how it ships Chrome. In 2023 Google began shipping weekly security updates and introduced an early stable release channel that sits between Beta and Stable. The move to a faster two-week stable cycle marks the latest step in a decade-long trend: Google shortened major updates from quarterly to six weeks in 2010, then to four weeks in 2021 to speed the delivery of critical fixes and streamline feature iteration. In a 2021 Chrome for Developers post, Pete LePage explained the rationale for that earlier change, noting that faster cadence "will give us more agility to get critical security and bug fixes out to users faster" and that it "doesn't mean we'll be shipping more features, or shipping new features in less time."

For developers and IT teams the immediate implication is a faster testing tempo. Google recommends using Beta builds to validate sites and applications ahead of stable releases; developers will need to compress their testing and deployment cycles to match the shorter intervals. Enterprise admins who require longer stability windows can continue to use the Extended Stable channel, which remains on an eight-week cadence.

Google says the smaller, more frequent updates will reduce the scope of each release and help its engineering teams respond more quickly when issues arise. For users, the shift promises quicker rollout of performance and security fixes; for developers and administrators, it raises pressure to accelerate testing and change management to keep pace with Chrome’s faster release rhythm.