What is launchservicesd, and why is it using CPU?
Last reviewed: 19 November 2026. Path, account, launchd job and man page checked on macOS 26.3.1.
launchservicesd is the macOS daemon that tracks and coordinates information about the applications running on the system. Its work follows app activity: launching, quitting and switching apps, and apps that start and exit repeatedly. It is normally near idle and is not something to quit.
launchservicesd at a glance
| launchservicesd | |
|---|---|
| Made by | Apple (part of macOS, Launch Services) |
| Type | System daemon |
| Location | /System/Library/CoreServices/launchservicesd |
| Runs as | root |
| Started by | launchd job com.apple.coreservices.launchservicesd |
| Can you quit it? | Not usefully. launchd starts it at boot and the system relies on it to know which apps are running. |
What is launchservicesd?
The launchservicesd(8) man page says it is used internally by macOS to track and coordinate information about the running applications on the system. Its launchd job, com.apple.coreservices.launchservicesd, runs as root and starts at boot (RunAtLoad).
It is a separate process from lsd, which serves the database of installed apps and handles open requests. launchservicesd is about the apps that are running right now: which ones exist, and their state.
Is launchservicesd safe?
Yes. launchservicesd is part of macOS at /System/Library/CoreServices/launchservicesd on the read-only system volume and is started by launchd at boot.
Why does launchservicesd use so much CPU?
- Apps launching and quitting. Each app launch and exit updates the information it keeps about running applications.
- An app that keeps relaunching. A helper app or menu bar app that crashes and is relaunched in a loop produces a constant stream of updates.
- Switching between apps. Changing the frontmost app is one of the pieces of running-app information other parts of macOS, such as the Dock, rely on.
How much CPU is normal for launchservicesd?
Typical: near 0% CPU, with small spikes as apps open and close.
Continuous CPU use while you are not opening or switching apps is not typical.
How do you find what keeps launchservicesd busy?
- Look for an app that keeps restarting. In Activity Monitor, sort by PID and look for an app or helper that keeps reappearing with a new PID.
- Check crash reports. Open Console and click Crash Reports. Repeated reports for the same app show which one is relaunching.
- Quit or update that app. Quit the app or remove it from Login Items & Extensions, then check whether launchservicesd settles. Update the app if it keeps crashing.
When should you worry about launchservicesd?
Worry only if it stays busy while you are not using apps, which points to an app relaunching in a loop.
A launchservicesd outside /System/Library/CoreServices would not be Apple's.
How do you check launchservicesd in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type launchservicesd 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 launchservicesd process with its PID, user, CPU and memory (RSS is resident memory in kilobytes).
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'launchservicesd' | grep -v grep
How can Thrum help with launchservicesd?
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 launchservicesd 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 launchservicesd
Can I quit launchservicesd?
It is a root process and launchd restarts it. Quitting it would disrupt app launching and the Dock, so leave it running.
Does launchservicesd decide which app opens a file?
That is the job of the Launch Services database served by lsd. launchservicesd tracks applications that are running.
Sources
- launchservicesd(8) man page: run man launchservicesd in Terminal