macOS process library
What is launchd on Mac?
launchd is the first process the kernel starts when your Mac boots, and it starts and manages almost every other background process. It reads job definitions from LaunchDaemons and LaunchAgents folders and launches services when they’re needed.
- Part of
- macOS’s service manager, started by the kernel at boot.
- Safe?
- Yes. It runs on every Mac. The third-party jobs it launches are what to check.
- Can I quit it?
- No. It is process ID 1, and macOS can’t keep running without it.
The short answer
launchd itself does very little work. When it shows CPU, it’s usually starting or restarting other jobs, and a background job that crashes and gets relaunched over and over can keep it busy. Look at what it’s launching, not at launchd.
Normal use
What launchd usually looks like.
launchd always shows process ID 1 in Activity Monitor and usually uses near zero CPU and a small amount of memory.
Short bursts at login and after waking from sleep are normal, since that’s when many background services start at once.
Why launchd uses so much CPU or memory
- Login and wake
Many system services and app helpers start right after you log in or wake your Mac, and launchd starts each one.
- A background job that keeps crashing
If a job is set to stay running and it keeps failing, launchd keeps relaunching it. Each restart costs a little CPU, and it adds up.
- Leftovers from apps you removed
Some apps install launch agents or daemons that stay behind after the app is gone and keep trying to start something that no longer works.
How to calm launchd down
Start at the top. Each step is more disruptive than the one before.
- Give it a minute after login
Activity right after login or wake usually fades on its own.
- Review background items
Open System Settings → General → Login Items & Extensions. Under Allow in the Background, turn off apps you don’t need running when they’re closed.
- Update or reinstall the app behind a busy helper
If one app’s helper keeps showing up and disappearing in Activity Monitor, update that app or reinstall it from the developer.
- Uninstall apps you no longer use
Use the app’s own uninstaller if it has one, so its launch agents and daemons are removed too. Third-party items live in
/Library/LaunchAgents,/Library/LaunchDaemons, and~/Library/LaunchAgents. - Restart
A restart reloads every job from scratch.
Seeing it in Spare
Find what it’s reacting to.
When launchd is busy, the cause is usually one of the jobs it starts. Spare groups helper processes under the apps they belong to, so an app’s background helpers show up as part of that app instead of as unfamiliar names in a long list.
Spare treats launchd as a system task and never offers to stop it.
Common questions
About launchd
Is launchd a virus?
No. launchd is part of macOS and is always process ID 1. Malware sometimes installs its own launch agents, which is why it’s worth reviewing background items you don’t recognize.
Why is launchd using CPU?
It’s usually starting other processes. A job that crashes and relaunches repeatedly is the most common reason for sustained use.
Can I disable or quit launchd?
No. Every service on your Mac depends on it. Turn off the specific background items you don’t want instead.
What’s the difference between a LaunchAgent and a LaunchDaemon?
Daemons run for the whole system, even before anyone logs in. Agents run for a single user while that user is logged in.
Related processes
Sources: Apple: Creating launch daemons and agents, Apple: Open items automatically when you log in. Reviewed October 6, 2026.
Get Spare
Free to use. Yours to explore.
Download Spare for Apple silicon, or explore the MIT-licensed source on GitHub. Free to use, with no subscription or account.
macOS 14+ · Apple silicon · Signed and notarized