How to free up RAM in Chrome without closing your tabs

You have thirty tabs open, the fan is running, and switching windows has started to stutter. The usual advice is to close some tabs. That works, and it is also why nobody does it — those tabs are your open loops, and closing them means losing your place.

There is a better move, and Chrome has supported it for years: release the memory a tab is holding without closing the tab.

Where the memory actually goes

Chrome runs each site in its own process. That isolation is a genuine security feature — a crash or an exploit in one tab cannot reach into another — but it means every open page carries its own overhead: the JavaScript heap, the DOM tree, decoded images, and whatever the page has cached in memory.

The JavaScript heap is usually the part that grows without bound. A news article parks at a few tens of megabytes and stays there. A design tool, a spreadsheet, a chat app or a video site that has been open since Tuesday keeps allocating: rendered frames, undo history, message backlogs, analytics buffers. This is why the tab you have forgotten about is so often the expensive one.

Discarding: the option most people never find

Chrome can shut down the process behind a page while leaving the tab itself in the tab strip. The title stays, the favicon stays, the position stays. The memory is returned to the operating system immediately. When you click the tab again, Chrome reloads the page — usually from cache, usually in well under a second.

This is called discarding, and it is the same mechanism behind Chrome's built-in Memory Saver. The difference is control. Memory Saver decides on its own schedule, shows you no numbers, and gives you no way to say “not this tab.”

Find the heavy tab first

Discarding at random is not much better than closing at random. What makes it worth doing is knowing which tab to release, and Chrome does not put that number anywhere you can see it. The Task Manager (Shift + Esc) comes closest, but it lists processes rather than the tabs you recognise, and it disappears the moment you look away.

MemoryStats reads each tab’s JavaScript heap and lists the tabs heaviest-first, with a bar per row so the outlier is obvious at a glance. That number is not the tab’s entire memory footprint — the process also holds the DOM, images and GPU resources — but it is the part that grows with what a page has been doing, which makes it a reliable signal for the tab worth releasing.

How to free up RAM in Chrome, step by step

1. Measure before you act. Open the MemoryStats panel. Every open tab is listed with its current reading, sorted so the worst offender is at the top.
2. Lock what you cannot lose. A half-written reply, a form you have filled in, a page mid-upload — lock those tabs. Locked tabs are never discarded, by you or by auto-mode.
3. Release the rest. One click discards the heavy tabs. The total at the top drops immediately, and the tabs stay exactly where they were.
4. Then stop doing it by hand. Turn on auto-mode and the browser cleans itself on a schedule, including while you are away from the keyboard.

What to be careful about

A discarded tab reloads from scratch. For the overwhelming majority of pages that is invisible. For three kinds of page it is not:

• Forms with unsaved input. Text you typed but never submitted may not survive the reload.
• Pages doing work in the background. An upload, an export, a long-running job in a web app.
• Anything behind a slow or one-time load. A dashboard that takes thirty seconds to build itself is not worth reclaiming 200 MB from.

Lock those. Everything else in a thirty-tab window is a page you will reload without noticing.

What you should expect to get back

On a browser that has been open all day, the top three or four tabs routinely account for most of the total. Releasing them typically returns a couple of gigabytes — enough that the fan stops and window switching goes back to being instant. The tabs are all still there.

That is the whole idea: you should not have to choose between keeping your work open and keeping your machine usable.