Thrum

What is mdworker_shared, and why are there so many of them?

Last reviewed: 19 November 2026. Path, account, launchd jobs and code signature checked on macOS 26.3.1.

mdworker_shared is a Spotlight worker that opens files and pulls out their text and attributes so they can be added to the search index. macOS runs several copies at once when many files need indexing, for example after an update or a large copy, and they exit when the work is done. They are part of macOS and safe to leave alone.

mdworker_shared at a glance

mdworker_shared
Made byApple (part of macOS, Spotlight)
TypeUser agent (on-demand worker)
Location/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Support/mdworker_shared
Runs asyour user
Started bylaunchd job com.apple.mdworker.shared
Can you quit it?Yes, without harm. It is a short-lived worker; Spotlight starts a new one when there are files to read.

What is mdworker_shared?

When mds decides a file needs indexing, it hands the file to an mdworker_shared process. The worker loads the Spotlight importer plug-in for that file type, reads the file, and returns its text and metadata (title, author, dimensions, duration and so on) to be written into the index by mds_stores.

Its launchd job allows multiple instances, so Activity Monitor often lists several mdworker_shared processes at the same time. They run as your user, which keeps the reading of your files inside your own account. A second job, com.apple.mdworker.mail, runs the same program for Mail data.

Is mdworker_shared safe?

Yes. The program sits in the Metadata framework on the read-only system volume and is signed by Apple (com.apple.mdworker_shared). Seeing many copies is normal and is not a sign of malware. Quitting one does no harm, but Spotlight will start another for the remaining files.

Why does mdworker_shared use so much CPU, disk and memory?

How much CPU is normal for mdworker_shared?

On an idle Mac with no new files there may be no mdworker_shared process at all, or one or two near 0% CPU. They exit on their own when they have nothing to do.

During heavy indexing, three or four workers at a few percent to tens of percent of CPU each is typical. The total settles back once the queue of files is empty.

How do you stop mdworker_shared from using so much CPU?

  1. Find out which files are being read. Run sudo fs_usage -w -f filesys mdworker_shared in Terminal for a few seconds and press Control-C. The paths show which folder keeps the workers busy.
  2. Exclude that folder from Spotlight. Open System Settings > Spotlight, click Search Privacy, and add the folder. Workers stop reading files inside it.
  3. Check the installed importers. Run mdimport -L to list the importer plug-ins. If an importer from an app you no longer use is listed, removing that app removes its importer.
  4. Let a reindex finish on power. After an update, keep the Mac awake and plugged in until the workers settle. Apple says indexing is faster when the Mac is idle and on power.

When should you worry about mdworker_shared?

If one mdworker_shared stays at high CPU for a long time while fs_usage shows it reading the same file over and over, that file or its importer may be causing trouble. Moving the file to an excluded folder confirms it.

A process with this name outside the Metadata framework path, or one that keeps running and opening network connections, would not be Apple's worker.

How do you check mdworker_shared in Activity Monitor and Terminal?

Open Activity Monitor (Applications > Utilities), and type mdworker_shared in the search field. The CPU tab shows its % CPU. The Disk tab shows its Bytes Written and Bytes Read. The Memory tab shows its Memory. Double-click the row for its parent process, memory details and open files.

In Terminal, the first command lists every mdworker_shared 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 'mdworker_shared' | grep -v grep
sudo fs_usage -w -f filesys mdworker_shared

How can Thrum help with mdworker_shared?

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 mdworker_shared 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. Click mdworker_shared in the list for its PID, threads and memory, and Quit or Force Quit it after a confirmation.

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 mdworker_shared

Why are there so many mdworker_shared processes?

Spotlight runs several workers in parallel so indexing finishes sooner. Each one handles a share of the files and exits when idle.

Is mdworker_shared the same as mdworker?

They are related programs. mdworker_shared is the shared worker used for most indexing on current macOS. mdworker is a separate program with its own launchd jobs, and it rarely appears.

Does mdworker_shared upload my files?

No. Apple says the Spotlight index is local and private and is not shared with Apple or your other devices.

Sources