Spotlight problems

Indexing that never completes

Updated 2026-07-31 · 4 min read

A progress bar that never fills usually means indexing is failing on one file and restarting.

Confirm it is actually stuck

Some rebuilds legitimately take many hours. Check whether work is happening:

mdutil -s /
sudo fs_usage -w -f filesys mdworker 2>/dev/null | head

If fs_usage shows mdworker cycling the same file or path repeatedly, it is stuck on that item, not progressing.

Identify the poison file

The repeated path in fs_usage is the culprit — often a corrupt PDF, a broken package, or a file on a flaky drive. Excluding it lets indexing finish:

Add its folder to Spotlight Privacy, or move the file out, then let indexing complete, then investigate the file separately.

The clean rebuild sequence

sudo mdutil -i off /        # stop
sudo mdutil -E /            # erase the index
sudo mdutil -i on /         # restart fresh

Erasing removes a corrupted store that a plain restart would keep tripping over.

The heavier reset

If rebuilds keep failing, delete the index store directly and let macOS recreate it:

sudo mdutil -i off /
sudo rm -rf /.Spotlight-V100
sudo mdutil -i on /

(The store is hidden at the volume root. This forces a completely fresh index.)

Underlying causes

• A failing drive — check Disk Utility First Aid
• A sync client rewriting files faster than they index — exclude its folder
• Low disk space — indexing needs room to write; free some first
• A specific corrupt file — the fs_usage method finds it

Most "stuck forever" cases are one bad file or a churning folder, not a broken Spotlight — which is why targeted exclusion beats endless rebuilding.

Common questions

Why is Spotlight indexing stuck at the same point?

Usually one corrupt or constantly-changing file. fs_usage on mdworker reveals the repeated path; exclude it and indexing finishes.

How do I completely reset the Spotlight index?

Stop indexing, delete /.Spotlight-V100 at the volume root, and re-enable — macOS builds a fresh store.