lsd high CPU on Mac? Launch Services, explained
lsd using high CPU on your Mac is the Launch Services database daemon: the registry of which app opens which file. Here's why it spikes, how to rebuild the database, and why it's not launchservicesd.
lsd is the Launch Services database daemon that keeps track of which app opens which file. When it spikes to high CPU, the cause is almost always a damaged or bloated Launch Services database, and the fix is to rebuild it. First, a naming point that trips up a lot of guides.
lsd is not "launchservicesd"
On modern macOS (Ventura, Sonoma, Sequoia and later), the process you'll see using CPU is lsd, at /usr/libexec/lsd. There's a separate, older daemon called launchservicesd at /System/Library/CoreServices/launchservicesd, a different process. Older articles that call the CPU-spiking Launch Services process "launchservicesd" are out of date. If you're on a recent macOS, you're looking at lsd.
What lsd does
Its man page says it "provides various services for CoreServices frameworks," and warns it "is not meant to be invoked directly and it must not be terminated." It maintains the Launch Services database: the registry of installed apps, their document-type and URL-scheme associations, and which app opens which file, including your "Open With" choices.
Why it's using high CPU
A damaged or bloated Launch Services database forces lsd to repeatedly re-read and re-verify registrations. Common triggers:
- Many apps installed, moved, or duplicated, including leftover app copies on mounted volumes or disk images.
- A bad registration, or an app that re-registers itself in a loop.
- Because modern macOS discovers apps via Spotlight, a Spotlight re-index can drive it too. (Documented Sonoma cases hit 100% CPU; one even wrote hundreds of gigabytes to disk.)
Is lsd a virus?
No. It's a legitimate Apple CoreServices daemon, and it must not be killed permanently. The high CPU is a symptom of a corrupt database or a misbehaving third-party app, not of lsd itself.
What to do about it
- Rebuild the Launch Services database with
lsregister, then reboot:/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/Support/lsregister -kill -r -domain local -domain system -domain user - If Spotlight is involved, rebuild its index too:
sudo mdutil -E /(see mdworker high CPU for the details). - Boot into Safe Mode, then restart normally. This clears many cases.
- Remove duplicate app copies, especially leftovers on external volumes or disk images.
Honest caveat: right after a rebuild your Mac is slower for a bit while the database repopulates; partly, you wait it out.
See it settle after a rebuild
After rebuilding Launch Services you want to confirm lsd actually calms down rather than looping again. Plumby shows live CPU in your menu bar with the process named plainly, so you can watch it return to idle, or catch the app that keeps re-triggering it. Measured from your Mac's real state, never estimated.
