What is launchd, and why is it using CPU on my Mac?
Last reviewed: 19 November 2026. Path, account and process ID checked on macOS 26.3.1.
launchd is the first process macOS starts at boot, with process ID 1, and it starts, stops and supervises every background daemon and agent on the Mac. It normally uses very little CPU; when it does show activity, it is usually starting a job over and over because that job keeps crashing or exiting. You cannot quit it, so the fix is to find and deal with the job it keeps launching.
launchd at a glance
| launchd | |
|---|---|
| Made by | Apple (part of macOS) |
| Type | System process (PID 1) |
| Location | /sbin/launchd |
| Runs as | root |
| Can you quit it? | No. It is the first process the kernel starts, and every other process depends on it. |
What is launchd?
launchd is the system and per-user daemon and agent manager in macOS. Its man page says that during boot it is invoked by the kernel to run as the first process on the system and to bootstrap the rest of the system, so it always has process ID 1 and runs as root. Activity Monitor shows it as the parent of almost every other process.
Each background job is described by a property list in /System/Library/LaunchDaemons and /System/Library/LaunchAgents (Apple's jobs), /Library/LaunchDaemons and /Library/LaunchAgents (jobs installed by an administrator or an app), or ~/Library/LaunchAgents (your own). A daemon is one system-wide instance; an agent runs once per logged-in user. launchd also manages the XPC services bundled inside apps and frameworks, and prefers to start jobs on demand, when something asks for them, rather than keep them all running.
The launchctl command is the interface to launchd. It can list jobs, print a job's state and tell you why a job was started.
Is launchd safe?
Yes. launchd is the core of macOS and lives at /sbin/launchd on the read-only system volume. There is only one real launchd, with PID 1; a second process called launchd with a different PID and path would not be Apple's. The iOS Simulator in Xcode runs its own launchd_sim, which is a different, expected process.
Why does launchd use so much CPU and memory?
- A job that crashes and restarts. If a job is set to stay running and keeps crashing or exiting, launchd starts it again. By default launchd.plist(5) says a job is not spawned more than once every 10 seconds, but a loop like this still shows up as steady launchd activity and log messages.
- Login and wake. At startup, login and wake from sleep, many jobs start at once or react to events, and launchd does a burst of work spawning them.
- Many short-lived jobs. Some third-party tools install agents that run every few seconds or watch a folder that changes often. Each run is a new process that launchd has to start and clean up.
- Many loaded jobs. launchd keeps a record of every loaded job and XPC service for the system and for each user, so its memory grows a little with the number of jobs installed. It is usually small compared with apps.
How much CPU is normal for launchd?
launchd should sit at or near 0% CPU most of the time, with short spikes at login, after waking and when apps start. Its CPU time in Activity Monitor grows slowly over days of uptime because it has been running since boot.
Repeated spikes every few seconds while the Mac is idle are not normal for launchd itself and almost always mean one job is being relaunched in a loop.
How do you find the job that keeps launchd busy?
- Look for a process that keeps restarting. In Activity Monitor, sort by PID and watch for a process whose PID keeps changing to a new, higher number. That is a job launchd is starting again and again.
- Check the log for respawn messages. Open Console, select the Mac under Devices, start streaming, and search for
launchd. Messages about a service exiting or being throttled name the job's label. - Ask launchd why a job runs. In Terminal,
launchctl blame gui/$(id -u)/<label>prints why launchd started one of your user's jobs, for example an XPC event or a Mach IPC request. Usesystem/<label>for a system daemon. - Remove or update the app that owns the job. If the label belongs to a third-party app, update or uninstall that app. System Settings > General > Login Items & Extensions lists apps with background items and lets you turn their background activity off.
- Restart the Mac. A restart reloads every job. If launchd is still busy afterwards, the job causing it is installed and starting again, and the steps above will find it.
When should you worry about launchd?
Worry if launchd stays above a few percent CPU for a long time while the Mac is idle, or if the log shows the same job exiting every few seconds. The cause is the job, not launchd, so look for the label in Console.
Unknown property lists in /Library/LaunchAgents, /Library/LaunchDaemons or ~/Library/LaunchAgents are worth checking: that is where apps, and occasionally adware, install their background jobs.
How do you check launchd in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type launchd 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 launchd process with its PID, user, CPU and memory (RSS is resident memory in kilobytes).
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'launchd' | grep -v grep
How can Thrum help with launchd?
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 launchd 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. Thrum lists launchd but has no Quit button for it, because macOS needs it to run.
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 launchd
Can I quit launchd?
No. It is process 1, the parent of every other process. Quitting it would stop the whole system, and macOS does not allow it.
Why are there so many processes started by launchd?
Almost every background process in macOS is a launchd job or an XPC service, so Activity Monitor shows launchd as their parent. Most of them start on demand and exit when idle.
How do I see which jobs launchd has loaded?
launchctl list lists your user's jobs with their PID and last exit status, and launchctl print gui/$(id -u) prints the whole user domain.
Sources
- launchd(8) man page: run man launchd in Terminal
- launchd.plist(5) man page (KeepAlive, ThrottleInterval): run man launchd.plist in Terminal
- launchctl(1) man page (print, blame): run man launchctl in Terminal
- Apple Developer: Daemons and Services Programming Guide
- Apple Support: Change Login Items & Extensions settings on Mac