Google began moving Chrome to a two-week stable release cycle Tuesday, Sept. 8, with Chrome 153 reaching desktop, Android and iOS users. The change doubles the cadence of major browser releases from once every four weeks and gives developers, security teams and enterprise administrators less time between platform changes.
The company announced the schedule in March and tied the shift to a faster-moving web platform. Its security team later said artificial intelligence is increasing the volume of vulnerability discovery and the speed at which both defenders and attackers can work. TechCrunch reported Tuesday that the new cadence is now in effect.
Google is shrinking the patch gap
Chrome already receives weekly security updates. The new schedule changes the pace of full beta and stable milestones, beginning with version 153. Google says smaller, more frequent releases should deliver fixes and features sooner while simplifying post-release debugging.
Security is a central reason for moving faster. Once a vulnerability fix becomes visible in Chrome’s public codebase, attackers can study it before the correction reaches most users. Google calls that exposure period the “patch gap.” In a July security update, the company said it was piloting two security releases per week and exploring dynamic patching that could eventually apply many fixes without a full browser restart.
The company also said AI-assisted tools are finding and helping repair far more bugs. Chrome’s security team reported that it received more bug reports by March 2026 than during all of 2025. It said Chrome milestones 149 and 150 fixed 1,072 security bugs, more than the previous 23 milestones combined.
Enterprise browser operations must accelerate
For businesses, the practical consequence is a shorter testing and deployment rhythm. Web applications, browser extensions, authentication systems and managed-device policies will encounter new stable versions twice as often. Teams that test browser changes only at monthly intervals may need more continuous regression checks and clearer ownership of update failures.
Google is preserving an eight-week Extended Stable channel for enterprise administrators and Chromium embedders that need additional validation time. That option creates breathing room, but it also makes release-channel governance more important: organizations must decide which users need speed, which environments need stability and how long they can safely defer a change.
Chrome’s market reach means the schedule is not merely an internal product decision. Mozilla, Microsoft and Brave have also moved toward faster browser releases, TechCrunch noted. The browser is becoming a continuously changing security surface, and the operating model around it now has to move at nearly the same speed.