What is Google Chrome Helper (Renderer), and why is it using so much CPU?
Last reviewed: 19 November 2026. Helper bundle names, bundle IDs and code signature checked in Google Chrome 157 on macOS 26.3.1.
Google Chrome Helper (Renderer) is a Chrome process that runs web pages: it lays out each page and runs its JavaScript, usually one process per site, with extensions in their own. High CPU means a page or extension is doing a lot of work, and many of them using memory means many sites are open. Chrome's Task Manager (More > More tools > Task Manager) shows which tab each one belongs to.
Google Chrome Helper (Renderer) at a glance
| Google Chrome Helper (Renderer) | |
|---|---|
| Made by | Google (part of Google Chrome) |
| Type | Helper process (Chromium renderer) |
| Location | /Applications/Google Chrome.app/Contents/Frameworks/Google Chrome Framework.framework/Versions/[version]/Helpers/Google Chrome Helper (Renderer).app/Contents/MacOS/Google Chrome Helper (Renderer) |
| Runs as | your user |
| Bundle ID | com.google.Chrome.helper.renderer |
| Can you quit it? | Yes. The tabs it served show an error page until reloaded; Chrome's own Task Manager can end it more precisely. |
What is Google Chrome Helper (Renderer)?
Chrome is split into a browser process (the window, address bar and bookmarks), a GPU process, utility processes and renderer processes. Google describes the renderer as controlling anything inside the tab where a website is displayed. On desktop, Chromium locks each renderer to a single site (Site Isolation), and since Chrome 67 cross-site iframes inside a page also get their own renderer, so one tab can use several.
On a Mac each kind of process is started from a separate helper app inside Chrome's framework. Renderers use Google Chrome Helper (Renderer).app, bundle ID com.google.Chrome.helper.renderer, which is why Activity Monitor lists many processes with this name. Chromium sets a soft limit on renderer processes based on the Mac's memory and reuses same-site processes above it.
Is Google Chrome Helper (Renderer) safe?
Yes, when it runs from inside Google Chrome.app. The helper is signed with Google's Developer ID (Google LLC, team EQHXZ8M8AV), which codesign -dv --verbose=2 on the Chrome app shows. Renderers run in a sandbox and reach the network only through Chrome's network service.
Why does Google Chrome Helper (Renderer) use so much CPU, memory and energy?
- A heavy web page. Web apps, ad scripts, endless feeds and pages that poll a server keep their renderer busy. One bad page can hold a renderer at 100% of a core.
- Extensions. Extensions run in renderer processes too, and content scripts run inside every page they touch. Google's Speed up Chrome article suggests turning off extensions you do not need.
- Many sites open. Because each site gets its own renderer, twenty tabs on twenty sites means about twenty renderers, each with its own memory.
- Background tabs with video or animation. Tabs you are not looking at can still play media or run timers. Chrome's Energy Saver reduces background activity when the Mac runs on battery.
- A spare renderer. Chromium often starts a spare renderer in advance so the next tab opens faster, so one idle renderer may appear with nothing visibly attached.
How much CPU is normal for Google Chrome Helper (Renderer)?
A renderer for a static page you are reading is at or near 0% CPU. While a page loads, scrolls or plays video, short bursts are normal.
Many renderer processes are normal. Each has its own memory, and the total depends on the sites you keep open.
How do you stop Google Chrome Helper (Renderer) from using so much CPU?
- Open Chrome's Task Manager. In Chrome, click More (the three dots), then More tools > Task Manager. Sort by CPU or Memory to see which tab, extension or subframe each process belongs to.
- End the process or close the tab. Select the busy item in Chrome's Task Manager and click End process. Google notes that unsaved work in that task is lost.
- Turn off extensions you do not use. Go to More > Extensions > Manage Extensions and switch off or remove extensions; check whether the busy renderer was an extension.
- Turn on Memory Saver and Energy Saver. Go to More > Settings > Performance. Memory Saver deactivates tabs you are not using, and Energy Saver limits background activity when the Mac runs on battery.
When should you worry about Google Chrome Helper (Renderer)?
If one renderer stays above 100% CPU after you close the tab Chrome's Task Manager points to, or the count keeps growing with few tabs open, check the Extensions page for something you do not recognize and remove it.
A process with this name that does not run from inside Google Chrome.app, or is not signed by Google, is not Chrome's.
How do you check Google Chrome Helper (Renderer) in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), and type Google Chrome Helper (Renderer) in the search field. The CPU tab shows its % CPU. The Memory tab shows its Memory. The Energy tab shows its Energy Impact. Double-click the row for its parent process, memory details and open files.
In Terminal, the first command lists every Google Chrome Helper (Renderer) 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 (Renderer)' | grep -v grep
pmset -g assertions # shows processes keeping the Mac awake
How can Thrum help with Google Chrome Helper (Renderer)?
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 (Renderer) 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 (Renderer) 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 (Renderer)
Why are there so many Google Chrome Helper (Renderer) processes?
Chrome runs each site and each extension in its own renderer process, and cross-site iframes get their own too. The count follows the number of sites and extensions, up to a limit based on the Mac's memory.
Can I disable Google Chrome Helper (Renderer)?
No. Chrome cannot show web pages without renderer processes. You can reduce how many are active with Memory Saver, fewer tabs and fewer extensions.
Why does Chrome's version folder appear in the path?
Chrome keeps its helpers inside a versioned folder of its framework, so the path changes with each update. On this Mac it was 157.0.8103.79.