Google accelerates Chrome updates with the shift to a two-week release cycle

Google begins rolling out Chrome 153 with a new bi-weekly release schedule, introducing significant technical enhancements and aiming for faster feature delivery and improved stability across desktop and mobile platforms.

Google has begun rolling out Chrome 153 Stable on desktop and mobile, and the release marks a structural shift in how the browser will be shipped. According to Google’s Chrome for Developers blog, this is the first major version under a new two-week release cadence, cutting the interval between milestone releases from the four-week rhythm adopted in 2021. The company says the change is intended to reduce the lag between an engineer finishing a feature and users actually receiving it.

The shorter cycle is also meant to make each release smaller and easier to stabilise. Google argues that, under the old system, a feature that missed a branch cut-off by a single day could be delayed by almost a month before reaching Stable. With updates now arriving every 14 days, the company says changes should spend less time waiting in Beta, while faster branch stabilisation may also help surface bugs and rendering regressions more quickly. Google has also said the revised timetable fits with a bi-weekly security sync, even though weekly security updates continue.

Chrome 153 brings a series of technical changes beneath the surface. Google has added native support for the Immersive Audio Model and Formats container in HTML5 media and WebAudio, giving browsers a royalty-free path for object-based and scene-based spatial audio. The release also moves the core XML parsing engine to Rust, a change aimed at reducing memory corruption and buffer overflow risks in a critical ingestion path. In addition, Chrome 153 includes performance work for CSS single-axis scroll containers, which should reduce micro-stutter in interfaces such as horizontal carousels and spreadsheet-style views.

The update also introduces new extension and platform features. Google’s extension documentation says the new browser.publicSuffix API lets extensions use Chromium’s built-in public suffix engine instead of bundling third-party domain parsing libraries, which should lower memory use and improve performance. Chrome 153’s beta notes also list declarative media capture elements such as and , alongside Iterator.zip() and Iterator.zipKeyed() in JavaScript. For enterprise users, the Extended Stable channel remains on an eight-week cycle, while ChromeOS will stay aligned by skipping odd version numbers rather than adopting the browser’s faster release pace.