What is Google Chrome Helper on Mac? High CPU fixes

What Google Chrome Helper does

Chrome doesn't put every tab and service into a single process. Chromium's architecture documentation separates the main browser process from renderer processes that handle web content and from other services. Process isolation helps contain faults and restrict access between components.

On a Mac, some of that work appears in Activity Monitor as Google Chrome Helper or Google Chrome Helper (Renderer). A renderer is doing web-page work. The label alone doesn't name the page, explain its CPU use or establish whether a particular workload is useful.

Several processes are therefore not, by themselves, evidence of a leak or malware. Nor is there a fixed healthy count to compare with every Mac. The number of tabs, site isolation, extensions and services makes a process-count rule a poor diagnosis.

Where it runs on this Mac

A read-only process check on our MacBook Pro with M2 Max, macOS 27.0.1, on 23 October 2026 showed Chrome 154.0.8037.98 helpers running in the logged-in user's account. The renderer executable was inside the installed Chrome application:

/Applications/Google Chrome.app/Contents/Frameworks/Google Chrome Framework.framework/Versions/154.0.8037.98/Helpers/Google Chrome Helper (Renderer).app/Contents/MacOS/Google Chrome Helper (Renderer)

This is a path from that installed version, not a path you should delete or a permanent version number. Chrome updates change the versioned folder. If a similarly named process is running somewhere unexpected, inspect the executable and the installed app rather than deciding solely from the displayed name.

The check establishes ownership and location; it wasn't a performance benchmark or a controlled test of Chrome's battery use.

Find the busy tab with Chrome Task Manager

Activity Monitor is useful for seeing that Chrome is busy, but Chrome's own Task Manager can attach browser task names to that work. This is the practical bridge between “Helper” and the tab or extension you can change.

1. Open Chrome's three-dot menu › More tools › Task Manager. This is the route in Google's current help instructions.
2. Look at the active task names. Note a tab, extension or background page that remains busy while the slowdown occurs. Sort Memory when investigating memory use, or inspect CPU when the problem is sustained computation.
3. Save work in the identified page. A form, editor or upload can contain work that hasn't reached the server.
4. Close an unnecessary tab normally. On a Mac, Command-W closes the current tab. If the task is stuck and you choose End Process in Task Manager, its unsaved work will be lost.
5. Repeat the original action. Check whether the problem returns on one site, with one extension, or only with many tasks open.

A quiet tab may become busy when you return to it, and a page can include content from more than one source. You don't need a perfect one-tab-to-one-process map to identify a repeatable offending task.

Reduce the work before changing browser settings

Begin with the task you found. Pause video or close a web app you no longer need. If the page is a document, save it and test reopening it. If the issue always follows one website, test that same site with optional extensions disabled rather than clearing all browser data immediately.

Google's extension route is Chrome three-dot menu › Extensions › Manage Extensions. Switch an optional extension off for a test; you can switch it back on. Don't disable an employer-required security extension without IT guidance, and don't remove everything at once if you want to know which change mattered.

Use a small test: one troublesome site, then the same site with a suspected extension disabled. If the result changes, record the extension version and contact its developer. That is stronger evidence than assuming every high Helper reading is Chrome itself malfunctioning.

Memory Saver and performance settings

Open Chrome three-dot menu › Settings › Performance. Google's Memory Saver guidance explains that inactive tabs can be deactivated and reload when you return. This can reduce the memory held by tabs you aren't using.

It is not a promise to stop an active tab's CPU work. Google lists activities that can prevent deactivation, including calls, screen sharing, downloads and partially filled forms. Choose exceptions for sites that need to stay active rather than assuming every idle-looking tab will be suspended.

In the same area, review Preload pages if you want to change speculative background loading. Treat it as a tradeoff between potential browsing speed and work done before a page is opened, not as a guaranteed fix for a renderer looping on an already open page.

For system memory, open Activity Monitor › Memory on macOS 15 Sequoia, macOS 26 Tahoe or macOS 27 Golden Gate. Read pressure during the problem. The RAM guide explains why a large memory total alone doesn't show a fault.

Update and investigate a persistent problem

Google's first general performance step is updating Chrome. Use Chrome menu › About Google Chrome or the update route documented in its help, then relaunch when offered after saving work. Update the extension too if your test points to one.

Clear a specific site's data only when the symptom suggests damaged or stale site state, and understand that it can sign you out or remove local site data. Our cache guide covers the browser-specific consequences. Cache deletion isn't an explanation for every busy helper.

If other apps also become slow, follow the wider slow-Mac diagnosis. Check memory pressure and free space before treating one Chrome process as the whole problem. For repeated app hangs, keep the task name, Chrome version and steps to reproduce it for Google or the relevant site developer.

Don't delete or permanently block the helpers

Chrome needs its bundled components to function. Deleting the nested Helper application or trying to prevent every renderer from launching breaks the browser's design rather than reducing the web workload. An updated Chrome installation will also replace its own components.

If you choose to stop using Chrome, remove the browser through its documented uninstall procedure after protecting bookmarks and other needed data. That is a separate decision from closing an expensive tab. See Activity Monitor's process guide for other names you may encounter.

How Tend helps

Tend folds helper executables inside Chrome's app bundle into one Google Chrome entry. The free list shows combined CPU, memory and estimated per-app watts; it doesn't identify which browser tab owns a helper. Use Chrome Task Manager for that. Energy totals cover 24 hours free, with 7- and 30-day views in Pro.

Questions

Related guides

Sources

Sources checked 23 October 2026. These are documented steps and specifications; no repair, installation or performance test was run for this guide.

• Chromium, Chromium multiprocess architecture
• Google, Speed up Chrome
• Google, Personalize Chrome performance
• Google, Update Google Chrome

Spotted something out of date? Tell us and we'll fix it.