macOS processes › Browsers and web content
What is Google Chrome Helper on Mac?
Google Chrome Helper processes are parts of Google Chrome. The plain Google Chrome Helper runs Chrome's background services, like networking, storage and audio, while variants named Renderer and GPU handle web pages and graphics.
What it does
Chrome splits its work across many processes so a crash in one doesn't take down the whole browser. The plain helper hosts utility services. All of them live inside the Google Chrome app in /Applications and quit when Chrome quits. Chrome's own task manager, under Window › Task Manager, names each one.
Why it gets busy
- Big downloads or many tabs loading at once, handled by Chrome's network service.
- Audio playing in a tab.
- Extensions doing background work.
Why is Google Chrome Helper using so much CPU?
Google Chrome Helper is Chrome's own work. Chrome's Task Manager (Window › Task Manager) shows which tab, extension or service is responsible.
Is it safe to quit?
Chrome starts the service again when it needs it. Quitting Chrome with Command-Q ends all its helpers cleanly.
Genuine Chrome helpers live inside /Applications/Google Chrome.app. A Chrome helper running from anywhere else is suspicious.
How to calm it down
- Open Window › Task Manager in Chrome to see exactly which service, tab or extension is busy.
- Turn on Memory Saver in Chrome's Settings › Performance.
- Disable extensions you don't use at chrome://extensions.
In SystemWatch
SystemWatch adds all of Chrome's helpers to one Google Chrome row, so you see the browser's real total, and the website edition can quit a single helper.
