Google Moves Chrome to Two-Week Releases to Speed Security Fixes

Google has shifted Chrome from a four-week release cycle to a two-week one, starting with Chrome 153 on desktop, iOS, and Android. The new schedule gives the browser a faster regular path for both security updates and product changes.

A faster route for fixes

Google’s security case centers on the N-day patch gap: the period between a vulnerability becoming known and its fix reaching users. Google says shorter release intervals can reduce that gap by moving fixes from Chrome’s public codebase to users more quickly. The supplied announcement describes that as an expected benefit, without a measured reduction.

Security work and feature work share a clock

The cadence change is not only about vulnerabilities. Google also says it will enable quicker iteration on Chrome features, including AI additions. That puts fixes for known flaws and new browser capabilities into the same recurring delivery window, even though they solve different problems.

Google links the faster cycle to a growing volume of patches and updates associated with automated AI tools and community bug reports. It also says faster-moving threats, some of which it attributes to AI, make speedier delivery of fixes more important.

Chrome is shortening an already faster cycle

This is Chrome’s second major compression of its release calendar in recent years. In 2021, Chrome moved from a six-week cycle to a four-week cycle; the latest change halves that interval again. Google is therefore treating release timing itself as part of its response to a heavier security workload and faster feature development.

Other browsers are moving faster too

Mozilla, Microsoft, and Brave have also begun adopting two-week release schedules, according to TechCrunch. Chrome’s move joins a broader shift toward more frequent browser updates, while Google’s stated rationale combines a security-delivery goal with faster iteration on its own browser features.