6 BEST Chrome Extensions to Reduce RAM (2026, Tested)

Chrome with 20 tabs typically uses 1.5–2 GB RAM. Ad-heavy tabs push that to 3 GB+ because each ad network spawns its own iframe process. Tab suspenders and ad blockers reduce different parts of this — combining both cuts memory 70%+.

Key takeaways

• Open Shift+Esc right now — the number you see is mostly ad subframes and idle renderer processes, not your actual tabs.
• Tab suspenders and ad blockers solve different problems. Suspenders free renderer memory from idle tabs. Blockers prevent ad iframes from loading at all. The biggest wins come from combining both.
• The Great Suspender is dead (MV2 removed 2025). Auto Tab Discard and SuperchargePerformance are the active MV3 replacements with real install bases.

You open Chrome’s Task Manager for the first time — Shift + Esc — and stare at the number: 3.1 GB across 18 tabs. Three of those tabs are from news sites you opened this morning. Each has spawned eight or nine Subframe processes, one per ad unit, each consuming 50-80 MB. The tabs themselves are barely the problem.

Two categories of extension attack this from different angles. Tab suspenders release the renderer process entirely from idle tabs — the tab stays visible in the strip but is no longer burning memory. Ad blockers prevent the heavy resources from loading in the first place, cutting the subframe count per tab.

What Drives Chrome’s RAM Usage

Before choosing an extension, the mechanism matters. Chrome’s multi-process architecture gives each tab, iframe, and service worker its own OS process. A single ad-heavy page can generate 10-15 Chrome processes: main renderer, ad subframes, network service, GPU compositing. That’s what the 3 GB reading is reflecting.

Tab suspension attacks the first row. Ad blocking attacks the second. Neither touches the GPU process or utility processes. For those, a Chrome restart is the only lever.

The 4 Extension Approaches (and What Each Ignores)

Extensions that reduce Chrome RAM fall into four functional categories. Most focus on one. The rare few combine two.

Tab suspenders call chrome.tabs.discard(), Chrome’s official API for releasing a tab’s renderer process. The tab remains in the strip and reloads on click. This works on any tab regardless of what’s on it. It doesn’t help with pages you’re actively browsing.

Ad and tracker blockers use Chrome’s Declarative Net Request (DNR) API to block network requests before they load. Fewer ad iframes means fewer subframe processes means lower RAM per tab. The effect compounds: blocking also speeds up page load because those requests never fire.

Tab managers like OneTab and Session Buddy reduce RAM by closing tabs and storing URLs — not suspending them. You lose live state (scroll position, form data, video timestamps). Effective for clearing clutter; not the same as suspension.

Script blockers like NoScript prevent JavaScript execution. This can dramatically reduce per-tab memory on JS-heavy pages but breaks most modern sites. Firefox-first, limited practical Chrome use.

Full Comparison Table

SuperchargePerformance: Suspension + Blocking Combined

The only extension that handles both levers in a single install. Tab suspension via chrome.tabs.discard() — the official Chrome API — discards idle tabs after a configurable timer. 25+ web apps are auto-protected and never suspended: Figma, Notion, Slack, Google Docs, and others that break when discarded. The RAM dashboard shows live per-tab memory so you can see what the extension is actually doing.

The blocking layer runs 186K+ DNR rules from 22 sources across 3 tiers (basic, standard, aggressive). Ads, trackers, analytics scripts, fingerprinting libraries, and malware domains. On a news site that previously spawned 10 ad subframes, those processes simply don’t start.

Honest limitations: uBlock Origin has deeper filter list coverage for blocking. Auto Tab Discard is lighter-weight if suspension is all you need — no blocking overhead, smaller extension. SuperchargePerformance earns its place when you want both layers without managing two extensions.

Zero telemetry. 100% local. Free core. No account required. Chrome Web Store Featured badge.

Auto Tab Discard: The Suspension-Only Option

Auto Tab Discard does one thing: suspends idle tabs using chrome.tabs.discard(). No ad blocking, no script control, no dashboard. Configure the inactivity timer (default: 10 minutes, adjustable up or down), set exclusions for pinned or audible tabs, and the extension handles the rest.

The footprint is minimal — no background processing beyond the timer checks, no filter rule compilation. For users who already run uBlock Origin and just want automatic suspension on top, this is the cleanest pairing. The extension has been on the Chrome Web Store for years and migrated to MV3.

Best for: users who have a separate ad blocker and want pure suspension with no overhead.

uBlock Origin: The Blocking Standard

v1.71.0, updated May 2026. The full uBlock Origin remains a Manifest V2 extension — Raymond Hill has not ported it to MV3, since MV3 cannot support its dynamic per-site rules and full cosmetic filtering. It preserves cosmetic filtering, dynamic per-site rules, and the network request logger: the deepest filter coverage available in a Chrome extension. It still installs and runs on current Chrome, though Google’s MV2 phase-out means its long-term Chrome future is uncertain.

On a 20-tab session with ad-heavy sites, blocking the ad networks means fewer subframe processes and meaningfully lower RAM — not from suspension, but from preventing those resources from loading at all. The service worker has a small background footprint (single-digit MB).

uBlock Origin Lite is the MV3 variant: no persistent background worker, declarative-only rules. Less coverage, zero overhead, and the version Google’s MV3 transition keeps viable on Chrome long-term. Useful on Chromebooks or constrained machines where every background process counts.

Best for: users who already have suspension handled and want maximum blocking coverage.

OneTab: Trading Live State for Memory

OneTab collapses all open tabs into a list, closes them, and shows you a single page of saved URLs. RAM drops to near zero for those tabs. The trade-off: you lose live state. Video timestamps, scroll positions, active form data — gone. When you restore a tab, it reloads from scratch.

For research sessions where you’ve accumulated 40 tabs of reference material you’re done actively reading, OneTab works well. For tabs you might return to mid-session with state intact, suspension is the right tool.

~3 million CWS users. Free. MV3.

Session Buddy: Session Save and Close

Session Buddy saves complete tab sets by name and closes them. Where OneTab is quick and flat, Session Buddy is organized and searchable. You can save a “Research - Competitor Analysis” session, close all those tabs, and restore later from a named entry.

Same trade-off as OneTab: closing means losing live state. Where it wins over OneTab is organization — sessions are named, dated, and searchable, which matters when you accumulate dozens of saved sets.

$0 free tier. Paid tier adds backup sync. MV3.

Chrome’s Built-in Memory Saver vs Extensions

Chrome 108 added Memory Saver. Chrome 140 (September 2025) improved it with ML-based prediction that estimates how likely you are to revisit each tab before discarding it — behavior that carries forward through Chrome 149.

Memory Saver since Chrome 140 is better than it was — ML prediction reduces unnecessary discards of tabs you revisit frequently. But it’s reactive: it only fires under memory pressure. An extension with a timer fires proactively. On a 16 GB machine that never hits pressure thresholds, Memory Saver may never trigger at all. An extension with a 30-minute timer reclaims that memory regardless.

For users on 8 GB machines who work with 10-15 tabs and notice occasional slowdowns, Memory Saver alone may be sufficient. For heavier workloads, extensions deliver consistent savings that system pressure thresholds don’t.

How Much Can You Actually Save

Combining suspension and blocking on a typical 20-tab session with mixed site types:

• Suspension alone (Auto Tab Discard, 30-min timer): 15 of 20 tabs discarded → ~900 MB-1.4 GB freed from renderer processes
• Blocking alone (uBlock Origin): ad iframes blocked across all tabs → ~300-600 MB fewer subframe processes
• Both combined (SuperchargePerformance): typically 1.5-2.0 GB reclaimed on a 20-tab session, measured via Chrome Task Manager

These numbers come from Chrome Task Manager readings across mixed browsing sessions (news, SaaS, social media). Your results depend on which sites you have open and how long tabs have been running. Measure your own: press Shift+Esc, note total memory, enable the extension, check again after 30 minutes.

Which Setup to Use

• Suspension + blocking, one extension, zero config: SuperchargePerformance
• Suspension only, lightest footprint: Auto Tab Discard
• Maximum blocking coverage, suspension handled separately: uBlock Origin + Auto Tab Discard
• Quick RAM recovery, don’t need live tab state: OneTab
• Organized session management, named saves: Session Buddy
• Light usage, 10 or fewer tabs, 16 GB+ RAM: Chrome’s built-in Memory Saver (no extension needed)
• Heavy workload, 20+ tabs, 8-16 GB RAM: SuperchargePerformance (consistent savings, not pressure-triggered)