How to Fix Spotlight Stuck at Indexing on macOS

Spotlight is supposed to be your Mac’s lightning-fast librarian. But when it gets stuck on
“Indexing…”, it turns into that one coworker who keeps “organizing” the supply closet for three days straight.
The good news: this problem is usually fixable without sacrificing your weekend (or your sanity).

In this guide, you’ll learn how to tell whether Spotlight is truly stuck, how to rebuild the index the safe Apple-approved way,
when Terminal commands make sense, and what to do if an external drive or a specific folder is the real villain.

What “Indexing” Actually Means (and When It’s Normal)

Spotlight works by building a searchable database (an “index”) of your files, apps, emails, messages, and more.
Indexing is normal after:

• A macOS update or upgrade
• Setting up a new Mac or migrating data
• Connecting a large external drive for the first time
• Adding or changing lots of files (Photos libraries, dev folders, cloud sync folders, etc.)

Depending on how much stuff you have, indexing can take minutes or hours. Sometimes it can take longer,
especially if your Mac is on battery power, low on free storage, or juggling a giant drive full of tiny files.

Step 1: Confirm Spotlight Is Truly Stuck (Not Just Busy)

Check Activity Monitor for Spotlight Processes

Open Activity Monitor (Applications > Utilities), click the CPU tab,
and look for these processes:

• mds (metadata server)
• mds_stores
• mdworker / mdworker_shared
• mdimport

If these processes are actively using CPU and the system is responsive, Spotlight may still be working.
If they’re stuck at near-zero activity for a long time while Spotlight still claims it’s indexing, that’s a clue something’s off.

Run a Quick Status Check in Terminal (Optional, but Useful)

If you’re comfortable using Terminal, you can check indexing status on your startup disk:

You’ll see whether indexing is enabled and whether Spotlight thinks it’s doing something. If you don’t love Terminal, no worrieskeep going.

Step 2: Do the Fast, Low-Risk Fixes First

Before we rebuild anything, try the “classic” troubleshooting trio. Yes, it’s cliché. It’s also cliché because it works.

1) Restart Your Mac

A restart clears temporary states that can stall indexing. After rebooting, give Spotlight 10–15 minutes and see if the progress changes.

2) Plug In Power (and Don’t Let the Mac Sleep)

Indexing is a background job, and macOS may slow it down on battery. Plug in your Mac and keep it awake for a while
(especially if you’re indexing a big drive).

3) Disconnect External Drives and Network Volumes (Temporarily)

External drivesespecially Time Machine drives, NAS shares, or drives with lots of mediacan cause indexing to crawl or loop.
Unplug everything except your power cable and see if indexing completes.

Step 3: Rebuild Spotlight the Safe, Apple-Approved Way

This is the best fix for most people because it’s built into macOS and doesn’t require command-line wizardry.
The trick is to briefly exclude the drive from Spotlight, then remove the exclusion. That forces a rebuild.

For macOS Ventura and Later (System Settings)

1. Open System Settings
2. Click Spotlight
3. Scroll to Search Privacy (or “Privacy” / “Search Privacy” depending on macOS version)
4. Click the + button and add your startup disk (often “Macintosh HD”)
5. Wait about 30–60 seconds
6. Select the disk you added, then click the – button to remove it
7. Close System Settings and give Spotlight time to reindex

For Older macOS Versions (System Preferences)

1. Open System Preferences
2. Go to Spotlight > Privacy
3. Add your startup disk to the list
4. Wait briefly, then remove it

Important: if you add your startup disk and forget to remove it, Spotlight will behave like it’s on strike foreverbecause you told it not to search your disk.
So add, pause, remove. That’s the whole dance.

Step 4: Fix the Most Common “Indexing Traps”

Sometimes Spotlight isn’t brokenit’s just trapped in an all-you-can-eat buffet of constantly changing files.
Here are the usual suspects:

Cloud Sync Folders (Dropbox, OneDrive, Google Drive)

These folders change constantly, which can keep indexing busy. If you have massive synced folders, consider excluding
the heaviest subfolders from Spotlight (especially archives).

Developer Folders with Tons of Small Files

If you code, Spotlight may be chewing through:
node_modules, build output folders, package caches, and dependency directories.
Excluding those can dramatically reduce indexing churn without hurting your everyday search.

Virtual Machines and Disk Images

VM bundles and mounted images can generate huge indexing workloads. Consider excluding VM directories and large, frequently mounted images.

External Drives That “Re-Enable” Indexing After Updates

After some macOS updates, indexing settings for external volumes can change, and drives you previously excluded may start indexing again.
If Spotlight suddenly got busy after an update, check Search Privacy and re-exclude drives you don’t want indexed
(like media archives or backup clones).

Step 5: Use Terminal to Force a Rebuild (When Settings Isn’t Enough)

If the privacy toggle method doesn’t work, Terminal can force Spotlight to erase and rebuild the index.
This is safe when typed correctlybut like cooking with a flamethrower, it rewards careful attention.

Option A: Erase and Rebuild the Index for the Startup Disk

You’ll be prompted for your Mac password. When you type it, the cursor won’t movethis is normal.
Press Return when done.

Option B: Turn Indexing Off and Back On (Sometimes Unsticks a Stalled State)

Option C: Target a Specific External Drive

If the problem is clearly tied to one external volume, rebuild just that volume’s index.
Replace DriveName with the exact volume name you see in Finder:

Option D: Rebuild Indexes for All Volumes (Use With Care)

This can be overkill if you have lots of drives mounted, but it can help if Spotlight is confused across multiple volumes.

Tip: If you keep backup drives or massive media drives connected, rebuilding “all volumes” can take a very long time.
Consider unplugging nonessential drives before you run global rebuild commands.

Step 6: Repair the Underlying Problem (So It Doesn’t Come Back)

Make Sure You Have Enough Free Storage

Spotlight needs room to build and maintain its index. If your disk is nearly full, indexing may stall or behave erratically.
A simple goal: try to keep at least 10–20% of your startup disk free.

Run Disk Utility First Aid

File system hiccups can cause indexing to loop. Run:

1. Open Disk Utility
2. Select your startup disk
3. Click First Aid

If First Aid reports errors it can’t repair, back up your data and consider getting helpSpotlight is often the messenger, not the villain.

Check for a “Problem Folder” and Exclude It

If indexing always gets stuck around the same time, a particular folder might be causing repeated failures.
Common examples include corrupted archives, massive caches, or directories that constantly rewrite themselves.

Try excluding likely culprits (big caches, VM folders, dev dependencies) and see if indexing finally completes.
You can always remove the exclusion later after you narrow it down.

Step 7: Try Safe Mode (Surprisingly Helpful)

Safe Mode can clear certain caches, limit third-party interference, and sometimes helps Spotlight “get its act together.”

Apple Silicon (M-series)

1. Shut down your Mac
2. Press and hold the power button until you see startup options
3. Select your startup disk, hold Shift, then click Continue in Safe Mode

Intel Macs

1. Restart your Mac
2. Immediately hold Shift until you see the login screen

Once you boot in Safe Mode, log in, wait a few minutes, then restart normally. Check Spotlight again.

Step 8: Create a Test User Account (Quick “Is It My Profile?” Check)

Sometimes Spotlight issues are user-specific (settings, caches, or app data in one account).
Create a temporary test user:

1. System Settings > Users & Groups
2. Add a new user (Standard is fine)
3. Log into that account and test Spotlight

If Spotlight behaves normally in the new user, your main account likely has a corrupt cache or a problematic folder.
Rebuilding the index (privacy method) in your main account often resolves it.

When to Stop Troubleshooting and Get Help

If you’ve rebuilt the index, checked storage, run First Aid, and Spotlight still “indexes forever,” it’s time to consider bigger causes:

• Repeated disk errors or SMART warnings
• System instability (crashes, freezes, unexpected restarts)
• Indexing that never completes after 24–48 hours on a reasonably sized disk
• Spotlight failing immediately after every rebuild

At that point, your best move is to back up your data and contact Apple Support or an Apple Authorized Service Provider.
Spotlight is rarely the root cause when the disk itself is having a bad day.

A Practical “Do This in Order” Checklist

1. Restart your Mac
2. Plug into power and keep the Mac awake
3. Unplug external drives and network volumes
4. Use Search Privacy to force a rebuild (add disk, remove disk)
5. Exclude obvious churn folders (cloud sync, VM bundles, dev dependencies)
6. Run Disk Utility > First Aid
7. Use Terminal: sudo mdutil -E /
8. Try Safe Mode, then reboot normally
9. Test with a new user account

From the Trenches: What Fixing Spotlight Really Feels Like (Real-World Experiences)

If you’ve ever watched Spotlight indexing like it’s trying to read the entire Library of Congress through a keyhole, you know the vibe:
fans spinning, the Mac running warm, and Spotlight acting like it has exactly one job and it’s determined to do it forever.
In real life, the “fix” usually isn’t one magical buttonit’s finding what Spotlight is obsessing over and removing the obstacle.

A super common scenario happens right after a macOS update. You install the update, everything looks fine, and then Spotlight starts indexing.
At first you think, “Sure, normal.” Hours later, it’s still at it, your searches are incomplete, and your Mac is suddenly auditioning to be a space heater.
In these cases, the Apple-approved rebuild trick (adding and removing your disk from Search Privacy) often feels like telling Spotlight,
“Hey buddy… start over, but this time, try not to get lost in the parking lot.”
It’s simple, it’s safe, and it works more often than you’d expect.

Another frequent story involves external drives. Someone plugs in a giant photo archive or a media drive with years of videos and a million tiny files.
Spotlight sees it and thinks, “Ah yes, delicious. A lifetime of content to index.” The Mac slows down, indexing seems endless, and Spotlight search results get weird.
The moment you unplug the external drive, indexing suddenly “improves,” which is basically the Mac’s way of whispering,
“I can’t focus while that hard drive is screaming at me.”
The practical move is either to exclude that drive from Spotlight (if you never search it) or to rebuild that drive’s index specifically.

Then there’s the developer-life version of this problem. You install a tool, clone a few repos, and now your drive contains
a glorious mountain of dependenciesespecially in folders like node_modules.
Spotlight tries to index the entire pile, and your Mac becomes a tiny furnace of good intentions.
Excluding those high-churn folders can feel oddly satisfying, like finally deciding you don’t need to alphabetize your junk drawer.
Your searches remain great for everyday stuff (apps, documents, messages), but Spotlight stops wasting time on constantly changing build artifacts.

Sometimes the “experience” is less dramatic and more confusing: Spotlight says it’s indexing, but CPU usage is low,
searches don’t improve, and it feels like nothing is happening. That’s when Terminal commands like sudo mdutil -E /
become the grown-up version of “turn it off and on again.” It’s not flashy, but it’s effectiveespecially when the index is corrupted.
The key is restraint: you don’t need to nuke everything on every drive unless you’re sure the problem is global.
Target the startup disk first, then any specific trouble volumes.

And yes, there’s always that moment where you wonder if Spotlight is personally mad at you. It’s not.
It’s usually dealing with a huge workload, a problematic volume, low storage, or a file system hiccup.
Once you treat the underlying causefree up space, run First Aid, exclude the chaos folders, rebuild the indexSpotlight typically snaps back into shape.
The best part is the “after” feeling: searches become instant again, Finder stops feeling sluggish, and your Mac finally stops sounding like it’s about to lift off.
It’s the quiet victory of modern troubleshooting: you didn’t defeat a monster, but you did convince your computer to behave like it remembers how.

Conclusion

When Spotlight gets stuck indexing, the smartest approach is to start simple and work up: restart, unplug external drives,
use the Search Privacy rebuild trick, and only then move to Terminal commands like sudo mdutil -E /.
In most cases, Spotlight isn’t “broken”it’s overwhelmed, confused by a problematic volume, or struggling with a disk issue.
Once you rebuild the index and remove the usual traps (giant externals, churn-heavy folders, low storage), Spotlight generally returns to doing what it does best:
finding your stuff fast, quietly, and without drama.