Freeing Chrome Memory on a Mac: What Works and What Returns
To free memory in Google Chrome right now, open Chrome's Task Manager, sort by memory, and end the tab or extension at the top of the list. To keep it free, turn on Memory Saver under Settings > Performance, which puts tabs you are not using to sleep and reloads them when you return. Those two steps cover most of the gain. What usually goes wrong afterwards is that the number climbs back within an hour, because the tabs that use the most memory are web apps people keep open all day on purpose. This guide covers the immediate release, the settings that keep memory down, how to read the Mac's own memory figures so you know whether there is a problem at all, and what to do about the tabs that refuse to stay asleep. The Chrome and Apple help pages cited here were checked on October 18, 2026.
First check whether memory is the problem
Chrome showing several gigabytes in use is not, by itself, a fault. macOS is designed to use memory rather than leave it empty. Apple's guide Check if your Mac needs more RAM in Activity Monitor says it directly: having free or unused memory does not necessarily improve performance, because macOS gets the best performance by managing all of the memory efficiently.
The figure to look at is Memory Pressure. Apple's page on viewing memory usage in Activity Monitor explains what each value at the bottom of the Memory tab means:
- Memory Pressure is a graph of how well memory is meeting demand, based on free memory, swap rate, wired memory and cached files.
- Compressed is memory the system has squeezed to make room. When the Mac approaches its limit, inactive apps are compressed first.
- Swap Used is space on the startup disk being used to move data out of RAM.
- Cached Files is memory holding recently used files, which stays available to speed up reopening them.
Open Activity Monitor from Applications > Utilities, click Memory, and watch the graph while working normally. If it stays low and the Mac feels responsive, Chrome's number is not worth fighting. If the graph sits high, the Mac slows when switching apps, and Swap Used keeps growing, then freeing Chrome memory will help.
Release memory now: Chrome's Task Manager
Activity Monitor lists Chrome as many separate processes called Google Chrome Helper, which does not say which tab is responsible. Chrome's own Task Manager does. On a Mac, open it from the menu bar with Window > Task Manager, or from the three-dot More menu under More tools > Task manager.
Each row is a tab, an extension, or a background process such as the GPU process. Click the Memory footprint column to sort by it. Typical findings:
- One web app far above the rest. Long-running apps such as a mail client, a design tool, a spreadsheet with many sheets, or a video call tab often grow over the day. Reloading that tab usually returns it to its starting size.
- An extension using memory on every page. Extensions that read every page, such as some ad blockers and shopping helpers, show their own row. If one is heavy and rarely needed, remove it from More > Extensions > Manage Extensions.
- Many small tabs. Thirty tabs at a modest size each add up to more than one heavy app. Closing or bookmarking a group of them is the fastest gain.
Select a row and click End process to stop it. The tab shows an error page and can be reloaded. Anything unsaved in that tab, such as a half-written form, is lost, so check before ending a tab that holds work.
Find a heavy extension the systematic way
Task Manager shows each extension's own process, but an extension can also add weight inside every tab it touches, which is counted against the tab rather than the extension. Google's troubleshooting page Fix connection and loading errors in Chrome describes a method that works just as well for memory. First open the same pages in an Incognito window, where extensions are off unless allowed. If the problem disappears there, return to a normal window, disable all extensions, and then re-enable them one at a time to find the one responsible.
Applied to memory, the test is simple. Open the three or four tabs used most, note their sizes in Task Manager, then repeat with extensions off. A large gap points to an extension. Removing an extension that runs on every site often frees more over a day than any tab setting, because its cost is repeated in each open tab.
Extensions that duplicate something Chrome already does are the usual candidates: tab suspenders on a Chrome version that has Memory Saver, a second ad blocker, or a shopping or coupon helper installed once and forgotten.
Restart Chrome as the last step
If Task Manager shows nothing unusual but memory pressure is still high, quitting Chrome with Command and Q and reopening it releases everything at once. Chrome can reopen the previous tabs if On startup in Settings is set to continue where you left off, and the tabs then load only when clicked. This is the cleanest reset, and it costs about a minute.
Keep memory down: Memory Saver and its settings
The Task Manager fix lasts until the next heavy tab grows. Memory Saver is the setting that keeps memory lower over the day. Google's Personalize Chrome performance page explains it: Chrome deactivates tabs you are not currently using, and an inactive tab reloads automatically when you go back to it.
To turn it on:
- Open Chrome, click More at the top right, then Settings.
- On the left, select Performance.
- Turn on Memory Saver.
- Choose a level.
The page lists three levels:
| Level | What Google says it does | Suits |
|---|---|---|
| Moderate | Tabs become inactive after a longer period | People who return to tabs often |
| Balanced (recommended) | Tabs become inactive after an optimal period | Most use |
| Maximum | Tabs become inactive after a shorter period | Macs with 8 GB of memory or heavy multitasking |
Why some tabs never go to sleep
The same page lists activities that can prevent a tab from being deactivated:
- Active audio or video, including calls
- Screen sharing
- Page notifications
- Active downloads
- Partially filled forms
- Pinned tabs
- Connected devices over USB or Bluetooth
Two items on this list explain most cases where Memory Saver seems to do nothing. Pinned tabs are excluded, and many people pin exactly the heavy apps: mail, chat and calendar. And page notifications keep a tab awake, which covers any web app that has permission to send notifications. If the heaviest tabs are both pinned and notifying, Memory Saver leaves them alone by design.
Exclude the sites that must stay awake
Going the other way, some tabs should never reload, such as a web app with a long-running upload. Under Settings > Performance, next to Always keep these sites active, click Add, then either pick from current tabs or type an address. Google's page explains the format: google.com covers all its subdomains such as drive.google.com, while a leading dot (.google.com) matches only that exact host.
See each tab's memory on hover
To keep an eye on usage without opening Task Manager, the same help page describes a setting on Mac under Settings > Appearance: turn on Show memory usage on tab hover preview card. Hovering over a tab then shows how much memory it uses. Turning on Inactive tabs appearance under Performance also marks sleeping tabs with a ring around the icon, which shows at a glance whether Memory Saver is working.
Energy Saver is a different setting
Energy Saver sits on the same Performance page but solves a different problem. According to Google's page, it reduces image capture rate and background tasks to extend battery life, works only when unplugged or when the battery is low, and does not turn on when the Mac is plugged in. It is not a memory tool.
Why the number climbs back
After all of the above, memory still rises over the course of a working day for three reasons.
The heavy tabs are the ones in use. Memory Saver only sleeps tabs you are not using. A mail tab checked every ten minutes is never idle long enough at the Moderate or Balanced level.
Pinned and notifying tabs are exempt. As listed above, these two conditions block deactivation. Unpinning a tab or turning off a site's notification permission lets Memory Saver act on it, at the cost of missing alerts.
Reloading costs something too. A sleeping tab reloads when clicked, which takes a moment and uses network and processor time. On a Mac where memory pressure is low, sleeping tabs aggressively makes the browser feel slower rather than faster. That is the reason to check the Activity Monitor graph first.
The tabs that are really apps
Most of the memory in a long Chrome session belongs to a small set of web apps kept open all day, mainly for one reason: to see when something new arrives. Mail, chat, project tools and social inboxes stay in pinned tabs so their unread counts remain visible, and those are exactly the tabs Memory Saver will not touch.
One way to change that is to separate "seeing that something arrived" from "keeping the whole app open". An app aggregation browser for macOS puts each web app in its own panel with its own session, and the one described on the Features page reads unread counts for services such as LinkedIn, Facebook, X and Slack straight from the service and shows them on the sidebar icon, so they can be watched in the background without keeping a tab open. It also collects alerts in one notification center with a Do Not Disturb schedule.
This is not a memory-saving feature in itself. Each app that is open still runs its own web page, and opening ten apps in a separate app uses memory just as ten tabs would. The gain comes only if the badges let you close apps you were keeping open just to watch for new messages. The free plan covers 1 workspace with up to 3 apps, and the pricing page lists the full version at $7 per month, $60 per year, or $129 one-time, with a 14-day trial and no card. The FAQ notes that Chrome extensions install from the Chrome Web Store as usual.
What to change first
Open Activity Monitor and check Memory Pressure before changing anything. If it is high, use Chrome's Task Manager to find and reload the heaviest tab, then turn on Memory Saver at Balanced and unpin any heavy tab you only keep pinned for its unread count. If the tabs you keep open all day are mainly for watching notifications, see whether SpaceDeck badges let you close them.
Frequently asked questions
Does closing Chrome windows free all of its memory?
Closing a window releases the memory used by its tabs, but Chrome keeps running in the background on a Mac until it is quit. Quitting with Command and Q releases everything Chrome was using. Reopening it with previous tabs restored loads each tab only when clicked.
Which Memory Saver level should be used on an 8 GB Mac?
Balanced is Google's recommended level and suits most use. If Activity Monitor shows high memory pressure and growing swap during normal work, Maximum makes tabs inactive sooner. Check whether the heaviest tabs are pinned, since pinned tabs are not deactivated at any level.
Why does Memory Saver not put a particular tab to sleep?
Google lists conditions that prevent deactivation, including audio or video playing, screen sharing, page notifications, active downloads, partly filled forms, pinned tabs and connected devices. A pinned mail or chat tab with notifications turned on meets two of these at once.
Is it safe to end a process in Chrome's Task Manager?
Ending a tab's process stops that page and shows an error that can be cleared by reloading. Anything not saved in that tab, such as text typed into a form, is lost. Ending an extension's process stops the extension until Chrome restarts or it is reloaded.
Is high Chrome memory use always a problem on a Mac?
No. macOS is built to use available memory, and Apple notes that free memory does not necessarily improve performance. The Memory Pressure graph in Activity Monitor is the better guide. If it stays low and the Mac feels responsive, no action is needed.