Make Screenshots Save Instantly, No Thumbnail

If you have a folder action, a Hazel rule, or a cloud-sync folder watching where your screenshots land, the floating thumbnail is quietly sabotaging it. macOS doesn't write the file until the preview fades — about five seconds later — so anything waiting on the file fires late or misses the moment entirely. Switch the thumbnail off and each capture is written to disk immediately, the instant the shutter closes.

The delay is a real file-write delay

The floating thumbnail isn't a preview of a saved file — it is the unsaved file, held in memory so you can drag or mark it up. macOS only commits the PNG to your save folder once the preview times out (~5 s), you click it, or you flick it off-screen. Until then, an automation watching that folder sees nothing. That's why:

• Watch-folder tools (Hazel, folder actions, custom fswatch scripts) trigger a few seconds after you'd expect.
• Cloud sync to iCloud Drive, Dropbox, or Google Drive doesn't start uploading until the delay ends.
• Scripts that grab "the newest file" right after a capture find the previous shot instead.

Turning off the thumbnail removes the holding period completely: the capture becomes a plain, immediate write.

Turn it off in the capture toolbar

1. Press Shift+Cmd+5.
2. Click Options.
3. Uncheck Show Floating Thumbnail.

Files now hit disk the moment each capture finishes, and downstream automations fire on time. This behaves the same on macOS 13 Ventura, 14 Sonoma, and 15 Sequoia.

Set it from the command line

For a scripted Mac setup or a dotfiles repo, the same preference is a single write:

# Write screenshots to disk immediately, no held preview
defaults write com.apple.screencapture show-thumbnail -bool false
killall SystemUIServer

To undo it and bring the preview (and the delay) back:

# Restore the floating thumbnail
defaults write com.apple.screencapture show-thumbnail -bool true
killall SystemUIServer

No logout is required — killall SystemUIServer reloads the screenshot service so the new value takes hold at once.

Pair it with a dedicated folder

Instant writes are most useful when they land somewhere your automation already watches. If your captures currently pile onto the Desktop, point them at a folder built for the pipeline instead — that combination gives you a clean, immediate hand-off from shutter to script.

Send the files somewhere your automation watches

Instant writes pair best with a fixed destination. See how to change where screenshots save on Mac to route every capture into the exact folder your Hazel rule or sync client is already watching.