macOS processes › Core system
What is launchd on Mac?
launchd is the first process macOS starts and the parent of almost everything else. It starts system services and your background items, restarts them if they stop, and launches others only when they're needed.
What it does
It runs as process ID 1 from /sbin/launchd. It reads job definitions, small property list files in the LaunchDaemons and LaunchAgents folders in /System/Library and /Library, and in the LaunchAgents folder in your user Library, and starts each job at startup, at login, on a schedule, or when another process asks for it. Starting services on demand is why many Apple processes appear and disappear in Activity Monitor.
Why it gets busy
- A background job that crashes and is restarted over and over, which keeps launchd working.
- Many processes starting at once, such as right after login or after installing software.
- Apps or scripts that start lots of short-lived helper processes.
Why is launchd using so much CPU?
launchd rarely stays busy. When it does, a background job is usually crashing and being restarted in a loop. Find it in Console's Crash Reports or in Login Items & Extensions.
Is it safe to quit?
macOS can't run without launchd. If it stopped, your Mac would have to restart.
The real launchd is process ID 1 and runs from /sbin/launchd. Malware doesn't replace it, but it often adds its own jobs to LaunchAgents folders, so check those if something unwanted keeps coming back.
How to calm it down
- Open System Settings › General › Login Items & Extensions and turn off background items you don't recognize or need.
- Open Console, select Crash Reports, and look for a name that repeats every few seconds. Update or remove that app.
- Restart after installing or removing software that adds background services.
In SystemWatch
SystemWatch's Startup Items view lists what launches at login and in the background, which helps you find the job behind a launchd spike.
