What is secinitd, and why is it using CPU on my Mac?
Last reviewed: 19 November 2026. Path, accounts, launchd jobs and man page checked on macOS 26.3.1.
secinitd is the macOS security policy initialization daemon: it initializes the runtime security policies for processes as they start, which includes the App Sandbox that restricts what an app may touch. It uses CPU when many apps, extensions or helper processes launch. It is part of macOS and does not need any action.
secinitd at a glance
| secinitd | |
|---|---|
| Made by | Apple (part of macOS, App Sandbox) |
| Type | System daemon and per-user agent |
| Location | /usr/libexec/secinitd |
| Runs as | root, plus one copy for your user and for some system accounts |
| Started by | launchd job com.apple.secinitd |
| Can you quit it? | Not usefully. launchd restarts it, and sandboxed apps cannot start without it. |
What is secinitd?
The man page says secinitd "is a system daemon that initializes the runtime security policies for processes." The best-known of those policies is the App Sandbox, which Apple describes as restricting access to system resources and user data to contain damage if an app is compromised. Apps from the App Store, and most Apple apps and extensions, run in a sandbox that is set up when they start.
There are two launchd jobs named com.apple.secinitd: a daemon that runs as root and an agent that runs a copy in each user context. On this Mac, copies were running for the logged-in user and for system accounts such as _locationd.
Is secinitd safe?
Yes. It is part of macOS in /usr/libexec on the read-only system volume. Seeing several copies under different user names is normal.
Why does secinitd use so much CPU and memory?
- Many sandboxed processes starting. Each sandboxed app, app extension, widget and XPC helper needs its policy set up when it launches. Logging in, opening many apps, or a browser starting many helper processes adds up.
- Processes that crash and relaunch. An extension or helper that keeps crashing and being restarted by launchd makes secinitd set it up again each time.
- Small resident footprint. It stays in memory between launches. A few megabytes per copy is typical.
How much CPU is normal for secinitd?
Near 0% CPU with short blips when apps start. A burst at login is expected.
How do you stop secinitd from using so much CPU?
- Look for something relaunching. In Activity Monitor, sort the CPU tab by PID or watch for a process that appears, disappears and reappears. A helper in a crash loop keeps secinitd busy.
- Check for crash reports. Open Console, click Crash Reports, and look for one app or extension with many recent reports. Updating or removing it stops the relaunching.
- Remove extensions you do not use. Open System Settings > General > Login Items & Extensions and turn off extensions you do not need, so fewer sandboxed processes start.
When should you worry about secinitd?
secinitd at steady high CPU for minutes is unusual and almost always a sign that another process is starting over and over. Find that process; secinitd itself is not the fault.
A secinitd outside /usr/libexec would not be Apple's.
How do you check secinitd in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type secinitd in the search field. The CPU tab shows its % CPU. The Memory tab shows its Memory. Double-click the row for its parent process, memory details and open files.
In Terminal, the first command lists every secinitd process with its PID, user, CPU and memory (RSS is resident memory in kilobytes).
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'secinitd' | grep -v grep
How can Thrum help with secinitd?
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 secinitd 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 secinitd
Why is secinitd running under _locationd and other accounts?
The agent copy runs for each user context that starts processes, including some macOS system accounts that run their own services.
Can I turn the sandbox off to stop secinitd?
No. The App Sandbox is part of how apps are built and signed; there is no user setting to turn it off, and secinitd's work is small.
Sources
- secinitd(8) man page: run man secinitd in Terminal
- Apple Developer: App Sandbox