Spotlight vs Finder search on macOS: when to use which (and when neither works)

Most macOS users think of Spotlight and Finder search as the same thing wearing two different hats. They are not. They share a backend — both lean on the mds daemon and the on-disk metadata index — but the way each surfaces results is genuinely different, and there are cases where one returns what you want and the other does not. This guide is the short, honest comparison.

Where the line actually sits

Spotlight is a launcher-style search: a floating panel summoned by ⌘Space, single query box, mixed result types (apps, files, system actions, web). It ranks for "best single match" and is happiest answering "open the thing I am thinking of".

Finder search is a directory-scoped browser: opened by ⌘F inside a Finder window, multi-column result list, restricted to file results. It ranks for "all matches in this scope" and is happiest answering "show me every file that matches".

Both query the same metadata index when one is available; when it is not, only Finder falls back gracefully.

When Spotlight is the right tool

Use Spotlight when:

You want one specific thing — an app, a file you know by name, a system setting.
The thing might not be a file. Spotlight surfaces apps, settings panels, calculator results, dictionary lookups, contacts.
You are happy with the top match and do not need a list.
Your hands are already on the keyboard and reaching for the mouse would be the slow part.

Spotlight's strength is recall-at-speed for known items. If you know exactly what you are looking for and you do not need to see alternatives, it is hard to beat.

When Finder search is the right tool

Use Finder search when:

You want every match, not the best one. "All .psd files modified this week" is a Finder query.
The match criteria are richer than a filename — kind, size range, modification date, "contains text".
You want to refine the query interactively — add filters, change scope, save the result as a Smart Folder.
You need the results to behave like files: drag them, tag them, move them, get info on them.
You are searching inside a specific volume or directory that is not your default search scope.

Finder search's strength is exploratory filtering. It is the only search surface on macOS that lets you build a real predicate visually.

What both share

The query layer underneath is the same mds machinery. Apple documents the predicate language behind both at the Spotlight metadata reference and the longer mdfind man page. The same kMDItem* attributes are usable from both surfaces. The same Privacy exclusion list scopes both.

That last point is important. If a path is on Spotlight → Privacy, neither surface will find files inside it. People sometimes assume Finder will fall back to a directory listing — it does, but only within the current folder, not recursively.

Where they diverge

A few specific behaviours worth knowing:

Default scope. Spotlight searches every indexed volume by default. Finder defaults to "This Mac" but remembers the last scope you chose; if you set it to a single folder, it stays there until you change it.

Live filesystem fallback. When the metadata index is rebuilding or disabled for a path, Finder will fall back to a slow live scan inside the current folder. Spotlight will not — it returns nothing.

Predicate complexity. Finder lets you stack filters in the UI ("Kind: PDF" + "Last opened: this month" + "Size > 5 MB") and save the result as a Smart Folder. Spotlight has no UI for predicates beyond a few magic keywords (kind:pdf, date:today).

Result types. Spotlight mixes file results with apps, settings, web hits, calculator answers, dictionary lookups. Finder shows only files and folders.

Latency. Spotlight is optimized for top-N latency. Finder is optimized for full-list completeness. On the same query, Spotlight usually shows its top hit before Finder is done counting.

When neither one works

The honest failure cases:

Metadata is missing. If mdls /path/to/file shows mostly (null) values, neither Spotlight nor Finder will find the file by content. Re-import with mdimport, or rebuild the volume's index with sudo mdutil -E / (see our Spotlight rebuild guide).
Path is on Privacy. Both will return zero hits. Audit System Settings → Spotlight → Privacy.
Volume indexing is off. mdutil -s /Volumes/MyDrive will tell you. Re-enable with mdutil -i on.
The file does not actually exist where you think it does. Always worth running find ~ -name "the-name*" 2>/dev/null as a sanity check.
The daemon is rebuilding. During post-upgrade rebuilds (see our update reindex guide) both surfaces are unreliable. Wait or work around.

The command-line answer when both are broken

When neither Spotlight nor Finder will find what you want, the CLI rarely fails:

# search by content text
rg "needle" ~/Documents

# search by filename, no index required
find ~/Documents -iname "*needle*"

# search via the Spotlight index from the CLI
mdfind -onlyin ~ "kMDItemDisplayName == 'thing.md'"

# rich predicates
mdfind "kMDItemKind == 'PDF Document' && kMDItemContentCreationDate > $time.this_month"

mdfind reads the same index Spotlight reads, so if Spotlight is failing for a reason that is not index-related, mdfind will usually succeed. rg and find bypass mds entirely — slower for large trees, but immune to indexer bugs.

What a launcher with its own index changes

If you have ever wished search "just stayed working" through mds outages, you are looking for a launcher that maintains its own index. CmdSpace is one such option: a local-only Rust-backed inverted index, scoped to your user folders, built and updated by CmdSpace itself, completely independent of mds. Sub-25ms latency on a 250k-file tree on an M-class Mac. Zero outbound network calls. $29 one-time, 60-day free trial. The Spotlight-to-CmdSpace migration guide walks through detaching ⌘Space and using both surfaces together.

You do not have to pick one. The pragmatic configuration in 2026 is:

⌘Space → a launcher with its own index (CmdSpace, Raycast, Alfred — whichever you prefer).
⌘F → Finder search, for exploratory filtering inside a known directory.
Spotlight → kept around because Mail, Notes, and Photos still depend on it, but pared down to local results in System Settings.

That layering takes about ten minutes to set up and removes a whole class of "where did my file go" frustration from your week.