Chrome moves to a two-week release cycle

From 8 September 2026, Chrome 153 introduces a new release rhythm: a stable version every two weeks instead of every four. Announced by Google in March, the change spans Desktop, Android and iOS, and reshuffles the testing calendar for web teams.

#What changes on 8 September

Chrome 153 marks the switch to a two-week cycle. Version 154 follows on 22 September, 155 on 6 October, and so on: roughly twenty-six stable versions a year, where the monthly cadence produced thirteen. The Beta channel moves in step, each beta shipping three weeks ahead of its matching stable. The Extended Stable channel keeps its eight-week cycle for fleets that value stability over freshness.

#Why Google is speeding up

The logic is one of small batches. Closer releases carry fewer changes at a time, which shrinks the regression surface at each step and cuts the delay between a feature landing and reaching the public. Security fixes, performance gains and new APIs arrive sooner, without the “big update” effect of the monthly cycle. The move extends a path begun in 2023 with weekly security updates.

Pinning code to a Chrome version number was never a good idea; at twenty-six releases a year, it becomes untenable.

#Feature detection becomes the only viable strategy

Doubling the number of versions makes version sniffing even more fragile than it already was. The right practice is to test for the actual presence of an API or property rather than the engine version. The same reflexes that apply to adopting container queries or migrating to htmx 4.0 apply here: test the capability, plan a fallback, never assume a number.

// Détecter la capacité, pas la version du navigateur
if (CSS.supports('container-type: inline-size')) {
  document.documentElement.classList.add('has-container-queries');
}

if ('URLPattern' in globalThis) {
  const route = new URLPattern({ pathname: '/articles/:id' });
  // routage côté client sans dépendance
}

// Anti-pattern : ne jamais faire ceci
// const version = navigator.userAgent.match(/Chrome\/(\d+)/);
// if (Number(version?.[1]) >= 153) { /* ... */ }

#Adapting monitoring and tests

For teams, the point is not to track every version but to build a routine. Testing on the Beta channel gives three weeks of lead time to catch a behaviour change before it reaches users. Feature tracking runs through the Chrome Status Roadmap and the Chromium dashboard, which announce changes step by step. The security headers the browser ships, such as those covered in guidance on Content-Security-Policy, also evolve version by version: validating them continuously avoids nasty surprises.

#Key takeaways

Chrome now ships a stable version every two weeks from 8 September, about twenty-six a year, with Beta three weeks ahead and Extended Stable on its eight-week rhythm. The practical consequence fits in one sentence: feature detection and Beta-channel testing definitively replace manual version tracking.

Further reading: the official announcement on the Chrome for Developers blog, Get features faster with Chrome’s two-week release cycle.