Chrome 149 Release Date + Chrome 150–153 Calendar (2026)

Chrome 149 released to stable on June 2, 2026 (build 149.0.7815.x) and was replaced by Chrome 150 on June 30. The next stable dates, from Chromium’s official schedule: Chrome 151 on July 28, Chrome 152 on August 25, and Chrome 153 on September 8, 2026 — the first release on the new two-week cadence.

Key takeaways

• Chrome 149 shipped June 2, 2026 and stopped being current on June 30, when Chrome 150 took over.
• Chrome 151 (July 28) deletes the last Manifest V2 code. MV2 extensions already stopped running in Chrome 138; 151 removes the leftover machinery.
• Chrome 152 (August 25) is the last four-week release. Chrome 153 arrives two weeks later, on September 8.
• No milestone on this calendar adds native workspaces, session snapshots, or tab search. Those stay extension territory.

Chrome Release Date Calendar: 148 Through 153

Every date below comes from Chromium’s milestone schedule at chromiumdash.appspot.com, checked July 2026. “Stable” is the day the rollout starts; most machines update within the following two weeks.

The four-week rhythm holds through 152, then compresses. If you track version numbers for compatibility testing, September is when the pace doubles.

Chrome 151 on July 28: The MV2 Cleanup Finishes

One dated fact matters here. Manifest V2 extensions stopped running on stable Chrome at version 138 (July 2025); Chrome 150 removed the first of two leftover developer flags, and Chrome 151 deletes the remaining MV2 feature code entirely. On August 31, 2026, the last MV2 listings also disappear from the Chrome Web Store. The full sequence, with what it means for uBlock Origin and other holdouts, is in the Manifest V2 end-of-life guide.

Practical takeaway: any extension you rely on past July 2026 must be Manifest V3. If it still works today on Chrome 150, it already is.

Chrome 153 Starts Shipping Every Two Weeks

Chrome 152 (August 25) closes out the four-week era. Chrome 153 lands September 8 — a two-week gap, and the new normal. Security fixes reach you faster; extension developers get half the time to react to breaking changes. The mechanics, including what happens to the Extended Stable channel for enterprises, are covered in Chrome’s 2-week release cycle explained.

What Shipped in Chrome 149

Chrome 149’s feature list was confirmed in the official release notes at developer.chrome.com and carried through to stable unchanged. The headline items:

BFCache WebSocket disconnect. The back/forward cache stores a full page snapshot so the back button restores instantly. Before 149, any page holding an open WebSocket was ineligible, which meant slow back-navigation in Notion, Figma, Linear, and Slack Web. Chrome 149 closes the socket on cache entry instead of refusing to cache; the app’s reconnect logic picks up when you return. This is the one 149 change a tab-heavy user feels daily.

CSS Gap Decorations. Grid and flexbox gaps became directly styleable, replacing the fragile per-item-border workaround. A developer feature with no user-visible behavior change.

Security tightening. SVG filters no longer apply to cross-origin iframes (a rendering-isolation fix Safari already shipped), and the CSS AccentColor keyword was restricted to installed PWAs to shrink a fingerprinting vector.

What 149 did not include: the IndexedDB SQLite storage backend, frequently misattributed to this release. It targeted Chrome 150 per chromestatus.com and never appeared in the 149 notes.

What None of These Releases Add for Tab Users

Across all six milestones on the calendar, the tab-management picture is static. Chrome 146 shipped native vertical tabs, and since then: no named workspaces, no automatic session snapshots, no keyboard search across every open tab. Nothing on the public roadmap through 153 changes that.

That set is what SuperchargeNavigation covers from Chrome’s side panel, as of July 2026: named workspaces with full isolation between projects, 50 rolling auto-snapshots taken every five minutes (about a four-hour recovery buffer), and Alt+K to search open tabs, bookmarks, and history from any page. The core is free, it runs without an account, and everything stays on your machine unless you switch on Chrome-native sync. Because it is Manifest V3, the 151 cleanup and the faster cadence leave it alone.

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 July 2026 you want milestone 150 (build 150.0.7871.x).
3. To preview the next milestone early, Chrome Beta runs alongside stable; the desktop beta channel moved to 151 on July 3.

If you landed here for the Chrome 149 date: June 2, 2026, and it has already been superseded. If you are planning around a future release, trust chromiumdash over any article, this one included — schedules occasionally slip. And if the release you were waiting for was supposed to bring workspaces or session recovery, stop waiting: no milestone through 153 has them, and the extension route works on every version in the table.