The short answer
Google Chrome Helper processes are part of Chrome: it runs web pages and extensions in “Helper (Renderer)” processes and drawing in “Helper (GPU)”, so dozens of them are normal. To find which tab or extension is responsible, open Chrome's own Task manager (Window → Task Manager, or ⋮ → More tools → Task manager), sort by Memory Footprint or CPU, and close, reload or disable what's at the top. Then check Activity Monitor's memory pressure graph: if it's green, Chrome's memory use isn't slowing the Mac down. If it's yellow or red with swap growing, close heavy tabs, turn on Memory Saver in Chrome's Performance settings, and disable extensions you don't need.
On this page
Why there are so many Chrome Helper processes
Chrome splits its work into separate processes. Chromium's documentation gives the reasons: a crash or hang in one site's process doesn't take down the others, and sites can run in parallel, at the cost of some memory for each process. On a Mac, Chrome keeps different sites in different processes, and extensions get processes of their own.
| Process name | What it runs |
|---|---|
| Google Chrome | The browser itself: windows, the tab strip and coordinating everything else. |
| Google Chrome Helper (Renderer) | Web pages and extensions. Each one runs one or more tabs or frames from the same site, or an extension. This is where most of the memory goes. |
| Google Chrome Helper (GPU) | Drawing pages, video and animation with the graphics processor. |
| Google Chrome Helper | Utility work such as networking, audio and storage. Chrome's Task manager lists these as “Utility”. |
Google Chrome
- What it runs
- The browser itself: windows, the tab strip and coordinating everything else.
Google Chrome Helper (Renderer)
- What it runs
- Web pages and extensions. Each one runs one or more tabs or frames from the same site, or an extension. This is where most of the memory goes.
Google Chrome Helper (GPU)
- What it runs
- Drawing pages, video and animation with the graphics processor.
Google Chrome Helper
- What it runs
- Utility work such as networking, audio and storage. Chrome's Task manager lists these as “Utility”.
So forty Chrome rows in Activity Monitor is normal, and none of them tells you which tab it belongs to. Activity Monitor also has no total for Chrome; you'd have to add the rows up yourself. See process vs app in the glossary.
First, check whether it's actually a problem
A large Chrome figure on its own isn't a fault. macOS hands spare memory to apps that ask for it. What matters is whether the Mac has run short. Open Activity Monitor, click Memory, and look at the Memory Pressure graph and Swap Used:
| Memory pressure | Chrome at the top? | What it means |
|---|---|---|
| Green | Yes | Chrome is using memory the Mac has to spare. Nothing to fix unless a tab is also using CPU or the Mac feels slow. |
| Yellow | Yes, and growing | Chrome is crowding other apps. Find the heaviest tabs and close or reload them, and turn on Memory Saver. |
| Red, Swap Used growing | Yes | The Mac is short of memory and is writing to swap. Save your work and close heavy tabs now, then use the steps below. |
| Yellow or red | No | Chrome isn't the main cause. See what is memory pressure to find the app that is. |
Green
- Chrome at the top?
- Yes
- What it means
- Chrome is using memory the Mac has to spare. Nothing to fix unless a tab is also using CPU or the Mac feels slow.
Yellow
- Chrome at the top?
- Yes, and growing
- What it means
- Chrome is crowding other apps. Find the heaviest tabs and close or reload them, and turn on Memory Saver.
Red, Swap Used growing
- Chrome at the top?
- Yes
- What it means
- The Mac is short of memory and is writing to swap. Save your work and close heavy tabs now, then use the steps below.
Yellow or red
- Chrome at the top?
- No
- What it means
- Chrome isn't the main cause. See what is memory pressure to find the app that is.
memory_pressure | tail -1
sysctl vm.swapusageHigh CPU is a different question. A “Helper (Renderer)” at high % CPU with memory pressure green is costing battery and heat, not memory. The next step finds it either way.
Step 1: find the tab or extension with Chrome's Task manager
Activity Monitor can't see inside Chrome, but Chrome can. Its Task manager lists each process with the tabs and extensions it runs.
- In Chrome, choose Window → Task Manager from the menu bar, or click ⋮ and choose More tools → Task manager. There's no keyboard shortcut for it on a Mac.
- Click the Memory Footprint column to sort by memory, or CPU to sort by processor use. Watch for a minute: what matters is what stays at the top.
- Read the Task column. Rows start with what they are: Tab: a web page, Extension: an extension, Subframe: content embedded from another site, such as a video player or an ad, Utility: background work, and GPU Process.
- Right-click any column heading to add more, such as JavaScript memory, GPU memory or Idle wake ups.
- To match a row in Activity Monitor, compare the Process ID column with the PID in Activity Monitor.
Google's own troubleshooting guide for IT admins describes the renderer process the same way: it is responsible for one or more tabs or extensions that are in use. So a busy “Helper (Renderer)” always comes down to a page or an extension, and the Task manager names it.
| What's at the top | What it usually means | What to do |
|---|---|---|
| One tab using several GB, still growing | A heavy web app (documents, design tools, dashboards, email) or a page that keeps growing the longer it's open. | Reload the tab. If it grows back every time, keep it closed when you aren't using it. |
| A tab with high CPU you aren't looking at | The page is running scripts, animation or video in the background. | Pause the video, or reload or close the tab. |
| An extension | The extension is doing work on every page, or has a problem. | Turn it off at chrome://extensions and compare. |
| GPU Process | Video, 3D content or many animated pages, across all tabs. | Close video tabs you aren't watching. If it stays high with little open, see the graphics acceleration step below. |
| Lots of tabs, none large | It's the number of tabs, not one page. | Turn on Memory Saver, and close or bookmark tabs you aren't using. |
One tab using several GB, still growing
- What it usually means
- A heavy web app (documents, design tools, dashboards, email) or a page that keeps growing the longer it's open.
- What to do
- Reload the tab. If it grows back every time, keep it closed when you aren't using it.
A tab with high CPU you aren't looking at
- What it usually means
- The page is running scripts, animation or video in the background.
- What to do
- Pause the video, or reload or close the tab.
An extension
- What it usually means
- The extension is doing work on every page, or has a problem.
- What to do
- Turn it off at
chrome://extensionsand compare.
GPU Process
- What it usually means
- Video, 3D content or many animated pages, across all tabs.
- What to do
- Close video tabs you aren't watching. If it stays high with little open, see the graphics acceleration step below.
Lots of tabs, none large
- What it usually means
- It's the number of tabs, not one page.
- What to do
- Turn on Memory Saver, and close or bookmark tabs you aren't using.
Step 2: fix what you found
- Close or reload the heavy tab. Reloading gives back the memory a long-running page has built up.
- Turn off extensions you don't use. Open
chrome://extensionsand switch them off. Turn the rest back on one at a time if you aren't sure which one was the problem. - Turn on Memory Saver. In Chrome, open Settings → Performance. Memory Saver frees memory from inactive tabs, which become active again when you go back to them. Choose Moderate, Balanced or Maximum, and add sites that must keep running, such as a call or music, under Always keep these sites active.
- Turn on Performance issue alerts. In the same Performance settings, they notify you when Chrome detects a performance problem and suggest a fix.
- See memory per tab. Turn on Show tab memory usage in Settings → Appearance, and hovering over a tab shows how much memory it's using.
- On battery, use Energy Saver. Also in Settings → Performance, it limits background activity and visual effects such as smooth scrolling and video frame rates.
- Update Chrome. Choose ⋮ → Help → About Google Chrome. Current versions need macOS 13 Ventura or later.
- Restart Chrome if it's been open for days. To get your tabs back afterwards, set Settings → On startup → Continue where you left off first. Closing the last window doesn't quit Chrome on a Mac; choose Chrome → Quit Google Chrome.
If the GPU Process stays busy with little open, try turning off Use graphics acceleration when available in Settings → System and relaunching Chrome. Treat it as a test: video and animation may get choppier and use more CPU. Turn it back on if it doesn't help.
The faster way: Chrome as one app in iKnowMyMac
iKnowMyMac counts every Chrome helper under Google Chrome, so Activity Monitor's dozens of rows become one row with one total, and you can expand it to see each process. The Memory tab shows how much each app grew in the last hour, and Diagnosis names Chrome when its growth is behind rising memory pressure and swap. To find the tab inside Chrome, use Chrome's Task manager as above.