Google Chrome Moves to Updates Every Two Weeks

Google Chrome is accelerating its release calendar. Beginning with Chrome 153, stable browser updates are moving from a four-week cycle to a two-week schedule across desktop, Android and iOS, bringing new features and security fixes to users more frequently.

Chrome’s two-week update cycle begins

Google announced the plan earlier this year and put it into practice with the September 8 launch of Chrome 153. Engadget and TechCrunch report that Chrome 154 is already scheduled for September 22, making the shorter cadence visible immediately rather than as a gradual transition.

The practical difference is straightforward: changes that once waited as long as a month for the next stable release can now arrive after roughly two weeks. That includes interoperability improvements, bug fixes and new browser features. Security patches already operate on their own urgent timelines, but a faster main release rhythm reduces the delay for fixes and changes bundled with stable versions.

Security pressure is shaping the schedule

Google has linked the shift to the growing volume of vulnerability reports and patches. The Chrome team uses automated tools powered by Gemini alongside findings from outside security researchers. As discovery speeds up, the company says shorter release windows make it easier to move completed fixes into users’ browsers before attackers can exploit disclosed weaknesses broadly.

Faster updates do not mean every organization must absorb major feature changes twice a month. Chrome’s Extended Stable channel remains available for schools and businesses that prioritize a more predictable deployment schedule. Under that option, security fixes continue weekly while major feature releases arrive every two months, giving administrators additional time for compatibility testing.

For most people, the transition should be largely invisible because Chrome updates automatically in the background. Users may notice version numbers changing more often, but the larger effect will be a steadier stream of small improvements rather than one larger monthly package. Restarting the browser when an update is ready will still be necessary to activate the newest version.

The new cadence also raises the importance of clear release notes and disciplined testing. Shipping twice as often creates more opportunities to deliver fixes quickly, but it also gives developers less time between stable milestones. Chrome 153 begins that balancing act with speed, security and reliability all under closer pressure.