Why Is Chrome Using So Much Memory? (And What Actually Fixes It)

Every tab is its own process

Chrome runs each tab (and often each extension, and each iframe on a complex page) as a separate operating-system process, not as a lightweight thread inside one big program. That's a deliberate design choice — if one tab crashes or a site runs runaway JavaScript, it doesn't take down every other tab with it. The tradeoff is that each of those processes carries its own baseline memory cost: its own copy of V8 (Chrome's JavaScript engine) running, its own rendering pipeline, its own cached images and scripts.

Open ten tabs and you're not running one browser with ten pages — you're running something closer to ten small programs, each with their own overhead, in addition to whatever the page itself actually needs.

Why it's worse on 4–8GB machines

On a 16GB+ machine, this mostly stays invisible — there's enough headroom that dozens of tabs don't register. On a 4–8GB laptop, the overhead eats a meaningfully larger share of what you have. Add a video call, a heavy site like a Figma file or a Notion doc, and a handful of background apps, and you can hit real memory pressure with what feels like a completely normal number of tabs open.

Once memory pressure is high enough, the operating system starts swapping — writing memory contents to disk and reading them back as needed — which is dramatically slower than RAM. That's usually the actual moment a computer "feels slow": not Chrome itself misbehaving, but the whole system fighting for memory.

What doesn't actually fix it

• Closing tabs you'll reopen anyway just relocates the problem — you lose your place and redo the searching later.
• Restarting Chrome helps briefly because it clears everything's accumulated memory, but the moment you reopen your tabs you're back where you started.
• Disabling extensions "to save memory" rarely moves the needle much unless the extension itself is unusually heavy — most of the cost is in the tabs, not the extensions.

What actually helps

• Suspending or discarding idle tabs — freeing the process's memory while keeping the tab itself (title, favicon) in place, so it reloads on demand rather than being gone. This is what Chrome's own Memory Saver does, and what dedicated tab-sleeping extensions do more visibly.
• Reacting to real pressure, not just time. A fixed "sleep after 10 minutes" timer helps, but it's blunter than watching your system's actual free-memory percentage and acting only when it's genuinely tight — which keeps tabs alive longer when you don't need the memory back yet.
• More RAM, if the machine supports it — not always practical, but worth saying plainly: software can manage the symptom, it can't manufacture memory that isn't there.