 Ben Mason  Deepak Ravichandran
Published: September 8, 2026
Earlier this year, we [announced our plan](https://developer.chrome.com/blog/chrome-two-week-release.md.txt) to
shift Chrome from a four- to a two-week release cycle with the goal of
delivering new features, performance improvements, and bug fixes faster. Today
we're putting that plan into action with the launch of
**Chrome 153 on Desktop,Android, and iOS.**
## Setting the standard for shipping velocity
Chrome has long led the industry in accelerating web innovation. In 2010, we
pioneered the "[Release Early, Release
Often](https://blog.chromium.org/2010/07/release-early-release-often.html)"
philosophy, establishing a predictable release cadence that transformed how the
web evolves. Building on that foundation, we took another major step in 2021 by
[moving to a four-week release
cycle](https://blog.chromium.org/2021/03/speeding-up-release-cycle.html),
further accelerating feature delivery and patch management. By shifting to a
two-week release cycle today, we are once again raising the bar for browser
delivery and security, setting a standard that many across the web ecosystem are
also adopting
\[[Microsoft](https://blogs.windows.com/msedgedev/2026/06/11/faster-updates-enterprise-friendly-schedule-the-new-microsoft-edge-release-cycle/),
[Mozilla](https://groups.google.com/a/mozilla.org/g/dev-platform/c/qlaQ1YSlOP8),
[Brave](https://github.com/brave/brave-browser/wiki/Brave-Release-Schedule)\].
This increased cadence is a win for the entire web. When browser updates are
deployed more quickly, developers can ship modern web features with confidence,
knowing that deployment windows are tighter, interoperability updates arrive
quickly, and safety improvements reach users faster across platforms.
## Faster fixes for greater security
Our shift to a faster release cadence works directly in tandem with our
[security
strategy](https://blog.google/security/chrome-stronger-with-every-update/). With
automated AI discovery tools and community bug reports generating higher patch
volume, shorter release cycles make managing security fixes significantly
simpler. Shrinking the window between landing a fix in the public codebase and
delivering it to end users keeps the "N-day" patch gap as small as possible,
helping us protect against fast-moving threats.
## What changes for developers, users and enterprise admins
| **Channel / Audience** | **From Chrome 153** |
|---|---|
| **Web developers** | Features reach Stable every two weeks. Scope per release is smaller, making regression isolation faster. |
| **Users** | Receive smaller, more frequent feature updates and quicker security fixes. |
| **Enterprise admins and embedders** | The two-week Stable option becomes the most secure choice and should be used by most of your enterprise users. The[Extended Stable](https://support.google.com/chrome/a/answer/16942104) channel is available for customers who cannot accommodate a two-week release cycle. |
> [!NOTE]
> **Note:** If your organization or application relies on Extended Stable, keep in mind that while security fixes continue to be backported on the regular weekly schedule, major feature updates arrive every eight weeks (for example, Chrome 156, Chrome 160). Ensure your test pipelines account for these eight-week milestone boundaries when planning enterprise deployments.
## Looking ahead
As Chrome 153 rolls out to devices today, [Chrome 154 Beta](https://developer.chrome.com/blog/chrome-154-beta.md.txt)
is already available
for testing, ahead of its Stable release scheduled for **September 22**.
We encourage all developers to bookmark the
[Chrome Status Roadmap](https://chromestatus.com/roadmap) and test your sites against Chrome
Beta channel releases. Together with our peers across the web platform, we look
forward to building a faster, safer, and more dynamic web environment with every
update.