Google has officially switched Chrome to a faster release schedule. The browser now ships updates every two weeks instead of four. This change arrived on Tuesday with the launch of Chrome 153. It rolled out across desktop, iOS, and Android simultaneously.
The shift ties directly to Chrome’s evolving security strategy. Google explained that the change reflects the new AI era. Automated AI tools and community bug reports keep pushing patch volume higher. Consequently, a shorter release cycle makes managing security fixes far easier.
Notably, Chrome 153 did not just arrive on time. In fact, it shipped a full two weeks early. Under the old calendar, it was due on September 22. Chrome 154 now lands on that same date instead. As a result, the calendar pulls forward with each successive milestone.
Faster-moving threats make this speed genuinely critical. Some of these threats can be attributed to AI too. The core goal involves minimizing the so-called N-day gap. Essentially, this measures the window between a known flaw and its patch. A shorter release schedule keeps that dangerous gap as small as possible.
The timing feels especially relevant given the release contents. Reportedly, Chrome 153 carried a hefty 230 security fixes total. It also addressed an active zero-day in the V8 JavaScript engine. Additionally, it patched five critical flaws across WebGL and Cast components.
AI now actively powers Chrome’s security work behind the scenes. Earlier this year, Google’s team built an AI agent using Gemini. This tool searches the Chrome codebase for vulnerabilities at scale. Consequently, defenders can find problems faster than manual review ever allowed.
However, weekly security updates will continue alongside the new cycle. Enterprise users also retain an Extended Stable channel option. That channel updates every eight weeks for managed devices instead. Meanwhile, Google recommends most enterprise users adopt the two-week option.
The move benefits the broader web ecosystem too. Chrome remains the most-used browser across the globe. In fact, Mozilla, Microsoft, and Brave have already begun adopting similar schedules. However, one practical downside emerges from the change. Chrome’s version number now advances twenty-six times yearly, aging compatibility documents twice as fast.
