How to Fix Spotlight Search Not Working on Mac

When Spotlight Search fails on macOS—manifesting as an unresponsive Cmd + Space shortcut, a blank search window that returns zero files or applications, partial results missing documents, or a perpetual “Indexing…” progress bar that never completes—the underlying metadata search daemon has encountered a corruption lock. Because Spotlight powers not only the system search bar but also Finder searches, Mail queries, and Siri suggestions, an inoperable Spotlight index cripples everyday productivity. The breakdown typically stems from corrupted CoreServices metadata stores (.Spotlight-V100), crashed mds background daemons, or invalid Spotlight privacy exclusions. Resolving this issue involves rebuilding the index database and restarting metadata processes.

How the macOS Spotlight Indexing Architecture Operates

Spotlight relies on two core background system daemons managed by launchd: mds (Metadata Server) and mdworker (Metadata Server Worker). The mds daemon maintains a continuous, low-level inverted index database stored in the hidden directory /.Spotlight-V100 on each mounted APFS or HFS+ storage volume. Whenever files are saved, modified, or downloaded, mdworker threads extract document text, EXIF photo metadata, and file attributes. If an interrupted system shutdown or storage shortage corrupts the index database header, mds drops file indexing and search queries return blank results.

Common technical reasons Spotlight stops working include:

• Corrupted .Spotlight-V100 Index Database: Malformed metadata binary records preventing search queries from traversing storage volumes. For hardware stalls, see our guide on fixing Wi-Fi No Hardware Installed on Mac.
• Stalled mds and mdworker Processes: High CPU loops or memory leaks in metadata workers attempting to parse damaged PDF or image files. For biometric glitches, see our guide on fixing Touch ID not working on Mac.
• Drive Excluded in Spotlight Privacy Settings: Accidental addition of the main Macintosh HD volume to the Spotlight exclusion list. For restart issues, check our guide on fixing Your Computer Restarted Because of a Problem on Mac.
• Low Available Disk Space: APFS storage volumes with less than 10% free space disabling background indexing daemons to conserve drive health.

System Daemon / Path	Operational Function	Diagnostic Command	Healthy Status
mds	Master metadata management server	sudo mdutil -s /	Indexing enabled.
mdworker_shared	Worker process extracting file metadata	top -l 1 | grep mdworker	Normal CPU usage (< 20% when idle)
/.Spotlight-V100	Hidden local volume search database	ls -ld /.Spotlight-V100	Valid root-owned index directory

Method 1: Force Re-index via System Settings Privacy List

The standard, graphical method to force macOS to delete and reconstruct its search index is adding and then removing the primary hard drive from Spotlight’s privacy exclusion list.

1. Click the Apple menu () > System Settings (or System Preferences on older macOS versions).
2. In the left sidebar, click Siri & Spotlight.
3. Scroll down to the bottom of the window and click the button labelled Spotlight Privacy…
4. Open a Finder window, click Macintosh HD (or drag your primary startup drive icon from the desktop), and drop it into the Spotlight Privacy window.
5. Confirm the prompt stating that searching this location will be prevented.
6. Wait 30 seconds. Next, select the drive you just added and click the minus (-) button at the bottom of the list to remove it.
7. Click Done. Removing the drive forces macOS to automatically initiate a full, clean re-indexing pass across the entire disk.

Method 2: Rebuild the Spotlight Index via Terminal (mdutil)

If the graphical privacy list method fails to trigger re-indexing, utilizing the administrative mdutil command-line utility provides direct control over the metadata daemon.

1. Open the Terminal app (press Cmd + Space, type Terminal, or navigate to Applications > Utilities > Terminal).
2. Check the current status of indexing across all mounted volumes:
   sudo mdutil -a -s
3. Turn off indexing on your primary drive:
   sudo mdutil -i off /
4. Purge the existing corrupted index database store:
   sudo mdutil -E /
5. Re-enable indexing on the root volume:
   sudo mdutil -i on /
6. You will see the confirmation message: Indexing enabled. Press Cmd + Space and type a query; a progress bar will appear indicating the estimated time remaining.

Method 3: Restart the Metadata Server Daemon (mds)

If the mds daemon is frozen in a deadlocked thread, terminating the process forces launchd to respawn the daemon immediately with a clean memory heap.

1. In the Terminal window, execute:
   sudo killall mds
2. Wait five seconds for the system manager to reload the process.
3. Verify that the daemon has respawned with a fresh Process ID (PID):
   ps aux | grep -i mds
4. Test your Spotlight search shortcut.

Method 4: Delete the Corrupted .Spotlight-V100 Index Folder Manually

In cases of severe filesystem corruption where mdutil commands return permission or filesystem errors, manually deleting the hidden database folder resolves stubborn stalls.

1. In Terminal, execute the following command to forcefully remove the hidden database directory:
   sudo rm -rf /.Spotlight-V100
2. Restart your Mac immediately:
   sudo reboot
3. Upon reboot, macOS detects the missing .Spotlight-V100 folder and automatically reconstructs the directory and begins background indexing.

Method 5: Check Keyboard Shortcut Conflicts

If pressing Cmd + Space does nothing at all (no search bar appears), another application or input source may have overridden the global shortcut.

1. Open System Settings > Keyboard.
2. Click the button labelled Keyboard Shortcuts…
3. Select Spotlight from the left list.
4. Ensure the checkbox labelled Show Spotlight search is ticked and configured to Cmd + Space.
5. Check the Input Sources category on the left to ensure the shortcut is not conflicting with “Select previous input source”.