Spotlight problems

When new files are invisible to search

Updated 2026-07-31 · 3 min read

You saved it thirty seconds ago and search denies it exists. Usually a delay, occasionally something else.

The normal delay

Spotlight indexes new files within seconds to a minute under ordinary conditions. Under load — a large copy, a build, a sync — it can be considerably longer.

Force one file to be indexed immediately:

mdimport /path/to/newfile.pdf

Then confirm it landed:

mdfind -name newfile

When it never appears

The location is excluded. Saved into ~/Library, inside a package, or a folder on the Privacy list.

The app wrote it atomically. Many apps save by writing a temporary file and renaming it. That is correct behaviour and occasionally confuses indexing; mdimport on the final path resolves it.

The volume is not indexed. Common on exFAT external drives:

mdutil -s /Volumes/DriveName

The index is mid-rebuild. Everything is unreliable until it finishes.

Why this is more annoying than it sounds

The moment you most want to find a file is right after creating it — an export, a download, a render. A search tool that is a minute behind is useless at exactly the moment you reach for it.

This is what filesystem change notifications solve: FSEvents reports the write as it happens, so an index built on it has the file before you have finished switching windows. A file saved a second ago being immediately findable is not a small difference in practice; it is the difference between trusting search and checking Finder instead.

Common questions

How long does Spotlight take to index a new file?

Usually seconds. Under heavy disk activity it can be much longer.

Can I force Spotlight to index one file?

Yes — mdimport /path/to/file.