Google has shifted its Chrome browser updates to a bi-weekly schedule to improve security responsiveness and introduce new developer features, marking a significant change in its release rhythm.
Google has begun shifting Chrome on desktop, Android and iOS to a two-week major release cycle, starting with Chrome 153 on 8 September 2026. The move replaces the four-week rhythm the browser had broadly followed since 2021, while the eight-week Extended Stable channel remains in place for organisations that need slower change and longer validation windows.
According to reporting on the launch, Chrome 152 reached Stable on 25 August 2026 and Chrome 153 followed just two weeks later, with Chrome 154 already scheduled for 22 September. ChromeOS is taking a slightly different route: it is adopting the new two-week branching pattern, but will still promote only even-numbered milestones to Stable, preserving a four-week user-facing cadence.
Google’s case for the faster timetable is straightforward. Smaller releases should let the company push security fixes, standards work and compatibility changes through more quickly, while also narrowing the gap between finding a flaw and shipping a patched build to millions of users. TechRadar reported that Google is increasingly leaning on AI-assisted vulnerability discovery and user-submitted bug reports, which has added pressure to deliver fixes faster.
The latest release is not just a schedule change. Chrome 153 adds support for the Immersive Audio Model and Formats, or IAMF, bringing native spatial-audio decoding into HTML media through Media Source Extensions. It also introduces a Rust-based XML parser for paths that do not require XSLT, replacing older libxml2-based handling in areas such as DOMParser, XMLHttpRequest responseXML, directly opened SVG documents and externally loaded SVG images. Google says the switch reduces exposure to memory-corruption bugs while maintaining web standards compatibility.
Other additions in Chrome 153 are aimed at developers building richer web applications. The release brings CSS scroll-axis-lock, a feature for controlling how scrolling gestures are constrained, along with single-axis scroll-container support for testing in Beta, Dev and Canary builds. It also adds dedicated and elements for browser-managed media capture, plus JavaScript’s Iterator.zip(), which allows multiple iterators to advance in step without custom coordination code.
Security remains the most immediate reason for the new cadence. The Drop Times reported that Chrome 153 shipped with 230 security fixes and that Google acknowledged an exploit for CVE-2026-87491 in the wild. Notebookcheck described the flaw as an out-of-bounds write in V8, Chrome’s JavaScript and WebAssembly engine, and said Google rated five of the fixes as critical. For users, the practical effect of the new cycle should be smaller, more frequent updates; for developers, it means testing will need to become a more regular discipline.
Disclaimer: This content is intended for informational purposes only. Readers are advised to exercise their own judgement, conduct due diligence, or consult a qualified expert before acting on any information provided.
