Google Chrome Helper High CPU on Mac: How to Fix It
Open Activity Monitor with a dozen Chrome tabs going and you’ll usually find several "Google Chrome Helper" processes, one or more pinned near 100% CPU. Here’s what they’re doing and how to fix it.
Quick Answer
"Google Chrome Helper" processes are normal — Chrome runs each tab, extension, and GPU task in its own separate process for stability and security, so seeing several is expected. High CPU usually traces back to one specific tab or extension: a heavy web app, an autoplaying video, a tracking-script-heavy site, or a misbehaving extension. Chrome’s own Task Manager (Window → Task Manager, or ⇧⌘Esc) shows CPU per tab so you can identify and close the exact culprit instead of quitting Chrome entirely.
Why There Are Multiple "Helper" Processes
Chrome uses a multi-process architecture: each tab (and often each extension and the GPU compositor) runs as its own separate "Helper" process. This is deliberate — if one tab crashes or hangs, it doesn’t take down the whole browser or your other tabs. The tradeoff is that a browser with many tabs open naturally shows several Helper entries in Activity Monitor, and it’s not obvious at a glance which one is the actual problem.
How to Find and Fix the Culprit
- Open Chrome’s Task Manager via Window → Task Manager (or Shift+Esc while Chrome is focused). Unlike macOS Activity Monitor, this shows CPU and memory per individual tab and extension.
- Sort by CPU and close or reload the tab(s) at the top — often a single page with heavy ads, video autoplay, or an infinite-scroll feed.
- Disable extensions one at a time if no single tab stands out; ad blockers and privacy extensions that scan every page are common offenders when misconfigured.
- Check for a stuck background tab. Tabs playing audio/video in the background (look for the speaker icon on the tab) keep decoding even when not visible.
- Update Chrome. Google regularly ships performance and memory fixes; an outdated version is more likely to have a known CPU-heavy bug.
Does Clearing Chrome’s Cache Help?
Clearing the cache mainly helps with disk space and occasional page-loading glitches, not runaway CPU from an active tab — the two are usually unrelated. If Chrome’s cache has grown large and is contributing to a cluttered disk, see our guide on clearing Chrome cache on Mac as a separate maintenance step.
Keep Your Whole Mac Running Light
Clear browser cache and background junk in one pass with TrimyMac, free to start.
Download TrimyMac FreeFrequently Asked Questions
Is Google Chrome Helper a virus?
No, it’s a legitimate part of Chrome’s architecture — each tab, extension, and the GPU process run as separate "Helper" processes by design. It becomes a concern only if it’s consuming abnormal CPU/memory, which points to a specific tab or extension, not malware.
How do I stop Chrome Helper from using so much CPU?
Open Chrome’s own Task Manager (Window → Task Manager) to see CPU usage per tab and extension, then close or reload the highest-usage tab. This is more precise than force-quitting Chrome entirely from Activity Monitor.
Why does Chrome use more CPU than Safari on Mac?
Chrome’s cross-platform rendering engine and extension ecosystem are generally less power-optimized for macOS than Safari, which is built and tuned specifically for Apple hardware. Heavy extension use widens this gap further.
Does closing tabs actually free up CPU immediately?
Yes — closing a tab terminates its Helper process, immediately releasing whatever CPU and memory it was using, unlike minimizing the window, which keeps the tab’s process running in the background.