Chrome Release Dates (2026): Every Version + What's Next

Chrome 152 is the current stable release, shipped August 25, 2026, four weeks after Chrome 151 (July 28). Chrome 153 is scheduled for September 8, the first release on a new two-week cadence that continues through 154 (September 22) and 155 (October 6).

Key takeaways

• Chrome 152 is current stable (August 25, 2026). Chrome 153 is scheduled for September 8.
• Chrome 153 (September 8) starts a two-week release cadence, confirmed through 154 and 155, replacing the four-week rhythm Chrome held for most of 2026.
• Chrome 151 finished deleting Manifest V2 from Chromium’s source. MV2 extensions stopped running for users back in Chrome 138 (July 2025). This was the last of the leftover code.
• No release through 155 adds native workspaces, session snapshots, or cross-tab search. That gap stays extension territory.

Current Chrome Version and What Ships Next

Chrome 151 became stable on July 28, 2026, four weeks after Chrome 150 (June 30). Chrome 152 shipped August 25, closing out the four-week era, and is the build most desktop installs are running per Chrome’s staged auto-update rollout. Check your own build at chrome://version. Anything below 152 means an update is pending.

Chrome Release Date Calendar: 148 Through 155

152 and 153 come from the Chromium schedule. Rows after 153 are projections. “Stable” marks the day the rollout starts. Most machines update within the following two weeks.

New rows get added as Chromium schedules further milestones. For anything past October, chromiumdash’s own schedule page is the primary source. The table is confirmed through 153, projected after.

Why Chrome’s Release Cadence Just Doubled

Chrome held a four-week rhythm through Chrome 152. Chrome 153, on September 8, 2026, is the first release on a two-week cycle, and Chromium’s schedule confirms the pattern through Chrome 155 (October 6). The gap between stable releases is now half of what it was for most of 2026.

Practical effect: security patches reach users roughly twice as often. The tradeoff lands on extension developers and IT admins running Extended Stable channels, who get half the lead time to test against a new milestone before it reaches users. The mechanics, including what happens to Extended Stable, are covered in Chrome’s two-week release cycle explained.

The Manifest V2 Cleanup Chrome 151 Finished

One dated fact matters here. Manifest V2 extensions stopped running on stable Chrome at version 138, back in July 2025. Chrome 150 removed the first of two leftover developer flags, and Chrome 151, live since July 28, 2026, deleted the remaining MV2 feature code and command-line overrides entirely. On August 31, 2026, the last MV2 listings were purged from the Chrome Web Store. The full sequence, with what it meant for uBlock Origin and other holdouts, is in the Manifest V2 end-of-life guide.

Practical takeaway: any extension you rely on today is Manifest V3, whether you noticed the switch or not.

What This Calendar Still Doesn’t Bring to Tabs

Across every milestone tracked here, Chrome 148 through the confirmed schedule for 155, the tab-management picture hasn’t moved. Chrome 146 stable March 2026. Vertical tabs flagless April 2026.. Since then, no named workspaces, no automatic session snapshots, no keyboard search across every open tab. Nothing on Chromium’s public roadmap through October changes that.

That gap is what SuperchargeNavigation covers from Chrome’s side panel: named workspaces (shared sign-in, no profile isolation), 50 rolling auto-snapshots taken every five minutes (at least about four hours (only added when tabs change)), and Alt+K to search open tabs, bookmarks, and history from any page. The core is free and runs without an account. Data stays on your machine apart from cross-device sync, which is on by default and rides Chrome’s own account sync. You can switch it off per device. Because it’s Manifest V3, neither the 151 cleanup nor the faster cadence touches it.

How to Check and Force Your Chrome Version

1. Open chrome://settings/help. Chrome checks, downloads any pending update, and prompts a relaunch.
2. Confirm at chrome://version. As of September 2026 you want milestone 152 or later.
3. To preview the next milestone early, Chrome Beta runs alongside stable and typically moves to the next number within days of a stable release.

If you’re checking whether you’re current, 152 is the number to look for as of September 2026. If you’re planning around a future release, trust chromiumdash over any article, this one included. Schedules occasionally slip. And if you were waiting for a release to bring workspaces or session recovery: stop waiting. Nothing through 155 has them, and the extension route above works on every version in the table.