What is lsd on my Mac, and why is it using CPU?
Last reviewed: 19 November 2026. Path, accounts, launchd jobs and man page checked on macOS 26.3.1.
lsd is a macOS daemon that provides services for the CoreServices frameworks, in particular Launch Services, the part of macOS that knows which apps are installed and which app opens each kind of file or link. It gets busy when apps are installed, updated or moved, after a macOS update, and when the Launch Services database is rebuilt. It is unrelated to the drug of the same name and must not be terminated.
lsd at a glance
| lsd | |
|---|---|
| Made by | Apple (part of macOS, Launch Services) |
| Type | System daemon and per-user agent |
| Location | /usr/libexec/lsd |
| Runs as | root, plus one copy as your user |
| Started by | launchd job com.apple.lsd (one daemon job and one agent job with the same label) |
| Can you quit it? | No. Its man page says it must not be terminated. |
What is lsd?
The lsd(8) man page only says that lsd provides various services for CoreServices frameworks, is not meant to be invoked directly and must not be terminated. Its launchd jobs show what those services are: they include com.apple.lsd.mapdb and com.apple.lsd.modifydb (reading and changing the Launch Services database), com.apple.lsd.open and com.apple.lsd.openurl (opening apps, documents and links), and com.apple.security.translocation.
Launch Services, as Apple's Launch Services guide describes it, lets apps open other apps, documents and URLs the way the Finder does, identifies the preferred app for a document or URL, and records which kinds of files and URLs each app can open. The lsregister tool inside the LaunchServices framework describes the store behind this as the Launch Services database. One copy of lsd runs as root and one as your user.
Is lsd safe?
Yes. lsd is part of macOS at /usr/libexec/lsd, started by launchd. The name stands for nothing alarming; it is a system daemon like the other d-suffixed processes.
Why does lsd use so much CPU?
- Installing, updating or moving apps. Each new or changed app has to be registered: its document types, URL schemes and other details are added to the database.
- After a macOS update. A system update changes many built-in apps, which are registered again.
- Disks full of apps. Connecting a drive or disk image that contains apps, or restoring from a backup, can lead to those apps being registered.
- Opening files and links. Every time you open a document or click a link, Launch Services looks up which app should handle it. This is quick, but many opens in a row add up.
How much CPU is normal for lsd?
Typical: near 0% CPU, with spikes when apps install or update. After a macOS update or a large app install, a few minutes of activity is expected.
lsd at high CPU for a long time with nothing being installed is unusual.
How do you stop lsd from using so much CPU?
- Let installs and updates finish. If you just updated macOS or installed apps, give lsd a few minutes. It settles once the new apps are registered.
- Look for an app that keeps changing. An app that rewrites its own bundle, or a folder of apps that a sync service keeps updating, makes lsd register it again and again. Pause the sync or move such copies out of synced folders.
- Remove duplicate copies of apps. Several copies of the same app in different folders or on disk images each get registered and can confuse which one opens files. Keep one copy in Applications.
- Rebuild the database only if links and files open in the wrong app. The
lsregistertool can rebuild the Launch Services database, but its own help says that after-deleteyou must restart. Use it only if file associations are broken, because every app is registered again afterwards.
When should you worry about lsd?
Worry if lsd stays busy for hours while nothing is being installed, or if files keep opening in the wrong app. Both point to a problem with registered apps rather than with lsd.
An lsd outside /usr/libexec would not be Apple's.
How do you check lsd in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type lsd 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 lsd process with its PID, user, CPU and memory (RSS is resident memory in kilobytes).
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'lsd' | grep -v grep
How can Thrum help with lsd?
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 lsd 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 lsd
Why are there two lsd processes?
One runs as root for the system and one runs as your user, each started by its own launchd job with the same label.
Is lsd the same as launchservicesd?
They are separate processes. lsd serves the Launch Services database and open requests; launchservicesd tracks and coordinates information about running applications.
Sources
- lsd(8) man page: run man lsd in Terminal
- lsregister help text: run /System/Library/Frameworks/CoreServices.framework/Frameworks/LaunchServices.framework/Support/lsregister -h
- Apple Developer: Launch Services Programming Guide, Introduction