What is corespotlightd on a Mac?

27 October 2026 · 5 min read

corespotlightd is a macOS process that collects searchable content from your apps, such as Mail, Messages and Notes, and hands it to Spotlight so you can find it with a search. It is part of macOS and safe to leave alone. It gets busy after a restore, a macOS update, a large mailbox sync or a new account, and it settles by itself once that backlog is indexed.

This post explains what it does, how it differs from the other Spotlight processes, what makes it work hard, and what to do if it does not stop.

What corespotlightd does

Spotlight has two jobs. One is finding files: documents, folders, photos and so on. The other is finding things that live inside apps and are not files you can see in Finder: an email, a message, a note, a contact or an item in an app that supports it. corespotlightd handles the second job. Apps tell it what they hold, and it keeps an index so a search can find those things in a moment.

Foreman, which has a plain-English name for about 120 macOS processes, calls it “Spotlight app data” and describes it as “Indexes content from apps (mail, messages, notes) for Spotlight.”

It is not the same as the processes that index files. Those are mds, mds_stores and mdworker, which what is mds_stores on a Mac and what is mdworker_shared on a Mac cover. The names look alike and often appear together in a process list, so a busy Spotlight can involve several of them at the same time. Telling them apart is the first step: if corespotlightd is the busy one, the work is about app content, not files.

Why corespotlightd gets busy

An index has to be built before it is useful, so the busy periods come from a large amount of new content arriving at once.

After you set up or restore a Mac. If you signed in to iCloud, restored from a backup or moved your data from another Mac, every app has a pile of content for corespotlightd to take in.
After a macOS update. Some updates rebuild or change the index, and the Mac does that work in the hours or days afterwards. Why is my Mac slow after a macOS update covers the rest of what happens then.
After adding a large mail account. A mailbox with many years of messages takes time to download and index.
After an app syncs a lot at once, for example Notes or Messages catching up after being offline.

In each case the work ends when the backlog is cleared. A Mac that is plugged in and left alone finishes sooner than one that is busy with something else, because macOS runs indexing as low-priority background work.

What to do about it

Mostly, nothing. Leaving the Mac awake and on power for a few hours overnight is the best thing you can do, and it is the best thing to try first.

If it is still busy after a day or two, work through this list.

Check whether the app behind it is the cause. If it began when you opened a huge mailbox, the mail app may still be downloading. Let it finish.
Restart the Mac. A restart clears any indexing job that got stuck.
Update macOS. A stuck index is sometimes a bug that a later update has fixed. Open System Settings, then General, then Software Update.
If it is still stuck, rebuilding Spotlight’s index is the last resort. It is a bigger step, because search is incomplete until it finishes and the Mac is busy for hours again, so read the mds_stores post on when it is worth it before you try it.

Do not delete files from the Library folder to stop it. It is tempting to follow an old forum thread that tells you to, but there is no need and it can cause more problems than it solves.

Can you end corespotlightd

You can, and macOS will start it again. It is part of macOS but runs under your own account, so ending it needs no administrator password. It also does nothing lasting: it comes back because the system relies on it, and it picks up the same work. At best you buy a moment of quiet.

If you want to see it before deciding, Foreman’s Processes page lists it under Background processes as “Spotlight app data”, and a click on CPU sorts the busiest to the top. Foreman also gathers copies of one background program into a single row with a count, for example “Spotlight file reader (4)”, which makes the Spotlight family easier to read.

Because it runs under your account, Foreman also offers Efficiency Mode for it, which is a gentler choice than ending it when indexing gets in the way of something you are doing. While it is on, the process runs at background priority and is held to about a quarter of the processor time it would take. The indexing still finishes, only later, and how much the rest of the Mac gains depends on how busy it is. Turn it off again from the toolbar or the right-click menu once you are done, so the backlog can clear.

For a quick look without Foreman, Terminal can show it:

top -o cpu

Look for corespotlightd in the list, and press q to leave. This only reads; it changes nothing. top counts each processor core as 100 percent, so its figures can run well above what a list showing a share of the whole Mac would show.

What it does not do

It is easy to read too much into this process, so here is what corespotlightd is not.

It is not malware. The name is long and unfamiliar, but it is an Apple process, and it lives in the system’s own folders.
It is not slowing your Mac permanently. It works in bursts and then stops.
It is not a sign that your mail is being sent anywhere. Its job is to build an index for search on your Mac.

If the Mac is hot and loud while it works, that is the cost of indexing, and it passes. If it does not pass after a few days, the steps above are the way to deal with it, and what to do when your Mac fans get loud is the next place to look.

The short version

corespotlightd feeds app content into Spotlight. It works hard after restores, updates and big syncs, then stops. Leave the Mac on power for a few hours first, then restart, update and trim Spotlight’s categories if it lingers. Foreman puts a plain name on it in your process list if you want to see it at work.