What Is corespotlightd? Fixing High CPU on a Mac

Activity Monitor shows a process called corespotlightd using a noticeable share of CPU, or a few hundred megabytes of memory, and it is not clear what it is or why it is there.

The short answer: corespotlightd is the part of Spotlight that indexes content inside your apps, the items apps choose to make searchable rather than files on your disk. It gets busy when an app adds or updates a lot of items at once, for example right after you install it, sign in or import a large library. It is safe, it runs under your own account, and it settles when the work is done.

What corespotlightd does

Spotlight indexes two kinds of things. Files on your disk are read by the mdworker_shared workers and stored by mds_stores. Content that lives inside apps is different: apps hand it to Spotlight themselves through Apple's Core Spotlight framework. Its interface, CSSearchableIndex, has a method called indexSearchableItems that apps call to add items to the index.

corespotlightd is the background service on your account that handles that indexing. Its launch configuration registers the service com.apple.spotlight.IndexAgent, and it runs from the system Metadata framework. On our test Mac, the Core Spotlight index lived in the user's own Library, under ~/Library/Metadata/CoreSpotlight.

On our test Mac, running macOS 27.0.1, ps showed it running under the logged-in user's account for more than a day, at 0% CPU and about 275 MB of memory while idle.

Why corespotlightd uses CPU

It works hardest when an app has a lot to add or change at once:

• An app you just installed or signed in to that makes its content searchable in Spotlight, indexing everything it has for the first time.
• A large import or sync into such an app, which means many new items at once.
• A new Mac or a fresh account, when apps index their content for the first time.

Its launch configuration also schedules a daily maintenance task, so short bursts of activity with nothing open are normal.

Is corespotlightd safe?

Yes. It is part of macOS and lives in the system Metadata framework:

/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Support/corespotlightd

You can check the path and the account it runs under in Terminal:

ps -axo user,pid,pcpu,rss,comm | grep corespotlightd

A process with this name running from anywhere else would be worth investigating.

How to calm corespotlightd down

• Let it finish. After installing an app, signing in or importing a large library, leave the Mac on and plugged in. Indexing app content is a one-time cost for each item.
• Find the app behind it. Think about what you just installed, signed in to or imported into. The app that recently received a lot of data is the one adding it to Spotlight. If it seems stuck, updating or restarting that app often helps, and so does restarting the Mac.
• Know what the Spotlight settings do. Unticking categories under Search results only changes what Spotlight shows; macOS describes it as "Only selected categories will appear in Spotlight search results", and it does not stop apps indexing their content. Search Privacy… excludes folders and disks, which affects file indexing rather than content inside apps.
• Do not bother quitting it. When we quit it on macOS 27, it exited cleanly and macOS started a new copy within a second, so quitting changes nothing.

See it in your menu bar

Because corespotlightd runs under your own account, MacStats can see it. When it is busy, it appears in MacStats' Top CPU or Top RAM list, and with MacStats Pro, clicking it gives you a plain-English explanation of what it is doing and whether you need to act.

Find out what Spotlight is doing before you start closing apps.

Download MacStats for Free

Frequently asked questions

What is corespotlightd on a Mac?

It is the Spotlight service that indexes content apps make searchable through Apple's Core Spotlight framework, rather than files on your disk. It runs under your own account.

Why is corespotlightd using so much CPU?

Usually because an app is adding or updating many items at once, for example right after you install it, sign in or import a large library. It settles when that indexing is done.

Why is corespotlightd using so much memory?

Some memory use is normal for an indexing service: on our test Mac it used about 275 MB while idle. Memory use alone is not a problem; check memory pressure in Activity Monitor before worrying.

Is corespotlightd a virus?

No. It is part of macOS and runs from inside the system's Metadata framework, the path shown in the section above. A process with that name running from anywhere else would be worth investigating.

Should I quit corespotlightd?

You can, but it does not help. In our test on macOS 27, macOS started a new copy within a second. Letting the indexing finish is the better option.