Design and diagrams decision

Xnapper

A capable developer can build the core screenshot+editor features, but matching the shipped app's distribution, licensing, polish, and support (and multi-device team billing) is more work; consider buying unless you only need a narrow self-hosted tool.

Visit website

Built by Tony Dinh, who ships 3 products in this index

You pay

$5/mo

$60/yr

Per seat. Read off the official pricing page.

You’d pay instead

$100one-off54 h to build

$0/mo1 h/mo upkeep

On cash alone, building overtakes the subscription at 2 seats.

Open-source builds that already do this

Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need - the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship. All Xnapper alternatives, with the arithmetic →

What a replacement has to do

  • Capture screen → annotate/redact → export/share

What it still won’t have

  • Polish and macOS-native UX/animations from a shipped commercial app
  • License Manager and Paddle-based payments/renewals integration
  • Ongoing product support, marketing, and existing user base
  • Cross-device license convenience and built distribution channels

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

Keep paying

Paying is—cheaper in year one.

On cash alone, building overtakes the subscription at 2 seats.

Paid seatsseats

Money you would actually spend

Keep paying
—

Subscription price × seats × 12

Build it
—

AI build —APIs + hosting —

Time you would spend

—

—

What you would spend

What we assumed

The verdict above measures whether you could build it. This one is only about money.

Runnable build prompt

Not run yet
Build a minimal macOS screenshot app in Swift/SwiftUI (macOS 12+) that captures region/window screenshots, provides an image editor with crop, arrows/shapes/text, blur redact, and export presets; integrate on-device OCR via Vision to detect selectable text and a single-click redact suggestion; include a preferences pane and simple license activation screen (local license key validation). Out of scope: server-side license manager, payment processing, team device management, advanced animation polish, cloud upload. Include unit/UI tests, error handling for permission denial (screen recording, accessibility), and an automated notarized build script.
How we checked4 sources · 3/3 runs agreed · evidence score 67

How the score was reached

  • Partly verdict base52
  • An open-source build was found+5
  • 4 cited sources+3
  • Price verified on pricing page+3
  • 3/3 assessment runs agreed+4
  • Evidence score67

The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.

How scoring works →

Cited sources · 4

Every page the run actually retrieved.

Integrity checks

What held up, and what did not.

✓ Price read off the page✓ 3 independent runs, one answer✓ Citations limited to fetched pages! 1 moat recorded