Tab Suspender Chrome Extensions: 6 Options Compared (2026)

Key takeaways

• Chrome Memory Saver suspends tabs only after RAM pressure builds. Timer-based extensions act proactively after idle time, regardless of system state.
• SuperchargePerformance (v1.4.3, June 2026) adds ad blocking and a RAM dashboard to tab suspension. Tab Wrangler (v8.3.0, April 30 2026) auto-closes and logs old tabs.
• Auto Tab Discard works but hasn’t updated on CWS since February 2024. The Great Suspender forks (Reloaded and Marvellous) are volunteer-maintained and both live on CWS.

Six open-source or free tab suspenders exist for Chrome in 2026. One hasn’t shipped a CWS update in over two years. One was banned for malware and survived as two forks. The right pick depends on what you’re actually after: proactive suspension, auto-close with a log, a memory dashboard, or ad blocking bundled in. This page covers the verified current state of each.

Why RAM Matters for Tab-Heavy Chrome

Each Chrome tab runs in its own renderer process. An active tab with a complex SPA, auto-refreshing feed, or video player can hold 200-400MB of RAM. At 30 tabs, Chrome can push past 6GB even before you open DevTools or a Figma file.

Tab suspension calls chrome.tabs.discard() — Chrome’s native tab lifecycle API. The tab’s renderer process exits, freeing 90-95% of that tab’s RAM. The tab stays visible in the strip with its favicon and title. Clicking it triggers a normal page reload. No scroll position is preserved (a Chrome API limitation that applies to every tab-discard tool, not just extensions).

Battery life tracks with RAM usage. Fewer active renderer processes mean fewer wakeups, less JavaScript executing in background tabs, and lower CPU temperature on laptops — the reason tab suspension matters beyond just raw memory numbers.

Chrome’s Built-in Memory Saver: The Baseline

Chrome 110 (launched February 2023) introduced Memory Saver under Settings > Performance. It discards inactive tabs when the system signals memory pressure. It ships with three modes — Moderate, Balanced (recommended), and Maximum — that adjust how soon a tab goes inactive.

The core limitation: it’s reactive. Memory Saver waits until Chrome detects the system is under RAM pressure before discarding anything. At 30 tabs, that can mean 2-3GB already consumed before the first discard fires.

Chrome 140 (September 2025) added an ML model that predicts how likely you are to revisit each tab. Tabs more likely to be revisited stay active; less-likely tabs get discarded first. This improves the reactive model but doesn’t change the fundamental timing — it acts when pressure arrives, not before.

What Memory Saver lacks: no configurable idle timer, no adjustable protection rules (it auto-exempts audio, video, screen share, downloads, forms, and pinned tabs, but you can’t tune that), no RAM savings dashboard, no visibility into which tabs were discarded and how much RAM was freed. It does let you mark specific sites “always keep active.”

For 10-15 tabs on a machine with 16GB RAM, Memory Saver set to Maximum is probably enough. At 20+ tabs or on a 8GB machine, the proactive vs. reactive gap becomes a real constraint.

What Separates Good Tab Suspenders

Before the extension reviews, these are the criteria that actually matter:

Idle timer control. Can you set how long a tab is idle before suspension? 5 minutes vs. 15 minutes changes the tradeoff between RAM savings and the annoyance of reloading tabs mid-task.

Audio tab protection. A tab playing music or a call should never be suspended mid-playback. This requires checking tab.audible before discarding — most extensions do it but not all do it reliably.

Pinned tab and form-input protection. Suspending a pinned Gmail tab or a tab with an unsaved form is disruptive. These protections are table-stakes but worth verifying.

Per-site whitelist. Figma, Notion, Slack, and other web apps break on reload. You need a way to exclude them without disabling suspension globally.

MV3 compatibility. Chrome disabled Manifest V2 extensions for standard users at Chrome 138 (June 2025). Any extension still on MV2 is dead for most users.

Update cadence. Chrome ships every four weeks. An extension unupdated for a year may still work, but it accumulates silent drift against API changes, permission model updates, and new Chrome flags.

Additional features. Does the extension bundle anything useful beyond suspension — ad blocking, a memory dashboard, tab logging?

The 6 Extensions

SuperchargePerformance

v1.4.3 · ~2,700 weekly users · 4.56/5 (16 ratings) · Updated June 2026 · MV3

Chrome Web Store

SuperchargePerformance uses chrome.tabs.discard() with a multi-signal protection layer on top: 25+ web apps auto-protected without manual whitelist configuration (Figma, Notion, Slack, Discord, Gmail, Google Docs, Sheets, Slides, Drive, Calendar, Linear, Miro, Canva, Lucid, Airtable, Asana, Monday, Teams, Spotify, YouTube Music, and more), audio detection via tab.audible, form-input detection, and pinned-tab protection. Timers are configurable: 15 minutes on the free tier, 5 minutes on the medium tier, custom seconds on PRO.

The RAM badge updates in real time — a running counter of memory freed across the session, rendered via OffscreenCanvas so it doesn’t inflate its own memory footprint. The popup shows per-tab savings.

On top of suspension, SuperchargePerformance runs a 186,645-rule DNR blocklist (compiled from 22 sources) that blocks ads, trackers, and malware at the network layer with zero per-request JavaScript overhead. This reduces active tab RAM by removing heavy assets before they load. AutoConsent handles cookie banners (2,800+ CMP rules). Stop Autoplay blocks video and audio from starting on load.

Zero telemetry, 100% local storage by default, no account required. Free core tier handles tab suspension and basic blocking.

Pick this if you want tab suspension, ad blocking, and memory metrics in one install with active maintenance.

One tradeoff: smallest user base (~2,700 weekly users) and fewest public reviews of any option listed here.

Tab Wrangler

v8.3.0 · 70,000 users · 4.4/5 (947 ratings) · Updated April 30, 2026 · MV3

Chrome Web Store

Tab Wrangler operates differently from the others: it auto-closes tabs after a configurable inactivity period rather than suspending them. Closed tabs go into a local log called the Corral, sortable by recency. Any tab in the Corral can be reopened with a click.

This distinction matters. Suspension keeps the tab in the strip (memory freed, tab still visible). Closing removes the tab entirely and saves its URL. If you prefer a cleaner tab count and don’t mind tabs disappearing from the strip, Wrangler’s approach is tidier. If you want to see suspended tabs at a glance, a suspender is the right choice.

Protections are configurable: pinned tabs, tabs with unsaved forms, and tabs that have been active recently can all be excluded. Lock any tab to prevent auto-close. MV3, open-source (MIT), actively maintained with GitHub commits through April 2026.

Pick this if you want a clean tab count with a recoverable log, not just suspended tabs in the strip.

Note: closing and restoring from the Corral is a different workflow from suspension. Pages reload on restore just as they do on discard — but the tab is gone from the strip until you explicitly recover it.

Auto Tab Discard

v0.6.8.2 · 100,000 users · 4.2/5 (364 ratings) · Last CWS update February 17, 2024 · MV3

Chrome Web Store

Auto Tab Discard does one thing cleanly: it calls chrome.tabs.discard() on idle tabs after a configurable timer. Audio protection, pinned tab protection, and form-input detection are all present. Per-domain whitelist. No dashboard, no ad blocking, no additional features.

It is MV3 and shows 100,000 users on CWS — the largest user base of any dedicated tab suspender on this list. The project is open-source.

The concern: its last CWS update was February 17, 2024 — more than two years before now. Chrome has shipped over 25 stable releases since then. The extension continues to work on current Chrome, and its MV3 architecture makes it less fragile to Chrome updates than MV2 extensions were, but no one has pushed a CWS patch in over two years. For users who want ongoing maintenance, that gap is worth knowing.

Pick this if you want a single-purpose, open-source suspension tool with no extras and the update gap doesn’t concern you.

Worth knowing: no CWS update since February 2024. Works on Chrome 149, but maintenance trajectory is unclear.

OneTab

2,000,000 users · 4.5/5 · Updated March 22, 2026 · MV3

Chrome Web Store

OneTab is not a suspender — it’s a tab consolidator. Clicking the OneTab icon closes all current tabs and converts them into a list on a single web page. You can restore individual tabs or all of them at once. Tabs can be shared as a URL or exported.

It belongs on this list because many people install it when they want to reduce RAM, and it does reduce RAM — by closing all your tabs. The tradeoff is that every restored tab requires a network reload, and the “tab list” page is a new tab you have to manage. There is no automatic suspension after idle time and no per-tab protection logic.

The practical question: if you’re comfortable with all your tabs disappearing into a list and selectively restoring them, OneTab works. If you want tabs to remain in the strip while sleeping, it’s the wrong tool.

March 2026 update keeps it current on Chrome 149. The rating across 2 million users reflects years of mixed opinions about the single-click-closes-everything behavior.

Pick this if you want to batch-close all tabs into a recoverable list rather than keep them suspended in the strip.

The limitation: all tabs close on activation; no automatic idle-based suspension.

The Marvellous Suspender

v8.1.3 · 90,000 users · 4.3/5 · Updated December 22, 2025 · MV3

Chrome Web Store

Marvellous Suspender is a community fork of The Great Suspender, maintained by a single volunteer (gioxx). It uses a custom suspension page rather than chrome.tabs.discard() — inactive tabs show a dedicated screen before reloading. This method can create an extra history entry depending on configuration: pressing Back after a suspended tab reactivates sometimes lands you on the suspension screen rather than the previous page.

The extension is MV3, open-source, and actively used at 90K users. The December 22, 2025 update is roughly six months old as of June 2026, which is within normal volunteer software cadence. See the full status page for a deeper look at the fork’s history and security posture.

Pick this if you want the original Great Suspender UX and trust the open-source volunteer maintenance model.

One friction point: the custom suspension page can create an extra history entry in some configurations, and updates depend on one volunteer developer.

Great Suspender Reloaded

v2.0.0 · 40,000 users · 4.2/5 · Updated May 1, 2026 · MV3

Chrome Web Store

The other surviving fork. Great Suspender Reloaded (maintained by tim-dim-ext on GitHub) shipped v2.0.0 on May 1, 2026 — the most recently updated free suspender on this list. It uses the same custom suspension-page approach as Marvellous Suspender.

Smaller user base than Marvellous (40K vs. 90K), but faster update cadence in 2026. The GitHub repo shows commits through April 30, 2026. The CWS title reads “Tab Suspender | The Great Suspender 2026,” which explains its search visibility.

For more context on both forks and the original Great Suspender’s history, see Great Suspender Alternatives in 2026.

Pick this if you want the most recently updated Great Suspender fork and can accept a smaller community than Marvellous.

Still a one-developer volunteer project, with the same structural caveats as any community fork.

Full Comparison Table

Data: Chrome Web Store listings verified June 2, 2026.

Picks

When Not to Install a Tab Suspender

Chrome Memory Saver handles most single-user scenarios adequately if:

• Your tab count stays below 15 on a regular basis
• You have 16GB RAM and typically run Chrome with one or two windows
• You don’t care about a RAM counter or per-tab metrics

Adding an extension has a cost: startup time, a small background process, and permissions. If your setup rarely hits memory pressure, the native option is the right default.

The case for an extension is clearest when you routinely open 30+ research tabs, work with Figma or linear open alongside 20 other tabs, or run Chrome on a machine with 8GB RAM shared with other apps. At that point, the proactive timer model and the savings gap over Memory Saver’s reactive baseline become concrete.

A tab suspender also can’t fix a Chrome process that has leaked memory through a bug. If Chrome’s total RAM keeps climbing after tabs are suspended, see Fix Chrome Memory Leaks on Windows 11 or the macOS equivalent.