Sweepfor Mac

Troubleshooting

Spotlight Not Working on Mac? Here's How to Fix It

Spotlight not finding files on Mac? Here's how to rebuild the index, fix indexing errors, and get search working again — every macOS scenario.

8 min read

You hit Cmd+Space and type the name of a document you opened yesterday. No results. Or partial results. Or worse: results pointing at apps and contacts but not your actual files. Or Spotlight just spins indefinitely. Whatever you’re trying to find, the system search has failed you, and the rest of macOS feels broken without it.

Spotlight is a stack of services — mds, mds_stores, corespotlightd — and any one of them being unhealthy breaks search. Diagnosing which layer is sick narrows the fix.

How Spotlight actually works

Three components run continuously:

  • mds (metadata server) — coordinates indexing across volumes.
  • mds_stores — does the actual indexing work, parsing file content.
  • corespotlightd — handles app-supplied search content (Mail, Notes, Messages).

The index lives in .Spotlight-V100 directories at the root of every indexed volume. Each volume has its own; if one is corrupt, search misses files on that volume only.

When you type into Spotlight, you’re querying these indexes plus live data sources (Calendar events, Contacts, Reminders, Mail). The visible result list is a merge.

Quick diagnostics

1. Check if Spotlight returns nothing or partial results

  • Nothing at all — Spotlight is fully broken. mds may be hung; the index may be missing.
  • Partial results — index is incomplete or one volume isn’t indexed.
  • App results but not files — file index is broken; app metadata is fine.
  • No mail results — corespotlightd or Mail indexing issue.

The pattern tells you where to focus.

2. Check indexing status

mdutil -s /

Outputs Indexing enabled. or Indexing disabled. for the startup volume. Add other volumes with mdutil -s /Volumes/External.

If it says disabled for a volume that should be searched, re-enable:

sudo mdutil -i on /

3. Watch indexing progress

mdutil -p /

Shows progress of an active indexing pass. If a fresh index is being built, expect hours of activity before search is comprehensive.

Skip the manual huntSweep clears the cruft that triggers most of these errors — caches, logs, leftover daemons. Download Sweep free →

Quick fixes that resolve most cases

1. Restart the Mac

The most common cause of broken Spotlight is mds getting stuck. Restart kicks all Spotlight processes back to clean state.

2. Kill and restart the indexing daemons

In Terminal:

sudo killall mds
sudo killall mds_stores
sudo killall corespotlightd

The system relaunches them. If they were stuck on a corrupt file, the relaunch may move past it.

3. Re-enable Spotlight on the volume

sudo mdutil -E /

The -E flag forces an erase and rebuild of the index. The system stops returning results until indexing completes (typically 1–4 hours on a busy disk).

If you want to rebuild a specific external volume:

sudo mdutil -E /Volumes/ExternalDrive

Force a complete rebuild

If mdutil -E doesn’t help, manually delete the index directory and let macOS recreate it:

  1. Open Terminal.
  2. Disable indexing on the volume:
sudo mdutil -i off /
  1. Remove the index directory:
sudo rm -rf /.Spotlight-V100
  1. Re-enable indexing:
sudo mdutil -i on /
  1. Trigger reindex:
sudo mdutil -E /

Wait. The full rebuild can take an entire workday on a 1 TB disk. Use Activity Monitor to watch mds_stores’ CPU and memory while it runs.

Tip: Don't power off the Mac during a Spotlight rebuild. Plug into power if you're on a laptop. Interrupted rebuilds sometimes leave the index in worse shape than before.

Add and remove Privacy folders to nudge indexing

A long-standing trick: add a folder to Spotlight Privacy, remove it, and the volume re-indexes.

  1. System Settings → Siri & Spotlight → Spotlight Privacy.
  2. Click + → add a top-level folder (or your whole startup volume by selecting Macintosh HD).
  3. Wait 10 seconds.
  4. Remove the folder.
  5. macOS rebuilds the index for that area.

This works for surface-level corruption without nuking everything.

Specific scenarios

Spotlight finds nothing in Mail

Mail uses corespotlightd. If only Mail results are missing:

  1. Mail → Mailbox menu → Rebuild (the active mailbox).
  2. If that doesn’t help: quit Mail, delete ~/Library/Mail/V*/MailData/Envelope Index*, relaunch Mail. Mail rebuilds its index.

Spotlight finds nothing in Notes or Messages

These use corespotlightd. To fully reset:

sudo killall corespotlightd

Wait several minutes for the daemon to reindex from the apps. Some apps re-add their data to corespotlightd only after they next launch and detect missing entries.

Spotlight ignores external drives

By default, indexing is on for external drives. Verify:

mdutil -s /Volumes/ExternalDrive

If disabled, enable. If enabled but search doesn’t find files there, force a rebuild:

sudo mdutil -E /Volumes/ExternalDrive

Some filesystems (NTFS, exFAT) have weaker metadata support and indexing is shallower. Don’t expect content search inside files on those volumes to work as well as on APFS.

Spotlight returns results from the wrong location

You search “report” and Spotlight returns the app, not the document. This is a relevance issue, not a broken index. Customize what Spotlight returns: System Settings → Siri & Spotlight → Search results → uncheck categories you don’t want. Apps and Top Hit are usually the priority items pushed up.

Spotlight is slow to return results

mds_stores might be busy indexing. Check Activity Monitor. If indexing is consuming high CPU, search will be slow until the pass completes. Especially common in the first hour after a macOS upgrade or major file move.

Diagnose AND clean in one appSweep finds the buildup behind the error and clears it. Try Sweep free →

When mds_stores is using 100% CPU forever

If mds_stores has been pinning a CPU core for hours without finishing, it’s probably stuck on a corrupt file or directory. To find what:

  1. Activity Monitor → search mds_stores → click the (i) → Open Files and Ports tab.
  2. Look at recent files. The list rotates as it indexes.
  3. If a specific path appears repeatedly, that’s the stuck file.

To skip past:

  1. System Settings → Siri & Spotlight → Spotlight Privacy.
  2. Add the parent folder of the stuck file.
  3. Wait for indexing to settle.
  4. Remove the parent folder if you do want it indexed.

This forces Spotlight to skip the area and complete the rest of the index. You can also outright delete the stuck file if you don’t need it.

When Spotlight integration is broken in apps

Some apps integrate with Spotlight via a bundled .mdimporter. If a specific app’s contents aren’t searchable:

mdimport -L

Lists active importers. Look for the one matching your app. If missing, the app’s importer plugin may be broken.

To force re-import:

mdimport -r /Applications/AppName.app/Contents/Library/Spotlight/AppImporter.mdimporter

Some third-party apps bundle their importer in a different path; check the app’s package contents.

Reset Spotlight via complete sequence

When nothing else works, the full reset:

  1. Disable Spotlight everywhere:
sudo mdutil -a -i off
  1. Delete all indexes:
sudo find / -name ".Spotlight-V100" -type d -exec rm -rf {} +
  1. Restart the Mac.

  2. Re-enable Spotlight:

sudo mdutil -a -i on
  1. Trigger rebuild:
sudo mdutil -a -E

Plan for a long indexing day. Don’t sleep the Mac mid-rebuild. By the next morning, search is comprehensive again.

When FileVault is involved

FileVault encrypts the volume, which doesn’t break indexing — Spotlight runs above the encryption layer. But FileVault’s initial conversion (or decryption) competes for disk I/O with Spotlight, slowing both. If you’re mid-encryption, expect search to be patchy until conversion finishes.

When the disk is failing

Persistent Spotlight failures despite full rebuilds, paired with other I/O symptoms (slow file copies, occasional read errors, kernel logs full of I/O retry messages), point at a failing disk. Spotlight can’t keep an index healthy on a disk that’s losing blocks.

Disk Utility → First Aid. If it reports errors, you have an answer. SMART status check via Disk Utility → View → Show All Devices → click physical drive.

Specific to corespotlightd

corespotlightd handles app-supplied data (Notes, Messages, Mail, Calendar, Reminders). To fully reset:

sudo rm -rf ~/Library/Caches/com.apple.helpd
sudo rm -rf ~/Library/Application\ Support/com.apple.spotlight.Shortcuts
sudo killall corespotlightd

After kill, the daemon takes 10–30 minutes to rebuild from app data sources.

When the answer is “wait it out”

Spotlight indexing is genuinely slow for a fresh rebuild. On a 256 GB SSD with average data, expect 1–2 hours. On a 2 TB drive with millions of files, expect 6–12 hours. Don’t keep restarting the rebuild; let it finish.

Prevent Spotlight from breaking again

  • Don’t yank external drives mid-indexing — common cause of corrupt indexes.
  • Keep at least 15% free disk space — full disks slow indexing dramatically.
  • Don’t store millions of tiny files in a single folder; some patterns of file structure stress mds_stores.
  • After macOS major upgrades, give Spotlight a full afternoon to finish indexing before assuming it’s broken.

Spotlight is one of macOS’s quietly hardest-working services. When it breaks, the recovery isn’t quick — full rebuilds take hours — but the procedures are reliable. Identify which layer broke, apply the right rebuild, and search comes back.

← Back to all guides