Chrome 153 launches today: Google’s accelerated 2-week release cadence begins

Today marks one of the biggest operational turning points in Chromium’s 18-year history. Google has officially begun rolling out Chrome 153 Stable to desktop and mobile devices, and while every major milestone brings a healthy batch of performance tweaks and new web APIs, this release represents something far bigger under the hood: it is the official launch of Google’s new two-week release cadence.

For years, Chrome operated on a predictable six-week schedule before Google shifted to a four-week update cycle back in 2021. Now, starting today with Chrome 153, major milestone releases will arrive twice as fast, fundamentally changing how new features, web standards, and security updates reach our laptops and phones.

Why Chrome is moving to a two-week release schedule

According to Google’s engineering roadmap on the Chrome for Developers blog, the shift to a two-week cycle is designed to eliminate the long lag between when an engineer completes a feature and when everyday users actually get to use it.

Under the previous four-week cycle, if a new browser API, CSS optimization, or performance patch missed a release branch cutoff by a single day, it had to sit in developer channels for another entire month before reaching the Stable channel. By cutting the release cycle down to 14 days, users will get:

• Shorter branch stabilization: Features spend less time sitting idle in Beta branches, accelerating deployment for web standards and bug fixes.
• Smaller, lower-risk updates: Because updates roll out twice as often, each individual milestone contains a more digestible set of changes, making it significantly easier to isolate bugs or rendering regressions.
• Bi-weekly security sync: While Google already ships weekly security patches, aligning major milestones with a tighter two-week schedule ensures underlying engine refactors land with minimal delay.

What’s new in Chrome 153: Spatial audio, Rust XML, and CSS scroll containers

Even with the faster release rhythm, Chrome 153 is packed with impressive under-the-hood upgrades that elevate web media and platform stability:

• Native IAMF 3D spatial audio: After years of tracking early signs of spatial audio heading to Chrome and Chromebooks, Chrome 153 officially introduces native decoding for the Immersive Audio Model and Formats (IAMF) container in HTML5 media and WebAudio. IAMF is an open-source, royalty-free standard that lets web developers stream object-based and scene-based 3D audio in browser games, VR web apps, and streaming media without paying licensing fees for proprietary codecs like Dolby Atmos.
• Memory-safe XML parsing in Rust: Continuing Google’s massive effort to eradicate memory safety vulnerabilities from Chromium, Chrome 153 migrates its core XML parsing engine (outside legacy XSLT) to Rust. This eliminates entire categories of memory corruption and buffer overflow bugs in one of the browser’s foundational data ingestion pipelines.
• CSS single-axis scroll containers: Web developers can now take advantage of optimized single-axis scroll containers (overflow-x: scroll / overflow-y: hidden). The rendering engine skips cross-axis layout passes entirely, eliminating micro-stutter and frame drops in horizontal dashboard carousels and web spreadsheets.
• Native chrome.publicSuffix extension API: Instead of extensions bundling bulky third-party domain parsing libraries to figure out multi-part domain suffixes (like .co.uk), extensions can now query Chromium’s built-in public suffix engine directly, slashing extension memory overhead and speeding up content blockers.

What this means for extensions, ChromeOS, and enterprise fleets

Whenever release schedules accelerate, the natural question is whether extension developers and IT administrators can keep up. Fortunately, Google has built in several guardrails:

• ChromeOS skipping odd versions: Because shipping an entire desktop operating system every 14 days is an unrealistic burden on OEM hardware validation, ChromeOS releases will soon skip odd numbers to stay synchronized with the browser while maintaining its stable 4-week hardware cadence.
• Enterprise Extended Stable: For school districts and enterprise IT teams that prioritize rock-solid stability over cutting-edge features, Google’s Extended Stable channel remains unchanged, updating on an eight-week cycle.
• Extension compatibility: Because Manifest V2 is officially dead after the Chrome Web Store purge on August 31, modern Manifest V3 extensions won’t be disrupted by the two-week schedule, as declarative net request rules and service workers operate independently of milestone version jumps.

How to update to Chrome 153 today

Chrome 153 is rolling out over the air starting today across Windows, Mac, Linux, and Android. To pull down the update on your desktop browser:

1. Click the three-dot menu in the top-right corner of Chrome.
2. Hover over Help and select About Google Chrome.
3. Chrome will automatically check for updates, download version 153.0.8010.x, and prompt a quick restart.