Reduce Chrome Memory Usage With TabFold Auto-Suspend

TabFold reduces Chrome's memory usage by suspending tabs that have been inactive longer than a timer you choose. A suspended tab releases the process memory its page was holding, stays exactly where it is in the tab strip, and comes back with its content preserved the moment you click it. Nothing is closed and nothing is lost — the RAM just stops being spent on pages nobody is reading.

Why idle tabs cost memory at all

Chrome gives every tab its own process memory. That isolation is good engineering — one crashed page cannot take the browser down — but it means a page that is loaded and idle still holds its full footprint. Forty research tabs is forty processes holding RAM for content nobody is looking at, and on a laptop that cost shows up as fan noise, battery drain, and a sluggish foreground tab.

Suspending inverts the deal: the tabs you are actually using get the memory the forgotten ones were hoarding.

Choosing your suspend timer

The inactivity threshold is yours to set, and the right value depends on how you browse. Keep it short if you open and abandon tabs quickly — the sooner an abandoned tab suspends, the sooner its memory returns. Set it longer if you cycle back through a reference set every few minutes; a timer shorter than your revisit rhythm means tabs suspend just before you need them, which is friction without benefit.

There is no universal correct number. Start in the middle, and adjust in the direction of whichever annoyance you notice: too much memory still used, or too many tabs reloading when you return to them.

Protecting tabs that must stay live

Three controls keep the memory saver away from tabs that should never suspend:

Control	What it protects
Domain whitelist	Sites that must always stay live — a web app mid-form, a dashboard that must keep updating, localhost during development
Pinned-tab exclusion	Your permanent tabs: mail, calendar, music
Active-window-only mode	Limits suspension (and every other action) to the window you are cleaning up

Developers should whitelist localhost first; a suspended dev server tab that reloads at the wrong moment is the fastest way to distrust a tab suspender.

What suspension does not do

Suspending preserves the tab's content, so clicking a suspended tab restores it rather than losing it. But a suspended tab is not a saved tab — a browser crash or an accidental window close still takes the set with it. For that protection, snapshot the session or export the list, both covered in sessions and export.

Next steps

• Make your tab set crash-proof
• TabFold basics and grouping