A screenshot app is not local or cloud. It is a chain.

A screenshot app is a chain.

Capture, OCR, licensing, history, and sharing can take different paths. The existing LazyScreenshots comparison index handles feature choice; the harder buyer question is where the data goes.

The buyer’s question is: which parts stay local, which parts leave the Mac, and what has to happen before that becomes true?

A screenshot app can capture pixels locally, run OCR locally, send an image to its own cloud only when you click Upload, send telemetry in the background, require an online activation check, and still describe itself as a local-first app.

Those are different things.

Apple’s own Screenshot tool gives us the clean baseline. Its options include destinations such as Desktop, Clipboard, Mail, Messages, Preview, or a custom folder. That documents where the capture is handed off; it does not establish an end-to-end privacy guarantee once another app or service receives the image. Apple’s Mac screenshot guide documents the capture modes, timer, destination options, and thumbnail workflow.

The third-party market adds more layers.

CleanShot says the Mac app works without requiring CleanShot Cloud. Its pricing page separates the app from Cloud: Basic includes the Mac app and 1 GB of storage, while Pro adds unlimited storage, sharing, branding, and team controls. The company says Cloud is used for screenshot uploading, not for the app’s other features. That is a meaningful distinction, but it is still a vendor description, not an independent network audit. CleanShot pricing

Shottr makes a different set of disclosures. It says the app checks for updates, needs an internet connection to validate and activate a license, and sends non-identifying telemetry that can be disabled in Preferences. Its upload terms are much more important than the word “local”: uploaded images become public to anyone who obtains the URL, and the company provides no guarantee about storage time or availability. A buyer who only reads “native Mac app” can miss the actual sharing risk. Shottr product page · Shottr terms

Snapline’s public FAQ says captures, OCR, and translation are processed on the Mac and stay there; Screen Recording is required for capture, while microphone, camera, and Input Monitoring are only requested for optional recording features. It also says paid licenses work offline after activation, while trials need periodic connectivity. The page names the permissions, offline boundary, and trial connectivity instead of collapsing them into one privacy label. Snapline FAQ

Dipshot makes a similarly narrow claim: native menu-bar capture, local processing, and no upload. CaptureBar’s App Store listing goes further, claiming “No account. No cloud upload. No tracking,” while Apple labels those privacy answers as developer-provided and unverified. The practical distinction is confidence: the buyer is reading a developer disclosure, not an independent audit. Dipshot FAQ · CaptureBar listing

So the buyer checklist should look like this.

1. What exactly does the permission unlock?

“Screen Recording” sounds broader than “take a screenshot,” but macOS uses that permission for screen capture, as Snapline’s public FAQ explains. If an app also asks for Accessibility or Input Monitoring, ask what extra capability that unlocks instead of treating every permission as part of the same capture job.

Ask for the permission-to-capability mapping. If an app requests Accessibility, what does it use it for? If it requests Input Monitoring, is that only for recording keystrokes? If the permission is denied, does the app fail clearly or produce an empty/black result?

The permission prompt belongs in the buying decision.

2. Does OCR stay on the device?

“OCR” is not a privacy policy.

CleanShot says its text recognition is on-device. Snapline says OCR and translation stay on the Mac. Snapzy publishes an open-source repository and a small synthetic OCR benchmark. Those are useful disclosures, but the buyer should still check whether translation, AI captions, QR recognition, or search indexing use a different service than basic OCR.

Ask: Does the text leave the machine, and does the app say so for every mode?

3. Is cloud sharing optional, automatic, or mixed into the default flow?

CleanShot separates local app use from optional Cloud upload. Shottr offers upload, but its terms say uploaded images become public to anyone who obtains the URL. A cloud link is not automatically unsafe, but it is a different object from a local PNG.

Look for:

• whether upload requires a deliberate click;
• whether the app creates a link automatically after capture;
• whether links can be revoked;
• whether the service promises storage duration;
• whether the image is public, unlisted, password-protected, or access-controlled.

The phrase “share instantly” should trigger more questions, not fewer.

4. What happens to the original?

Redaction is where screenshots become risky.

A blur or pixelation effect can be a visual layer. A burned-in black rectangle is a different thing. The buyer needs to know whether the original pixels remain underneath, whether annotations are editable later, and whether the exported file contains metadata.

For safe handling, redact, export a new file, reopen it, and inspect what is still selectable or recoverable. That is a test to run later with synthetic data; a marketing page cannot prove the result.

5. What is sent during licensing and support?

Shottr says it contacts its site for update checks and license validation and offers a telemetry opt-out. Xnapper says its perpetual license can work indefinitely without renewing and that updates can be renewed later. CleanShot says its one-time license includes a year of updates and can keep working without renewing them.

These are not the same model.

“Local” can still mean “activation check.” “No cloud upload” can still coexist with update telemetry. A buyer should read the license and privacy pages, not only the feature page.

6. Does the local claim cover history and search?

History is where a screenshot app stops being a camera and starts being a library.

If the app searches screenshots by OCR text, ask where that index lives. If history syncs between Macs, ask whether the image bytes sync too. If a capture is deleted from the app, ask whether it also disappears from the filesystem or cloud.

The most honest product pages say what stays local and what is exported. The vague ones force the buyer to infer the architecture.

The short version

Ask six narrower questions about a screenshot app’s boundary:

1. What does each permission unlock?
2. Does OCR leave the device?
3. Is cloud sharing optional and reversible?
4. Is redaction destructive or just a visual layer?
5. What data is sent for activation, updates, or telemetry?
6. Where do history and search indexes live?

Before buying, ask where the app’s OCR index and exported images live.