For developers

You screenshotted that stack trace. Now find it.

Terminal output, API responses, config screens and error dialogs — captured constantly, and actually needed again weeks later.

Try free for 14 days

The build breaks the same way twice

You hit a build error, screenshot the terminal, work around it, move on. Three weeks later the same error shows up on a different machine and you know — you know — you have seen this exact message before.

So you open the Desktop. Four hundred files called Screenshot 2026-08-14 at 11.03.47 AM.png. You sort by date, guess a fortnight, and open a dozen at random before giving up and debugging it from scratch.

With Screenshot Inbox that's ⌥Space, then EXC_BAD, then Return. The capture appears with the matching line highlighted on the image, the full text goes to your pasteboard, and you paste it into the issue.

XcodeFileEditView100%4:32 PM
timeoutesc
$ swift build -c release
Compiling ScreenshotInboxCore (48 sources)
error: connection timeout after 30000ms
at PackageResolver.resolve(_:) line 212
host: github.com attempt 3 of 3
** BUILD FAILED **
Terminal — build failureTerminal9 Augerror: connection timeout after 30000ms
OCRQualityTool — batch run
thermal state: nominal
low power pause triggered 0 times
no timeout observed
queue drained, newest first
Xcode — Vision throughputXcode22 Julthermal state: nominal, no timeout observed
$ swift build -c release
Compiling ScreenshotInboxCore (48 sources)
error: connection timeout after 30000ms
at PackageResolver.resolve(_:) line 212
host: github.com attempt 3 of 3
** BUILD FAILED **
Copy TextCopy ImageCopy Both
↑↓ move↵ copy text⌘↵ copy image On this Mac only
The overlay opens over whatever app you're in. Type a fragment you half-remember, and the match is highlighted on the image itself — because the text inside the screenshot is real, indexed text.

What you get

Monospaced terminal text is the easy caseHigh contrast, aligned, digitally rendered — exactly what Apple Vision is best at. Line breaks are preserved, so a copied stack trace pastes into an issue looking like a stack trace.
Search that survives a typoOne character misread in a hex value or a UUID doesn't hide the capture. Exact search runs first; a bounded edit-distance pass runs when it finds nothing.
Filter by content typeAn offline classifier separates code, terminal output and error dialogs from everything else, so "show me errors from August" is two clicks and no tagging.
Never leave the editorThe overlay opens over Xcode, VS Code, or your terminal, and closes without disturbing what was underneath. Retrieval that costs a context switch is retrieval you won't do.
Extracted URLs and entitiesThe Sentry link, the docs page, the ticket number in that screenshot are pulled into structured fields — filterable, and openable without retyping.
Import the backlog you already havePoint it at Desktop and Downloads. Everything you captured before installing becomes searchable, and the import resumes if you quit halfway.

"Won't this eat my battery and my CPU?"

Recognition runs on a background queue that never blocks the interface, processes newest-first so the capture you just took is ready immediately, and pauses automatically in Low Power Mode. It's native Swift calling Apple's Vision framework — no Python runtime, no bundled inference server, no model download, nothing you'll find sitting in Activity Monitor.

Try it on your own screenshots

Fourteen days, everything unlocked, no account and no card. Import the folder you already have on day one — that's what makes the trial a fair test rather than a demo.

Try free for 14 daysBuy for $22