Chrome Two-Week Releases Begin With Version 153

Chrome two-week releases are now live. Google put the schedule announced in March into operation on September 8 with Chrome 153 across desktop, Android and iOS, creating smaller Stable milestones twice as often while retaining separate weekly security updates.

Key takeaways

Chrome 153 began the new cadence on September 8.
Stable feature milestones now arrive every two weeks.
Extended Stable remains available for organizations needing a slower validation cycle.

Everyone else is reporting a faster browser calendar; we are explaining how the new cadence changes testing evidence for developers and managed fleets.

Fact	Verified detail
Implementation date	September 8, 2026
First milestone	Chrome 153
Platforms	Desktop, Android and iOS
Stable cadence	Every two weeks
Extended Stable	Feature milestones every eight weeks; security fixes continue separately

How Chrome two-week releases work

Google’s September 8 implementation post says Chrome 153 starts a two-week Stable cycle across desktop, Android and iOS. TechCrunch and TechRadar independently confirmed that the planned change had taken effect. Google’s release record separately lists Chrome 153 desktop builds for Windows, macOS and Linux, making the rollout a concrete event rather than another schedule announcement.

The cadence applies to major Stable milestones, which carry browser capabilities and platform changes. It should not be confused with Chrome’s weekly security-update process. Google says more frequent, smaller milestones should make regressions easier to isolate and move fixes and features to users sooner.

Chrome 154 Beta was already available when Chrome 153 rolled out, with its Stable release scheduled for September 22. That overlapping pipeline is the operating mechanism: developers test the next milestone while the current one reaches users, shortening the interval without eliminating beta validation.

Chrome two-week releases change enterprise testing

For managed fleets, the calendar compresses the time between compatibility decisions. A company that previously treated each monthly milestone as a large certification project may need a continuous test lane covering authentication, extensions, internal web apps and device policies. Smaller releases can reduce the amount of change per test, but only if the checks are automated and produce evidence quickly.

Google recommends the regular two-week Stable option for most enterprise users and presents Extended Stable for organizations that cannot absorb that pace. Extended Stable receives major feature milestones every eight weeks, while security fixes continue on their own schedule. Administrators therefore should not describe the slower channel as “no updates”; it changes feature timing, not the obligation to patch.

The practical risk is version fragmentation. Desktop browsers may update while embedded Chromium products, virtual desktops or mobile fleets follow different operational windows. Teams should record browser version, operating system and test result together so a support ticket can be tied to the exact milestone that introduced a behaviour.

What web teams should change now

Developers should add Chrome Beta to automated compatibility tests and treat a failing test as a release-blocking signal only after reproduction against the relevant build. A two-week cadence leaves less room for a manual sweep at the end of each cycle, but it also gives teams earlier feedback when beta testing runs continuously.

Extension owners need the same discipline for manifest changes, enterprise policies and browser APIs. Our coverage of the Chrome V8 zero-day fix showed why version evidence matters during urgent patching. The new milestone rhythm adds another reason to identify the installed build before assuming that all users see the same platform behaviour.

Communications should distinguish feature milestones from security updates. Telling employees that Chrome now “updates every two weeks” can falsely suggest they may defer a weekly patch notification. The accurate message is that Stable feature versions advance every two weeks, while security releases can still arrive between them and may require a restart.

Chrome two-week releases turn browser compatibility into a continuous operational process: teams gain smaller change sets and faster delivery, but they also need automated beta testing, exact version records and a clear separation between feature milestones and security patches. The schedule is useful only when deployment evidence moves at the same speed.

Related Lapaas Voice reading: AI-assisted browser security research and Microsoft’s school AI safety standard.

Frequently asked questions

When did Chrome two-week releases begin?

Google started the new Stable milestone cadence on September 8, 2026 with Chrome 153 across desktop, Android and iOS.

Does Chrome now receive security fixes only every two weeks?

No. The two-week change applies to Stable feature milestones; Google continues separate weekly security updates and can issue urgent fixes when needed.

What should enterprises do if two weeks is too fast?

Google provides Extended Stable for slower feature-milestone adoption, while organizations must still plan for security fixes and verify the exact channel policy.