How to Auto-Close Chrome Tabs (Suspension Is Better)

Key takeaways

• Tab Wrangler (v8.3.0, updated April 2026) auto-closes inactive tabs after a configurable timer and keeps a recoverable list — it works.
• Tab suspension frees 90-95% of a tab’s RAM while keeping tabs visible in the bar. Same savings, zero loss of context.
• Closing is the right call if you never go back. Suspension is right if you might — which is most people, most of the time.

You have 50 tabs open. You know you should close some. You also know you’ll need at least 15 of them later and won’t remember which ones. So you leave them all open and Chrome eats 6GB of RAM. What if tabs could close themselves — the ones you haven’t touched in an hour, the ones from yesterday’s research rabbit hole?

That instinct is right. The execution depends on what “close” actually costs you.

Auto-Close Extensions That Actually Work

Tab Wrangler is the main option here, and it’s a solid one. Version 8.3.0 is live on the Chrome Web Store as of April 30, 2026 — actively maintained on MV3. It does exactly what the name says: set an inactivity threshold (default is 20 minutes, configurable to anything), and tabs that go untouched get closed automatically. Pinned tabs and audio tabs are protected.

Tab Wrangler’s recovery list — the Tab Corral — is a built-in list of everything Tab Wrangler has closed. You can reopen from there at any time. Tab Wrangler also respects a per-domain whitelist, so you can lock specific sites open permanently.

Chrome itself has no native auto-close feature. Memory Saver (available in Chrome Settings → Performance) suspends inactive tabs, but it never closes them — they stay in the bar. If you want actual closure with automatic tab pruning, Tab Wrangler is the tool for it.

The Problem With Closing Tabs

Closing works. But there’s a cost most guides skip over.

When a tab closes — even to Tab Wrangler’s Corral — reopening it means a full network reload. You get the current page state, not the one you left. Scroll position: gone. Form data: gone. Session cookies on sites that log you out aggressively: gone. If the page was behind a login wall that expired, you’re clicking through again from scratch.

Tab Wrangler’s Corral mitigates the “where did that tab go” problem but not the reload cost. If 20 tabs close overnight and you need 5 of them tomorrow morning, you’re making 5 cold network requests and navigating back to wherever you were on each one.

If you rarely revisit closed tabs, that cost is zero. But the tabs you actually want back tend to be exactly the ones you were mid-thought on.

Tab Suspension: Same RAM Savings, Tabs Stay

Chrome’s chrome.tabs.discard() API does something different. It evicts a tab’s content from memory — freeing 90-95% of the RAM that tab was using — but leaves the tab in the bar. The favicon stays. The title stays. The URL stays. Nothing looks different to you.

Click that tab and it reloads from the stored URL, the same as clicking a just-closed tab from Tab Wrangler’s Corral. But you didn’t have to go find it in a list. It was sitting there the whole time.

SuperchargePerformance uses chrome.tabs.discard() with configurable timers (5 or 15 minutes on the free tier, custom on PRO). The same protections apply: audio tabs never get suspended, pinned tabs stay loaded, and tabs with unsaved form inputs are detected and skipped. 25+ auto-protected web apps — Gmail, Google Docs, Figma, Notion, Slack, Spotify, and others — are excluded by default because suspending mid-edit is worse than leaving them loaded.

The badge counter in the extension popup shows total RAM freed across your session. On a heavy workday with 30+ tabs, the savings compound quickly.

Auto-Close vs Suspension: Side by Side

The RAM savings column is nearly identical in practice. The real difference is where the tab lives after the timer fires.

When Auto-Close Is Actually Right

There are two situations where closing beats suspension:

Genuine tab hoarding. If you routinely hit 80-100+ tabs and know you’ll never return to the majority of them, suspension just hides the problem. The tabs are still there, still in the bar, still piling up. Tab Wrangler closes them and enforces a hard limit on what stays open. For true hoarders, that forcing function has real value.

The hybrid approach. You don’t have to pick one. SuperchargePerformance suspends tabs after 15 minutes to free memory throughout the day. Tab Wrangler handles the pruning side: close anything untouched for 24 hours. Run both and you get suspension for same-session tabs (memory freed, context preserved) and auto-close for anything that’s been sitting around for a day or more.

If you never go back to a tab, close it. If there’s any chance you’ll want it, suspend it instead of closing.

Quick Setup Guide

If memory is the primary concern and you want tabs to stay recoverable without list-hunting: SuperchargePerformance. If you want Chrome to enforce an actual tab limit and actually clear out the old ones: Tab Wrangler. If your tab count regularly climbs past 80: run both.