Chrome is using too much memory, and here is what helps

Activity Monitor is open, the list is sorted by memory, and the top eight rows all say Google Chrome Helper. The fans have been running since lunch. Somewhere under those rows is a mail tab, a chat tab, a project board, and about thirty things opened while looking something up. The question that follows is almost always the same: is Chrome broken, is the Mac too small, or is this just what a browser does now. The honest answer is that those are three different problems, they need different fixes, and they can be told apart in about five minutes.

Chrome is supposed to look like many processes

The first thing that makes the number look alarming is that Chrome does not appear as one row. It appears as a browser process, a GPU process, a network service, one renderer per site, and a separate process for each extension that runs in the background. Adding those rows together gives a figure that no single-process browser would ever show, which is why Chrome looks worse in Activity Monitor than it sometimes is.

This split is deliberate. The Chromium project describes Site Isolation as a security boundary rather than a performance choice.

It ensures that pages from different websites are always put into different processes, each running in a sandbox that limits what the process is allowed to do. Source: chromium.org

The same page puts a figure on what the separation costs. The figure given for desktop, measured in Chrome 67, is about 10 to 13 percent when isolating all sites with many tabs open. That is the price of one compromised page being unable to read another site's session, and it is not a setting worth hunting for a way to disable.

What this means in practice is that the total is not the useful number. A browser holding forty pages across twelve sites will always have a large total. The useful number is which individual rows are large, and whether they belong to things actually being used. That is a different question, and Chrome answers it directly.

Sort by memory before changing a single setting

Chrome ships a task manager that lists every tab, every extension, and every internal process with its own memory figure. Google's instructions are short.

At the top right, select More. Select More tools and then Task Manager. Source: support.google.com

Once it is open, clicking the Memory column sorts the list. Three findings turn up often enough to be worth expecting.

The first is an extension background page near the top. These appear as their own rows, labelled as background pages, and they run whether or not the extension is being used that day. A clipboard tool, a price tracker, or a screenshot utility installed a year ago can sit above every real tab on the list.

The second is a chat or mail application that has been open since morning. Long-lived web applications accumulate. A message list that has scrolled through two thousand messages holds all of it, and closing and reopening the tab resets it to a fraction of the size.

The third is a page nobody remembers opening. A documentation site left in a background window, a video paused three hours ago, a dashboard that refreshes itself. None of these feel like work in progress, and all of them are resident.

The task manager also ends processes directly, though Google's page carries the obvious warning that any unsaved work in that task is lost. Ending a tab process is a diagnostic move, not a fix. The value of the exercise is the list, not the killing.

The number that decides whether this matters is memory pressure

A Mac reporting most of its RAM in use is not a Mac in trouble. macOS deliberately fills unused memory with cached files, and Apple's own description of the Activity Monitor memory pane makes the intent plain.

The size of files cached by the system into unused memory to improve performance. Source: support.apple.com

The row that actually reports strain is Memory Pressure, which Apple describes as a graphical representation of how efficiently memory is serving current processing needs. Green pressure with high memory used is a machine doing its job. Yellow or red pressure that stays there is a machine short of room.

Two other rows on the same pane are worth reading together with it. Compressed shows memory that has been squeezed to free space, and Swap Used shows space being borrowed from the startup disk to hold what no longer fits. A session with low compression and no swap is comfortable no matter how large the totals look. A session with swap growing through the afternoon is the case where something genuinely has to close.

This distinction decides which of the following sections is relevant. If pressure is green, the complaint is about a tab reloading or a page feeling slow, and that is a Chrome settings question. If pressure is red with swap climbing while several native applications are also open, no browser setting will fix it, because the browser is not the only claimant.

Memory Saver, and what it takes in exchange

Chrome's built-in answer is to deactivate tabs that are not in use and reload them on return. The setting lives under Performance, and it offers three levels with wording taken from the settings page itself.

Level	What Chrome says it does	Who it suits
Moderate	Tabs become inactive after a longer period of time	Machines with room to spare, sessions where reloads are annoying
Balanced	Tabs become inactive after an optimal period of time	The default, and the right starting point for most sessions
Maximum	Tabs become inactive after a shorter period of time	Small-memory Macs where reloads cost less than swapping

The cost of deactivation is state. A form half filled in, a board with filters applied, an editor holding an unsaved draft, a dashboard that takes twenty seconds to authenticate: all of these are rebuilt from scratch on return. For casual reading tabs that is free. For the four or five applications that run all day, it is the most irritating thing the browser does.

Chrome's exclusion list exists for exactly that case. It is called "Always keep these sites active", and sites can be added either by picking them from currently open tabs or by typing an address. The accepted pattern is documented as [scheme://][.]host[:port][/path][@query], which means a bare domain such as example.com matches the domain and its subdomains, while a leading dot narrows the match. Adding three applications there and leaving Maximum on for everything else is a more useful configuration than either extreme on its own.

Four levers, and what each one actually costs

Once the expensive rows are known and memory pressure has been read, the available moves are limited and easy to rank. The ranking below is by cost to the person doing the work, not by megabytes saved.

Lever	Effect on memory	What it costs
Remove unused extensions	Removes whole background processes permanently	A few minutes, once
Close reading tabs opened today	Large, immediate, and recurring	Nothing, if they were genuinely disposable
Memory Saver plus an exclusion list	Steady reduction across idle tabs	Reloads on anything not excluded
Separate long-lived apps from browsing	Makes the first three durable instead of daily	A change in how the session is arranged

The first two are where most of the recoverable memory is, and neither requires a setting. The third is the one people reach for first and is genuinely useful, but it manages the symptom every day rather than removing the cause.

The fourth is the only one that changes the shape of the problem, and it is worth being precise about what it means. In a single window, a mail client that must never reload and a documentation page opened for ninety seconds sit in the same tab strip, are subject to the same rules, and are closed by the same instinct. Every memory decision becomes a judgement call about a specific tab, made dozens of times a day.

Three moves that look like fixes and mostly are not

A search for this problem turns up the same three suggestions, and each one is worth a short answer before it eats an afternoon.

The first is installing a tab suspender extension. Chrome now discards idle tabs on its own, so the extension duplicates a built-in behaviour while adding a background process of its own to the task manager list. Before Memory Saver existed this was the only option. It no longer is, and the exclusion list gives finer control than most of these extensions offer.

The second is turning off hardware acceleration. This moves work from the GPU to the CPU rather than reducing what is held in memory. On a Mac it usually makes scrolling and video worse while leaving the memory figure roughly where it was. It is a reasonable thing to try when a specific page renders incorrectly, and a poor thing to try when the complaint is memory.

The third is quitting and reopening Chrome. This genuinely works, and that is exactly why it is misleading. It works because it closes everything, including the twenty pages that were never going to be read again, and then restores only what was pinned or in a saved group. The relief comes from the closing, not from the restart, and it returns within a day because nothing about the session changed. Anyone who finds themselves restarting the browser as a daily ritual is describing a session that is too large to hold, not a browser with a leak.

Buying more memory is the one item on this list that always works, and it is also the one that cannot be undone. It is worth doing after the measurement step rather than before, because an extension background page costs the same on a 64 GB machine as on a 16 GB one.

When the session, not the browser, is the thing to change

A different arrangement removes the judgement call. When each long-lived web application lives in its own window with its own session, the set of things that must stay resident is fixed and small, and everything opened for ten minutes of reading stays in a separate pile that can be closed without thinking about it. Mail, chat, and the project tool become named places rather than tabs that happen to have survived. The Workspaces page describes how that grouping is arranged on macOS, and the Features page covers what each application window keeps on its own, including separate cookies for accounts that would otherwise conflict.

There is a second effect worth noting. Because Chrome puts each site in its own process, a heavy application that misbehaves takes its own process with it. In a forty-tab window that means hunting through a strip to find what died. With one application per window, recovery means reloading one window, and the other applications never noticed.

None of this replaces the measurement step. A session arranged into windows still benefits from removing a background extension nobody uses. The difference is that the arrangement holds from one week to the next, while a tidy tab strip lasts until the next thing worth reading turns up.

What to change first

Open the Chrome task manager, sort by memory, and deal with the three largest rows today: remove any extension background page that belongs to something no longer used, and close anything opened for reading. Then add the two or three applications that must never reload to the always active list and leave Memory Saver on for the rest. If the same applications are still open a month from now, give each one its own window and its own session, which is the arrangement SpaceDeck is built around on macOS.