corespotlightd on Mac: what it is, why it is high, what to do

What corespotlightd does

Spotlight has two indexes. One covers files on disk: names, contents of documents, metadata like dates and tags. That is built by mds, mds_stores and mdworker. The other covers things that are not files at all: individual emails in Mail, a note in Notes, a text in Messages, a page you visited in Safari, a contact, a calendar event, items a third-party app chooses to expose. That second index is Core Spotlight, and corespotlightd is the daemon that builds and maintains it.

Apps feed it. When Mail downloads a thousand messages, it hands each one to corespotlightd to index. When Notes syncs from iCloud, same thing. When a document app saves a new version of a file, it can ask for that version to be re-indexed. The index lives in ~/Library/Metadata/CoreSpotlight and normally stays small, a few hundred MB to a few GB depending on how much mail you keep.

So if it is busy, something upstream is sending it work. The question is always: which app, and why is it sending so much?

Why corespotlightd is using CPU right now

In rough order of how often each one is the answer:

1. You just updated macOS. Major updates change the index format, so Core Spotlight rebuilds from scratch. On a Mac with years of mail this takes an hour or more, mostly while you are not using it.
2. You signed in to a new or wiped Mac. Mail, Notes, Messages and Photos all download and index at once. Expect a busy first day.
3. An app imported a lot. A new mailbox with 50,000 messages, a large Notes import, Messages in iCloud turned on for the first time.
4. The Pages-on-iCloud loop. This is the one behind the long Apple Community thread. Starting with macOS Sequoia 15.2, people found corespotlightd running at 100 to 400 percent for weeks. The trigger many of them narrowed down: Pages, Numbers or Keynote files stored in iCloud Drive. Each autosave creates a new revision, each revision gets re-indexed, and the index folder balloons. One user in that thread wrote: "Even deleting the metadata folder every day, it quickly grows to over 50GB." Glenn Fleishman at Six Colors confirmed the workaround: "Moving the file to a local directory (in my Documents folder) while editing eliminated the problem."
5. A damaged index. After a crash or a full disk, the index can be corrupt and the daemon keeps retrying. Less common than people assume.
6. An external or network drive. Plugging in a drive full of documents gives both Spotlight indexers a new pile of work.

The first three settle on their own. The fourth does not, and it is the reason this process has its own 500-reply thread.

What normal looks like, and what is not

The difference between a healthy index build and the bug is not the peak CPU. It is how long the peak lasts and whether it comes back.

The healthy pattern: a big number that shrinks over an hour and stays small. The bug pattern: a big number that comes back every time you open a document, with the fan on and the Mac beachballing in ordinary apps. As one M2 Ultra owner put it, "the corespotlightd process often occupies more than 100% of the CPU load, sometimes spiking as high as 400%."

A second check: the size of ~/Library/Metadata/CoreSpotlight. Press ⇧⌘G in Finder, paste that path, and Get Info on the folder. A few GB is normal. Tens of GB, growing daily, is the loop.

Is it safe to quit corespotlightd?

Quitting it does no harm: launchd restarts it within a second and it resumes the index from where it stopped. It also does no good, because the work is still queued. People who force quit it every morning are not fixing anything.

What you should never do is delete system folders or turn Spotlight off with Terminal commands you found in a thread. Those advice posts tend to end with search broken across the whole Mac. The decision tree below covers the general case for any process.

For corespotlightd the answer is almost always the same: let it settle, and if it will not, remove what is feeding it rather than fighting the daemon.

What to do, in order

1. Give it time, plugged in

   If you updated macOS or signed in today, wait. Leave the Mac on power with the lid open for an hour or overnight. Spotlight work runs faster when the Mac is idle and on mains power.

2. Check for the Pages-on-iCloud trigger

   Do you keep Pages, Numbers or Keynote documents in iCloud Drive, especially ones you edit often? Move the ones you are working on to a local folder (Documents on this Mac, not the iCloud version) and watch Activity Monitor for ten minutes. For many people in the Apple thread this was the whole fix.

3. Exclude the folder from Spotlight

   If you need those files in iCloud, open System Settings, Spotlight (or Siri & Spotlight on older versions), scroll to Search Privacy, and add the folder that holds them. Spotlight stops indexing it and corespotlightd calms down. You lose search inside those documents, nothing else.

4. Find the app that is feeding it

   In Activity Monitor, look for an app that is also busy at the same time: Mail syncing a huge mailbox, Notes, a document app. Pausing that app's sync (for Mail, take the account offline for an hour) lets the indexer catch up.

5. Restart

   A restart clears a daemon stuck on a bad item. If CPU drops and stays down, you are done.

6. Update macOS

   Apple has shipped fixes for pieces of this problem across the 15.x and 26.x updates. System Settings, General, Software Update. If you are on an older point release, this is the cheapest thing to try.

7. Rebuild the index, last resort

   In Spotlight's Search Privacy list, add your whole startup disk, wait a minute, then remove it. Spotlight rebuilds the file index from scratch, which takes an hour or more and makes search incomplete until it finishes. Do this only when the steps above have failed, and never while on battery.

When to worry

corespotlightd is never a security problem. It cannot be quit permanently, it does not phone home, and it does not damage data. The things worth acting on are side effects:

• Disk space. An index folder that grows by tens of GB per week will fill a 256 GB drive. One user measured it: "corespotlightd was creating 30 Gb of data per week!" Check the folder size if free space is falling for no reason.
• SSD writes. The same growth means constant writing. Not dangerous in itself, but a sign the loop is running.
• Heat and battery. A laptop at 300 percent CPU all day gets hot, runs kernel_task up, and loses hours of battery life. That is the real cost.
• It survived every step above. Then it is a bug in your macOS version, and the honest answer is the Spotlight Privacy exclusion until Apple fixes it. Safe to Quit tracks which process is hot over hours, so you can see whether the exclusion actually worked rather than checking Activity Monitor every ten minutes.