Mac slow after a macOS update? Here's what's normal

The most common reason a Mac feels slow in the first day or two after installing a macOS update is background reindexing — Spotlight and Photos rebuilding their databases, not a defect in the update itself. It usually clears up on its own within a day or two, and forcing it to stop early tends to add time rather than save it. This guide starts with the checks that tell reindexing apart from an actual problem, gives real timelines from named sources instead of one invented number, and ends with what's actually worth investigating if the slowness is still there a week later.

Is it reindexing, or something wrong? Check these three things first

Three things separate ordinary post-update reindexing from an actual problem, and all three take under a minute to check without changing anything.

A brief spike from any of these processes — a few seconds while you're actively searching, or right after a photo import — is normal at any time and has nothing to do with an update. What actually points at reindexing is one or two of these processes sitting near the top of Activity Monitor's CPU tab for an hour or more, right after you installed something, with no obvious reason you're causing it yourself.

The Spotlight icon in the menu bar is a faster confirmation than opening Activity Monitor at all: click it, and an "Indexing" note under the search field, instead of the normal empty search box, tells you directly.

How long reindexing actually takes

There's no single official number, and that's worth saying plainly instead of inventing one. Apple's own instructions for forcing a Spotlight reindex say only that it "can take some time, depending on the amount of information being indexed" (Apple: rebuild the Spotlight index on your Mac) — accurate, and not especially useful on its own.

Real, dated reports fill that gap better than a guess does. MacPaw's own how-to for macOS Tahoe, last updated May 26, 2026, describes the effect lasting "nearly 48 hours" on the author's own Mac, with performance feeling normal again after about 72 hours (MacPaw: fix a slow Mac after a macOS Tahoe update). EaseUS's equivalent guide, updated June 17, 2026, puts the range more loosely at "hours (or days)," depending on the size of the drive being indexed (EaseUS: Mac runs slowly after update). Neither of those is a lab measurement — they're one company describing what they personally saw, which is exactly why the chart below has three separate points on it instead of one tidy average.

The extreme end is real too, and worth naming honestly rather than hiding. A thread on MacRumors' forums, started April 13, 2026, documents a rebuild still running after 46 hours on an M4 Max with 128 GB of RAM and roughly 420,000 objects to index. The poster's own theories about exactly why — a single-core compaction bottleneck, a feedback loop with fileproviderd — are their own speculation, by their own admission, not a confirmed Apple bug (MacRumors: severe Spotlight reindexing problems). Treat that thread as proof a stuck-for-days case exists, not as a diagnosis of your own Mac.

Put those together and a reasonable expectation is a few hours on a fast Apple Silicon Mac with an average amount of data, stretching toward two or three days on an older Mac, a large drive, or a very full photo library. SwoopByte hasn't measured this directly. If that changes, a real number from our own testing would replace this range, not sit next to it as one more guess.

What not to do while it's running

The instinct to "fix" a slow Mac is exactly what makes this take longer, in two specific ways.

Don't delete ~/Library/Metadata/CoreSpotlight/ to force a fresh start. It's advice you'll find repeated in a few places, and it does technically work — but what it actually does is throw away the index Spotlight had already built and make it start over from nothing. If you're already twelve hours into a reindex, deleting that folder doesn't skip the remaining wait. It resets the whole thing.

Don't repeatedly force-quit mdworker either. It's managed by launchd, the same background process manager behind most of macOS's core services, and launchd relaunches it within seconds of it exiting — the same pattern that shows up with tccd's own post-update CPU spikes, a smaller and separate case we cover on its own if that's the process you're actually seeing (what tccd does on a Mac, and why it briefly spikes CPU). Quitting mdworker repeatedly buys you nothing and interrupts whatever chunk of indexing was mid-write the moment you killed it.

The same logic that makes RAM cleaners mostly pointless applies to the CPU or junk "optimizer" tools sold for this exact moment: flushing caches macOS was already using on purpose doesn't make reindexing finish faster, because reindexing was never a cache problem to begin with.

The other real causes, ranked below reindexing

Reindexing explains most "slow right after an update" reports. When it doesn't, three other causes are worth checking, roughly in this order.

First-boot revalidation on a major version jump. Moving between major versions — Sonoma to Sequoia, Sequoia to Tahoe — does extra one-time work on the very first login: system caches rebuild against the new OS, and Launch Services, the part of macOS that knows which app opens which file type, rebuilds its own database to match. That work is normally over within the first login itself, not something that drags on for days the way Spotlight can. The next jump is already on the calendar: macOS 27, "Golden Gate," has been in public beta since July 2026, is the first version built only for Apple Silicon, and a general release is widely expected around mid-September 2026 — Apple hasn't published an exact date, so treat that as trade-press reporting, not a confirmed one. Installing it the week it lands is the largest version jump most current Macs will have been through in years, and everything on this page will apply to it, likely for longer than an ordinary point update.

An old login item or launch agent that doesn't get along with the new OS. A helper process that crashes and relaunches in a loop looks a lot like a stuck update from Activity Monitor's CPU tab — the tell is a process restarting over and over rather than one that's simply been running steadily, which Console.app's crash reports will show directly if you search for the app's name. Removing or updating that one app, not the whole OS, is the actual fix.

Storage running low enough to affect everything else. A nearly full startup disk slows Spotlight's own indexing down further, on top of leaving less room for swap. We've already covered exactly what fills that space and how to check it — see what's actually inside System Data on a Mac, including why that category alone often spikes for a day or two right after an update, rather than repeating the same breakdown here.

If it's battery life, not speed, that's a different question — already answered

A Mac that drains its battery noticeably faster right after the same update is a real, separate, better-documented pattern, even though Spotlight reindexing shows up on that list of causes too. See why your MacBook's battery might be draining fast if that's what you're actually seeing, rather than general sluggishness.

When it's actually worth investigating

Give it a week. If your Mac is still dragging seven days after the update, and Activity Monitor shows nothing from mdworker, mds_stores, or photoanalysisd anywhere near the top of the CPU tab, this isn't reindexing anymore, and it's worth actually digging in rather than waiting longer.

Start with Activity Monitor's Memory tab and its Memory Pressure graph — a yellow or red reading points at a memory problem, not an indexing one, and we've covered exactly what that graph means and what to do about it in full elsewhere. If memory checks out, storage is the next place to look: here's how to actually go find what's using your disk when the Storage pane's own numbers aren't specific enough on their own. And if none of that turns anything up, the honest possibility left is that the new macOS version genuinely asks more of your Mac's particular hardware than the last one did — a real trade-off of staying current, not a bug waiting to be found.

Where SwoopByte Battery fits

Activity Monitor answers every check on this page, but only as a snapshot — you have to reopen it and re-sort to see whether a process is still churning an hour later. SwoopByte Battery is being built to show a live breakdown of which apps and processes are actually consuming energy on your Mac right now, alongside a history chart, so a process still eating CPU and battery hours after you first looked doesn't quietly slip past you. It's planned to stay completely free, with no Pro tier, for Apple Silicon MacBooks on macOS 14 or later. See the product page and join the waitlist.

FAQ

How long does it take for a Mac to speed up after a macOS update?

There's no fixed number. Real reports range from a few hours on a fast Apple Silicon Mac with an average amount of data to about 48 hours in MacPaw's own documented case, and up to several days in less common cases with a large drive or photo library. Give it at least 24 to 48 hours before assuming something's actually wrong.

Should I force-quit mdworker or mds_stores to make my Mac faster after an update?

No. Both are managed by launchd, which relaunches them within seconds of being quit, so force-quitting achieves nothing except interrupting whatever indexing was already in progress. Letting them finish is faster than repeatedly killing and restarting them.

Is it safe to delete ~/Library/Metadata/CoreSpotlight to fix a slow Mac after an update?

It won't fix a slow Mac. Deleting it throws away Spotlight's existing index and forces a full rebuild from scratch, which restarts the wait instead of shortening it. Deleting it only makes sense if Spotlight's index is genuinely corrupted, not as a general speed fix.

Why is my Mac's fan running loud right after a macOS update even though I'm not doing anything?

Sustained CPU use from Spotlight (mdworker, mds_stores) or Photos (photoanalysisd) reindexing in the background is the most common cause, and both can push the CPU hard enough to spin the fan with no app open. Check Activity Monitor's CPU tab to confirm one of those processes is actually responsible before assuming a hardware problem.

How can I tell if Spotlight is still indexing instead of something else being wrong?

Click the Spotlight icon in the menu bar — an "Indexing" note under the search field confirms it directly. Activity Monitor showing mdworker or mds_stores sustained near the top of the CPU tab, and a search for a file you know exists coming up empty, both point at the same thing.

My Mac is still slow a week after installing a macOS update. What should I actually check?

If Activity Monitor shows nothing from mdworker, mds_stores, or photoanalysisd using significant CPU, reindexing is no longer the explanation. Check the Memory Pressure graph for a memory problem, then available storage, before assuming the new macOS version itself is simply heavier than your Mac's hardware.

Related guides