BondiWhy is Chrome using so much memory on my Mac?
Add Bondi as a preferred source on GoogleChrome splits itself into dozens of processes, one for many of the tabs and extensions you have open. Activity Monitor then shows a pile of "Google Chrome Helper" rows, none of them huge, and the real total is easy to miss. To see how much RAM Chrome is using on a Mac, add every one of those processes up.
Key points
- Chrome's memory is the sum of the app plus every Google Chrome Helper, renderer and related process.
- In one real reading, Chrome was 68 processes using 6.69 GB. The biggest single row was 600.8 MB.
- Watch memory pressure, not one helper. Green means the Mac is comfortable; yellow or red is when Chrome's total starts to matter.
One reading, with Chrome open
This is the Mac I measure on: a 14-inch MacBook Pro (M1 Max, 64 GB), 16 October 2026, memory pressure Normal. Chrome had a normal work session open. Visual Studio Code and Cursor were running too.
| App | Processes | Memory | CPU |
|---|---|---|---|
| Google Chrome | 68 | 6.69 GB | 9.9% of one core |
| Visual Studio Code | 36 | 4.38 GB | 4.9% |
| Cursor | 40 | 2.77 GB | 43.8% |
| macOS | 651 | 15.36 GB | — |
Grouped by Bondi. Chrome was the heaviest app. It was not the busiest: Cursor was using more CPU at that moment.
Of those 68 Chrome processes, 39 were named Google Chrome Helper (Renderer) and 11 were Google Chrome Helper. Those names are the tabs, extensions and sandboxed pieces. None of them is the answer on its own. Together they were 6.69 GB.
That is one Mac, in the middle of work. Fewer tabs uses less; a long session with many windows uses more. An earlier reading on the same Mac had Chrome at 80 processes and 12.23 GB. The number moves with what you have open.
How to add it up
In Activity Monitor: Memory tab, type Google Chrome in the search field, then choose View → All Processes, Hierarchically. Expand Chrome and add the rows. Activity Monitor doesn't give you a total.
In Chrome itself: choose Window → Task Manager. That list is Chrome's own view of its tabs and extensions, which is handy for closing one heavy tab without quitting the whole browser.
In Bondi: Chrome is one row, helpers included.
What actually helps
Only do this if memory pressure is yellow or red, or the Mac feels slow:
- Close tabs you don't need, especially video, docs and tools that stay live in the background.
- Turn off extensions you aren't using. Each one is often its own process.
- In Chrome, open Settings → Performance and turn on Memory Saver, which puts idle tabs to sleep. I haven't measured how much it saves on this Mac, so I won't quote a figure.
- Quit Chrome from the Chrome menu (not the red traffic light) if helpers are still running after you close the windows.
Don't hunt down individual Google Chrome Helper rows and force-quit them. That's how you crash a tab.
Questions
Why is Chrome using so much memory on a Mac?
Each tab, extension and some background work runs in its own process, so the total is spread across dozens of rows. In one reading, that total was 6.69 GB across 68 processes.
How much RAM does Chrome use on a Mac?
It depends how many tabs and extensions you have open. On this Mac it has been 6.69 GB in one session and 12.23 GB in another. Add every Chrome process; the biggest helper is not the total.
Is Chrome making my Mac slow?
Memory and CPU are different. In this reading Chrome was the RAM hog (6.69 GB) but only 9.9% of one CPU core. If the Mac is slow, check memory pressure first, then Activity Monitor's CPU tab.
Also as plain text, for AI assistants and readers.