Is Spotlight Indexing Killing Your Mac's Performance?

Open Activity Monitor on a slow Mac and there’s a decent chance you’ll see one of two processes near the top: mds_stores or mdworker_shared. Both belong to Spotlight, the system-wide search engine that powers Cmd+Space, Finder search, and a lot of macOS features people don’t realize are Spotlight-driven (like Mail’s search, Notes search, and the suggestions in Safari).

When Spotlight’s indexing is healthy, you don’t notice it. When it’s struggling — too much to index, a corrupted index, or a stuck job — it can absolutely tank your Mac’s performance for days at a time.

Here’s how to tell whether Spotlight is your problem and how to fix it.

What Spotlight actually does

Spotlight maintains an index of file metadata across your drives. Every file you create, modify, or move generates work for Spotlight to update its index. The point is that when you search “invoice 2024,” macOS instantly knows which 47 files match without scanning the disk.

The processes you’ll see:

• mds — the main metadata server, manages indexing schedule
• mds_stores — the storage backend, persists the index
• mdworker_shared — workers that actually read files and extract metadata
• mdworker — older worker process

Some indexing activity is constant and normal. Sustained high CPU usage from these processes for days is not.

Symptoms of Spotlight problems

Watch for:

• Mac runs hot and fans run for no obvious reason
• Battery drains faster than usual
• Spotlight search is slow or returns no results
• Search in Mail or Notes doesn’t find recent items
• Activity Monitor shows mds_stores or mdworker_shared at 50%+ CPU consistently
• Disk Utility shows high disk activity even when you’re not doing anything
• All this has been going on for days

If multiple of these are true, Spotlight is the likely culprit.

There’s a faster waySweep handles this automatically and lets you approve before anything’s deleted. Try Sweep free →

When Spotlight is reindexing for legitimate reasons

Some scenarios where Spotlight indexing is expected and you should just wait:

1. First boot after a macOS update — Spotlight reindexes against the new schema
2. After Migration Assistant or restoring from backup — fresh index of all migrated files
3. After connecting a new external drive — indexes the drive’s contents
4. After a major file import — reindexes affected files
5. First boot of a new Mac — initial index

In these cases, plug in your Mac, leave it on overnight (multiple nights for big libraries), and let Spotlight finish. There’s not much to do beyond patience.

If indexing has been running for over a week without obvious progress, something is wrong.

Step 1: Check what Spotlight is doing

Open Terminal (Applications → Utilities → Terminal). Run:

mdutil -s /

This tells you the indexing status of your startup volume. Possible responses:

• “Indexing enabled” — normal state, Spotlight active
• “Indexing and searching disabled” — Spotlight off
• “No index” — index missing, will be rebuilt

To see indexing progress on the system, run:

mdutil -sa

This shows status for all volumes.

Step 2: Check what files are being indexed

Spotlight indexing is sometimes pegged because it’s stuck on specific files. Common culprits:

• VM disk images (Parallels, UTM, VMware) — huge files that Spotlight tries to index
• Time Machine backups on local drives — sometimes Spotlight tries to index these
• Docker volumes — many small files generated and deleted constantly
• Code repository directories with thousands of files
• Photo or video archives
• .localized folders and other macOS internals

Excluding these from Spotlight prevents it from constantly reindexing them.

Step 3: Exclude folders from indexing

System Settings → Siri & Spotlight → Spotlight Privacy. Add folders that don’t need to be searchable:

• VM disk locations
• Docker data directories (often ~/Library/Containers/com.docker.docker)
• Media archive folders (4K video, raw photo libraries you’ve already organized)
• Code project directories with build artifacts
• External drives that are bulk storage

After adding exclusions, indexing finishes faster (less to index) and ongoing work is reduced.

Step 4: Force a clean reindex (the nuclear option)

If Spotlight is genuinely stuck — pegged for a week, search returns nothing useful, indexing seems to never finish — force a complete reindex.

Method 1: via System Settings

1. System Settings → Siri & Spotlight → Spotlight Privacy
2. Click ”+” and add your startup disk (Macintosh HD)
3. Wait 30 seconds
4. Click ”−” to remove it

This wipes the index and starts fresh. Takes hours to complete; leave the Mac on, plugged in, idle.

Method 2: via Terminal

sudo mdutil -E /

This is the same effect, faster to type. You’ll be prompted for your admin password.

After either method, Spotlight rebuilds. Performance is impacted during the rebuild but normalizes when it finishes.

Step 5: Check disk space and drive health

A near-full drive can cause Spotlight indexing to hang or run forever. The index needs space to write to. Below 10% free, expect indexing problems.

System Settings → General → Storage. If you’re tight, free up space.

A failing drive also causes Spotlight problems — the indexing tries to read files and the disk returns errors. Run Disk Utility’s First Aid on your drive (Applications → Utilities → Disk Utility).

Skip the manual huntSweep finds every cache, log, and forgotten file in seconds — and only removes what you OK. Download Sweep free →

Step 6: Disable Spotlight entirely (last resort)

If you really don’t use Spotlight search and don’t want the indexing overhead:

sudo mdutil -ai off

This disables indexing on all volumes. You’ll lose:

• Cmd+Space app launching (it’ll still work but slower)
• Search in Mail, Notes, Reminders
• Finder search
• Many “smart” features that depend on metadata

I don’t recommend this for most users. Better to exclude problematic folders and let Spotlight do its job for the rest.

To re-enable later:

sudo mdutil -ai on

When mds_stores is using disk, not CPU

Sometimes the issue is disk activity, not CPU. mds_stores writes to /.Spotlight-V100/ on each indexed volume. If that folder gets corrupted or massive, you get constant background disk writes.

The Spotlight-V100 folders can grow unexpectedly large — sometimes 5-10GB on a heavily used Mac. A clean reindex (Step 4) regenerates these folders fresh and usually smaller.

Network drives and Spotlight

If you have network drives mounted (NAS, file server), Spotlight may try to index them. This causes network and CPU use even when you’re not actively using those drives.

In System Settings → Siri & Spotlight → Spotlight Privacy, add network drives to prevent indexing. Most NAS devices have their own search anyway.

When you find Spotlight is fine but Mac is still slow

If you’ve checked Activity Monitor and Spotlight processes are not pegged, it’s something else. Don’t go down the Spotlight rabbit hole if the data doesn’t support it. The processes to watch:

• kernel_task — high values suggest thermal throttling
• WindowServer — if pegged, UI is struggling
• bird — iCloud Drive sync
• cloudd / accountsd — iCloud account services
• photoanalysisd — Photos library work
• App-specific processes — browsers, sync apps, etc.

Each has its own diagnostic flow. Spotlight is one cause among many. If it’s not the cause, no amount of Spotlight tuning will help.

Healthy Spotlight behavior

After an initial index of a fresh Mac (typically 1-3 hours), Spotlight processes should:

• Use minimal CPU during normal use (under 5%)
• Spike briefly when files change
• Not consistently appear in Activity Monitor’s top processes
• Search results return in milliseconds

If you’re seeing this, Spotlight is healthy. If you’re seeing constant high CPU from Spotlight processes for days, something is wrong, and the steps above will fix it most of the time.

The goal is for Spotlight to be invisible — a feature you use without thinking about it. Get there, and your Mac feels noticeably faster all day.