How to Stop mds_stores from Overusing CPU and Memory on macOS

The macOS Spotlight indexing daemon mds_stores can unexpectedly consume large amounts of CPU and RAM, slowing the system and causing fans to run loudly [1]. This behavior often appears even when no major file changes occur, and it may be linked to oversized directories, external drives, or specific app activity [1].

Key takeaways

• mds_stores is the core Spotlight metadata server that indexes files and should only use modest resources [1].
• High CPU usage (over 40 % or a full core) may indicate a corrupted Spotlight index or excessive folder monitoring [2].
• Disabling Spotlight temporarily, limiting indexed locations, or forcing a full re‑index are common remediation steps [1].
• Killing the process in Activity Monitor, running Disk Utility’s First Aid, and booting in Safe Mode are additional troubleshooting methods [2].
• If the issue persists, excluding large folders via System Preferences → Spotlight → Privacy or reinstalling the index may be required [1].

Spotlight’s metadata server and why it can misbehave

Spotlight relies on the Metadata Server (MDS) to keep a searchable database of files, a task performed by the mds_stores process [2]. Under normal conditions the daemon uses minimal CPU, but users have reported spikes that push a single core to 100 % and cause noticeable heat and fan noise [1]. The problem can arise when an application constantly modifies a folder, when very large directories (such as massive Time Machine backups) are indexed, or when external drives are connected, prompting the system to re‑index large volumes [1]. Some reports also mention browser extensions, like a Pinterest add‑on for Firefox, as a trigger [1].

Step‑by‑step fixes recommended by experts

The first line of defense is to verify whether Spotlight is the culprit. Running sudo mdutil -a -i off in Terminal disables indexing; if CPU usage drops, mds_stores is confirmed as the source [1]. Afterward, re‑enable indexing with sudo mdutil -a -i on and consider narrowing the indexed scope via System Preferences → Spotlight → Privacy, adding folders or disks that do not need to be searchable [1]. For a more thorough reset, deleting the Spotlight database (sudo rm –rf /.Spotlight-V100/*) forces a fresh rebuild, though this can take several hours [1].

If disabling Spotlight does not resolve the issue, users can kill the mds_stores process in Activity Monitor; macOS will automatically restart it [2]. Running First Aid in Disk Utility checks for file‑system corruption that might be confusing the index [2]. Booting into Safe Mode disables third‑party extensions and can help isolate the offending component; the process should be killed and First Aid rerun while in Safe Mode [2]. Logging in with a guest account is another diagnostic step, though the source does not detail its outcome [2].