Chrome 153 is changing the browser update game, starting with desktop and mobile – Automated Home

A browser update arriving every two weeks may sound like a small scheduling change, but Chrome 153 marks a major shift in how quickly the web platform can evolve. Google has moved Chrome from four-week major releases to a tighter two-week cycle.

The change affects Chrome on desktop, Android, and iOS, beginning with Chrome 153 on September 8, 2026. Instead of waiting about a month between major milestones, users will see smaller updates arrive more frequently, while enterprises retain a slower Extended Stable option.

For smart-home users, the faster rhythm could matter beyond security patches. Chrome often serves as the control surface for cameras, dashboards, streaming services, and connected devices, so improvements to media, scrolling, browser security, and web APIs can reach those experiences sooner.

Chrome now updates every two weeks

Since 2021, Chrome had generally followed a four-week major release cadence. That changed during the transition to Chrome 153: Chrome 152 became Stable on August 25, 2026, and Chrome 153 followed just two weeks later on September 8, officially beginning the new two-week schedule across desktop, Android, and iOS.

Chrome 154 is scheduled for Stable release on September 22 and was already in Beta when Chrome 153 launched. Google is also keeping an eight-week Extended Stable option for managed organizations that need more time between major feature updates.

ChromeOS follows the new two-week branching rhythm but keeps a four-week Stable cadence by promoting only even-numbered milestones to Stable.

Why is Google speeding up Chrome?

Google says the shorter cycle is intended to make the web platform fresher, safer, and easier to manage when changes cause problems. Smaller milestones can let developers deliver modern web APIs and interoperability improvements within weeks instead of waiting months.

The schedule can also reduce the time between discovering a vulnerability and delivering a patched milestone to a broad user base. Chrome already ships security updates as needed, but a two-week major rhythm gives larger hardening changes a faster path.

Chrome 153 adds spatial audio

Chrome 153 adds native decoding and playback support for the Immersive Audio Model and Formats, or IAMF, inside HTML media elements through Media Source Extensions. IAMF is an open, royalty-free spatial-audio format supporting channel-based, scene-based, and object-based presentations.

The standard gives web developers a way to deliver immersive 3D audio across compatible devices without depending on proprietary spatial-audio formats or complex JavaScript channel routing. Chrome 153 separately adds a WebAudio feature that lets developers configure the audio render-quantum size.

Rust strengthens a critical browser component

Chrome 153 also expands the use of a memory-safe Rust implementation for XML parsing in cases that do not require XSLT. The affected scenarios include DOMParser, responseXML in XMLHttpRequest, directly opened SVG documents, and SVG images loaded as external resources.

The new parser is intended to replace Chromium’s use of libxml2, which is written in C. Google says the Rust implementation eliminates potential memory-corruption bugs in these XML-parsing paths while maintaining compatibility with existing web standards.

Scrolling and camera controls get better

Chrome 153 adds scroll-axis-lock, a CSS property that lets developers prevent browsers from automatically locking a scrolling gesture to one axis. The separate single-axis scroll-container feature is also available for developer testing in Chrome 153 Beta, Dev and Canary, allowing one axis to scroll while the other remains clipped.

Chrome 153 also introduces dedicated <camera> and <microphone> HTML elements. These user-activated controls give web apps a browser-managed way to request video or audio capture while preserving Chrome’s existing permission safeguards.

JavaScript gets another useful addition

Chrome 153 adds support for Iterator.zip(), a JavaScript capability that lets developers process multiple iterators together. It is designed for situations where separate data streams need to advance in lockstep rather than being handled through more complicated custom logic.

The practical applications can include synchronizing sensor feeds, coordinating animation timelines, or processing parallel data transformations. Developers still decide whether the feature fits a particular application, but native support can reduce the amount of supporting code required.

Little-known fact: Google and Samsung already market IAMF-based spatial audio under the consumer brand “Eclipsa Audio,” which debuted on Samsung’s 2025 TV and soundbar lineup.

What the new cycle means for users

For most people, the biggest difference should be less dramatic than the version numbers suggest. Updates will be smaller and more frequent, which can make individual downloads and installations feel less significant than the larger monthly milestones Chrome previously delivered.

Users should also gain faster access to web platform features and security hardening. A developer feature that misses one release cutoff will generally have another two-week opportunity, while fixes and compatibility improvements can move through the pipeline more quickly.

Developers face a tighter testing rhythm

Google’s engineering cadence now branches new milestones, promotes Betas, and ships new Stable releases at two-week intervals rather than four-week intervals. A feature that misses one milestone therefore has another release train approaching roughly two weeks later.

That faster pipeline makes Chrome Beta more important for web teams. Google recommends testing sites against Beta and monitoring the Chrome Status Roadmap for upcoming platform changes. Under the new schedule, Beta generally reaches testers roughly three weeks before that milestone’s Stable release.

For websites serving smart-home dashboards or media controls, the tighter cadence means compatibility testing needs to become more regular. Teams still need to monitor APIs, layouts, media behavior, and device integrations as browser changes reach users more frequently.

AI and security are driving the shift

Google’s accelerated schedule arrives as AI changes both browser development and the security environment. Automated AI tools can increase the speed of vulnerability discovery and exploit development, making shorter windows between security work and widespread deployment increasingly valuable.

AI is also pushing browsers into a more competitive phase, with products such as Brave, DuckDuckGo’s browser, Perplexity’s Comet, and Opera Neon experimenting with new experiences. Faster Chrome iteration gives Google a more responsive platform for its own AI features and browser improvements.

Little-known fact: Perplexity, maker of the AI-powered Comet browser, previously offered to buy Chrome outright for $34.5 billion.

Chrome’s faster rhythm changes the web

Chrome’s move follows earlier changes in its release history. Before 2021, major Chrome releases arrived about every six weeks, followed by the four-week era that became standard through 2026. The new schedule compresses that cycle again.

Chrome 153 therefore represents more than another browser version number. It establishes a faster pipeline for security work, web standards, media capabilities, and performance improvements, while the Extended Stable channel preserves a slower option for organizations with stricter validation requirements.

For smart-home users, the practical takeaway is straightforward: the browser controlling cameras, dashboards, streaming services, and IoT tools will evolve more often. Smaller milestones could mean quicker fixes and improvements, provided websites and connected services keep pace with Chrome’s faster rhythm.

TL;DR

• Chrome 153 starts Google’s two-week major release schedule for desktop, Android, and iOS, replacing the four-week cadence used since 2021.
• Chrome 154 is scheduled for September 22, while enterprise and education customers can continue using the eight-week Extended Stable channel.
• Native IAMF decoding expands Chrome’s support for spatial audio, giving compatible web media services a more open path across modern connected devices.
• Rust-based XML parsing improves a security-sensitive browser component by reducing exposure to memory-corruption and buffer-overflow vulnerabilities.
• New scrolling controls and dedicated camera and microphone elements give developers more precise tools for smoother, richer web applications today.
• Users should receive smaller updates more often, while developers will need to test more regularly as Chrome’s Beta and Stable cycles accelerate.

This article was made with AI assistance and human editing.

If you liked this, you might also like: