How to Fix mds_stores High CPU on Mac
If mds_stores causes high CPU usage, Kudu can help clean clutter and improve Mac performance.
By Kudu Team
Fix this automatically with Kudu
Run a free system scan to detect and resolve this issue automatically — no manual steps required.
Download Kudu Free →What Causes This?
mds_stores is part of macOS Spotlight indexing. It scans and organizes files so search results appear quickly, but CPU usage can spike when Spotlight is rebuilding its index, processing a large number of new or changed files, or getting stuck on corrupted metadata. This often happens after a macOS update, restoring files from backup, connecting an external drive, or when the disk is low on free space.
Common Symptoms
- Mac fans run loudly even when you are not doing much
- Activity Monitor shows
mds_storesusing a high percentage of CPU - Spotlight searches feel slow or incomplete
- The Mac becomes hot, laggy, or drains battery faster than normal
- High CPU usage starts after adding many files or plugging in an external drive
How to Fix It Manually
-
Confirm that
mds_storesis the problem- Open Activity Monitor from Applications > Utilities.
- Click the CPU tab.
- Look for
mds_storesin the process list and check whether it stays high for several minutes.
-
Wait if indexing recently started
- If you just updated macOS, restored files, or copied lots of data, Spotlight may simply be rebuilding its index.
- Leave the Mac plugged in and idle for a while, then check Activity Monitor again.
- If CPU usage drops after some time, no further action may be needed.
-
Restart your Mac
- Click the Apple menu > Restart.
- After logging back in, wait a few minutes and recheck Activity Monitor.
- Temporary indexing glitches often clear after a restart.
-
Exclude problem folders or drives from Spotlight
- Open Apple menu > System Settings.
- Go to Siri & Spotlight.
- Scroll down and open Spotlight Privacy or Search Privacy.
- Add folders, external drives, or locations with constantly changing files, such as backup folders, virtual machine images, or large archives.
- Remove any drive you do want indexed later after CPU usage settles.
-
Rebuild the Spotlight index
- Open Apple menu > System Settings > Siri & Spotlight.
- Open Spotlight Privacy.
- Drag your Macintosh HD into the privacy list to stop indexing it.
- Wait about a minute, then remove it from the list.
- Spotlight will rebuild the index from scratch, which can fix corrupted metadata causing
mds_storesto loop.
-
Check available storage
- Open Apple menu > About This Mac > Storage or System Settings > General > Storage.
- Make sure you have a reasonable amount of free space available.
- Delete or move large unnecessary files if the disk is nearly full, since low storage can make indexing slower and less stable.
-
Disconnect or test external drives
- Safely eject external drives one at a time.
- Watch Activity Monitor after each one.
- If CPU usage drops, that drive may contain files Spotlight is struggling to index. You can exclude it from Spotlight privacy settings.
Fix It Automatically with Kudu
If you do not want to hunt through storage, caches, and problem files manually, Kudu can help speed up the cleanup process. It can identify clutter, free up disk space, and reduce the conditions that often cause indexing services like mds_stores to stay busy longer than they should.
Fix this automatically with Kudu
Run a free system scan to detect and resolve this issue automatically — no manual steps required.
Download Kudu Free →Related guides
How to Fix kernel_task High CPU on Mac
Learn why kernel_task uses so much CPU and how Kudu can reduce background clutter on your Mac.
How to Fix WindowServer High CPU on Mac
Reduce WindowServer CPU usage on macOS by cleaning clutter and improving overall system responsiveness with Kudu.
How to Fix Chrome High Memory Usage on Mac
Reduce Chrome memory usage on macOS by clearing cache and cleaning system clutter with Kudu.
How to Fix High Memory Pressure on Mac
Learn why memory pressure is high on your Mac and how Kudu can clean clutter to improve responsiveness.