What is sandboxd, and why is it using CPU on my Mac?
Last reviewed: 19 November 2026. Path, account, launchd job and man page checked on macOS 26.3.1.
sandboxd is the macOS daemon that performs services for the Sandbox kernel extension, including recording sandbox violations: attempts by a sandboxed process to do something its sandbox does not allow. It uses CPU when a process keeps hitting its sandbox's limits, because each violation can be logged with a backtrace. It is part of macOS; the fix is usually in the app that causes the violations.
sandboxd at a glance
| sandboxd | |
|---|---|
| Made by | Apple (part of macOS, Sandbox) |
| Type | System daemon |
| Location | /usr/libexec/sandboxd |
| Runs as | root |
| Started by | launchd job com.apple.sandboxd |
| Can you quit it? | Not usefully. launchd restarts it when the sandbox needs it. |
What is sandboxd?
The man page says sandboxd "performs services on behalf of the Sandbox kernel extension." Its options show one of those services: -b logs "basic sandbox violation information without a backtrace" and -s skips symbolicating backtraces, so by default it records violations with symbolicated backtraces, which takes CPU.
A sandbox violation happens when an app or helper that runs in the App Sandbox tries to read a file, open a connection or use a service its rules do not allow. The attempt is blocked; sandboxd's job is the follow-up work. It runs as root from the com.apple.sandboxd launchd job.
Is sandboxd safe?
Yes. sandboxd is part of macOS in /usr/libexec on the read-only system volume. Its activity means the sandbox is blocking something, which is the protection working, not a problem with sandboxd.
Why does sandboxd use so much CPU?
- An app repeatedly breaking its sandbox rules. A sandboxed app or extension that keeps trying something it is not allowed to do generates a stream of violations, and each one is processed.
- Symbolicating backtraces. Turning raw addresses in a backtrace into function names is the expensive part, which is why its man page offers an option to skip it.
- Older apps after a macOS update. An app built for an older macOS may run into rules that changed, until its developer releases an update.
How much CPU is normal for sandboxd?
0% CPU nearly all the time. Occasional short activity is normal, since some violations happen during ordinary use.
How do you stop sandboxd from using so much CPU?
- Find the violating process. Run
log show --last 10m --predicate 'eventMessage CONTAINS "deny"' | grep -i sandbox | tail -50in Terminal. Each line names the process and the operation that was denied. - Update that app. Install the latest version of the app named in the log. Developers fix sandbox problems in updates.
- Give the access it needs, if appropriate. If the denial is for a folder or device, check System Settings > Privacy & Security. An app that has been allowed through the proper setting stops being denied.
- Quit or remove the app. If an app you do not need keeps causing violations, quit it or remove it and its login items.
When should you worry about sandboxd?
Sustained CPU from sandboxd means something is hitting the sandbox continuously. That is usually a bug in an app, but if the process named in the log is something you did not install, investigate it.
A sandboxd running from outside /usr/libexec would not be Apple's.
How do you check sandboxd in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type sandboxd in the search field. The CPU tab shows its % CPU. Double-click the row for its parent process, memory details and open files.
In Terminal, the first command lists every sandboxd process with its PID, user, CPU and memory (RSS is resident memory in kilobytes).
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'sandboxd' | grep -v grep
How can Thrum help with sandboxd?
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 sandboxd 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. macOS does not let apps quit processes owned by root or other users, so Thrum shows them for information and leaves stopping them to the steps above.
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 sandboxd
Is a sandbox violation a sign of malware?
Not by itself. Ordinary apps cause violations when they try something their sandbox does not permit. The violation is blocked either way.
Can I disable sandboxd?
No. It is part of the sandbox system that protects the Mac, and there is no user setting for it.
Sources
- sandboxd(8) man page: run man sandboxd in Terminal
- Apple Developer: App Sandbox