Why Chrome uses so much memory when you have a lot of tabs open

Chrome gives most tabs their own operating system process. That is the short answer: memory grows roughly with the number of things you have open, because each one is running its own sandboxed copy of the rendering engine along with whatever JavaScript that site chose to load. Thirty tabs is closer to thirty small programs than to one program with thirty documents in it.

So if you want the number to come down, there are only three levers: have fewer tabs live at once, let Chrome put the inactive ones to sleep, or fix the handful of tabs that are using far more than their share. The third one is usually the surprise, and it is where I would start.

How do you see which tabs are using the most memory?

Chrome has a task manager of its own, opened with Shift + Esc on Windows and Linux, or from the Window menu on macOS. It lists every tab and every extension as its own row with live memory and CPU columns, so sorting by memory shows exactly which tabs are responsible.

Do not guess, and do not trust an article's numbers — including mine. Memory use varies enormously between a plain text article and a web app with a live document open, and the only figures that matter are the ones on your machine.

Sort by memory and look at the top five. In my experience the result is rarely "lots of tabs, evenly spread". It is usually two or three heavy things — a video call, a design tool, a spreadsheet, a social feed left open since morning — sitting far above everything else, with a long tail of articles using comparatively little.

That changes what you should do about it. Closing fifteen light tabs may free less than closing one heavy one.

While you are there, sort by CPU too, and watch it for a minute without touching anything. A tab using measurable CPU while you are not interacting with it is running code continuously. Sometimes that is legitimate — a live dashboard, a queued upload. Often it is an ad script or an animation nobody needed.

Why does Chrome give each tab its own process?

Chrome isolates tabs in separate processes so that one crashing or compromised page cannot bring down the browser or read the contents of another tab. The memory that costs is the price of that isolation, and it is mostly not waste.

Separate processes are what stop one badly-behaved page from taking the whole browser down with it, and what stop a page in one tab from reading the contents of another. When a site crashes and you get a single dead tab rather than losing everything, that is the isolation doing its job. Chrome is spending memory to buy stability and security.

It also means the number is not directly comparable across browsers, and that "Chrome uses more RAM than X" comparisons are often measuring different architectures rather than different levels of efficiency.

Two practical consequences worth knowing:

Unused RAM is not a virtue. An operating system that leaves memory idle is not being efficient, it is being wasteful. Memory is there to be used. The number that matters is not how much is allocated but whether your machine is under pressure — swapping to disk, stuttering when you switch windows, taking a beat to respond.

Pressure is what you are actually diagnosing. If everything feels fine, a large memory figure is not a problem to solve. If things are slow, then the figure is worth chasing.

How do you make Chrome sleep the tabs you are not using?

Turn on Memory Saver, under Settings → Performance. Chrome then discards tabs you have not touched for a while and reclaims their memory, and a lot of people never switch it on.

With it on, Chrome discards tabs you have not touched for a while. The tab stays in the strip with its title and favicon; the page behind it is released. Clicking it reloads the page.

That is genuinely effective, and it is free. It also has a specific cost that is worth understanding before you rely on it, because it is the thing people find annoying enough to switch the feature back off:

A discarded tab reloads from the top. Chrome restores the page, not your position in it. A long article returns to the first paragraph. A video returns to zero. Anything you had typed into an unsubmitted form may be gone.

Chrome does let you exempt specific sites from being discarded, in the same settings panel. That is worth doing for the two or three sites where losing your place genuinely hurts — the documentation you are working through, the video course you are partway into.

Why is it so hard to just close tabs?

Closing tabs is hard because most open tabs are not open in order to be used — they are open because closing them would lose something. That is the pattern I kept noticing in myself, and it is why the memory problem is so persistent.

Most of my open tabs were not open because I was using them. They were open because closing them had a cost. A half-read article meant hunting for the paragraph again. A tutorial forty minutes in meant dragging the video scrubber around trying to find the spot. A page I might need later meant remembering it existed at all.

So the tab stayed. Then the next one did. Thirty tabs is not thirty things you are doing — it is one thing you are doing and twenty-nine you are afraid of losing.

That reframes the fix. Telling someone to "just close tabs" does not work, because the tabs are a symptom. What works is making a tab cheap to close.

Some ways to do that, in rough order of effort:

• Bookmark it and close it. Free, built in, and the answer for anything you want to keep permanently rather than finish today. A bookmarks folder called "read later" costs nothing.
• Use browser tab groups. Right-click a tab, add it to a group, and collapse the group. Chrome can also save a group, which closes the tabs while keeping the set. Good for keeping a project together — though collapsing does not free the memory, it only tidies the strip. There is more on this in how to keep work and study tabs separate.
• Send it to your phone. Chrome's "Send to your devices" moves a page off the machine entirely.
• Save your position, not just the page. This is the gap the built-in options leave: bookmarks and saved groups both restore the URL, not where you were in it.

That last gap is the one I ended up building TabVault to fill — it saves the tab along with its exact scroll position, and for a YouTube video the exact timestamp, so reopening it puts you back where you stopped. It is free, needs no account, and keeps everything in your own browser. But I want to be straight about the order here: turn on Memory Saver first, find your heavy tabs in the task manager first. Those are free and they address the larger share of the problem. An extension is worth adding only once you know the specific thing you keep losing.

Do extensions add to Chrome's memory use?

Yes. Every installed extension runs as its own process, and some of them run on every page you load whether or not you use them, so an extension audit belongs in any memory clear-out. It is easy to audit tabs and forget that part.

In that same task manager, extensions appear as their own rows. Some sit at essentially zero. Some run on every page you load, all the time, whether or not you are using them.

Two questions worth asking of each one:

1. Have I used this in the last week? An extension you are not using is not neutral — it is a cost you pay on every page load for a benefit you stopped receiving.
2. Does it need to run everywhere? An extension that only acts when you click its button should not be consuming resources on every tab.

I have written about how to judge which extensions earn their place separately, and about what to check before installing one — the safety question is different from the performance one.

What actually reduces Chrome's memory use?

1. Open the task manager and look. Find your two or three heavy tabs. This is the highest-value five minutes available.
2. Turn on Memory Saver, and exempt the handful of sites where losing your place matters.
3. Audit your extensions. Remove anything unused. Check what is consuming CPU while idle.
4. Make closing tabs cheap — bookmarks, tab groups, or something that saves your place — so the underlying habit changes rather than being fought.
5. Restart Chrome occasionally. Long-running sessions accumulate. This is unglamorous and it works.

And one thing that usually does not help as much as people expect: adding RAM. It raises the ceiling, which is worth doing if you are genuinely swapping to disk constantly. But if the real problem is one runaway tab or six unused extensions, more memory just gives them more room.

What if none of it helps?

If Memory Saver, a task manager audit and an extension clear-out have all been done and the machine still struggles, the bottleneck may not be Chrome at all. A mechanical hard drive rather than an SSD, a background sync client, or a security suite scanning every file can each produce symptoms that feel like browser slowness. I have written separately about working out what is actually slow on an older machine.