What is Firefox GPU Helper, and why is it using so much CPU?
Last reviewed: 19 November 2026. Path, bundle ID and process type checked with Firefox 157 on macOS 26.3.1.
Firefox GPU Helper is Firefox's GPU process: it does compositing and talks to the Mac's graphics hardware in an isolated process, on behalf of every tab. Video, WebGL, games and animated pages make it busy, and the load from all windows adds up in this one process. Pausing media and keeping hardware acceleration on usually brings it down.
Firefox GPU Helper at a glance
| Firefox GPU Helper | |
|---|---|
| Made by | Mozilla (part of Firefox) |
| Type | Helper process (Firefox GPU process) |
| Location | /Applications/Firefox.app/Contents/MacOS/gpu-helper.app/Contents/MacOS/Firefox GPU Helper |
| Runs as | your user |
| Bundle ID | org.mozilla.firefox-gpu-helper |
| Can you quit it? | Yes. Firefox starts a new one; windows may redraw while it does. |
What is Firefox GPU Helper?
Mozilla's process model documentation describes the GPU process as performing compositing and communicating with GPU hardware in an isolated process. In Firefox 157 on macOS it runs from a separate helper app, gpu-helper.app, inside Firefox's bundle, and its command line ends with the process type gpu.
There is one GPU process for the whole browser. Firefox's Task Manager (about:processes) lists it as GPU with its PID, so you can match it to Activity Monitor.
Is Firefox GPU Helper safe?
Yes. It is inside Firefox.app, has the bundle ID org.mozilla.firefox-gpu-helper, and is covered by Mozilla's signature on the app.
Why does Firefox GPU Helper use so much CPU, energy and memory?
- Video in any tab. Every playing video is composited here, including muted autoplay in background tabs.
- WebGL, canvas and games. Pages that draw every frame keep the GPU process and the graphics processor busy for as long as they are open.
- Large or many windows. Big windows on high-resolution displays, and many windows at once, mean more pixels to composite on each frame.
- Graphics buffers. Textures and frame buffers for open pages are held for the GPU, which shows up as memory in this process.
How much CPU is normal for Firefox GPU Helper?
With static pages open it is quiet, rising while you scroll or a page animates. Steady use during video playback is expected.
Only one Firefox GPU Helper runs per Firefox session.
How do you stop Firefox GPU Helper from using so much CPU?
- Find the drawing tab. Open
about:processesand look at which content process is busy alongside GPU. Pause or close tabs with video, games or animation. - Keep hardware acceleration on. In Settings > General > Performance, keep Use recommended performance settings selected, or select Use hardware acceleration when available. Without acceleration, drawing work moves to the CPU.
- Check graphics details. Help > More Troubleshooting Information opens about:support, whose Graphics section shows what Firefox is using for compositing.
- Restart Firefox. Quit with Command-Q and reopen to start a fresh GPU process if it stays busy after the drawing tabs are closed.
When should you worry about Firefox GPU Helper?
Constant high CPU with no video, games or animation open, or repeated graphics glitches, are reasons to restart Firefox and update it. Help > About Firefox checks for updates.
A process named Firefox GPU Helper outside Firefox.app is not Mozilla's.
How do you check Firefox GPU Helper in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), and type Firefox GPU Helper 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 Firefox GPU Helper process with its PID, user, CPU and memory (RSS is resident memory in kilobytes).
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'Firefox GPU Helper' | grep -v grep
pmset -g assertions # shows processes keeping the Mac awake
How can Thrum help with Firefox GPU Helper?
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 Firefox GPU Helper 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 Firefox GPU Helper 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 Firefox GPU Helper
Does Firefox use a GPU process on macOS?
Yes. In Firefox 157 on macOS 26 the GPU process runs as Firefox GPU Helper. Mozilla's documentation says the GPU process is not used on every platform, so older versions may not show it.
Is Firefox GPU Helper the same as plugin-container?
No. plugin-container hosts Firefox's content, network and media processes; the GPU process has its own helper app.
Sources
- Firefox Source Docs: Process Model
- Firefox 157 interface strings (about:processes and Performance settings), read from Firefox.app on this Mac