Getting Started

Snapdown is a Windows 11 desktop application. Install it, make one small finding first, then export a bundle that another engineer or a coding agent can reproduce.

Written for Snapdown 1.0.0

Installation options

OptionUse it whenWhat to download or run
Setup installerYou want Snapdown installed for your Windows account.Download and run Snapdown-Setup.exe from the official releases repository.
ScoopYou manage developer tools from a terminal.Coming soon

Coming soon

Both channels are published from wiradeltaid/snapdown-releases. Prefer that repository over copies on file-sharing sites. Snapdown runs as a normal, non-elevated process; it does not need Administrator access and installs no background service.

Your first finding

  1. Open the screen you want to review

    Bring the application, browser, local build, or design into its real state. Capture is explicit: Snapdown does not record your display continuously.

  2. Start a capture

    Use the capture button in the editor or the global hotkey Alt+Shift+S. You can rebind or turn off the global hotkeys in Settings.

  3. Select the smallest useful region

    Hover a window or control to use its detected bounds, or drag a region and use the pixel loupe at the edge. Include the label, state, error, or alignment that proves the issue, and leave unrelated desktop space out.

  4. Write the observation and place a marker

    Describe the current result and the expected result. Add marker 1 beside the exact visual detail; line 1. under Marker Notes in the copied Markdown is the same marker in text form.

  5. Hand over a bundle

    Group related findings into a bundle, then copy its Markdown to the clipboard or export it as a PDF. Read the Markdown once before handing it over: it should make sense to someone who did not watch you capture it.

Make one finding about one visible fact. “The Save button is clipped at 125% display scaling; it should remain fully visible” is actionable. “Layout looks wrong” is not yet evidence.

Where Snapdown keeps data

Snapdown has no account and no cloud library. It keeps ordinary local files under your Windows user profile:

StorePathContents
Library database%APPDATA%\com.wiradelta.snapdown\library.dbSQLite database holding finding notes, marker positions, bundles, timestamps, and references to image files.
Image vault%USERPROFILE%\Pictures\SnapdownVault\ by defaultOrdinary PNG files for raw and annotated captures. The installer asks where to put the vault, and you can move it later in Settings; Snapdown moves the existing files there.

Back up both locations if the review history matters. The database records the relationships; the vault holds the image evidence. Deleting a finding or a bundle inside Snapdown is permanent: it removes the database row and the image files.

Vault maintenance

After months of reviews the vault can grow. Settings has two maintenance tools:

  • Reclaim space: shows the storage used by unsealed bundles and discarded capture states. An unsealed bundle keeps both the raw capture and the annotated version; once a review is exported or closed, Reclaim space lets you remove the old raw captures while keeping the final PNG files.
  • Orphan Report: compares the vault folder with the records in library.db and reports two kinds of mismatch: image files on disk with no database record, and database rows that point to missing files. Snapdown never deletes files silently; every action asks you to confirm.

Update policy and network access

Normal use does not need a network connection. The update check sends one unauthenticated HTTPS GET to https://wiradelta.com/api/v1/update/snapdown/, a server run by Wira Delta Indonesia behind Cloudflare. Its User-Agent header carries the Snapdown version, your Windows version, and your processor architecture. It sends no account, user name, computer name, device identifier, or telemetry. Like any request, it shows our server your IP address. The server keeps each request’s IP address, time, and User-Agent for 30 days; after that only daily counts by version, Windows version, and architecture remain, plus an estimated number of devices. The installer and Scoop builds send the same check, and GitHub does not receive it.

The check runs every 24 hours and is on by default. Turn it off with Check automatically every 24 hours in Settings > About; the Check for Updates button stays for a manual check. The check only reports that a newer version exists. The download is a separate step you start: in the installer build, Download and Install fetches the installer from GitHub Releases in wiradeltaid/snapdown-releases and compares its SHA-256 digest with the one in the manifest before running it. In the Scoop build, Snapdown downloads nothing and shows scoop update snapdown for you to run. Turning the check off does not affect capture, annotation, storage, or export. Read Privacy for the complete data statement.

Uninstall and reset

Remove the application

  • Setup installation: remove Snapdown from Settings > Apps > Installed apps in Windows.
  • Scoop installation: run scoop uninstall snapdown.

The Setup uninstaller asks whether to delete Snapdown's preferences and database (%APPDATA%\com.wiradelta.snapdown); it never deletes the vault folder. A Scoop uninstall removes only the application folder and leaves your settings in %APPDATA%. That separation keeps an update or uninstall from destroying screenshots and notes without your knowledge.

Perform a full local-data reset

Close Snapdown, back up any bundles you need, then delete %APPDATA%\com.wiradelta.snapdown\library.db and the image vault folder (by default %USERPROFILE%\Pictures\SnapdownVault\). This permanently removes the library and its images. There is no Snapdown recycle bin and no cloud copy.

If you chose a different vault in Settings, delete that folder instead of the default path. When you open Snapdown again, the library starts empty.