Google has shifted Chrome from a four-week release cycle to updates every two weeks, beginning with Chrome 153 on desktop, iOS and Android. The company says the faster cadence will help it manage a growing flow of security fixes and product changes.
A shorter cycle can reduce the “N-day” gap: the period after a vulnerability and its fix are publicly known but before that patch reaches users. That window is especially risky because attackers can study a public change and target systems that have not yet updated. Google says AI-assisted security work and community bug reports are increasing the volume of patches it must ship.
The schedule also gives Chrome a quicker route for product experiments, including AI features, as new browser competitors enter the market. Other Chromium-based browsers have begun adopting a similar two-week cadence, extending the change beyond Google’s own users.
More frequent versions do not guarantee immediate protection on every device. Organizations still need to test and deploy updates, and users must allow their browsers to restart. The practical benefit is a smaller release bottleneck between a completed fix and the point when it becomes available.