What is mds, and why is it using CPU on my Mac?
Last reviewed: 19 November 2026. Path, account, launchd job and man page checked on macOS 26.3.1.
mds is the Spotlight metadata server: it receives file changes and search requests and hands indexing work to its helper processes. It is busy after a macOS update, when many files change, and when a new disk is connected, and it settles once the index is current. It is part of macOS and should be left running.
mds at a glance
| mds | |
|---|---|
| Made by | Apple (part of macOS, Spotlight) |
| Type | System daemon |
| Location | /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Support/mds |
| Runs as | root |
| Started by | launchd job com.apple.metadata.mds |
| Can you quit it? | No. Its launchd job is set to keep it alive, so launchd starts it again straight away. |
What is mds?
The mds(8) man page calls it the metadata server: it serves every client of the metadata APIs, including Spotlight. In practice it sits in the middle of Spotlight. It learns which files have changed, decides what needs indexing, sends the work to mdworker_shared processes that read the files, and answers searches from Spotlight, Finder and the mdfind command. mds_stores writes the results into the index on each volume.
launchd starts mds at boot as root and keeps it running. Its job also schedules two maintenance tasks, a health check and the deletion of abandoned indexes, which launchd runs about every six days at maintenance priority.
Is mds safe?
Yes. mds is installed inside the CoreServices framework on the read-only system volume and is signed by Apple (signing identifier com.apple.mds). Apple's man page says users should not run it manually and that it has no settings of its own; Spotlight's options live in System Settings > Spotlight.
Why does mds use so much CPU and disk?
- Reindexing after a macOS update. Apple says Spotlight indexes at initial setup, after software updates or upgrades, and as data changes, and that the first pass can take hours or days. mds coordinates all of it, so it stays busy until the pass is done.
- Large batches of file changes. Unpacking an archive, syncing a cloud folder, restoring from a backup or building software changes thousands of files. mds receives each change and queues it for indexing.
- A disk Spotlight has not seen before. Connecting an external drive with indexing turned on makes Spotlight build an index for that volume, which mds organizes from start to finish.
- Search requests. Every Spotlight search, Finder search, smart folder and
mdfindquery is answered through mds. Apps that run many metadata queries add short bursts of CPU.
How much CPU is normal for mds?
With no files changing and nobody searching, mds is typically near 0% CPU and holds a modest amount of memory. Short spikes when you save files or search are expected.
During a full reindex after an update, mds together with mds_stores and several mdworker_shared processes can use noticeable CPU for an hour or more. Apple notes indexing goes faster when the Mac is idle and plugged into power.
How do you stop mds from using so much CPU?
- Check the indexing state. Press Command-Space: while Spotlight is indexing, an indexing progress indicator appears at the top of the Spotlight window. In Terminal,
mdutil -s /shows whether indexing is enabled for the startup disk. - Leave the Mac on power and idle. Let a post-update index finish. Keeping the Mac awake, connected to power and on a network lets Spotlight finish faster, according to Apple.
- Exclude folders and drives you never search. Open System Settings > Spotlight, click Search Privacy, and add busy folders such as virtual machine bundles, build output or backup drives. Spotlight stops indexing them, so mds has less to coordinate.
- Rebuild an index that never settles. If mds stays busy for days and searches miss files, add the affected disk to the Search Privacy list, wait a few seconds, remove it again and quit System Settings. Spotlight then reindexes that disk from the start.
When should you worry about mds?
Look closer if mds stays high for many hours on an idle Mac where nothing is syncing or changing, or if it keeps returning to high CPU every few minutes. That usually points to a folder that is rewritten constantly; excluding it in Search Privacy is the fix.
An mds process running from any path other than the Metadata framework path above, or as a user other than root, would not be Apple's.
How do you check mds in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type mds in the search field. The CPU tab shows its % CPU. The Disk tab shows its Bytes Written and Bytes Read. Double-click the row for its parent process, memory details and open files.
In Terminal, the first command lists every mds process with its PID, user, CPU and memory (RSS is resident memory in kilobytes). fs_usage prints each file it reads or writes until you press Control-C; it needs an administrator password.
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'mds' | grep -v grep
sudo fs_usage -w -f filesys mds
How can Thrum help with mds?
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 mds 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 mds
What is the difference between mds and mds_stores?
mds is the coordinator that receives file changes and search requests. mds_stores is the process that writes to and reads from the index stored on each volume.
Can I disable mds?
Not safely. macOS protects its launchd job, and Spotlight, Finder search and many apps rely on it. To stop indexing a disk, use sudo mdutil -i off / or add the disk to Search Privacy instead; mds keeps running but has much less to do.
Why does mds run as root?
It handles changes on every volume for every user, so it runs as a system daemon. The workers that open your files, mdworker_shared, run as your own user.
Sources
- mds(8) man page: run man mds in Terminal
- mdutil(1) man page: run man mdutil in Terminal
- Apple Support: About Spotlight indexing and search results on Apple devices