Search for a fix to Chrome eating memory and you will be told to install a tab suspender. Most of that advice was written before Chrome had one built in.
Here is what each thing actually does, and the more useful question underneath.
The short answer: they are the same mechanism
Chrome's Memory Saver deactivates tabs you have not used recently. The page is unloaded from memory, the tab stays in your tab strip with its title and history intact, and Chrome rebuilds it when you click back.
A tab suspender extension unloads the page from memory, keeps the tab in your tab strip with its title and history intact, and rebuilds it when you click back.
That is not a coincidence. Extensions do this through a Chrome API that discards a tab, which is the same underlying capability Chrome uses for Memory Saver. Almost every "tab suspender saves you gigabytes" article you will find predates late 2022, when Chrome shipped this for everyone.
So the honest framing is not Memory Saver versus suspending. It is: Chrome already does this, and the only thing left to argue about is who decides when.
What Memory Saver gives you
It is at chrome://settings/performance, and it is worth opening because most people have never configured it.
Three modes. Moderate waits longer before deactivating a tab, so you get less memory back and fewer reloads. Balanced is the recommended default and picks its own timing. Maximum deactivates soonest, frees the most, and reloads most often.
An exclusion list. "Always keep these sites active" never gets deactivated whatever mode you pick. Entering google.com covers subdomains too; entering .google.com excludes them. This is the setting to reach for when a site that does background work keeps dying on you.
Inactive tab appearance. Turn this on and deactivated tabs show a ring around the icon, so you can see what will reload before you click it.
Where it fails: it decides, not you. There is no "free memory right now, I am about to do something heavy". And it will not touch the tab you are looking at, which is often the expensive one.
What a suspender extension adds now
Genuinely one thing: control. Suspend this tab now. Suspend everything except this one. Suspend before you open the video call.
That is a real convenience if you work in bursts and know when you are about to need headroom. It is not a different technology and it will not free memory Chrome could not have freed.
Where it fails: it is the same trade, made manually. And a suspender that is doing its job well is indistinguishable from Memory Saver doing its job well, which is why so many people install one, see no difference, and conclude it did nothing.
The bigger point: high RAM usage is probably not your problem
This is the part the RAM-fixing articles skip, because it undercuts the reason they exist.
Unused memory is wasted memory. Your operating system deliberately fills it with caches and open pages because empty RAM does nothing for you. Chrome showing 6 GB on a 16 GB machine is not a fault. It is Chrome using what is there.
The symptom people actually have is slowness, and slowness starts when you run out of physical memory and the system begins swapping to disk. Below that line, freeing a gigabyte changes nothing you can perceive. Above it, everything drags.
So the question is not "how much is Chrome using". It is "am I running out". If you are not, suspending tabs will make your browser slower in exchange for a number that looks nicer in Task Manager.
Find out what is actually heavy
Press Shift+Esc in Chrome and you get Chrome's own task manager, listing memory per tab and per extension. Sort by memory footprint.
The thing most people discover is that tab count is a bad predictor. Forty parked article tabs can total less than one spreadsheet, one design tool, or one chat app left open since Monday. Those heavy tabs are usually the ones you are actively using, which means neither Memory Saver nor a suspender will touch them.
If your machine is genuinely under pressure, closing one heavy tab beats suspending thirty light ones.
What suspending costs you
Worth knowing before you set Maximum mode and forget about it.
Reloads take time and data. Coming back to a discarded tab means fetching it again. On a slow connection, a metered one, or a heavy site, that wait is the price of the memory you saved.
Some page state does not survive. A reload is a reload. Unsaved form input, position in a long page, playback position, anything held only in the page can be gone. Chrome preserves some of this and not all of it.
Background work stops. A deactivated tab is not running. If it was tracking something, holding a session, or waiting on a long job, it is not any more. This is exactly what the exclusion list is for.
What to actually do
- Turn Memory Saver on and leave it on Balanced. It is free, it is built in, and it covers the ordinary case
- Add the two or three sites you cannot afford to have reload to "Always keep these sites active"
- Press Shift+Esc when things feel slow rather than guessing. Fix the specific heavy tab
- Only reach for a suspender extension if you want manual control at a specific moment. Not because you expect a different result
If Chrome feels slow and you have plenty of free memory, the problem is not memory and no suspender will fix it.
Where our own tool sits
Tab Rescue (we make this) has tab suspending in it, and we would rather be straight about what that is worth: it is the manual-control convenience described above, nothing more. If Memory Saver is already on and working for you, our suspend button is not a reason to install anything.
The reason Tab Rescue exists is the other problem. Suspending protects your memory. Nothing built into Chrome protects your tabs. It takes a snapshot of every open window and tab every five minutes and keeps the most recent twenty, so a crash, a forced update or a wrongly closed window does not cost you the day. Tab groups come back with their names and colors, pinned tabs come back pinned, and restoring opens new windows rather than replacing what you have.
Free, including the automatic backups, crash recovery, one-click restore, suspending, export and import, and five named sessions. Nothing leaves your device, no account, and incognito windows are never captured.
The honest summary
Memory Saver and tab suspender extensions do the same job through the same mechanism, and Chrome doing it automatically is good enough for nearly everyone. The extension version buys you timing, not capability.
And before optimizing any of it, check whether high memory is your actual problem. Usually it is not, and the tab you should worry about losing matters more than the memory it is using.
Tab Rescue is free on the Chrome Web Store.