What is containermanagerd, and why is it using CPU?
Last reviewed: 19 November 2026. Path, accounts, launchd job and man page checked on macOS 26.3.1.
containermanagerd is the macOS daemon that creates, removes and manages the containers of sandboxed apps and their plug-ins, the private folders in ~/Library/Containers where those apps keep their data. It is busy when apps are installed, opened for the first time or updated, and when containers are checked or migrated after a macOS update. It is safe and normally near idle.
containermanagerd at a glance
| containermanagerd | |
|---|---|
| Made by | Apple (part of macOS, App Sandbox) |
| Type | Per-user agent |
| Location | /usr/libexec/containermanagerd |
| Runs as | your user |
| Started by | launchd job com.apple.containermanagerd |
| Can you quit it? | You can, but launchd starts it again as soon as a sandboxed app needs its container. |
What is containermanagerd?
The containermanagerd(8) man page says it creates, destroys and otherwise manages containers for applications and their plug-ins, and works with the sandbox and secinitd to provide application containerization. A sandboxed app, which includes every Mac App Store app and many Apple apps, can only write inside its own container, so each one gets a folder of its own.
The man page lists the folders it looks after: ~/Library/Containers, ~/Library/ContainerManager and ~/Library/Caches/com.apple.containermanagerd. On this Mac it runs as the logged-in user from the com.apple.containermanagerd launch agent, with extra copies for a few system accounts that run sandboxed services.
Is containermanagerd safe?
Yes. containermanagerd is part of macOS at /usr/libexec/containermanagerd, started by launchd. The man page says users should not run it manually.
Why does containermanagerd use so much CPU and disk?
- Opening a sandboxed app for the first time. The first launch of a sandboxed app or one of its extensions creates its container and the folder structure inside it.
- Updates and migrations. After a macOS update or Migration Assistant, containers for many apps can be checked or updated, which reads and writes in ~/Library/Containers.
- Many apps and extensions. Each app extension, such as a share extension or widget, can have its own container, so a Mac with many apps has many containers to manage.
- Deleting apps. Removing a sandboxed app can lead to its container being cleaned up.
How much CPU is normal for containermanagerd?
Typical: near 0% CPU, with short bursts when apps are installed, opened for the first time or updated. A longer burst after a macOS update or migration is expected.
Sustained CPU for hours while nothing is being installed is unusual.
How do you stop containermanagerd from using so much CPU?
- Let it finish after an update. After a macOS update or migration, give it time while the Mac is awake and on power.
- Check which app is involved. In Console, stream messages and filter for
containermanagerd. Repeated messages naming one app's bundle identifier show which container it keeps working on. - Update or reinstall that app. If one app keeps triggering container work, update it or reinstall it from its source. Do not delete its folder in ~/Library/Containers while the app is installed: that folder holds the app's data.
- Restart the Mac. A restart resets containermanagerd's state. If it is busy again with the same app, that app is the cause.
When should you worry about containermanagerd?
Worry if containermanagerd stays busy for a long time with repeated log messages about one app. That app's container may be damaged, and contacting its developer or reinstalling helps.
A containermanagerd outside /usr/libexec would not be Apple's.
How do you check containermanagerd in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), and type containermanagerd in the search field. The CPU tab shows its % CPU. The Disk tab shows its Bytes Written and Bytes Read. Double-click the row for its parent process, memory details and open files.
In Terminal, the first command lists every containermanagerd 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.
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'containermanagerd' | grep -v grep
sudo fs_usage -w -f filesys <PID> # PID from the ps line above
How can Thrum help with containermanagerd?
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 containermanagerd 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 containermanagerd 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 containermanagerd
What is in ~/Library/Containers?
One folder per sandboxed app or extension, holding its preferences, caches and documents. Deleting a folder deletes that app's data.
Why are there several containermanagerd processes?
One runs for your user and others run for system accounts whose services are also sandboxed.
Sources
- containermanagerd(8) man page: run man containermanagerd in Terminal