Filters and smart collections

Updated 1 September 2026

Filters work with or without a search query. Often the fastest way to find something is to stop typing and start narrowing.

Available filters

Source app — which application was in front when you took the capture. This is recorded from window metadata at the moment of capture rather than guessed from the pixels afterwards, which is why it’s reliable enough to filter on.

Date range — a preset or a custom range.

Tag — tags you’ve added by hand, plus automatic ones.

Content type — code, terminal, error, receipt, chat, article or UI, assigned by an offline classifier.

Has a URL — captures with a web address in them.

Entity — captures containing an email address, an amount, a date or a tracking number.

Sensitive content — captures where something API-key-shaped was detected. Useful before sharing, and see Redaction.

A note on captures taken while the app was closed

Screenshots ingested during a catch-up scan have no source app recorded, on purpose. The app was not running when they were taken, so it cannot know what was in front — and attributing them to whatever happened to be frontmost at launch would be a plausible-looking lie.

They’re searchable by every other filter.

Smart collections

Any combination of search terms and filters can be saved as a smart collection. It appears in the Library’s left rail and stays live: new captures that match show up in it automatically.

They behave like folders and cost nothing to maintain, because they aren’t folders — a capture can be in any number of them, and nothing is moved or copied.

Useful ones people set up:

Tags

Select captures in the Library and add a tag from the context menu. Manage Tags renames and deletes across the whole library — deleting a tag removes the tag, never the screenshots.

Automatic tags come from the classifier and appear alongside your own. They’re distinguished visually so it’s clear which are yours.


Didn't answer it? Write tosupport@screenshotinbox.com — one person reads it, and questions that land here twice become a new page.