Why searching a Mac feels slow, and what fast search does differently
· 6 min read
Searching a Mac feels slow for three reasons, and only one of them is a fault. Spotlight is doing more work than you asked for (matching file contents, ranking the results, consulting the network), the index may be rebuilding after an update or a migration, and the results window redraws as several different providers report back at different speeds.
Most of that is fixable in settings. The part that is not fixable is architectural, and it is the reason a name-only search feels instant by comparison.
Spotlight is not a filename search
When you type three letters into the Spotlight window, macOS is not scanning filenames. It is asking a set of providers for matches: the file index (names, contents and metadata), applications, System Settings panes, Mail, Messages, contacts, calendar events, the dictionary, unit and currency conversions, and, unless you have turned it off, suggestions from Apple’s servers.
Then it ranks everything into one list and picks a Top Hit.
That is a good design for “what do I want”, and a slow design for “where is that file”. The pause before the list settles is not the disk being read. It is ranking, plus waiting on whichever provider is slowest, which on a poor connection is the network one.
The wait you can remove today
Turn off the providers you do not use. Open System Settings, then Spotlight (on Ventura and Sonoma the pane is Siri & Spotlight). Under Search results, switch off categories you never search: Fonts, Developer, Presentations, Events & Reminders, whatever is noise for you. Fewer providers means less to wait for and a shorter list to read.
Turn off web results if you never click them. In the same pane, the options that send your search terms to Apple for suggestions are separate switches. Off means no network round trip in the middle of typing, which is the single most noticeable change on a slow or captive connection.
Check whether the index is actually finished. In Terminal:
mdutil -s /
It reports whether indexing is enabled for the volume. If a Mac has just been updated, restored from a backup, or migrated from another machine, the whole disk is being read again and searches are slow until it finishes. Activity Monitor tells the same story: look for mds, mds_stores and mdworker using CPU steadily. That is normal for hours, not for days.
Exclude volumes you never search. A scratch drive, a Time Machine disk, a virtual machine image or a folder full of build artifacts costs indexing time and pollutes results. Add them in the privacy list at the bottom of the Spotlight settings pane. Anything listed there is not indexed, which is the point, so add nothing you might later want to find.
Give the disk some room. Indexing needs free space to work in, and a volume with a couple of percent free behaves badly in general, not only in search.
When the index itself is wrong
If searches are slow and also wrong (files missing, results stale, a folder that never appears), the index is a genuine suspect. Rebuilding is a real fix, and it is also hours of background work, so it belongs at the end of the list rather than the start.
sudo mdutil -E /
That erases and rebuilds the index for the volume. Expect fans, expect heat on a laptop, and expect search to be worse before it is better. Spotlight cannot find a file you know exists covers the five things worth ruling out before you get to this.
Finder search has its own slowness
Finder search shares the index, but it can also fall off it.
Search a network share and there is usually no index to consult, so Finder crawls the volume over the network. That is not a Mac problem to tune; it is the file server deciding how fast it answers.
Search with a Contents criterion and you have asked for text matching, which is real work per file. Choosing the Name matches suggestion under the search field instead is often the difference between a spinner and an instant list. Search inside one folder only on a Mac covers scoping and criteria properly.
What a name-first search does differently
The alternative approach drops nearly everything Spotlight does and keeps one thing: names and paths.
Read the file table once, hold every filename in memory as a flat list, and answer each keystroke by narrowing the previous result rather than starting a new query. No contents, no ranking model, no providers to wait on, no network. The work per keystroke becomes a scan of a list that is already in RAM, spread across all the cores the Mac has.
The numbers that come out of that design are different in kind, not degree. Everywhere was measured on an older Intel Mac holding six million files: the catalog builds at 193,000 files per second, first setup takes 31 seconds (and searching works before it finishes), the first keystroke returns in under 10 ms and each further keystroke in under 2 ms, the window opens in under 50 ms, and it catches up after the Mac wakes from sleep in under 500 ms. Six million filenames cost about 308 MB of memory.
Those are the trade being made explicit: memory and a one-time read, in exchange for no wait per keystroke.
The honest trade
A name-first search is not a Spotlight replacement, and anyone telling you otherwise is selling something.
It does not search inside documents. If what you remember is a phrase from the middle of a contract, the content index is the only thing that will find it, and Spotlight has one. It does not answer questions, do conversions, or launch apps and system settings panes. Those are launcher features, and they are genuinely useful.
What it replaces is the specific case of “I know roughly what this file is called and I want it now”, which for most people is the majority of searches and the one Spotlight handles least well.
The practical setup for a lot of people is both: Spotlight kept for content, apps and settings, with its noisier providers switched off, and a name-first search on a different key for files. Full Disk Access on a Mac covers the permission any such tool has to ask for, and why.
Questions
Will turning off Spotlight indexing make my Mac faster? Not in any way you will notice, and it makes search useless. Indexing is intensive for the first day after a big change and close to free afterwards. Excluding a specific noisy volume is the version of this idea that is actually worth doing.
Why is search slow only for the first few seconds after I wake the Mac? The index catches up on everything that changed while the disk was idle, and the providers that were asleep have to reconnect. A few seconds is normal. Minutes, every time, suggests something is still indexing.
Does more RAM make search faster? Only indirectly, by keeping caches resident. Spotlight’s delay is mostly ranking and providers, not memory pressure. An in-memory name search is the case where RAM genuinely buys speed, and even six million files fit in a few hundred megabytes.
Is a spinning hard disk the problem? It makes the first index build far slower and content searches painful. Once an index exists, queries hit the index rather than the whole disk, so an older drive hurts less than you would expect for name searches and much more for content ones.