Google Chrome is shifting its major release cadence—starting with version 153, stable releases will now arrive every two weeks instead of the previous four-week interval. This marks the end of the roughly one-month milestone upgrades and brings quicker delivery of new features, bug fixes, and performance improvements. Before 2021, Chrome used an even longer six-week schedule for major updates.
Why the Accelerated Release Pace?
The purpose behind this move is straightforward: get enhancements to users faster. Smaller batches of changes make it easier to spot and fix regressions, tightens deployment windows, and ensures modern web features can be adopted with more confidence. Chrome’s slower update schedule made it harder to respond quickly; with a two-week cycle, there’s more agility, especially in dealing with security issues.
Security, Enterprise Options, and Version Roadmap
Security features are central to this shift. As threats evolve rapidly—accelerated by advances in artificial intelligence—Google aims for updates that reduce the window of vulnerability. Faster releases mean patches and safety improvements reach users sooner. For most users, the new two-week Stable channel will be the path forward.
However, enterprise customers get a more conservative alternative: the Extended Stable channel. That option rolls out updates every eight weeks. Chrome 156 and then 160 are upcoming in that schedule. Still, Google recommends that enterprise users consider switching to the two-week Stable release for faster benefit.
Version 153 has begun rolling out today across desktop, Android, and iOS platforms. The following major update, Chrome 154, is set to release on September 22, maintaining the two-week rhythm.
Historically, Chrome has gradually increased its update tempo. Under the four-week milestone model, many new features and fixes were held back until the next major release. By shrinking the time between milestones, Google expects more consistent upkeep—and an ability to launch version-sensitive web standards and fixes far more rapidly.
In user terms, this means smaller download sizes, more frequent improvements to performance and stability, and a shorter lag time before security updates reach all your devices, whether desktop or mobile.
What this means: Chrome’s move to a bi-weekly major release cycle is a big disruption to how we’ve come to expect browser updates. For users, it means staying more current and secure. For developers, it requires faster adaptation to new features and compatibility shifts. For enterprise IT teams, it raises decisions around update channels and balancing stability with timeliness.
