Thrum

What is Google Chrome Helper (no Renderer or GPU), and why is it busy?

Last reviewed: 19 November 2026. Helper bundle names and bundle IDs checked in Google Chrome 157 on macOS 26.3.1.

Google Chrome Helper, with nothing in brackets, is the helper Chrome uses for its utility and service processes, such as the network service, storage service and audio, which Chromium has split out of the main browser process. Its CPU and network use reflect work for all tabs, such as downloads, many pages loading or audio playing. Chrome's own Task Manager labels each of these processes by its job.

Google Chrome Helper at a glance

Google Chrome Helper
Made byGoogle (part of Google Chrome)
TypeHelper process (Chromium utility and service processes)
Location/Applications/Google Chrome.app/Contents/Frameworks/Google Chrome Framework.framework/Versions/[version]/Helpers/Google Chrome Helper.app/Contents/MacOS/Google Chrome Helper
Runs asyour user
Bundle IDcom.google.Chrome.helper
Can you quit it?Yes, but the Chrome feature it serves (often the network service or audio) stops until Chrome restarts it.

What is Google Chrome Helper?

Chromium's design separates components such as the network service and the storage service from the browser process, and runs small or risky tasks in sandboxed utility processes. On a Mac, these are started from Google Chrome Helper.app, so several processes with the same name are common.

Web pages are not in these processes; they run in Google Chrome Helper (Renderer). Graphics run in Google Chrome Helper (GPU). The plain helper's job varies from process to process, which is why Chrome's Task Manager is the easiest way to tell them apart.

Is Google Chrome Helper safe?

Yes, when it runs from inside Google Chrome.app and is signed by Google LLC. A process with this name elsewhere, or with a different signature, is not part of Chrome.

Why does Google Chrome Helper use so much network, disk and CPU?

How much CPU is normal for Google Chrome Helper?

Most plain helpers sit near 0% CPU and rise briefly when Chrome loads pages, writes data or plays sound. The network service helper is active whenever pages are loading.

Several Google Chrome Helper processes at once is normal; each runs a different service.

How do you see what a Google Chrome Helper is doing?

  1. Match it in Chrome's Task Manager. Open More > More tools > Task Manager. Rows such as Utility: Network Service or Utility: Audio Service show the job of each helper, with the same process ID that Activity Monitor shows.
  2. Watch its traffic. Note the PID in Activity Monitor and run nettop -p <PID> in Terminal to see which hosts the network service is talking to.
  3. Stop large transfers. Type chrome://downloads in the address bar and pause or cancel downloads you do not need.
  4. Relaunch Chrome. Quitting Chrome with Command-Q ends all its helpers. If a helper stays high after relaunch with no tabs open, update Chrome from More > Help > About Google Chrome.

When should you worry about Google Chrome Helper?

A plain Chrome helper that stays above 50% CPU for many minutes with no downloads and no audio is unusual. Check Chrome's Task Manager for the service name and relaunch Chrome.

Helpers keep running only while Chrome runs. If Google Chrome Helper processes remain after Chrome has quit, double-click one in Activity Monitor to see its parent process.

How do you check Google Chrome Helper in Activity Monitor and Terminal?

Open Activity Monitor (Applications > Utilities), and type Google Chrome Helper in the search field. The Network tab shows its Sent Bytes and Rcvd Bytes. The Disk tab shows its Bytes Written and Bytes Read. The CPU tab shows its % CPU. Double-click the row for its parent process, memory details and open files.

In Terminal, the first command lists every Google Chrome Helper process with its PID, user, CPU and memory (RSS is resident memory in kilobytes). fs_usage prints each file it reads or writes until you press Control-C; it needs an administrator password. nettop shows its live network traffic.

ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'Google Chrome Helper' | grep -v grep
sudo fs_usage -w -f filesys <PID>    # PID from the ps line above
nettop -p <PID>    # PID from the ps line above

How can Thrum help with Google Chrome 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 Google Chrome 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 Google Chrome 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 Google Chrome Helper

What is the difference between Google Chrome Helper, (Renderer) and (GPU)?

Renderer processes run web pages and extensions, the GPU process draws to the screen, and the plain helper runs Chrome's utility services such as networking, storage and audio.

Can I stop Google Chrome Helper from running in the background?

When Chrome is quit, its helpers end. If Chrome keeps running after you close its windows, look for apps or extensions that run in the background; Chrome lists the setting Continue running background apps when Google Chrome is closed under More > Settings > System.

Sources