Processes

mds_stores is using high CPU. Is Spotlight busy or stuck?

By the Noah team·Updated August 31, 2026·5 min read
Short answermds_stores is part of Spotlight, the search index built into macOS. High CPU is usually normal after a macOS update, migration, large file change, or newly connected drive. It becomes suspicious when the load persists without progress, Spotlight results stay broken, or the logs show the same failure repeating. Do not kill the process just because it is busy: macOS restarts it, and interrupted indexing may simply begin again.

You opened Activity Monitor because the Mac was hot or slow and found mds_stores near the top. The name looks opaque, but the job is ordinary: it maintains the metadata database Spotlight uses to find files quickly.

The useful question is not whether it is running. It is whether Spotlight is making legitimate progress or repeating work it cannot finish.

What mds_stores does

Spotlight does not scan the whole disk every time you search. macOS keeps an index of file names and metadata so results appear quickly. mds coordinates that work, while mds_stores maintains the stored index. Related workers may appear beside it while files are examined.

Because this is a protected macOS process, repeatedly force-quitting it is not a repair. The system can relaunch it, and the indexing work remains unfinished.

When high CPU is normal

The Mac was updated or migrated, many files were added or renamed, or an external disk was just connected. Spotlight says it is indexing, and the CPU use changes over time.

Indexing is real work. It can use substantial processor time while the Mac reads metadata and updates its database. The duration depends on the amount and type of data, the storage device, and whether files keep changing. There is no honest universal completion time.

Fixleave the Mac awake, connect power, and give the work room to finish. If an external disk triggered the load and you do not want it searchable, add only that disk to Spotlight Privacy instead of disabling Spotlight everywhere.

Signs indexing may be stuck

The same high load returns for a long period without an obvious file change; Spotlight results are missing or stale; or the index repeatedly restarts and never becomes useful.

Those symptoms can point to one troublesome volume, repeated metadata-import failures, permission trouble, or an index that needs rebuilding. CPU alone cannot distinguish them. You need the indexing state, mounted volumes, companion processes, and recent Spotlight errors.

What Noah can determine on this Mac

NoahNoah can measure mds_stores and its companion processes, check uptime and mounted volumes, and inspect recent logs for repeated failures. That lets Noah distinguish an active index from a loop much more reliably than a screenshot of Activity Monitor.

Noah will not claim corruption from one hot reading or promise when indexing will finish. If a rebuild is justified, it should target the affected disk or folder and happen with your approval.

Safe manual checks

  1. Open Spotlight and search for a known file. Look for an indexing progress message and check whether results are improving.
  2. In Activity Monitor, search for mds. Recheck later to see whether CPU changes rather than relying on one sample.
  3. Disconnect an unneeded external volume normally. If the load falls, that volume was likely being indexed.
  4. If results remain wrong, follow Apple's supported Spotlight rebuild steps using Spotlight Privacy.
Try Noah free

See what Spotlight is doing.

Just tell Noah what's wrong:

mds_stores keeps using CPU on my Mac.
Check whether Spotlight is stuckFirst conversation free7-day free trial afterOnly with your OK

Already have Noah? Open it on this problem →

Frequently asked questions

Is mds_stores malware?

No. It is a standard macOS process used by Spotlight. Its unfamiliar name does not make it suspicious.

Is it safe to quit mds_stores?

Force-quitting it does not solve the reason indexing is busy. macOS can restart it, and interrupted work may resume. Diagnose the indexing state first.

Should I disable Spotlight?

Usually no. If one disk or folder causes unnecessary indexing, exclude that location. Disabling Spotlight everywhere removes useful search and hides the underlying cause.

Keep readingWhen a single file or plug-in is the problem →Find the real reason your Mac is slow →Why your Mac is hot and the fans are loud →What high swap usage means →

Commands in this guide are standard, read-only macOS diagnostics unless noted; anything that changes your system is called out. When in doubt, back up first with Time Machine.