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

Reply
Question marked as Top-ranking reply

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).


348 replies

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 !!!

Dec 6, 2025 4:08 AM in response to Mitch Stone

New information about Spotlight slowing down and glitching your computer.  I don't recommend it for anyone who regularly uses Spotlight Search but I don't - and am giving it a try to solve an ongoing issue for me and a lot of other folks.


I read a piece by Michael Simon in MacWorld that addressed the problem many of us have been having with glitches caused by Spotlight.  He claimed that he solved his same problems by toggling off items under System Settings/Spotlight.  He disabled 'Show related content' and 'Help Apple improve search'.


I have been regularly deleting large folders in ~/Library/Metadata/CoreSpotlight/ and this insight from Michael Simon seems to follow that same reasoning.  Again, if you regularly use Spotlight Search, you obviously want to leave at least the first item enabled.


Simon also suggested disabling System Settings/ Spotlight /results from apps for Pages.


After making these changes, my problems stopped. I am no longer regularly deleting huge folders in ~/Library/Metadata/CoreSpotlight/ .

Dec 2, 2025 10:26 AM in response to fronesis47

Just to add to the debate, in my experience it is also a problem on Tahoe 26.1, although I had not noticed it until recently. Accordingly I'm not sure if my issue, on an M3 14" MBP, arose after or before the latest update.


I'm currently sat in front of my laptop with no real activity ongoing and "corespotlightd" is consuming well in excess of 125% of CPU time.


My experience tells me that it's associated with Pages files regardless of whether they are stored in the cloud or locally.


I hope this helps.


Stephen


Dec 2, 2025 9:21 AM in response to KnightsWhoSay9

Moving Pages documents out of iCloud helps for some, but not others. I've seen the issue triggered by locally stored documents as well. So, it’s worth trying. If it works for your situation, great -- but it isn't the cure-all. As I mentioned above, I've gotten results by making a copy of the file and working with it instead. This has helped at least twice for me. For others, it doesn't seem to help at all. So it’s also not the cure-all -- but still worth trying.

Dec 2, 2025 2:31 AM in response to Mitch Stone

Hi all,

Just recently converted from Windows and also had this issue, which is obviously unacceptable.

Working on an Air M4, sequoia 15.7, mostly with web browsers and pages.

It seems as the issue arises when Pages documents are stored in iCloud.

Tried to block spotlight entirely by a terminal command found in a forum, but that didn't do the trick.

Tried to uncheck Pages from syncing to iCloud, but didn't do the trick.


Then:

Tried to store all documents locally (in Library folder, not User folder as I suspect it to route back into iCloud(?)) - and it seems to do the trick.

Deleted the metadata folder, which before instantly reoccurred and started to grow, and now it hasn't reoccurred for a few hours, at least. And no corespotlightd process running.

Having several Pages docs open, problem seems to be solved for the moment, but will update if it doesn't last.

Just have to remember to backup my files "manually".

Nov 30, 2025 9:16 AM in response to Mitch Stone

Same problem here.


Pages file on in iCloud Drive/Documents. Pages file is open. CoreSpotlight folder has grown to 60GB. Mac hangs every 10 seconds, pausing the mouse pointer and audio glitches. In Activity Monitor, Pages and corespotlightd both unusually high CPU usage, over 50%.


Quit Pages, move file to local disk. Open document. Issue doesn't happen.


macOS 26.1 (25B78)

Pages version 14.4 (7043.0.93)

Nov 22, 2025 2:39 PM in response to Mitch Stone

I’m sick of Apple not fixing this. I’ve started using MS Word instead of Pages and I have no problem, BUT I prefer Pages over Word. I sent my MacBook Pro back and forth 4 times to them and on the 5th time, they sent me a new MacBook Pro, but within weeks it started have the Corespotlightd problem using 200-300% CPU. It is clear this multi-billion dollar company plans to do nothing. I have been telling people to buy Dell instead. This will probably be my last MacBook Pro.

Nov 19, 2025 1:25 PM in response to fronesis47

This is what annoys me about Apple. What remaining updates to sequoia has left. They mainly focus on securities. We has users need to hammer them on fixing these high CPU issues. These macOSes are turning into Windows. I have problem with Backgroundshortcutrunner process. BTW you guys know about Onyx utility that cleans up Spotlight? It safely deletes indexes safely. You rebuild or delete the index.

Nov 19, 2025 1:24 PM in response to Mitch Stone

I am using an M4 iMac. I've been posting about these problems for some time in this and other threads. I wanted to update what I've already posted.


I am still seeing all the documented issues with corespotlight folder sizes increasing and regularly delete folders in ~/Library/Metadata/CoreSpotlight/ when they exceed 4 GB in Tahoe. This solves the issues.


Curiously, I left for a long appointment this morning with these folders as large as 14 GB but didn't have time to delete them as usual. When I returned several hours later, the folder sizes had dropped back to around 1 GB.


I primarily use Pages and first saw the issues in Pages. Lately I have been viewing large mp4 movie files with QuickTime from a webcam I leave on at night for security. I record with OBS Studio on an Intel 21.5 iMac I upgraded to an SSD from the Fusion Drive. I saw the corespotlight folders increase on the M4 iMac after watching the movies for just over an hour for night time movement, at a speed of 10X and occasionally stopping to make screenshot movie captures of nighttime activity.


I sometimes notice Safari running slowly and large folders are always the culprit. Again the issue is resolved by deleting large folders.


My M1 MBA is using Tahoe and has no problems.


I am hoping to add to the information already known about this problem.





Nov 19, 2025 11:56 AM in response to ericmurphysf

I can confirm that Tahoe does not "cure" the problem as such. But I have discovered that it is triggered only by certain Pages documents, and they do not have to be particularly large to manifest the issue. The commonality seems to be how heavily the document is edited.


I had not seen the problem for months, then recently, I shared a 10k word Pages document. After some rounds of editing (track changes turned on), the process began to heat up. It did not cause serious performance issues, but it often showed as the most active process in Activity Monitor. Perhaps Tahoe mitigated it somewhat? Hard to know.


The process continued to spike even after I turned off sharing for this document and moved it out of iCloud (I did this in two steps). I then made a Finder copy of the file. This copy does not trigger the process spike, even when left open for days. So it seems the way Pages stores versions is at least partly the culprit.


I wish, nearly a year later, we were further along on this. At least we now have some management strategies available to us.

Nov 19, 2025 10:23 AM in response to fronesis47

fronesis47 wrote:

The big question for me is what is the situation with Tahoe, 26.1?
Multiple posters here have asked about Tahoe, but I get the sense that most of us on this thread with the problem have not updated to Tahoe. I have yet to see multiple reports from users running Tahoe that the problem persists. And that's the only thing that gives me a glimmer of hope...

I've been running Tahoe on the systems that support it (my iMac Pro does not) since a few weeks after it came out. So far I have not observed any discernible difference in this particular problem, or bug, or whatever it is.

Nov 19, 2025 8:21 AM in response to fronesis47

In my year-plus of dealing with this issue, I've reached the following conclusions (which may not be generalizable to other users, but they seem to at least be consistent for my particular use case):


  • The problem is significantly more severe on Intel systems than on Apple Silicon systems.
  • The problem, at least in my case, is strongly linked to editing large Pages files. On my two Intel systems (a 27-inch iMac and an iMac Pro), I only regularly edit large Pages files on the former. CoreSpotlight metadata accumulates rapidly, getting to 40 GB or more every few days to maybe a week at most. On the latter system where I rarely edit large Pages files, CoreSpotlight metadata has only accumulated to about 25 GB since August.
  • Deleting metadata when it approaches or exceeds 40 GB (on systems with 32 GB or more RAM and 2 TB of SSD storage) seems to prevent the various Spotlight processes from consuming large amounts of CPU time and interfering with system stability/responsiveness. Since this fix works for me, I've been able to continue to edit large Pages files which are synced via iCloud without killing system responsiveness.
  • On Apple Silicon systems, the amount of CoreSpotlight metadata appears to wax and wane, presumably as macOS deletes out-of-date metadata.
  • On Intel systems, metadata only seems to accumulate, unless the system is restarted (after say a software update). Frequently after a restart, I have seen CoreSpotlight metadata decline from say 25 GB to <10 GB.


While this clearly doesn't work for everyone, I have found that I can maintain system stability and responsiveness by a) closing large Pages documents (and quitting Pages entirely) when not actively editing them; and b) keeping an eye on the CoreSpotlight folder in ~/Library/Metadata, and deleting the contents of the folder when it approaches or exceeds ~40 GB (a value that may be different if your system has more, or less, RAM and/or storage.

Nov 19, 2025 7:44 AM in response to Mitch Stone

As this thread approaches its one-year anniversary, there's still no definitive identification of the specific bug, nor any clear admission from Apple that it's a bug. But I do think we've managed to synthesize a lot of information:

  • The problem starts with Pages. It's not clear whether the core problem here is the way Pages saves its unlimited revisions, the way it allows for unlimited undos, or the way it builds the index for spotlight, but it starts here.
  • Spotlight is clearly involved, as it's building a searchable index, and whatever is wrong with the Pages file gets made worse with spotlight. There is clear evidence for this when the metadata folder balloons to 30, 50, or 150Gb in no time at all.
  • Users often only realize there is a problem when the corespotlightd process starts to work overtime, but that's clear a knock-on effect from the size of the metadata folder.
  • Cloud activity exacerbates the problem: so moving files out of iCloud and not sharing files may help.
  • Deleting the metadata folder is also a very practical workaround.


The big question for me is what is the situation with Tahoe, 26.1?

Multiple posters here have asked about Tahoe, but I get the sense that most of us on this thread with the problem have not updated to Tahoe. I have yet to see multiple reports from users running Tahoe that the problem persists. And that's the only thing that gives me a glimmer of hope...

Continued corespotlightd process CPU overload issues

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.