What is mdworker on a Mac, and why is it running?
Last reviewed: 19 November 2026. Path, launchd jobs, man page and binary architectures checked on macOS 26.3.1.
mdworker is a Spotlight worker process that mds uses to scan and index files when a volume is mounted or a file changes. On current macOS most of that work is done by mdworker_shared, and mdworker is started only by a few specific launchd jobs. When it does appear, it is busy for the same reasons as other Spotlight indexing and stops when the work is done.
mdworker at a glance
| mdworker | |
|---|---|
| Made by | Apple (part of macOS, Spotlight) |
| Type | Worker process (several launchd jobs) |
| Location | /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Support/mdworker |
| Runs as | your user |
| Started by | launchd job com.apple.mdworker.single.arm64 |
| Can you quit it? | Yes. It is started on demand and Spotlight starts it again if it still has work. |
What is mdworker?
The mdworker(8) man page describes it as the metadata server worker, used by mds to scan and index files as a volume is mounted or a file changes. On macOS 26 the everyday worker is mdworker_shared; mdworker is the same kind of worker launched under separate jobs.
Four launchd jobs point at mdworker: com.apple.mdworker.single.arm64 and com.apple.mdworker.single.x86_64 (per-user agents), com.apple.mdworker.sizing (a per-user agent that runs with low-priority disk access), and com.apple.metadata.mds.spindump (a root daemon). The program is a universal binary, and the x86_64 job asks for its Intel version, which on an Apple silicon Mac runs under Rosetta 2. That is why Activity Monitor can show an mdworker with Kind "Intel".
Is mdworker safe?
Yes. It lives next to the other Spotlight programs in the Metadata framework on the read-only system volume and is signed by Apple (com.apple.mdworker). An mdworker running as Intel on an Apple silicon Mac is expected, because of the job described above.
Why does mdworker use so much CPU and disk?
- Files handed to a single-architecture worker. When mds sends work to one of the
singlejobs, mdworker reads those files and extracts their text and metadata, which costs CPU in proportion to the size of the files. - A newly mounted volume. The man page names mounting a volume as one of the moments mdworker scans files, so connecting a drive with indexing on can start it.
- Running under Rosetta 2. The Intel copy is translated by Rosetta 2 on Apple silicon, which adds some CPU overhead compared with the native worker.
How much CPU is normal for mdworker?
On most Macs mdworker is not running at all, or appears briefly and exits. When it does run, short bursts of CPU while it reads files are normal.
It should not stay busy for long periods. If it does, the same Spotlight causes apply as for mdworker_shared: a large batch of files, a full reindex, or a folder that changes constantly.
How do you stop mdworker from using so much CPU?
- See what it is reading. Run
sudo fs_usage -w -f filesys mdworkerin Terminal for a few seconds and press Control-C to see which files it opens. - Check its Kind. In Activity Monitor's CPU tab, the Kind column shows Apple or Intel. An Intel mdworker is the Rosetta copy started by the
single.x86_64job. - Exclude the busy location. Add the folder or drive to System Settings > Spotlight > Search Privacy so Spotlight stops indexing it.
- Review importer plug-ins. Run
mdimport -Lto list installed Spotlight importers. Removing an app you no longer use also removes the importer it installed.
When should you worry about mdworker?
Look into it if mdworker stays at high CPU for hours with no new files arriving, or restarts constantly. fs_usage usually shows a single file or folder behind it.
A process called mdworker running from anywhere other than the Metadata framework path above is not Apple's worker.
How do you check mdworker in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), and type mdworker in the search field. The CPU tab shows its % CPU. The Disk tab shows its Bytes Written and Bytes Read. Double-click the row for its parent process, memory details and open files.
In Terminal, the first command lists every mdworker 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' | grep -v grep
sudo fs_usage -w -f filesys mdworker
How can Thrum help with mdworker?
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 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 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
Why does mdworker show as Intel on my Apple silicon Mac?
One of its launchd jobs is configured to run the x86_64 version of the program, which runs under Rosetta 2. The program itself contains both Apple silicon and Intel code.
Can I delete mdworker?
No. It is on the sealed, read-only system volume, and Spotlight depends on it. Exclude folders in Search Privacy instead.
Sources
- mdworker(8) man page: run man mdworker in Terminal
- mdimport(1) man page: run man mdimport in Terminal
- launchd job files: /System/Library/LaunchAgents/com.apple.mdworker.single.x86_64.plist and com.apple.mdworker.sizing.plist