# Chrome 152: What Changes for Tab and Memory Users? (2026)

> Chrome 152 (stable Aug 25, 2026) adds near-zero native tab or memory tools, but it seals the Manifest V2 shutdown. What changes, plus the 153 cadence shift.

- Canonical: https://www.superchargebrowser.com/library/chrome-152-whats-new-tab-memory-users/
- Published: 2026-06-29
- Updated: 2026-07-13
- Source: SuperchargeBrowser (https://www.superchargebrowser.com)

Chrome 152 reaches stable on August 25, 2026, per Chromium's official schedule. For tab and memory users it adds almost nothing native. The one web-platform change worth knowing is the CPU Performance API (`navigator.cpuPerformance`, a 1–4 device tier). The bigger story: Chrome 152 closes the Manifest V2 era for good.

This is a forward-looking read. Items below are traced to chromestatus.com milestone-152 entries and the published Chrome release schedule, not the full 152 release notes, which aren't out yet. Anything still in flux is labeled as flagged or expected.

## Chrome 152 Release Date and the 153 Cadence Shift

Chrome 152 is the **last release on the four-week cycle**. Starting with Chrome 153 in September 2026, Google moves to a two-week cadence. Version numbers will then climb about twice as fast.

| Milestone | Stable date (as of July 2026) | Cadence |
|-----------|-------------------------------|---------|
| Chrome 150 | June 30, 2026 | 4-week |
| Chrome 151 | ~July 28, 2026 | 4-week |
| Chrome 152 | August 25, 2026 | 4-week (last) |
| Chrome 153 | September 2026 | 2-week (new) |

For most readers the cadence change matters more than any single 152 feature. Smaller, faster updates mean the gap between "a fix shipped" and "it reached you" shrinks. It also means version-pinned guides go stale faster, so check `chrome://version` rather than trusting a number you read months ago.

## What Chrome 152 Actually Changes for Tab and Memory Users

Short answer: one thing, and it's indirect.

The **CPU Performance API** is flagged to ship enabled-by-default in milestone 152 (chromestatus.com). It adds `navigator.cpuPerformance`, a read-only integer from 1 (weak) to 4 (fast), where 0 means unknown. A site can read your device tier and decide to drop heavy animations or serve a lighter media stream on low-end hardware.

What it does for you: on a tier-1 or tier-2 machine, well-built sites can choose to do less work, which can ease CPU and memory pressure. What it does not do: change anything about how Chrome itself manages tabs or RAM. There is no new suspension behavior, no Memory Saver upgrade, no tab-group change in the 152 entries.

If you came looking for a native fix for tab reloads or runaway memory, Chrome 152 is not it. That part of Chrome has not moved since the 146–151 stretch.

## Manifest V2 Is Fully Closed by Chrome 152

This is the real headline, and it predates 152 by two milestones.

- **Chrome 150** (stable June 30, 2026, one day after this article) removed the last flag keeping Manifest V2 extensions running. uBlock Origin's dynamic filtering stopped working.
- **Chrome 151** (~July 2026) cleared the remaining overrides, including the enterprise policies power users leaned on.
- **Chrome 152** (~August 2026) inherits a finished job. There is no MV2 left to disable.

The practical consequence for memory-conscious users: every tab suspender, ad blocker, and content filter you rely on must be Manifest V3 by the time 152 lands. Tools that never migrated are dead, not degraded. If an extension silently stopped blocking ads or stopped reclaiming memory in late June or July, the MV2 shutdown is the likely cause, not a bug on your end.

## What Chrome 152 Still Doesn't Add: Workspaces, Suspension, Snapshots

The gaps tab-heavy users have tracked since Chrome 146 stay open in 152.

| Capability | Native in Chrome 152? |
|------------|----------------------|
| Named workspaces that persist across restarts | No. Not on any milestone. |
| Rolling session snapshots (time-travel) | No. Not on any milestone. |
| Per-tab suspension with naming + scheduling | No. Memory Saver only, no controls. |
| Cross-tab + history keyboard search | No. Extension territory. |

Chrome's Memory Saver still discards inactive tabs, and that reclaims real RAM. But it gives you no naming, no per-site rules, and no session history. None of that changes in 152.

This is where our two extensions fit, and both are Manifest V3-native, so the 152 shutdown leaves them working. **SuperchargePerformance** suspends tabs via `chrome.tabs.discard()` with multi-signal protection (audio, pinned, and form-input tabs are spared), and on its default setting it unloads any tab over 200 MB after three minutes idle, ahead of the main timer. It also ships a 195K-rule MV3 blocklist for ad and tracker filtering. **SuperchargeNavigation** adds named workspaces with full isolation, 50 automatic snapshots taken every five minutes, and Alt+K to search open tabs, bookmarks, and history from any page. Both are free at the core, store data locally, and need no account.

## Before You Update: A Quick Check

When 152 lands, open `chrome://settings/help` to pull it, then confirm milestone 152 at `chrome://version`. If an extension you depend on went quiet recently, check its Chrome Web Store listing for a Manifest V3 version before assuming Chrome broke it.

If you need named sessions, scheduled suspension, or a search bar across every open tab, Chrome 152 still won't give you those. If you only want Chrome to free memory from idle tabs and nothing more, Memory Saver alone covers it.

> **Verification note (checked June 29, 2026):** Chrome 152 features confirmed against chromestatus.com milestone-152 entries and the Chromium release schedule. The full Chrome 152 release notes publish closer to the August stable date; this page will be updated if the flagged items shift.

---

Canonical URL: https://www.superchargebrowser.com/library/chrome-152-whats-new-tab-memory-users/