What is mds_stores, and why is it using so much CPU on my Mac?
Last reviewed: 19 November 2026. Path, account and launchd job checked on macOS 26.3.1.
mds_stores is the part of Spotlight that writes and updates the search index for each disk. It uses a lot of CPU and disk after a macOS update, after you copy or download many files, or when you connect a new drive, and it settles once the index is up to date. It is safe and should be left running; exclude busy folders in Spotlight's Search Privacy settings if it never settles.
mds_stores at a glance
| mds_stores | |
|---|---|
| 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_stores |
| Runs as | _mds_stores (a system account) |
| Started by | launchd job com.apple.metadata.mds.index |
| Can you quit it? | Not usefully. launchd starts it again when Spotlight needs the index. |
What is mds_stores?
mds_stores is the Spotlight process that owns the index stores: the databases on each volume that Spotlight searches when you press Command-Space or search in Finder. Other parts of Spotlight read the contents of files (mdworker_shared) and coordinate the work (mds); mds_stores takes what they find and writes it into the index.
It runs as its own system account, _mds_stores, not as your user, and launchd starts it on demand through the com.apple.metadata.mds.index job. The index for the startup disk lives in a hidden .Spotlight-V100 folder at the top of the volume.
Is mds_stores safe?
Yes. mds_stores is part of macOS, lives inside the CoreServices framework in /System/Library, and is signed by Apple. That folder is on the read-only system volume, so a program with the same name elsewhere on the disk would not be this process. You can check the path in Activity Monitor: double-click the process and click Open Files and Ports, or use the ps command below.
Why does mds_stores use so much CPU and disk?
- First index after an update or a new Mac. After a macOS update, a migration, or erasing the index, Spotlight indexes the whole disk again. This can keep mds_stores and mdworker_shared busy for an hour or more on a full disk.
- Many new or changed files. Copying a large folder, unpacking an archive, syncing a cloud folder or building code creates many files, and each one is added to the index.
- A new or external drive. When you connect a drive that Spotlight has not indexed, it builds an index for that volume too. Large backup or media drives take longest.
- Folders that change all the time. Folders that are rewritten constantly, such as virtual machine disks, database files, build output or download caches, make Spotlight re-index the same data repeatedly.
- A damaged index. If the index is damaged, Spotlight may keep rebuilding it. Searches that miss files you know exist are a sign of this.
How much CPU is normal for mds_stores?
Short bursts of CPU and disk activity whenever files change are normal. After a macOS update or when a new drive is attached, high CPU for an hour or more is also expected; the time depends on how many files the disk holds.
When the Mac is idle and no files are changing, mds_stores should be at or near 0% CPU. A process that stays high for many hours with nothing changing is worth looking into.
How do you stop mds_stores from using so much CPU?
- Let the first index finish. After an update or a new drive, keep the Mac awake and connected to power and let indexing finish. Activity Monitor's CPU tab shows mds_stores and mdworker_shared dropping back toward 0% when it is done.
- Check whether indexing is on. In Terminal, run
mdutil -s /to see whether indexing is enabled for the startup disk. Run it with another volume path to check an external drive. - Exclude busy folders. Open System Settings > Spotlight, click Search Privacy, and add folders that change constantly and that you never search, such as virtual machine folders, build folders or large download caches.
- Exclude drives you never search. Add a backup or archive drive to the same Search Privacy list. Spotlight stops indexing it and removes its index.
- Rebuild the index of a folder or drive. If searches miss files and mds_stores never settles, Apple's method is to add the affected disk or folder to the Search Privacy list, wait a few seconds, remove it again, and close System Settings. Spotlight then indexes that location again from the start.
sudo mdutil -E /in Terminal erases the whole index of the startup disk and has the same effect for everything on it.
When should you worry about mds_stores?
Look closer if mds_stores stays above about 50% CPU for many hours while the Mac is idle and no files are changing, or if it returns to high use every few minutes. That pattern usually points to one folder that is rewritten constantly; sudo fs_usage -w -f filesys mdworker_shared shows which files are being read.
A process named mds_stores running from a location other than the CoreServices framework path above would not be Apple's. That is very unlikely, but the path check takes seconds.
How do you check mds_stores in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type mds_stores 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_stores 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_stores' | grep -v grep
sudo fs_usage -w -f filesys mds_stores
How can Thrum help with mds_stores?
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_stores 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_stores
Can I quit or force quit mds_stores?
You can, but launchd starts it again as soon as Spotlight needs it, and any indexing work starts over. It is better to exclude busy folders or let indexing finish.
Does turning off Spotlight indexing stop mds_stores?
Running sudo mdutil -i off / stops indexing on the startup disk, and mds_stores then has little to do. Spotlight can no longer find files on that disk, and other features that rely on the index, such as searching in Mail, are affected.
Why does mds_stores use so much memory?
It holds parts of the index in memory while it updates them, so its memory use grows during heavy indexing. macOS reclaims that memory when other apps need it.
What is the difference between mds, mds_stores and mdworker_shared?
mds is the Spotlight server that receives file changes and search requests, mdworker_shared reads the contents of files, and mds_stores writes the results into the index on each volume.
Sources
- mdutil(1) man page: run man mdutil in Terminal
- Apple Support: About Spotlight indexing and search results on Apple devices