Image and video decision
Shotomatic
A competent macOS developer can reproduce the core features (timed captures, keypress automation, URL-list website captures and exports) in a few months; there are no evident durable moats and relevant open-source prior art exists, so building is realistic for a small team.
Visit website↗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.
What a replacement has to do
- Capture timed screenshots (or a list of webpages), optionally simulate keypresses between shots, store image sequence locally, and export as images/PDF/ZIP/MP4.
What it still won’t have
- Built-in license-key activation and billing via Lemon Squeezy
- Updates distribution managed while subscribed
- Polished native macOS UI and cross-device activation for up to 3 Macs
- Integrated docs/FAQ/changelog and support channels
What remains hard
- Product polish and ongoing maintenance
First-year cost
Keep paying
Paying is—cheaper in year one.
On cash alone, building overtakes the subscription at 2 seats.
Money you would actually spend
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
Build a native macOS screenshot automation app using Swift (AppKit) for UI and local orchestration plus a headless Chromium (launched locally) for website batch captures. In scope: timed screen capture (full/window/region), keypress simulation, record-and-playback click sequences to build step-by-step guides, URL-list batch capture with per-URL viewport/timing/cookie settings, local storage of captures, export to JPG/PNG, multipage PDF, ZIP packaging, and MP4 timelapse generation. Out of scope: payment/licensing infrastructure, cloud sync, multi-device activation. Include error handling for permission denial (screen recording), retries for page loads, unit tests for capture/export codepaths, and end-to-end tests for website-capture flows.
How we checked
How the score was reached
- Partly verdict base52
- An open-source build was found+5
- 5 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 · 5
Every page the run actually retrieved.
- official productShotomatic - Screenshot Automation for Mac
- official pricingShotomatic Pricing
- official docsShotomatic Features
- open sourcesw33tLie/macshot
- open sourceksnip/ksnip
Integrity checks
What held up, and what did not.
