Why Is Chrome Using So Much Memory? (And How to Fix It)

Chrome fans go up, the laptop gets warm, and Activity Monitor or Task Manager shows a number that makes you wince. It is one of the most common complaints about Chrome, and it is not really a bug. Chrome uses so much memory because of a deliberate design choice: every tab, most extensions, and even Chrome’s GPU and networking functions run as their own separate process instead of sharing one big process.

That design is why one crashed tab does not usually take down your whole browser, but it also means memory use climbs almost linearly with how much you have open. This guide walks through why that happens, how to find the actual culprit tab or extension, and the built-in Chrome settings that cut memory use without you giving up any tabs. It also covers what to do when memory pressure crashes Chrome before you can save anything yourself.

Why Is Chrome Using So Much Memory?

Chrome uses so much memory because it isolates each tab, extension, and internal function into its own process rather than sharing memory across everything. That isolation protects you from one bad tab crashing your entire session, but the tradeoff is that RAM use scales with how many tabs, windows, and extensions you keep open at once.

A handful of quiet tabs is not what usually causes trouble. The spikes come from a specific mix: a video call, several Google Docs, a couple of Slack or Gmail tabs, and a dozen extensions all running in the background at the same time. Each of those is individually reasonable, but Chrome is adding them up as separate processes, not sharing the load.

Here is a fast way to match your situation to the right fix, with more detail on each one further down the page.

This is not unique to Chrome. Every Chromium-based browser, including Edge and Brave, uses the same multi-process model under the hood, so you will see similar memory patterns there. The setting names differ, which we cover further down.

How Much Memory Should Chrome Use?

There is no single correct number, because Chrome’s memory use scales with what you actually have open, not a fixed baseline. A browser with three tabs and no extensions will use far less than one with forty tabs, five extensions, and a video call running.

What you can look at instead of a target number is whether Chrome is behaving. If pages load quickly, switching tabs feels instant, and your fans stay quiet, the memory number in your system monitor is not a problem worth chasing. If typing lags, tabs go unresponsive, or your whole system slows down, that is the actual signal to act on, regardless of the specific gigabyte figure you are seeing.

Chrome’s own engineering does give one concrete, useful figure here: according to Chrome’s developer blog, a tab that Chrome has discarded (freed from memory while keeping its title and favicon visible) can use up to 80 percent less memory than the same tab active. That is the number worth remembering, because it tells you how much headroom Memory Saver and manual discarding can realistically free up on a memory-constrained machine. If you are on an older laptop, our guide on why Chrome is lagging covers the wider set of slowdown causes beyond memory alone.

Watch behavior, not just the number. A high memory figure with a responsive browser is not worth fixing. A modest figure with a frozen browser is. Use Task Manager, covered next, to confirm which one you are dealing with.

How Do I Find Out Which Tab or Extension Is Using the Most Memory?

Open Chrome’s built-in Task Manager to see memory use broken down by every tab, extension, and background process. It is separate from your operating system’s task manager and shows Chrome-specific detail you cannot get anywhere else.

1. Open Task Manager. Press Shift+Esc on Windows or Linux. On Mac, open the Chrome menu (the three dots), then More Tools, then Task Manager.
2. Sort by memory. Click the Memory column header so the heaviest tabs and extensions rise to the top.
3. Identify the culprit. Look for tabs using far more than the others, or extensions with generic names you do not recognize.
4. Act on what you find. Close or reload a runaway tab, or disable a suspicious extension from chrome://extensions.

For a closer look at a specific tab’s memory behavior, Chrome also has an internal diagnostic page at chrome://discards. It lists your open tabs with an Urgent Discard button you can use to manually free a tab’s memory and watch it reload when you click back to it. It is more of a debugging tool than something you need to check regularly, but it is useful if you want to confirm that discarding helps on a particular page.

If you would rather browse a full reference of shortcuts like this one, our Chrome shortcuts guide covers the rest of the keyboard shortcuts worth knowing.

How Do I Turn On Memory Saver in Chrome?

Turn on Memory Saver in Chrome Settings, then Performance, where a single toggle deactivates tabs you are not using to free up memory for the ones you are. Reopening a deactivated tab reloads it automatically, so you are not losing anything permanently, just freeing the RAM it was holding while idle.

The same Performance page also has an Energy Saver toggle, which is a different feature aimed at CPU and battery use rather than memory directly. Energy Saver stops eligible CPU-intensive background tabs, and tabs playing audio or in a video call are exempt from it, so a Zoom call in the background will not suddenly go quiet. Turning both settings on together is reasonable; they address related but distinct problems.

Balanced is the sensible default. Unless you have a strong reason to change it, leave Memory Saver on Balanced. Maximum deactivates tabs aggressively enough that you will notice more reload delays when switching back to older tabs.

Does Closing Tabs Actually Free Up Memory?

Yes, closing a tab releases the memory it was using, but reopening it with Ctrl+Shift+T (Cmd+Shift+T on Mac) reloads the page from scratch, including any unsaved form data or scroll position. That is a meaningfully different outcome from Memory Saver deactivating a tab, which keeps the tab’s title and favicon visible in the tab strip and restores it automatically on click.

If you want to close a batch of tabs at once rather than one at a time, Chrome supports multi-select: Ctrl+click each tab you want, or click the first and Shift+click the last for a range, then right-click any selected tab for bulk actions. This is faster than closing tabs individually when you are trying to clean up a cluttered window in one pass. For the full range of ways to handle a window with too many tabs open, see our guide on too many tabs.

Tab groups can also help here, not by reducing memory directly, but by making it easier to see what you can safely close. Right-click a tab, choose Add tab to group, and give it a name and color; a whole group you no longer need can then be closed together. Chrome also added native vertical tabs, letting you see more open tabs at a glance down the side of the window, which makes spotting stale tabs easier before you clean them up.

Closing is not saving. Closing tabs to fight memory pressure is only safe if you have a way to get them back. If any of those tabs represent research, a half-finished form, or a dozen product comparisons, save them as a session first rather than trusting you will remember every URL.

Do Extensions Make Chrome Use More Memory?

Yes, every enabled extension can run its own background process, and a large collection adds up the same way a large collection of tabs does. An extension does not need to be actively doing something visible to consume memory; many run scripts continuously in the background to watch for page changes, sync data, or check for updates.

The fix is the same instinct as with tabs: audit what you use. Open chrome://extensions and look at what is installed, not just what you remember installing. Browser extensions accumulate over months, often installed for a single task and then forgotten. Disabling ones you have not used recently is low-risk, since disabling is reversible and does not delete any data the extension stored.

If you use Task Manager (covered above) and sort by memory, extensions show up in that same list, sometimes labeled by name and sometimes just as “Extension.” That is your fastest way to catch one that is behaving badly rather than guessing from the full list in chrome://extensions. Our guide on managing Chrome extensions covers the broader workflow for keeping your extension list under control.

Should I Use a Tab Suspender Extension Instead of Memory Saver?

For most people, no, Chrome’s built-in Memory Saver is the current, Google-supported way to suspend inactive tabs, and it does not carry the risk of a third-party extension going unmaintained or changing hands. Third-party tab suspenders were popular before Chrome shipped its own version, and the cautionary tale here is well known.

The Great Suspender, once one of the most popular tab suspenders on the Chrome Web Store, was removed by Google and force-disabled in February 2021 after a change of ownership added code that was flagged as malware, including tracking and ad-fraud exploit code. It is a useful reminder that a suspender extension has deep access to every tab it manages, so the maintainer matters as much as the feature set.

If you had tabs suspended by The Great Suspender before its removal and are trying to recover the URLs, our great suspender recovery tool page walks through the unofficial workaround people have used. For a broader comparison of suspender options available today, see our tab suspender roundup.

How Does Chrome Compare to Edge, Firefox, and Vivaldi for Memory Use?

Every major Chromium-based browser has some version of Chrome’s tab-deactivation approach, just under a different name and with different specifics. Knowing the equivalent term matters if you or a teammate use more than one browser day to day.

Microsoft’s own Edge engineering blog put a number on Sleeping Tabs’ effect: using it typically reduces memory usage by 32 percent on average, and a sleeping tab uses 37 percent less CPU on average than one that is awake, according to a 2020 post from the Edge developer team. Chrome has not published an equivalent single average figure, though its 80 percent maximum for a fully discarded tab, cited above, is the closest comparable claim from Google’s own developer blog.

If you are weighing whether to switch browsers over memory use alone, it is worth knowing the differences are more about naming and defaults than one browser being fundamentally lighter. Our Chrome vs Edge comparison and Edge browser overview go deeper on how the two compare beyond just memory. Firefox users chasing the same fix should also check our Firefox tabs guide for how unload tabs and tab groups work together there.

How Do I Reduce Chrome Memory Usage Without Losing My Open Tabs?

Reduce Chrome’s memory usage by combining Memory Saver, an extension audit, and Task Manager checks, then save your open tabs as a session before you close anything so the cleanup never costs you information you needed. The built-in tools free up memory; a session manager protects the tabs themselves, and the two are not the same job.

This distinction matters because the instinct under memory pressure is to start closing tabs fast, and that is exactly when you are most likely to lose something you needed, whether it is a half-filled form, a dozen research tabs, or a client’s project spread across three windows. BelayTab exists for this moment specifically. Saving a window takes one click or the shortcut Ctrl+Shift+S, and you can choose to save just selected tabs, a single tab, or every open window, with tab groups, pinned tabs, and tab order kept intact.

Because BelayTab also snapshots every open window automatically every 5 minutes, plus each time a window closes, you get a safety net even if you forget to save manually before Chrome slows to a crawl or crashes outright. Every session also keeps the last 20 versions, so restoring never overwrites what is there now, it just adds another version to the history. You can see the full detail on how this works on our automatic snapshots page and the restore tabs feature page.

What Should I Do If Chrome Crashes or Runs Out of Memory?

If Chrome crashes under memory pressure, restart it and check whether “Continue where you left off” is turned on in Settings, then On startup, since that setting reopens the pages you had open when Chrome quit. That is Chrome’s own built-in recovery path, and it is worth confirming it is enabled before you need it, not after.

That native recovery has real limits, though. It depends on Chrome shutting down in a state where it can remember your last session, which is not guaranteed during a hard crash, a forced quit, or an operating system freeze severe enough to kill the browser process outright. It also will not help if you closed a window intentionally days ago and only now realize you needed one of those tabs back. For a step-by-step walkthrough of Chrome crash recovery specifically, our Chrome crashed guide covers the built-in options in more detail, and our piece on Chrome running out of memory covers that specific error message.

This is where automatic, standing snapshots earn their keep over a setting you have to remember exists. Because BelayTab snapshots every window every five minutes and again whenever a window closes, a crash mid-afternoon still leaves you with a recent, restorable copy, not just whatever Chrome managed to preserve on its own. BelayTab’s Recovery screen brings snapshots, deleted sessions, your browser’s recently closed windows, and past exports into one place, so you are not hunting across several menus while Chrome is still misbehaving.

Memory pressure in Chrome is manageable with the tools already built in: Task Manager to diagnose, Memory Saver to reduce, and a periodic extension cleanup to keep things from creeping back up. What those tools do not do is guarantee you never lose a tab in the process, which is the gap worth closing separately, before the next time your fans spin up.