Chrome 153 begins Google’s fortnightly browser release cycle
Google has released Chrome 153 for desktop, iOS and Android, marking the browser’s formal shift from a four-week release cycle to a two-week cadence. The company said the change, announced earlier this year, is intended to strengthen patch management as AI affects both software development and the security environment.
Chrome’s revised schedule is designed to shorten the period between a security fix appearing in the public codebase and reaching users. Google describes this interval as the “N-day” patch gap: the time between a vulnerability becoming known and systems receiving the patch.
Faster releases target the patch gap
Google said automated AI tools and reports from the security community have increased the volume of patches and updates that Chrome must handle. Releasing every two weeks gives the project more frequent opportunities to deliver those fixes to users, particularly as threats are moving more quickly and some are also linked to AI.
The underlying pressure is not limited to new vulnerabilities. A public fix can leave organisations exposed if endpoint deployment lags behind disclosure. In that context, Chrome vulnerability remediation accelerated by AI illustrates the scale of Chrome vulnerability remediation as AI accelerates bug discovery, while the shorter cadence aims to reduce the time until fixes are available in stable releases.
Google has adjusted Chrome’s schedule before for similar operational reasons. In 2021, it reduced the cycle from six weeks to four weeks after building on its long-standing “release early, release often” approach.
AI competition also raises the pace of product work
The two-week schedule is also intended to speed up feature delivery. Google is testing additional AI capabilities in Chrome and wants to iterate on them more rapidly. AI-assisted development has helped produce a wider field of browser competitors, including Brave, Dia, Opera Neon, Perplexity’s Comet and DuckDuckGo’s browser.
Chrome’s scale makes the change relevant beyond Google’s own product. Mozilla, Microsoft and Brave have already begun moving towards a two-week release schedule, reflecting Chrome’s influence on browser-industry practices.
What organisations should do
Businesses using managed Chrome deployments should review update policies, test essential web applications more often and monitor whether endpoints remain aligned with the stable channel. A two-week release rhythm makes timely browser patching and compatibility validation a more regular operational requirement.