How much memory should Chrome use on a Mac?

There is no fixed right number, because macOS uses free memory on purpose. Apple's guidance is to look at the Memory Pressure graph in Activity Monitor instead. Green means the Mac is coping, even if Chrome's total looks large. Yellow or red means something needs to close.

Does Memory Saver deactivate pinned tabs?

No. Google's help page lists pinned tabs among the things that prevent deactivation, along with tabs playing audio or video, sharing the screen, sending notifications, downloading, or holding a partly filled form. Unpin a tab if you want Memory Saver to be able to deactivate it.

Is anything lost when Memory Saver deactivates a tab?

The tab reloads automatically when you return to it. Partly filled forms are protected because they block deactivation, but scroll position or in-page state on some sites may reset after the reload. Add a site to "Always keep these sites active" if that matters for it.

Is it safe to click End Process in Chrome's Task Manager?

Yes, for tabs and extensions. Google notes that any unsaved work in that task will be lost, so save first. An ended extension stops working until it is started again, so check afterwards that the ones you rely on are running.

Why does Chrome use more memory than Safari for the same tabs?

Part of the difference is Site Isolation. Chrome puts each site in its own process for security, and the Chromium project lists higher memory use as a known tradeoff of that design. The exact gap depends on which sites and extensions are open.

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

When Chrome is using too much memory on a Mac, start with one question: is the Mac actually short of memory, or is Chrome just using memory that was free anyway? Open Activity Monitor, click Memory, and look at the Memory Pressure graph at the bottom. If it is green, macOS is coping and the big Chrome number is not slowing you down. If it is yellow or red, open Chrome's own Task Manager from the three-dot menu under More tools, sort by Memory, and end or close the one or two tabs at the top. Then turn on Memory Saver under Settings, Performance, so tabs you are not using are deactivated automatically. Everything below explains why those three steps come in that order, and what to do when they are not enough.

Read memory pressure before reading the Chrome number

Activity Monitor lists Chrome as dozens of rows named Google Chrome Helper, and adding them up produces a frightening figure. That figure alone says little. Apple's guide to checking whether your Mac needs more RAM is blunt about it: having free or unused memory does not necessarily improve performance, because macOS gets the best performance by using and managing all of the memory.

The signal that matters is the Memory Pressure graph. Apple defines it in three colors:

Green. The Mac is using all of its RAM efficiently.
Yellow. The Mac might eventually need more RAM.
Red. The Mac needs more RAM.

Apple's page on viewing memory usage explains what feeds that graph: the amount of free memory, the swap rate, wired memory and file cached memory. Two numbers next to it are worth reading. Compressed shows memory macOS has squeezed to make room for active apps. Swap Used shows how much the Mac is writing to the startup disk because RAM is full. A large and growing swap figure, with pressure in yellow or red, is the real definition of "too much memory," whichever app is causing it.

So the order is simple. If pressure is green and the Mac feels fine, leave Chrome alone. If pressure is green but the Mac still feels slow, the cause is probably CPU, not memory, and the CPU tab in Activity Monitor is the place to look. Only when pressure is yellow or red does trimming Chrome's memory pay off.

Why Chrome shows up as so many processes

Chrome splits itself into many processes on purpose. The browser itself, the GPU work, each extension and, most importantly, each site run separately. This is a security design called Site Isolation. The Chromium project's Site Isolation page states that cross-site documents are always put into a different process, whether in the current tab, a new tab or an embedded frame.

That page is also candid about the cost. It lists higher overall memory use as a known tradeoff, and puts the figure for desktop Chrome 67 at about 10 to 13 percent when isolating all sites with many tabs open. It is a measurement from an older version, but it shows the size of the effect: isolation adds a slice on top, it does not double the total.

In practice this means three things:

A single news page with ads and embedded videos can be several processes, because each third-party frame from a different site gets its own.
An extension that runs on every page adds a little work to every tab.
Closing a tab frees its processes. Hiding it in a collapsed group or another window does not.

None of this is a fault to fix. It is the reason one crashing tab does not take the whole browser down, and the reason a malicious page has a harder time reading data from another site.

Find the one tab that is actually heavy

Most memory complaints come down to a few tabs, not all of them. Chrome's help page on speeding up Chrome gives the route to find them:

Click the three-dot menu at the top right of Chrome.
Choose More tools, then Task Manager.
Click the Memory column to sort by it.
Look for items labeled Background page, which belong to extensions or apps running behind the scenes.
Select the task you do not need and click End Process.

Google's page warns that ending a task loses any unsaved work in it, so save first in anything with a form or an editor.

The usual suspects at the top of the list:

Long-lived web apps. Mail, chat, project boards and spreadsheets that have been open for days keep growing as they load more data.
Media and maps. Video players, design tools and map views hold large images and buffers.
Extensions with background pages. Each one runs all the time, whether or not you are using it.

There is also a quicker way to spot heavy tabs as you work. The Chrome performance settings page explains that on a Mac you can turn on Show memory usage on tab hover preview card under Settings, Appearance. Hover over a tab and its memory use appears on the preview card.

Memory Saver, and what it will not touch

Memory Saver is Chrome's built-in answer, introduced in a Google post from December 8, 2022 that claimed up to 40 percent and 10GB less memory. It deactivates tabs you are not using, and a deactivated tab reloads automatically when you return to it.

To set it, open Chrome's three-dot menu, then Settings, then Performance, and turn Memory Saver on. Google's help page lists three levels:

Level	What Google says it does
Moderate	Moderate savings, tabs become inactive after a longer period
Balanced (recommended)	Balanced savings, tabs become inactive after an optimal period
Maximum	Maximum savings, tabs become inactive after a shorter period

The detail that most guides skip is the list of things that prevent a tab from being deactivated. According to the same help page, these include active audio or video, screen sharing, page notifications, active downloads, partially filled forms, pinned tabs, and connected USB or Bluetooth devices.

Read that list again with a typical workday in mind. Gmail, Slack and a calendar are often pinned, and they all send notifications. Those are exactly the tabs that tend to grow largest over a long day, and Memory Saver is designed to leave them alone. It works well on the thirty research tabs you opened and forgot. It does very little for the five apps that never close.

Two related settings on the same page are worth knowing. Inactive tabs appearance marks deactivated tabs in the tab strip by drawing the tab icon inside a ring, so you can see at a glance which tabs Memory Saver has put to sleep and which are still holding memory. Performance issue alerts is on by default: when browsing becomes slow, Chrome shows a notification recommending tab deactivation, and clicking Fix now accepts it. If those alerts appear often while memory pressure in Activity Monitor is red, with Memory Saver already on, that is a strong hint the always-open tabs are the problem, since the forgotten ones are already being handled.

If a site keeps getting deactivated when you do not want it to, add it under "Always keep these sites active" on the same Performance page. The help page explains the format: google.com covers subdomains such as drive.google.com, a leading dot as in .google.com excludes subdomains, and an asterisk can be used as a wildcard in the host or query, as in youtube.com/watch?v=*.

Four other levers, and their cost

After Task Manager and Memory Saver, the remaining options each trade something away.

Remove extensions you do not use. Chrome's help page recommends turning off or removing them from the three-dot menu, Extensions, Manage Extensions. The cost is nothing for extensions you forgot you had. Keep the ones you rely on and drop the rest.

Change preloading. On the Performance page, Preload pages can be set to Standard preloading or Extended preloading, or turned off. Preloading fetches pages Chrome predicts you will open. Turning it off saves a little memory and network, at the cost of slightly slower clicks.

Turn on Energy Saver on battery. Google describes it as reducing image capture rate and other background tasks, and stopping eligible CPU-intensive background tabs, while leaving video calls and audio alone. It only works when the Mac is unplugged or the battery is low. This is a battery tool more than a memory tool, but it helps on a MacBook running on battery.

Restart Chrome once in a while. Long-running web apps grow over days. Quitting Chrome with Cmd+Q and reopening it, with Continue where you left off set in Settings, On startup, reopens the same pages and loads them fresh. The cost is a minute of reloading and any unsaved form state.

What does not reliably help: clearing the cache. The cache is mainly files stored on disk, and the pages you reload rebuild it anyway.

When the always-open apps are the real load

If the Task Manager list is topped by the same five web apps every day, the browser settings above have reached their limit. Those apps are pinned, they notify, and they are meant to stay open, so Memory Saver will not deactivate them by design.

Two approaches help here. The first is to accept the load and give it a separate home. Moving the always-open apps into a different window or app does not make them lighter, since they are still the same web pages. What it does is separate the two kinds of browsing: Chrome goes back to being a place for pages you open and close, where Memory Saver can do its job, and the apps sit somewhere you can see their cost on their own.

App aggregation browsers on macOS take this approach. Each web app gets a fixed place in a sidebar with its own session, and notifications from all of them arrive in one place. The supported apps page lists the services that can be added by name, and the comparisons with Wavebox and Rambox show how others in the category handle the same idea.

The second approach is honest arithmetic. If pressure stays yellow or red with only the apps you truly need open, the Mac is short of memory for the workload. Apple's guide explains how to check whether your model has upgradeable memory: hold Option, choose Apple menu, System Information, then Memory under Hardware. On most recent Macs it does not, and the next machine should have more.

What to change first

Open Activity Monitor and check memory pressure. If it is yellow or red, sort Chrome's Task Manager by Memory, close the top offenders, and turn on Memory Saver at Balanced. If the heavy rows are always the same pinned apps, consider moving them out of Chrome into an app aggregation browser such as SpaceDeck, so Chrome's own tab deactivation can work on the rest.