mds_stores using high CPU on Mac? Spotlight indexing, explained

You opened Activity Monitor because the fans were up and the Mac felt sluggish, and near the top of the list is something cryptic: mds_stores, using a lot of CPU, often with mds and mdworker nearby. First, the reassuring part: this is almost never a virus. Seeing mds_stores use high CPU on a Mac usually means Spotlight is rebuilding its search index, not that anything is wrong.

What mds_stores actually is

These aren't apps you installed. They're the processes behind Spotlight, the built-in search that powers Command-Space, Finder search, and the "suggestions" in Mail and other apps. The mds in the names stands for metadata server:

• mds coordinates the whole thing: it watches for file changes and decides what needs indexing.
• mdworker (and mdworker_shared) do the actual reading: opening files, pulling out text and metadata to catalog.
• mds_stores manages the index stores themselves: the databases Spotlight writes to and later reads from when you search.

So we can rule out the scary explanation early: malware shows up as some other process, not as the machinery of Spotlight. High mds_stores CPU is macOS building the catalog that makes search instant later.

Why mds_stores is using so much CPU

Indexing is heavy work. To make search feel instant, Spotlight has to open and read a large number of files up front (every document, message, and PDF) and write what it finds into its index. That's a lot of CPU and disk at once. The key thing to understand is that this is front-loaded, one-time work. Once the index catches up, the processes drop back to near-idle and only stir when files change.

Howard Oakley of The Eclectic Light Company notes that since Time Machine moved to APFS, it's increasingly mds_stores specifically (the store manager) that shows up in these blips rather than the older mdworker. Either way, the cause is the same: a big batch of indexing to get through.

What sets off a big re-index

A spike almost always traces back to something that gave Spotlight a lot of new material at once:

• A macOS update. After upgrading, macOS often rebuilds or revalidates the index; this is the single most common trigger, and the most misread ("my Mac got slow right after updating").
• A big copy, restore, or migration. Moving in from Migration Assistant, restoring a backup, or copying a large folder hands Spotlight thousands of files to catalog.
• A newly mounted external drive. Plug in a full external disk and Spotlight starts indexing it; that's what makes searching it work later.
• Cloud-sync churn. Dropbox, Google Drive, iCloud Drive, or Photos pulling files down and shuffling them around means constant changes for mds to re-index.
• A corrupted or stuck index. Occasionally the index gets into a bad state and the processes churn without ever finishing.
• Developer workflows. Build folders, caches, and dependency trees that rewrite thousands of small files constantly keep mds_stores busy re-indexing the same locations. (Big regenerable folders like node_modules are a classic offender; see is it safe to delete node_modules.)

What's normal, and what isn't

• Normal: high mds_stores or mdworker CPU for a while after an update, a restore, or plugging in a new drive; then it settles down and stays quiet. Indexing a large volume can take a long time, from many minutes to a few hours, and occasionally longer on a very full or very large disk. Let it run.
• Worth investigating: mds_stores sits pegged high for days, or it spikes, calms, and spikes again on a loop with no obvious cause. That points to a stuck index or an app rewriting the same files nonstop.

There's no official "normal percentage" here. Judge it by direction: is it working through a backlog and trending down, or stuck in place while nothing is changing?

How to check in Activity Monitor

1. Open Activity Monitor (in Applications → Utilities, or search for it with Spotlight).
2. Click the CPU tab.
3. Type mds into the search box in the top-right to filter down to mds, mds_stores, mdworker, and mdworker_shared.

Watch for a minute. If the numbers are high but drifting down, indexing is progressing; leave it alone. If one is stuck high indefinitely, or you can see a sync app or a build process hammering the disk alongside it, you've found the folder churn feeding the re-index.

High numbers in Activity Monitor aren't automatically bad, by the way; the same is true of your RAM, where a "full" reading is usually healthy. If it turns out to be a different process at the top of the list, kernel_task and WindowServer each run high for their own reasons, and this is one of the processes to check when the fans are loud for no obvious reason.

Safe fixes

Work from gentlest to most drastic:

• Let it finish. Usually the right answer. Plug in to power, give it an hour or two, and check again. After an update or migration, this is expected behavior settling down.

• Exclude folders that don't need searching. If a specific folder or drive keeps triggering re-indexing (a giant media library, a backup disk, or churning build/cache folders), add it to Spotlight's exclusions. Go to System Settings → Spotlight (called Siri & Spotlight on some macOS versions), scroll to Search Privacy, click the +, and choose the folder or disk. Spotlight stops indexing it, so it also stops appearing in search there.

• Rebuild a stuck index (power-user option). If mds_stores is stuck for days and won't settle, you can erase and rebuild the index for a volume in Terminal:

  sudo mdutil -E /
  

  Apple's own description of the -E flag is that it erases each local index store, and the stores "will be rebuilt if appropriate." To rebuild a specific external drive, point it at that volume instead, e.g. sudo mdutil -E /Volumes/YourDrive (and mdutil -s / shows whether indexing is even enabled). The caveat: this deletes the catalog, so Spotlight has to build it again from scratch, which means mds_stores will be busy, and your fans possibly loud, again for a while right after. It's a fix for a corrupted index, not a way to make indexing stop.

What not to do: don't reach for disabling Spotlight entirely as a first move. You can (sudo mdutil -i off /), but you'd trade a temporary CPU spike for permanently broken search: no Command-Space, no Finder search, no Mail suggestions. That's fixing a passing symptom by removing a feature you use every day.

By the time you've opened Activity Monitor, the frustrating part of an mds_stores spike is that you still can't tell whether it's normal catch-up work or a stuck index, or whether the fans are Spotlight's fault or something else's. Plumby keeps a live readout of CPU, memory, and temperature in your menu bar and holds onto that history across reboots, so you can see whether mds_stores is trending down and finishing or stuck, and which process is actually driving the heat. It names the real cause and flags when a reading is simply normal under load, so a loud fan points you to the real culprit, not a virus you never had.