Apps & Consumer
Chrome moves to two-week release cycle, citing AI-driven security shifts
Google has shifted Chrome from a four-week to a two-week release schedule, starting with Tuesday's launch of Chrome 153 on desktop, iOS, and Android.
Chrome has officially switched from a four-week to a two-week release schedule, as Google promised earlier this year, with Tuesday’s launch of Chrome 153 on desktop, iOS, and Android. Google says the shift is tied to Chrome’s evolving security strategy in the AI era: as automated AI tools and community bug reports have pushed up the volume of patches and updates, a shorter release cycle makes those fixes easier to manage.
The company says this matters because faster-moving threats — some also attributable to AI — can be addressed more effectively by shrinking the window between landing a fix in the public codebase and getting it to end users. A shorter schedule helps keep the “N-day” patch gap, the time between a vulnerability becoming known and getting patched, as small as possible.
Faster releases also let Chrome ship features more quickly, which Google frames as important in the AI era, since AI-assisted software development has enabled a wave of new browser competitors. While OpenAI’s ChatGPT Atlas browser has been shut down, alternatives still competing for a piece of Chrome’s market include Brave, Dia, Opera Neon, Perplexity’s Comet, and DuckDuckGo’s browser, among others. Google is also experimenting with adding more AI features to Chrome and iterating on them rapidly, which similarly demands faster updates.
Because Chrome is the most-used browser globally, Google argues the change can help set the standard for the rest of the industry; Mozilla, Microsoft, and Brave have already begun adopting a faster two-week schedule of their own, following Chrome’s lead. This isn’t the first time Chrome has adjusted its cadence to enable faster patch management — it first moved to a four-week cycle in 2021, down from six weeks, after establishing its “release early, release often” principles more than a decade earlier.
Why it matters
Chrome setting a faster patch cadence pressures rival browsers to match it or risk looking slower to close security gaps just as AI tools accelerate both attacks and the software fixes meant to stop them.