Shotcraft

Why Shotcraft

Existing tools (screenshots.pro, Bannerbear, Placid) all require uploaded screenshots. Shotcraft captures from your running app. Point it at a dev server or staging URL, give it your auth flow, and one command later you have a complete marketing screenshot set.

Six first-party templates

App Store iPhone + iPad, Play Store phone + tablet, GitHub README hero, and Open Graph / Twitter cards. Apple’s, Google’s, and GitHub’s exact target dimensions, out of the box.

Capture matches your app

Playwright drives a real Chromium against your live app. Mobile and tablet viewports, your real auth flow, your real demo data, your real chart animations.

Templates as packages

Each template ships as its own npm package. Pick what you need; build your own with a 60-line wrapper.html. Community templates use the shotcraft-template-* naming convention.

One config, every output

shotcraft.config.ts describes your screens once. Switch templates, swap themes, change captions — the capture pass adapts and the render pass produces every variant in parallel.

Quickstart

pnpm add -D shotcraft @shotcraft/template-app-store-iphone @shotcraft/template-readme-hero
pnpm shotcraft init       # scaffold shotcraft.config.ts
pnpm shotcraft doctor     # sanity-check the config
pnpm shotcraft            # capture + render end-to-end

PNGs land in ./screenshots/{template-id}/{name}-{theme}.png.

→ Full getting-started walk-through

Open source, pnpm-first

MIT licensed. Built as a pnpm monorepo so the CLI, the templates, and the hosted companion site stay coherent. Contributions welcome — see the template-author guide to publish your own templates.