Thrum

What is plugin-container (FirefoxCP), and why is it using so much CPU?

Last reviewed: 19 November 2026. Path, bundle ID, process types and display names checked with Firefox 157 on macOS 26.3.1.

plugin-container is the program Firefox starts for its child processes: web content for tabs, extensions, the network socket process, media decoding and utilities. Activity Monitor shows them by role, such as FirefoxCP Isolated Web Content or FirefoxCP Web Content, while Terminal shows plugin-container. Firefox's Task Manager (about:processes) shows which tab or extension each one is running.

plugin-container at a glance

plugin-container
Made byMozilla (part of Firefox)
TypeHelper process (Firefox content and utility processes)
Location/Applications/Firefox.app/Contents/MacOS/plugin-container.app/Contents/MacOS/plugin-container
Runs asyour user
Bundle IDorg.mozilla.plugincontainer
Can you quit it?Yes. Tabs in that process show a crash page until you reload them; about:processes can unload them more gently.

What is plugin-container?

Despite the old name, plugin-container has nothing to do with browser plug-ins today. Mozilla's process model documentation lists a parent process that draws the interface, and sandboxed content processes of several types: shared web content, isolated web content for a single site, extensions, privileged pages such as the new tab page, service workers and preallocated spares. It also lists a data decoder (RDD) process for media and utility processes.

Firefox labels each process for macOS, so Activity Monitor shows names such as FirefoxCP Isolated Web Content, FirefoxCP Web Content, FirefoxCP WebExtensions, FirefoxCP Privileged Content, FirefoxCP Socket Process, FirefoxCP RDD Process and FirefoxCP Utility Process. On the Mac used for checking, Firefox 157 was running 24 of them.

Is plugin-container safe?

Yes. It lives inside Firefox.app and is signed with Mozilla's Developer ID (Mozilla Corporation, team 43AQ936H96). Content processes are sandboxed.

Why does plugin-container use so much CPU, memory and network?

How much CPU is normal for plugin-container?

Content processes for pages you are reading sit at or near 0% CPU, and Firefox's Task Manager shows idle ones as idle. Brief spikes while pages load are normal.

The count rises and falls with the number of sites and extensions; twenty or more processes with many tabs is expected.

How do you find which Firefox tab is behind a busy plugin-container?

  1. Open Firefox's Task Manager. Choose Tools > Browser Tools > Task Manager, or type about:processes in the address bar. Each process shows its PID, CPU, memory and the tabs or subframes it hosts.
  2. Unload or kill the busy one. In about:processes, the action next to a process can Unload tabs and kill process, or close a single tab. The tabs come back when you click them.
  3. Test without extensions. Choose Help > Troubleshoot Mode… to restart Firefox with extensions turned off. If CPU falls, remove extensions one by one in Tools > Extensions and Themes.
  4. Check hardware acceleration. In Firefox Settings > General > Performance, Use recommended performance settings controls Use hardware acceleration when available. Leave it on unless you are troubleshooting display problems.

When should you worry about plugin-container?

A content process that stays near 100% CPU with its tabs closed, or memory that keeps rising on a page you are not using, points to that site or an extension. Unload it from about:processes.

A plugin-container that is not inside Firefox.app, or not signed by Mozilla, is not Firefox's.

How do you check plugin-container in Activity Monitor and Terminal?

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

In Terminal, the first command lists every plugin-container process with its PID, user, CPU and memory (RSS is resident memory in kilobytes). nettop shows its live network traffic.

ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'plugin-container' | grep -v grep
nettop -p <PID>    # PID from the ps line above

How can Thrum help with plugin-container?

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 plugin-container 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 plugin-container 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 plugin-container

Why is it called plugin-container if Firefox has no plug-ins?

The name dates from when the process hosted plug-ins such as Flash. Firefox now uses the same program for all of its child processes and sets a descriptive FirefoxCP name for each one.

What does Isolated Web Content mean?

It is a content process that holds pages from a single site, so one site cannot read another site's data in memory.

Is Firefox GPU Helper a plugin-container process?

No. Firefox starts its GPU process from a separate helper app called Firefox GPU Helper.

Sources