What is Google Chrome Helper (GPU), and why is it using so much CPU?
Last reviewed: 19 November 2026. Helper bundle names, bundle IDs and the graphics acceleration setting checked in Google Chrome 157 on macOS 26.3.1.
Google Chrome Helper (GPU) is Chrome's single GPU process, which draws everything Chrome shows on screen and sends graphics and video work to the Mac's GPU for all tabs at once. It gets busy with video, WebGL, games, animated pages and many windows, and it uses more when Chrome cannot use hardware acceleration. Pausing media and checking that graphics acceleration is on usually brings it down.
Google Chrome Helper (GPU) at a glance
| Google Chrome Helper (GPU) | |
|---|---|
| Made by | Google (part of Google Chrome) |
| Type | Helper process (Chromium GPU process) |
| Location | /Applications/Google Chrome.app/Contents/Frameworks/Google Chrome Framework.framework/Versions/[version]/Helpers/Google Chrome Helper (GPU).app/Contents/MacOS/Google Chrome Helper (GPU) |
| Runs as | your user |
| Bundle ID | com.google.Chrome.helper |
| Can you quit it? | Yes. Chrome restarts it; pages may flicker or redraw while it does. |
What is Google Chrome Helper (GPU)?
Google describes the GPU process as handling GPU tasks in isolation from other processes. Renderers do not draw to the screen themselves; they send drawing commands to this process, which composites the final image for every Chrome window.
There is one GPU process per Chrome session, so its CPU and GPU time is the sum of all tabs that draw or play video. On a Mac it is started from the Google Chrome Helper (GPU).app bundle inside Chrome's framework.
Is Google Chrome Helper (GPU) safe?
Yes, when it runs from inside Google Chrome.app and is signed by Google LLC. It is part of Chrome's normal design and starts with the browser.
Why does Google Chrome Helper (GPU) use so much CPU, energy and memory?
- Video in any tab. Video playback, including muted autoplay in background tabs, is composited here. High-resolution or high frame-rate video costs the most.
- WebGL, games and canvas animation. 3D pages, browser games, map views and animated charts draw constantly, which keeps the GPU process and the graphics processor busy.
- Graphics acceleration turned off. With Use graphics acceleration when available off, drawing work falls back to the CPU and this process uses much more CPU for the same pages.
- Many large windows and displays. Several large windows on high-resolution displays need large drawing buffers, which raises the GPU process's memory.
How much CPU is normal for Google Chrome Helper (GPU)?
With static pages open, it sits at a low, steady level and rises while you scroll or a page animates. Continuous use during video is expected.
Its memory includes graphics buffers, so it can be one of Chrome's larger processes on a Mac with several displays.
How do you stop Google Chrome Helper (GPU) from using so much CPU?
- Find the tab that draws or plays video. Open More > More tools > Task Manager in Chrome. The GPU process appears as one row; close or pause the tabs with video, games or animation and watch it drop.
- Check graphics acceleration. Go to More > Settings > System and make sure Use graphics acceleration when available is on, then relaunch Chrome.
- Turn on Energy Saver. Go to More > Settings > Performance and turn on Energy Saver. Google says it reduces background tasks when the Mac is unplugged or the battery is low.
- Update Chrome. Open More > Help > About Google Chrome to install updates, then click Relaunch.
When should you worry about Google Chrome Helper (GPU)?
If the GPU process stays busy with every tab closed, or Chrome shows graphical glitches, relaunch Chrome. If it persists, open chrome://gpu to see whether hardware acceleration is reported as available.
A process named Google Chrome Helper (GPU) outside Google Chrome.app would not be Chrome's.
How do you check Google Chrome Helper (GPU) in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), and type Google Chrome Helper (GPU) in the search field. The CPU tab shows its % CPU. The Energy tab shows its Energy Impact. The Memory tab shows its Memory. Double-click the row for its parent process, memory details and open files.
In Terminal, the first command lists every Google Chrome Helper (GPU) process with its PID, user, CPU and memory (RSS is resident memory in kilobytes).
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'Google Chrome Helper (GPU)' | grep -v grep
pmset -g assertions # shows processes keeping the Mac awake
How can Thrum help with Google Chrome Helper (GPU)?
Thrum keeps a live CPU graph in the menu bar. One click shows the eight processes using the most CPU, so you can see when Google Chrome Helper (GPU) is among them and how much it takes. An optional alert tells you when a process stays above a CPU level you choose (50 to 200% of one core) for 1 to 10 minutes. Click Google Chrome Helper (GPU) in the list for its PID, threads and memory, and Quit or Force Quit it after a confirmation.
Thrum is $4.99 once with a 14-day free trial and no account. It requires macOS 26 Tahoe on Apple silicon or Intel.
Questions about Google Chrome Helper (GPU)
Should I turn off hardware acceleration in Chrome?
Usually not. Turning off graphics acceleration moves drawing work to the CPU, which raises CPU use. It is a troubleshooting step for display glitches, not for performance.
Why does Google Chrome Helper (GPU) have the same bundle ID as Google Chrome Helper?
Both helper apps use com.google.Chrome.helper in Chrome 157, while the renderer helper uses com.google.Chrome.helper.renderer. The process name, not the bundle ID, tells you which kind of process you are looking at.