Level 2

306 points

Continued corespotlightd process CPU overload issues

I am wondering if anyone has discovered any new ideas for stopping the corespotlightd process from hogging the CPU. According to Activity Monitor, the corespotlightd process often occupies more than 100% of the CPU load, sometimes spiking as high as 400% on my M2 Ultra Mac Studio. This problem has become so severe that it often pinwheels under normally non-intensive tasks. It can cause the video to flicker on my Studio Display. In one case it caused my Mac to kernel panic (crash).

I encountered this bug only after installing Sequoia 15.2, but having researched this issue extensively, I find that Mac users have identified it since at least macOS Ventura. So here are some solutions we don't need to hear again:

Reindexing Spotlight by adding and removing volumes in Spotlight Privacy. This provides relief only temporarily. Within hours the process is again grinding the Mac to a halt.

Killing the corespotlightd in Activity Monitor. Again, this is at best only a temporary solution as the process will reinstate itself.

A "clean" install of macOS. First of all, no such process really exists. The OS recovery process simply reinstalls a new copy of the System files. Nobody reports this as a fix. An internal drive wipe and reformat, and restore from Time Machine is also unlikely to help, as it simply returns your Mac to its previous state. If the corespotlightd problem results from a corrupted file, the problem will likely simply be recreated in your reinstall. "Nuke and pave" might solve the problem if it caused by a format or directory issue on your startup volume. This does not seem to be the case, but if anyone has permanently cured the problem by this method, please report it.

What we do need to hear is from anyone who has spent time with Apple Support on this issue and been provided with solutions that actually work, or has new ideas about what causes it. Feels like we're on our own here, since Apple seems to be stumped.

Posted on Dec 19, 2024 11:21 AM

Top-ranking reply

ericmurphysf

Level 2

307 points

Posted on Jan 31, 2025 8:44 AM

Okay, I have a new hypothesis as to what's going on here with corespotlightd. This process is one of at least four that are responsible for macOS's Spotlight functionality. The three others are mds, mdworker, and md_stores. I cribbed the following descriptions of these three processes from the HowToGeek website:

The two processes [mds and mdworker] are part of Spotlight, the macOS search tool. The first, mds, stands for metadata server. This process manages the index used to give you quick search results. The second, mdworker, stands for metadata server worker. This does the hard work of actually indexing your files to make that quick searching possible.

And for md_stores, from the TechNewsToday site:

Mds_stores is the core indexing process of the macOS. On normal days, it usually takes up a noticeable [sic, probably should be un-noticeable] amount of CPU. However, when you reinstall your OS or add new files/directories, your system will automatically start to reindex these new databases, which sees the mds_stores CPU usage skyrocket.

The macOS Spotlight feature makes use of two processes for indexing the system database; mds and mds_stores. The mds (Metadata Server) process is responsible for tracking and recording files and folders in your operating system. md_stores then compiles and manages these mds metadata, which Spotlight later uses for searching certain documents within your OS.

So it may be that corespotlightd is in fact an unwitting victim of other processes' having gone awry. On my two Intel systems, by three months after installing macOS 15.0, metadata associated with Spotlight located at ~/library/metadata had reached half a terabyte on both systems. It sounds like this data was actually written out by either mdworker, mds_stores, or both. And then, corespotlightd has to wade through these gigabytes upon gigabytes of metadata to actually produce search results, and as that task gets harder and harder with more and more metadata being produced, eventually Spotlight search results (which includes search and smart folders through Mail) degrade to the point of uselessness.

While I haven't managed to halt the rapid growth of metadata on these two Intel systems (Apple Silicon Macs still have the issue but to a much milder degree), simply deleting the metadata out of the ~/library/metadata/Corespotlight and ~/library/metadata/SpotlightKnowledgeEvents (while leaving the folders themselves intact) resulted in a near-immediate improvement in three areas: greatly reduced use of storage space; vastly improved search results; and much lower processor utilization by corespotlightd.

As noted, this metadata still continues to pile up (especially if I have a large (>5 MB) Pages file open). But if I have to empty out these two folders once every few weeks until Apple resolves the issue, that's not the end of the world).

View in context

348 replies

Mar 6, 2025 11:38 AM in response to Mitch Stone

Mitch Stone wrote:

Did you try my suggestion? For me, it actually did help a lot. I'm not sure I understand the resistance to it, given the simplicity and apparent effectiveness. I'd really like to know if it works as well for others as it did for me.

Based on the totality of posts on this thread, it seems very likely that while using Pages is not the sole cause of corespotlightd (and Spotlight metadata) running amok, it seems to be possibly the largest contributor. So far, users seem to have had decent luck with one, two, or all three of the following:

Mitch's recommendation of duplicating a Pages file (thus removing versioning information, which seems to be what spikes corespotlightd activity and Spotlight metadata accumulation), and then making further edits to the duplicated version.
Removing Spotlight-related .plists.
Removing Corespotlight metadata from the ~/library/metadata folder(s)

None of these workarounds are permanent fixes. But they seem to buy at least temporary reprieve (I deleted Spotlight metadata yesterday afternoon, and right now the system fan is at 12%, system CPU usage is below 20%, and corespotlightd doesn't even appear in the top forty processes). If I have to delete metadata once a week or so (a task that takes all of ten seconds), that's a small price to pay for acceptable performance.

If you're running into performance issues, including Time Machine issues, I would recommend you try some or all of these fixes. Apple may or may not ever get around to addressing these issues (which seem to disproportionately affect Intel systems which are obviously not Apple's priorities these days). But these fixes, singly or in some combination, seem to work for a lot of people. I'd at least give them a try. None of them seem to have negative consequences, unless you're unusually dependent on versioning in Pages.

Mitch Stone Author

Level 2

306 points

Mar 16, 2025 9:20 AM in response to Daniel_145

I've made this point often, including in this discussion. It seems someone will always chime in with a magical solution that involves typing a command string into Terminal, often without explaining what it actually does. Any Terminal command that begins with "sudo" (super-user do) is dangerous, especially if it includes "rm" (remove). Just don't!

This is a very lengthy discussion but I also highly recommend Finder copying the Pages document that is causing the problem for you and working with it instead of the original. This worked for me. You may also find you need to delete the metadata, but I can report I've never needed to take this measure, and the issue is now under control, at least. I always suggest trying the least destructive possible solution first.

Also, I believe the consensus is that iCloud is not the source of the issue. It seems to originate from Spotlight trying to index heavily edited Pages documents, whether they are local or cloud stored.

Daniel_145 wrote:

The lesson here - anyone looking for suggestions to fix this, please be very careful what you try. People are capable of giving you absolutely destructive instructions even on the developers forum. Please double-check anything before you run anything.

KWiPod

Level 2

158 points

Jul 13, 2025 11:37 PM in response to KWiPod

Last week, I called Apple Support and described the corespotlightd issue on my 4-months-old M4 MacBook Air [MacOS 15.5]. An appointment was made with the Genius Bar at my local Apple Store.

At this appointment, I explained our Pages [v14.4] corespotlightd issue to a lovely chap and we ran the hardware check which passed, ruling out my machine. I showed the Genius this forum, and he arranged for next-level-up Apple Support to call me the next day.

On that call, I shared my screen and showed the (also lovely) support chap this forum. After creating a New User (to rule out a user-specific problem), I opened Activity Monitor, highlighted corespotlightd, created a Pages document and saved it to iCloud. After a few edits, corespotlightd spiked.

The support chap then consulted and I was put on to a new (equally lovely, even higher-up) support chap to whom I showed this forum. He wanted me to duplicate the problem whilst screen recording. Unfortunately, I was unable to duplicate the spiking so the he sent me an email that allows me to send him a screen recording of the issue, should I be able to get it to happen.

I have been trying each day to capture the problem, but have, so far, failed. I will keep trying every day.

So we know that several individuals in Apple’s support hierarchy are at least aware our corespotlightd spiking issue. How high in that hierarchy, I cannot say.

Perhaps, if a few more of us follow the Apple Support approach, we may be able to get this issue acknowledged and then solved.

Jan 1, 2025 8:46 AM in response to MgS_2012

Thanks for your posts! I have large Pages files on my M2 MB Air and Apple Intelligence turned on. Editing those docs is when I first noticed the problem that eventually led me to corespotlightd high CPU usage. I’m wondering if Writing Tools in Apple Intelligence is the culprit. I talked with Apple Support yesterday (NYE) and made it to the point in troubleshooting where we identified it as a User issue and not system wide. We progressed to a system re-install, which you already know doesn’t work. I’ll talk with Support again tomorrow, but in the meantime, I’ve turned off Apple Intelligence on my Mac to see if it will also calm down

briantf

Level 1

20 points

Jan 1, 2025 10:07 PM in response to briantf

This seems to be promising. Corespotlightd now at 0% while reindexing in progress .

Disable system integrity protection. Boot into recovery mode and access the terminal. Run csrutil disable
rm -rf ~/Library/Metadata/CoreSpotlight (the bloated files here contain the crux of the issue)
sudo mdutil -a -i off
Remove the spotlight index. rm -rf /System/Volumes/Data/.Spotlight*
sudo mdutil -a -i on
sudo mdutil -E
Follow step 1 but instead, run csrutil enable

Mitch Stone Author

Level 2

306 points

Feb 4, 2025 9:20 AM in response to ericmurphysf

This is certainly interesting, and I also had the inkling from watching the Activity Monitor that more than one process is implicated. However I do wonder why I've been able to mitigate this issue successfully by simply deleting the spotlight plist. My system has been behaving itself for the last couple of weeks since I did this last. I don't know if anyone tried this before moving on to more drastic measures.

ericmurphysf wrote:

Okay, I have a new hypothesis as to what's going on here with corespotlightd. This process is one of at least four that are responsible for macOS's Spotlight functionality. The three others are mds, mdworker, and md_stores. I cribbed the following descriptions of these three processes from the HowToGeek website:

Mar 9, 2025 9:37 PM in response to Mitch Stone

I just experienced this issue and my ~/Library/Metadata/Corespotlight was 50GB when I first looked, and within an hour it was 60GB in size! I just deleted that, and my caches folder and it appears to have fixed the issue. Thanks for the wonderful folk in here who identified a way to fix it for now.

Mar 16, 2025 8:27 AM in response to Daniel_145

Daniel_145 wrote:

What would you recommend, please? Reboots don't help, killing the spotlightd process in Activity Monitor helps only for a few minutes. Closing the Pages app helps but unfortunately I really need the document, it's the only reason why I didn't buy a pen and paper instead

Delete the contents of the ~/library/metadata/coresporlight/ folder. This has worked for multiple users including myself.

It's a temporary fix, in that eventually that folder will grow to the size you're seeing now. But I just see it as maintenance. Every couple of weeks I delete that data.

KWiPod

Level 2

158 points

Apr 2, 2025 12:23 AM in response to KWiPod

Since updating to MacOS Sequoia 15.4 (24E248) on Monday March 31st, all the spiking issues I described have stopped. Fingers crossed !

Mitch Stone Author

Level 2

306 points

May 13, 2025 1:52 PM in response to LAWM0N

No evidence points to iCloud being implicated in this issue in any way whatsoever. Certain large Pages documents that have been extensively edited appear to be the most common trigger of this issue, and it is not dependent on them being stored locally or in the cloud. Either way, the Spotlight data is stored locally, and it is the size and/or complexity of this data that seemingly causes the process to freak out.

LAWM0N wrote:

Are you saying 'do not use iCloudDrive for Pages or Numbers?' Ever? Or just do not use past contents (after downloading past contents onto your computer, but OK to use from now on?

Mitch Stone Author

Level 2

306 points

Oct 25, 2025 12:06 AM in response to dar221

I have had little to add to this discussion for a while, as this issue seemed to go away for me. Then, recently, I began working on a new Pages document. It isn't a particularly large document (around 10k words) stored in iCloud. I had been writing and editing it for several weeks, leaving it open for days at a time, without any apparent issues. Then I shared it for collaboration, with tracking changed turned on. Almost immediately after my collaborator began editing, the corespotlightd process shot up. So for me, at least, it is clearly not an iCloud issue per se. Shortly after closing the document, the process settles back down.

I also found a feature in Activity Monitor that I had not noticed before (possibly it is new in Tahoe). Double-clicking on the CPU pane brings up a window illustrating the CPU load per core. I have no idea of how to interpret this graph, or why all of the cores are labeled "Performance" except 1-4 and 13-16, which are labeled "Efficiency." In any case this is the graph from when the corespotlightd process exceeded 100%. A lot of red bars. Otherwise they are mostly green, and it seems even under this load, half of the cores are not in use at all.

Shared here in the hopes that someone will understand what this means.

Etc@

Level 1

18 points

Dec 13, 2025 12:57 AM in response to Mitch Stone

I just bought a MacBook Air 2022 M2 with 16GB, after the immediate update it runs now Tahoe 26.1. I face the same problem, with the corespotlightd slowing down my processor, consuming energy, and stopping Pages from working every minute or so for a few seconds. I transferred the two Pages documents I was working on on my SSD, and miracle. My CPU load is below 10%, the machine is fast with corespotlightd at 0.1% ! I have Key, Numbers, Safari (a full load of tags open), Preview, Mail… open, and no troubles.

SO : it's not the system, it's just Pages.

Why is this not fixed ? please "Apple Guys" if you can't read that, ask an İ.A. to read the complaints and search the codes, or do your job, that shouldn't be so complicated !!!

Jan 7, 2025 6:07 AM in response to Mitch Stone

Hi, Mitch. After talking with Apple Support, I discovered I had a different problem. I'm a bit embarrassed about it. Router performance is basic 101 troubleshooting and I failed to speed test the router as part of looking into continued lags and spinning wheels after I had turned off Apple Intelligence (which successfully addressed corespotlightd hogging the CPU). I ran a speed test and it showed my router was running at an upload speed of 2.61, dreadfully slow, especially when working with large documents on iCloud (where all my Pages documents reside). Also, there's several discussions out there regarding how quickly we can upload documents to iCloud, which might cause delays and even spinning wheels while editing large documents, like the Pages documents I've been working with. So, I'll need to decide if I want to fork out $50 a month to increase my upload speed or just move my large Pages docs to my computer and back them up to my external drive. >>sigh<<

Mitch Stone Author

Level 2

306 points

Jan 28, 2025 8:41 AM in response to ericmurphysf

Interesting. Checking these folders on my M2, I find that the size of the CoreSpotlight folder is 37GB, but no file within it is even a megabyte in size. The SpotlightKnowlegeEvents folder clocks in at 463 MB. It contains far more subfolders, so it is difficult to figure out where this data is hiding. Has your performance been improved by deleting the contents of these folders?

And another FWIW: Since the last time I deleted the Spotlight plist about a week ago, I have had no corespotlightd process issues. So I do think this is worth trying.

ericmurphysf wrote:

I'm not sure how many other people with this issue have seen degraded Spotlight results (including in Mail) as a result of corespotlightd's misbehavior, but I managed to at least temporarily resolve some of these issues by, on the advise (or at least consent) of Apple support, deleting the contents of the two folders, CoreSpotlight and SpotlightKnowledgeEvents, from ~/library/metadata/.

Note that I deleted the contents of these two folders, not the folders themselves. Also note that on Apple Silicon systems the SpotlightKnowledgeEvents folder is inside the CoreSpotlight folder. On Intel systems, it's at the root of ~/library metadata.

However, deleting the contents of these folders (on my system those contents comprised over half a terabyte of data) did not permanently resolve the issue. In barely twelve hours Spotlight added 22 GB of new metadata to these two folders. But I think until Apple resolves this issue (I doubt it will be in 15.3), simply deleting the contents of these folders when they get over a couple of hundred GB will definitely improve system performance, especially search.

Also note that in my experience these issues are less serious on Apple Silicon Macs. On my M2 Max MBP and my M1 Ultra Mac Studio, these folders are large but not enormous; 40 GB on the first system and 18GB on the second one.

Feb 3, 2025 4:05 PM in response to CaptainJoy

CaptainJoy wrote:

ericmurphysf asked:

How heavy a user of Pages are you?

I use Pages all the time. As a rule, I always have at least one Pages document open, and often one or more are >10 MB.

I suspect this is the root of the problem. I don't know if the amount of metadata accumulated on your system is comparable to mine, but for the last quarter of last year I was editing at least one file (on multiple Macs) that by that time had grown to ~200 MB (roughly 1,200 pages with many embedded graphics), and I'm pretty certain the result was half a terabyte of metadata saved in my user library folder. I strongly suspect a consequence of that amount of metadata was system instability, major issues with Time Machine backups, and degraded search performance in Spotlight to the point of unusability.

Since deleting this metadata last week, all three of these issues have resolved. The one remaining issue is that metadata continues to accumulate at an alarming rate, which will likely force me to remove it just as I did the last time, probably within the next two months. I'm pretty sure this is a bug somewhere in Apple's code that will need to be resolved via a future macOS update.

Continued corespotlightd process CPU overload issues