Chrome shifts to two-week releases with Chrome 153, citing AI-driven security pressure

Chrome has officially cut its release cycle from four weeks to two, a change Google had promised earlier this year and which took effect with Tuesday's launch of Chrome 153 for desktop, iOS and Android, according to TechCrunch.

Security drove the decision

Google frames the faster cadence as part of its security strategy for the AI era. Automated AI tooling and community bug reports have pushed up the volume of patches and updates the team has to manage, and the company argues that a shorter cycle makes that workload easier to handle, TechCrunch reports.

The bigger payoff is timing. A two-week schedule shrinks the gap between a fix landing in Chrome's public codebase and that fix reaching end users — which in turn keeps the "N-day" window, the period between a vulnerability becoming publicly known and it being patched on user machines, as small as possible. Google also points to faster-moving threats, some of which it attributes to AI, as a reason to compress the timeline.

Feature speed matters too

Security is not the only motivation. Shorter cycles also let Chrome ship features more quickly, and TechCrunch notes this has become a competitive issue: AI-assisted software development has made it easier to build a browser, producing a wave of challengers including Brave, Dia, Opera Neon, Perplexity's Comet and DuckDuckGo's browser. OpenAI's own browser effort, ChatGPT Atlas, has been shut down, but the field remains crowded.

Google is also adding AI features to Chrome and iterating on them rapidly, which the company says demands faster update channels in its own right.

The rest of the browser market is following

Because Chrome is the most-used browser in the world, its engineering decisions tend to become industry defaults. TechCrunch reports that Mozilla, Microsoft and Brave have already started adopting two-week schedules of their own, meaning the change effectively resets the pace of browser updates across the board.

This is not Chrome's first acceleration. The browser moved from a six-week cycle to four weeks in 2021, itself a follow-up to the "release early, release often" philosophy Google established more than a decade earlier.

What changes for web developers

For anyone building for the web, the practical effect is a faster drip of smaller changes rather than bigger monthly drops. New platform features, deprecations and behaviour changes will surface roughly twice as often, which turns monitoring Chrome release notes and beta channel churn into a biweekly habit rather than a monthly one. Teams that test against a pinned browser version — extension developers, enterprises with managed fleets, QA pipelines — have less time to validate each stable build before the next one arrives, even though each individual release carries fewer changes.

Why it matters

Chrome's dominance means this is more than an internal Google change: it effectively doubles the update tempo for the mainstream web. On the security side, a shorter N-day window means known vulnerabilities spend less time unpatched on user machines, a meaningful improvement at Chrome's scale. Strategically, it shows Google treating AI as both a risk multiplier — generating faster attacks and a higher volume of bug reports — and a product accelerant that requires rapid iteration on Chrome's own AI features. With rivals already matching the pace, the two-week browser release is on its way to becoming the industry norm.