How to Rebuild the Spotlight Index on macOS in 2026 to Fix Search & Free Space

If Spotlight returns blank results, surfaces outdated files, or your Mac's storage graph shows an unexpectedly large "System Data" slice, it may be time to rebuild the Spotlight index on your Mac. The index is a hidden database that macOS uses to answer every search query in milliseconds — and like any database, it can grow stale, bloated, or corrupted over time. This guide walks through every method available in 2026 (macOS Sequoia and the upcoming Tahoe release) on both Apple Silicon and Intel machines, explains what the index actually contains, and shows you how to reclaim the disk space it wastes.

What Is the Spotlight Index and Where Does It Live?

Spotlight's index is stored in a hidden bundle called .Spotlight-V100 at the root of each mounted volume. On your startup disk that path is:

• /.Spotlight-V100 — primary index for the boot volume
• /Volumes/YourExternalDrive/.Spotlight-V100 — per-volume index on external drives

Inside that bundle macOS maintains several sub-databases: a content store (Store-V2), an inode map, and a journal. On a busy developer machine with millions of files in ~/Library/Developer/Xcode/DerivedData, ~/.m2/repository, or node_modules trees, these databases can balloon to several gigabytes.

A secondary metadata cache lives at /private/var/folders/ in per-user temporary directories, and Spotlight's daemon logs land in /private/var/log/DiagnosticMessages/. Neither of those need to be touched manually — they are rebuilt automatically.

Signs Your Spotlight Index Needs Rebuilding

• Spotlight returns "No Results" for files you can see in Finder.
• Search results include files you deleted weeks ago.
• The mds or mds_stores process pegs a CPU core for hours.
• Your storage bar shows System Data growing without a clear cause.
• After a major macOS upgrade, search feels noticeably slower than before.
• QuickLook previews fail for file types that worked previously.

How to Rebuild the Spotlight Index on Mac (Step-by-Step)

There are three methods. Start with Method 1 — it is safe, reversible, and handles the vast majority of cases.

Method 1: System Settings Privacy Panel (recommended)

1. Open System Settings (the gear icon in the Dock or Apple menu).
2. Click Siri & Spotlight in the sidebar.
3. Scroll down and click Spotlight Privacy…
4. Drag your startup disk (usually named "Macintosh HD") from Finder into the Privacy list. Spotlight immediately stops indexing that volume and discards its index database.
5. Wait about 5 seconds, then select the disk you just added and click the minus (−) button to remove it from the exclusion list.
6. macOS now queues a full re-index. Click Done.

Re-indexing typically takes 10–45 minutes depending on drive speed and file count. Your Mac remains fully usable throughout. You can track progress by opening Spotlight (⌘Space) — a progress bar appears beneath the search field while indexing is active.

Method 2: Terminal — mdutil command

For scripted workflows or when System Settings is inaccessible, use the mdutil command-line tool:

1. Open Terminal (in /Applications/Utilities/).
2. Disable indexing on the startup volume to force a clean wipe:
   sudo mdutil -i off /
3. Delete the existing index:
   sudo mdutil -E /
4. Re-enable indexing:
   sudo mdutil -i on /
5. Verify the new index is building:
   mdutil -s /
   You should see output like Indexing enabled. (...Indexing).

If you want to rebuild the index on an external drive instead of the boot volume, substitute / with the volume mount point, for example /Volumes/BackupSSD.

Method 3: Exclude Noise Directories First, Then Rebuild

If your index keeps bloating because of build artifacts, add exclusions before triggering a rebuild. Common culprits on developer machines:

• ~/Library/Developer/Xcode/DerivedData — Xcode intermediates; can exceed 50 GB.
• ~/.m2/repository — Maven/Java dependency cache.
• ~/.cargo — Rust crate registry and build artifacts.
• node_modules directories scattered across projects.
• ~/Library/Caches — application caches that Spotlight has no reason to index.

Add these via the Privacy panel (Method 1 step 3–5 above, dragging folders instead of the whole disk), then use sudo mdutil -E / to wipe and restart the index lean. You can also learn more about why System Data grows so large on macOS — Spotlight databases are one of several contributors.

How Much Space Does the Spotlight Index Use?

The size of /.Spotlight-V100 varies significantly by machine role. The table below shows typical ranges measured on real Apple Silicon and Intel machines running macOS Sequoia in mid-2026:

If your index sits at the high end of these ranges, it is worth excluding noisy directories before the next rebuild. On developer machines this alone can trim several gigabytes from System Data.

How Long Does Rebuilding Take and Will It Slow My Mac?

macOS throttles the mds_stores process aggressively when the machine is on battery or under load, so you may not notice any slowdown during normal work. On AC power the indexer runs harder and finishes faster. A cold index on a 1 TB SSD full of media typically completes in under 30 minutes on an M-series chip. Intel machines with spinning hard drives may take several hours.

During indexing, Spotlight search still works but returns partial or cached results. You can force-check progress at any time with:

mdutil -s /

Once it returns Indexing enabled. without a progress note, the index is complete.

Spotlight, QuickLook, and Font Caches — Related Caches Worth Clearing

Spotlight is part of a family of macOS caches that occasionally need resetting together. If QuickLook thumbnails are wrong after a Spotlight rebuild, clear the QuickLook cache as well:

qlmanage -r cache

Font caches live at /Library/Caches/com.apple.FontRegistry and ~/Library/Caches/com.apple.FontRegistry. A corrupted font cache can prevent Spotlight from indexing PDF and document metadata correctly. Reset it with:

sudo atsutil databases -remove

Then restart your Mac to let macOS rebuild both the font registry and any Spotlight metadata that depended on it. For a broader look at what accumulates in ~/Library/Caches and which folders are safe to clear, see our guide on clearing system cache on Mac.

Keeping the Spotlight Index Lean Over Time

A one-time rebuild helps, but the index will bloat again if root causes are not addressed. A few habits that keep it manageable:

• Add build artifact directories to the Privacy exclusion list — DerivedData, .gradle, target/ (Rust/Java), and node_modules have no useful metadata for search and can each hold millions of small files.
• Delete unused Xcode simulators and archives — these live at ~/Library/Developer/Xcode/Archives and ~/Library/Developer/CoreSimulator/Devices and are indexed by default.
• Unmount external drives when not in use — each mounted volume gets its own index; drives you rarely search do not need one.
• Run a storage audit periodically — a tool like Crumb can audit all of these cache and build artifact locations at once and show what is safe to remove before you delete anything.

Troubleshooting: Spotlight Keeps Crashing or Won't Finish Indexing

If mds crashes in a loop or indexing never completes, try these steps in order:

1. Boot into Safe Mode (hold Shift on Intel; hold Power button until options appear on Apple Silicon, then Shift-click Continue). Safe Mode rebuilds several system caches and disables third-party kernel extensions that can interfere with mds.
2. Check for a corrupted .Spotlight-V100 bundle: sudo ls -la /.Spotlight-V100/Store-V2/. If the directory is empty or shows errors, re-run sudo mdutil -E / after the Safe Mode boot.
3. Reset the mds daemon directly: sudo launchctl stop com.apple.metadata.mds followed by sudo launchctl start com.apple.metadata.mds.
4. If the problem persists after all of the above, run First Aid on the disk in Disk Utility — a filesystem error is occasionally the real culprit behind an index that will not build.