Screenshot to Documentation

DocSnap

Twenty ticket screenshot folders in, twenty step-by-step docs out, one command.

Free right now — no account, no card

Get DocSnap free Windows & Mac · one file, nothing to install

Preview

1 interface design, then a screenshot of it running. Drag, scroll or use the arrows.

Interface design DocSnap, 1 of 1
Screenshot DocSnap running on Windows today

Free while we’re in preview

Get DocSnap

Twenty ticket screenshot folders in, twenty step-by-step docs out, one command.

The Mac button is for Apple Silicon. On an older Intel Mac, get this one instead.

One file, both ways. Double-click it for the window. Run the same file from a command prompt with arguments and it behaves as the command-line tool, because the engine is inside it. Nothing else to download and nothing to keep beside it.

Early preview. The window has been built and run, but not yet on a real Windows PC or Mac, so expect rough edges. The engine underneath it is fully tested.

  • One file — no installer
  • Runs on your machine, offline
  • Source code published below

Free while in preview. It isn’t signed yet, so Windows or macOS will ask you to confirm the first time you open it. At launch, DocSnap is included in every plan along with the rest of the range.

You took the screenshots during the ticket. They’re in a folder called 4471, named 01-login.png through 09-done.png. DocSnap reads that folder, reads a captions.txt beside them if you bothered to write one, and produces a Markdown document with one numbered step per image.

Why it’s a command and not a window

Give it twenty folders on one line and twenty documents come back, each named after its folder, with a summary of how many steps it found and how many captions matched. One folder per ticket, one per test case, all in one go. If you’d rather drag images into a browser and caption them one at a time, that’s SnapDocs, the sibling app.

Nothing is required except the images

A screenshot with no caption line still becomes a step. No captions.txt at all is fine too. Only an empty folder counts as a mistake, because that usually means you pointed at the wrong path. validate reports what’s still uncaptioned without writing anything.

Images are linked by relative path, so the docs need to live next to the screenshots. --html gets you a styled HTML copy alongside.

Reading on the job itself

Advanced & technical details Command-line builds, source code, checksums and a recorded session — for developers and IT teams

A working CLI prototype of the batch doc-assembly engine: point it at many screenshot folders with a simple captions.txt sidecar and it generates Markdown/HTML docs for every one in a single headless invocation — the scriptable, bulk counterpart to the sibling SnapDocs browser app. Live capture, scrolling capture, OCR, and annotation are still on the roadmap.

Naming status

Working name only — brand verdict **AVOID** (Very High). Collision: DocSnap. Rename completely.

What it draws on

Existing paid software whose best ideas shaped this program: Snagit, Screenpresso Pro, FastStone Capture, ClipboardFusion Pro.

Command line

There is nothing extra to install. The program you download is the command-line tool as well: give it arguments instead of double-clicking it and it runs as one, with its output on your terminal. The standalone builds below are the same engine on its own, for machines where you would rather not ship a window at all.

DocSnap - batch, headless documentation generator from screenshot folders

Usage:
  docsnap build <folder> [<folder> ...] --title "Doc Title" [--out-dir dir] [--html] [--sort name|mtime]
  docsnap validate <folder> [<folder> ...]
  docsnap help

Commands:
  build      Generate Markdown (and optionally HTML) docs from folders of
             screenshots plus an optional captions.txt sidecar file.
  validate   Report which screenshots are missing captions, without
             generating any files (read-only, QA-oriented check).

Run 'docsnap build -h' or 'docsnap validate -h' for command-specific help.

Recorded from the shipped binary, not written by hand.

Source

Every file the program is built from:

console.go · console_test.go · guided.go · main.go

SHA-256 checksums · build instructions & scope notes · full build plan