SiftMac
What is this process? · Updated 22 November 2026

What is corespotlightd, and why is it using so much memory?

By Mohit Nippanikar, who makes SiftMac

The short answer
On this page
  1. What corespotlightd is
  2. Why it’s busy
  3. What to do about it
  4. Should you quit or disable it?
  5. Questions

1. What corespotlightd is

The process is /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework/Versions/A/Support/corespotlightd, in the same folder as the rest of Spotlight. launchd runs it for your account from /System/Library/LaunchAgents/com.apple.corespotlightd.plist. A related managedcorespotlightd sits beside it.

It serves Core Spotlight, the framework Apple gives developers to make their content searchable. Apple’s developer documentation describes the deal: an app decides what’s worth finding, such as photos, contacts, purchases or anything else someone might look for, and adds details about each item to a Core Spotlight index. The app is responsible for adding and maintaining its entries, either while it runs or through an extension when the system asks.

Apple says these indexes stay on the device, private to its owner, and aren’t shared with Apple or synced to your other devices. On the Mac this page was written on, the apps with entries included Mail, Notes, Reminders, Safari, System Settings, the App Store and iCloud Drive.

2. Why it’s busy

Apple says the Spotlight index updates when you install new apps that allow their content to be indexed, and as new email or messages arrive. So corespotlightd works hardest when apps have a lot to add:

Memory is where it shows up most. In Activity Monitor’s Memory tab, a corespotlightd that grows during a big indexing job is expected; one that stays large for days with nothing new arriving is worth a restart.

3. What to do about it

  1. Give a backlog time, plugged in and online: Apple says indexing finishes faster that way, in case mail or other data has to download first.
  2. Look for the app behind it. If it got busy right after you installed or updated something, or opened an app with lots of data, update that app or check its settings for search or Spotlight options.
  3. Restart it if memory stays high. Select corespotlightd in Activity Monitor, click the Stop button and choose Quit. launchd starts a fresh copy.
  4. Check Spotlight settings. System Settings › Spotlight (Siri & Spotlight on older versions) lists the kinds of results Spotlight shows. Apple suggests reviewing them if searches aren’t finding something.

To see how much space the app index takes:

du -sh ~/Library/Metadata/CoreSpotlight 2>/dev/null

It grows with what your apps hold, so a Mac with a big mail archive and lots of notes has a bigger one. sudo mdutil -E / rebuilds the disk’s file index in .Spotlight-V100; Apple doesn’t document a separate rebuild for this one.

4. Should you quit or disable it?

Quitting it is safe and sometimes useful, as above: it comes straight back, with a fresh memory footprint, and apps keep their entries. It lives on macOS’s sealed system volume, so there’s no switch to remove it, and turning off System Integrity Protection to try would be the wrong fix.

Don’t delete ~/Library/Metadata/CoreSpotlight by hand. Apps maintain their own entries in it, and Apple doesn’t document clearing it. If one app’s content is the problem, updating or removing that app is the clean way to change what’s in the index.

Without corespotlightd, Spotlight would still find files, but not the mail, notes, reminders and other app content people search for every day.

Questions

What’s the difference between corespotlightd and mds_stores?

mds_stores keeps the index of files on each disk. corespotlightd keeps the index of items apps hand to Spotlight through Core Spotlight, stored in ~/Library/Metadata/CoreSpotlight.

Is it safe to quit corespotlightd?

Yes. launchd starts it again straight away. Quitting it is a reasonable way to bring down its memory if it has stayed high long after indexing should have finished.

Does corespotlightd send my data to Apple?

Apple says Core Spotlight indexes stay on the device, private to its owner, and aren’t shared with Apple or synced between devices.

Why does corespotlightd use memory when I’m not searching?

Indexing happens in the background as apps add and update items, not only when you search.

How SiftMac handles it. SiftMac doesn’t list or clear anything in ~/Library/Metadata/CoreSpotlight; that index belongs to macOS and your apps. Its own plain-words search uses Spotlight’s file index, not this one.

Download SiftMac · scanning is free, and so is your first 2 GB of cleaning · See how it works