What is mdworker_shared on Mac, and why is it using so much CPU?
mdworker_shared is a macOS system process that reads the contents of files so Spotlight can search them.
| Shown in Activity Monitor as | mdworker_shared |
|---|---|
| Made by | Apple, part of macOS |
| WhySlow's verdict | Leave it. Settles on its own |
See what’s slowing your Mac right now: download WhySlow free. One-click fixes cost $10, once or yearly.

Measured on a MacBook Pro (M4 Max, 128 GB) on 4 October 2026: Each mdworker_shared process used 0.1 to 0.2% CPU and about 3 MB of memory while nothing was being indexed.
Why is mdworker_shared using so much CPU?
Busy when many new or changed files need indexing, like builds or big downloads.
What mdworker_shared does
Spotlight uses mdworker_shared processes to read the contents of files for indexing, and you often see several at once, one per kind of work. Folders with huge numbers of small files, like code builds, package caches and photo exports, keep them busy; excluding those folders in Spotlight settings helps.
Should you quit mdworker_shared?
No. mdworker_shared is part of macOS. Quitting it can break things, and macOS starts it again anyway. When it is busy, it usually settles on its own.
Check that search still finds your files
Try finding a file you know exists and note whether the result is missing. Indexing after an update or large transfer can take time without indicating a fault. If you exclude a folder in Search Privacy, its contents will no longer appear in Spotlight results; choose folders deliberately.
Rebuilding is a troubleshooting step for unexpected search results. It can make indexing activity increase before it settles. Follow Apple’s current instructions for your macOS version and allow that new pass to finish before judging the result.
Is mdworker_shared a virus?
The name mdworker_shared alone can't prove a process is genuine, and this page isn't a security scan. Check where it runs from: genuine macOS processes run from system folders such as /System/Library and /usr/libexec. In Activity Monitor, double-click mdworker_shared and choose Open Files and Ports to see its location. If it appeared right after you installed something unexpected, don't grant it more permissions, and ask the software vendor or Apple Support.
How to check mdworker_shared on your Mac
Open Activity Monitor (Applications › Utilities), choose the CPU tab and type mdworker_shared in the search field. The % CPU column shows how busy it is: 100% means one full processor core. Watch it for a minute while you repeat the task that felt slow.
What to do if mdworker_shared stays busy
- Allow indexing to finish after an update or a large file transfer. Apple says it can take hours or days, depending on how much information is being indexed.
- Keep busy folders out of the index: open System Settings › Spotlight › Search Privacy and add folders like Xcode DerivedData, Docker data or virtual machine folders.
- See whether indexing is on and still running: in Terminal, mdutil -s / reports the indexing status of your startup disk.
- If Spotlight search results remain incomplete or unexpected after indexing, follow Apple’s rebuilding instructions (System Settings, or sudo mdutil -E / in Terminal). High CPU alone does not mean the index is broken; rebuilding starts the indexing work again.
How WhySlow helps with mdworker_shared
- Shows how much CPU and memory mdworker_shared is using right now, in plain English.
- Opens Spotlight settings so you can keep big folders out of the index.
- Offers a Spotlight index rebuild when search results need repair; rebuilding starts a fresh indexing pass.
Free to explain. One-click fixes cost $10, once or yearly.
Sources
The process description comes from WhySlow’s app catalog. Diagnosis depends on your workload and the version of macOS or the app you use. For an unfamiliar process, start with Apple’s guide to inspecting processes and reading CPU activity.
For indexing problems, follow Apple’s Spotlight guidance. Duration varies; a fixed three-hour cutoff is not a reliable diagnosis.
Need a broader starting point? Follow the slow Mac checklist or learn about memory pressure.