Free while we’re in preview

Get TransferForge

Offload a card, then hand the client a manifest proving every file arrived.

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, TransferForge is included in every plan along with the rest of the range.

Getting the files across is half the job

The other half is being able to say, a year later, exactly what came off that card. TransferForge copies a shoot folder to a destination and writes a JSON manifest grouped by media type: RAW, JPEG, Video, Audio and Other, each with a file count and byte total, plus a per-file entry carrying its SHA-256 and status. All five groups always appear, including the empty ones. --client and --job are carried through exactly as typed, so the report can go out with an invoice.

Copy, read back, compare, rename

Every file is written under a temporary name. The freshly written destination file is then re-read and re-hashed, and only when that hash matches the source is it renamed into place. Nothing is ever left half copied at a real filename. A destination file that already matches is skipped, so re-running after a card got yanked mid-transfer picks up only what’s missing.

When something fails verification

That file is not left at the destination, the rest of the batch continues, and the process exits 2 so a script can tell. The report is never allowed to claim success while verify_failures is above zero. Explorer drag-and-drop panels and sync rules aren’t part of this CLI build.

Reading on the job itself

How to copy a large folder and know every file arrived Copy first, then re-read every file from the destination disk and compare its checksum against the source. ...

The rest of Verified Copy & Sync

Copying that proves it arrived. Read the copy back, move between drives, empty a card safely, and keep the proof.

CopySure

Simple Ready

Copies a tree, then re-reads every file off the disk and checks it byte for byte.

MoveGuard

Pro Ready

Moves files, then proves the copy landed intact before it deletes the original.

SyncProof

Team Ready

Copies one build to three shares at once and says which share came out bad.

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

A working CLI prototype of the client-deliverable transfer engine: the same checksum-verified, resumable copy as CopySure/MoveGuard, but producing a professional JSON manifest grouped by media type (RAW/JPEG/video/audio) with counts and sizes — a real proof-of-transfer document, not just a console log. Explorer integration and sync rules are still on the roadmap.

Naming status

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

What it draws on

Existing paid software whose best ideas shaped this program: TeraCopy Pro, Beyond Compare, SyncBackPro, Copywhiz.

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.

transferforge - checksum-verified, resumable, parallel shoot-folder transfer
with a client-deliverable JSON manifest grouped by media type.

Usage:
  transferforge transfer <src> <dst> --report report.json [--workers N] [--client NAME] [--job NAME]
  transferforge help

Flags for "transfer":
  --report PATH   Path to write the JSON transfer manifest (required)
  --workers N     Number of parallel copy workers (default 4)
  --client TEXT   Free-text client name, carried through into the report
  --job TEXT      Free-text job/shoot name, carried through into the report

Recorded from the shipped binary, not written by hand.

Windows (amd64) macOS (Apple Silicon) macOS (Intel) Linux (amd64)

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

TransferForge

Preview