How to reduce Chrome memory usage without closing tabs

Chrome runs every tab as its own process. That design is why one crashed tab doesn’t take the browser down, and it’s also why 40 tabs can quietly claim most of your RAM. You have two honest options: make the tabs you keep use less memory, or keep fewer tabs. This guide covers both, and none of it requires losing a single tab.

First, see what is actually eating the RAM

Before fixing anything, look. Chrome has its own task manager: press Shift+Esc on Windows or Linux, or open the ⋮ menu, then More tools, then Task manager. Click the Memory footprint column to sort.

Two things usually surprise people here. First, the biggest consumer is often not the count of tabs but two or three heavy web apps. Second, extensions are processes too, and they appear in the same list. Whatever you find at the top of that list is where the rest of this guide pays off.

1. Turn on Memory Saver

Chrome’s built-in answer, and the right starting point. Open chrome://settings/performance and switch on Memory Saver. Chrome will then discard tabs you haven’t used in a while: the tab stays in the strip with its title and favicon, but the page behind it is unloaded and its memory comes back. Click the tab and it reloads.

You can pick how aggressive it is (Moderate, Balanced, or Maximum), and list sites that should never be discarded under Always keep these sites active. Put your music player and anything with a long form in that list.

The trade: a discarded tab reloads from scratch when you return, so anything you typed but never saved is gone, and the reload takes a moment. That’s inherent to discarding, not a Chrome quirk. The same trade applies to every tool in this article.

2. Put tabs to sleep yourself

Memory Saver decides for you, on its own schedule. Sometimes you know better: the research window you won’t touch until the meeting, the twelve documentation tabs from yesterday. Chrome can discard any tab on demand, and there are a few ways to trigger it.

The hidden built-in way is chrome://discards, an internal page that lists your tabs with a discard action for each. It works, but it’s a diagnostics page, not something you’d keep open.

This is what the sleep action in our extension, UtilEngine, is for. The Session Manager shows every window you have open as a live board. Each tab row has a sleep button, and each window has one that puts every tab except the active one to sleep in a click. Sleeping tabs dim with a moon on the board, including tabs Chrome’s own Memory Saver discarded, and they wake when you click them. It uses the same native discard mechanism as Chrome itself, so it needs no special permissions and nothing about your tabs depends on the extension afterward.

To be clear about the trade: UtilEngine is a paid launcher extension ($49 once) and sleep is manual by design; it doesn’t run a timer. If what you want is set-and-forget automatic suspension beyond what Memory Saver does, the open-source Auto Tab Discard does that for free. What UtilEngine adds is control and a safety net: you choose what sleeps, you see everything that’s asleep in one place, and the same board saves whole windows as sessions with hourly snapshots behind them.

3. Close tabs you can get back

The uncomfortable truth about tab memory: a discarded tab still costs a little, and a closed tab costs nothing. Most people keep tabs open not because they need them now but because closing feels like losing them.

That’s a solvable problem. Chrome can save all open tabs as bookmarks or tab groups, and a session manager can save a whole window as a named session you restore in one command, days or machines later. Once restoring a window is genuinely one keystroke away, closing it stops being scary, and closed windows are the best memory optimization there is.

4. Trim the extension list

Back in Chrome’s task manager, count the rows that start with “Extension:”. Each one is a resident process, and a heavy one can cost more than several tabs. Remove what you don’t use, and for the borderline cases, disable rather than uninstall: chrome://extensions, toggle off, see if you miss it this week.

This is also a fair test to apply to UtilEngine itself, by the way. One launcher replacing a calculator extension, a JSON formatter, a session manager, and an AI sidebar usually comes out ahead of running all four.

Which one should you use?

• Set-and-forget, no install: Memory Saver, on Balanced.
• A window you’re done with until Thursday: save it as a session, then close it.
• Tabs you need open but not running: put them to sleep.
• RAM still missing after all that: check the task manager for heavy extensions.

Common questions

Does Memory Saver close my tabs?

No. A discarded tab stays in the tab strip with its title and favicon. The page is unloaded from memory and reloads when you click it. You only lose unsaved page state, like half-filled forms, not the tab itself.

Why does Chrome use so much memory in the first place?

Isolation. Every tab, and every extension, runs in its own process so that a crash or an exploit in one page can’t reach the others. That’s a real safety win that costs RAM. The fixes in this guide don’t fight the design; they just stop you paying for tabs you aren’t using.

Do sleeping tabs survive a browser restart?

The tabs come back the way Chrome normally restores your windows, but sleep state isn’t something Chrome persists on your behalf. If losing a window would hurt, the answer isn’t sleep, it’s a saved session or a snapshot. Our guide on restoring tabs after a crash covers every recovery route.

Is a tab suspender extension still worth installing in 2026?

The automatic part is built into Chrome now, so the old-style suspender is mostly obsolete. What’s still worth having is on-demand control and visibility, which is a different job. If you’re here because your old suspender vanished, we wrote an honest comparison for people leaving The Great Suspender.