Google to double Chrome update frequency to every two weeks starting September 2026

Google will halve the time between releases of its Chrome browser to two weeks, across versions of the software for desktop operating systems, Android, and iOS. The text ads giant announced the change on Tuesday in a post penned by Chrome Browser Release Team Manager Ben Mason and Distinguished Engineer Deepak Ravichandran.

"While releases will be more frequent, their smaller scope minimizes disruption and simplifies post-release debugging," the pair wrote. "And thanks to recent process enhancements, we are confident this shift will maintain our high standards for stability."

The Googlers justified the change on grounds that "The web platform is constantly advancing, and our goal is to ensure developers and users have immediate access to the latest performance improvements, fixes and new capabilities."

The new cadence commences on September 8th with the release of Chrome 153.

Why Google is accelerating Chrome releases

This marks the second major cadence reduction in Chrome's history. In 2021, Google reduced the release cycle from six to four weeks, citing similar reasons: improved internal processes and the need for faster security fixes. The company is now doubling down on that strategy.

Chrome Gemini panel became privilege escalator for rogue extensions

Indie web browser Ladybird flutters toward Rust with a little help from AI

Google patches Chrome zero-day as in-the-wild exploits surface

Google to foist Gemini pane on Chrome users in automated browsing push

What the change means for users and enterprises

For regular users, the change means more frequent access to new features, performance improvements, and security patches. The smaller scope of each release is designed to minimize disruption while maintaining stability.

Enterprise users face a more complex decision. Google isn't changing its Extended Stable releases, which continue to ship every eight weeks for organizations that need longer testing cycles. However, the company's guidance is clear: "The forthcoming fortnightly releases will be the most secure option and should be used if security is a larger concern than maintenance costs."

This creates a classic security versus stability trade-off for IT departments. Organizations that prioritize security will need to adapt to the faster release cycle, while those that prefer stability can stick with Extended Stable but accept the security trade-off.

Impact on the broader ecosystem

The change also affects the beta channel, which will now release every two weeks. This gives enterprise users and developers advance notice of upcoming changes that might impact their SaaS services or web applications.

Chrome's release cycle affects more than just the browser itself. Many other browsers are built on Chromium, and developers who target the web need to test against the latest Chrome features. The faster release cycle means the web platform will evolve more quickly, potentially accelerating innovation but also requiring more frequent testing and updates from dependent projects.

Chrome's release history and security context

Chrome pioneered the rapid release model for browsers, moving from annual releases to six-week cycles in 2010, then to four weeks in 2021. This latest change continues that trend toward continuous delivery.

Security has been a key driver of these changes. Chrome has faced numerous zero-day exploits in recent years, with Google often racing to patch vulnerabilities being actively exploited in the wild. The faster release cycle means security fixes reach users more quickly.

What remains unchanged

Despite the accelerated release schedule, Google is maintaining several existing programs:

• Extended Stable releases continue every eight weeks for enterprise and embedded use cases
• Beta releases now align with the two-week cadence, providing advance visibility
• Chromebook extended release options remain available

The company appears to be betting that its improved internal processes can handle the increased release frequency without sacrificing the stability that made Chrome successful in the first place.

This change reflects the accelerating pace of web development and the growing importance of rapid security response in an era of increasingly sophisticated online threats. Whether the benefits of faster feature delivery and security patches outweigh the costs of more frequent updates remains to be seen, but Google is clearly committed to pushing the boundaries of browser release velocity.