Chrome 153 began rolling out on September 8, 2026, launching Google’s two-week release cycle for the browser on desktop, Android and iOS. For developers and IT teams, the practical change is a shorter interval between major versions reaching users, making browser compatibility checks a more frequent planning task.
Google’s launch announcement confirms that the schedule announced earlier this year is now in operation. Chrome 154 is already available in Beta, with its Stable release scheduled for September 22, 2026. That date is a release target, not a statement that every device will update simultaneously.
Build testing around the new cadence
The original release plan moves both Beta and Stable from four-week to two-week cycles. Dev and Canary retain their existing schedules. Google also separates Chromebook delivery from the browser timetable because those releases require dedicated platform testing.
For a team maintaining a web application, a useful response is to include Chrome Beta in regular compatibility testing and review upcoming changes before each Stable milestone. Critical flows such as sign-in, payments and file uploads are sensible candidates for repeatable checks. This is a testing recommendation, not evidence that Chrome 153 breaks those functions.
The shorter calendar does not remove the need to assess individual changes. A new browser version number alone says little about whether a particular application needs work.
Feature releases and security updates are different
Extended Stable retains its eight-week feature schedule for organisations that need more time between major updates. Google says security fixes continue to be backported weekly. Teams using that channel should distinguish feature compatibility testing from the task of deploying security fixes.
In its July 30 security update, Google described a separate pilot for two security releases per week. That pilot should not be confused with the now-active two-week major release cycle.
Delivery also differs from installation. Google explains that downloaded browser updates are staged and applied when Chrome restarts. A faster release schedule therefore does not, by itself, establish that an organisation’s browsers are running the latest fixes. Deployment checks still need to confirm the version actually in use.
