Processes

mdworker_shared is using high CPU. Which file is Spotlight stuck on?

By the Noah team·Updated September 2, 2026·5 min read
Short answermdworker_shared is the part of Spotlight that opens individual files and pulls out the details worth searching. Several copies running at once during a burst of indexing is normal. It becomes suspicious when the processes appear and disappear in a repeating cycle for hours, because that pattern usually means one file or one file-reading plug-in fails and the work restarts. The file causing it is the thing to find, not the process.

You found several copies of mdworker_shared in Activity Monitor, each using processor time. They are Spotlight's workers: short-lived helpers that read one file at a time so it can be searched later.

Many workers during a burst of indexing is ordinary. The same workers restarting all afternoon is not, and the difference is what to look for.

What mdworker_shared does

Spotlight does not read every file each time you search. It builds an index in advance. mds coordinates that, and mdworker_shared does the reading — opening a file and extracting the parts worth searching, such as text or document properties.

It uses a small plug-in for each kind of file, called an importer. Apps install their own, so a third-party importer can affect indexing long after you stopped using the app that installed it.

The workers are meant to be short-lived. macOS runs several at once and ends them when the work is done, which is why the process list keeps changing while indexing.

When the load is ordinary indexing

You updated macOS, copied a large folder, restored a backup, or plugged in an external disk. Several workers are busy and the activity settles after a while.

Reading many files is genuinely expensive, and Spotlight prefers to get it done. The time it takes depends on how many files there are, how large they are, and how fast the disk is.

Fixleave the Mac awake and on power until the burst settles. If an external disk started it and you do not need to search that disk, add only that disk to Spotlight Privacy.

Signs one file or importer is failing

Workers keep restarting in a cycle for hours with no file change to explain it, the load returns immediately after every restart, or Spotlight results for one folder never improve.

When a worker cannot finish a file, the file stays unindexed and the work is attempted again. The usual causes are one damaged or unusual file, a third-party importer that fails on a format it claims to handle, or a network volume that stalls mid-read.

Processor use cannot distinguish those. What separates them is which location the workers are reading and whether the same failure repeats in the logs.

What Noah can determine on this Mac

NoahNoah can take a reading of the mdworker_shared processes, see which volumes are mounted, and check recent logs for the same failure repeating. That points at a location rather than at the process.

Each reading is a single snapshot, not a recording, so judging whether the cycle repeats is still yours. Noah cannot list Spotlight's importer plug-ins or query indexing status either, so the Privacy-list step above stays yours. It will not delete a file it decided was the problem.

Safe manual checks

  1. In Activity Monitor, sort by CPU and watch for a minute. Note whether workers finish or keep restarting.
  2. Disconnect an external or network volume normally. If the cycle stops, that volume was being read.
  3. In System Settings, open Spotlight and add a suspect folder to Privacy. Indexing should stop for that location only.
  4. If search results stay wrong, follow Apple's supported Spotlight rebuild steps for the affected disk.
Try Noah free

Search that works without the fan noise.

Just tell Noah what's wrong:

mdworker_shared keeps using CPU on my Mac.
Find what Spotlight is stuck onFirst conversation free7-day free trial afterOnly with your OK

Already have Noah? Open it on this problem →

Frequently asked questions

Why are there several mdworker_shared processes?

macOS runs more than one worker so files can be read in parallel. Several at once during indexing is normal, not a sign of duplication.

Is it safe to quit mdworker_shared?

Quitting one ends that file's work, and macOS starts another. It does not address the file or plug-in that is failing, so the cycle returns.

Should I turn Spotlight off?

Usually no. If one folder or disk is responsible, exclude that location in Spotlight Privacy. Turning off search everywhere hides the cause and removes something useful.

What is the difference from mds_stores?

mds_stores maintains the stored index. mdworker_shared reads individual files to fill it. A repeating worker cycle points at a file or importer; steady mds_stores load points at the index itself.

Keep readingWhen the index itself is the problem →Find the real reason your Mac is slow →Why your Mac is hot and the fans are loud →

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.