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

Chrome 152 reached stable on August 25, 2026. For tab and memory users it added 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 closed the Manifest V2 era for good.

This is a confirmed read of what shipped. Items below are traced to the full Chrome 152 release notes and the Chrome release schedule.

Chrome 152 Release Date and the 153 Cadence Shift

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

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 shipped 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 138 (July 24, 2025) disabled MV2 in-browser for consumers. uBlock Origin was dead on stable from there. Chrome 150 (June 30, 2026) removed the last developer flag.
• Chrome 139 (2025) removed the enterprise MV2 policy. Chrome 151 (July 28, 2026) deleted the last code and flags.
• 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. Tools that never migrated are dead, not degraded. An MV2 extension has not run on stable Chrome since July 2025. The August 31, 2026 store purge deleted its listing, so the dead tool is also gone from the store.

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

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

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 (one sign-in, one cookie jar, no profile isolation), 50 automatic snapshots taken every five minutes, and Alt+K to search open tabs, bookmarks, and history from any page. Both are free, no account. SuperchargeNavigation keeps data local; sync (on by default) rides Chrome’s account.

Before You Update: A Quick Check

If you are still on an older build, open chrome://settings/help to pull 152, then confirm milestone 152 at chrome://version. If an extension you depend on went quiet in late June or July, 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 September 4, 2026): Chrome 152 features confirmed against the shipped milestone-152 release notes and the Chromium release schedule.