Post-transfer verification

Transfer complete ≠ transfer correct.

xfercheck independently SHA256-hashes both sides after any transfer and writes an archivable HTML integrity report. It works with rsync, Syq, scp, AirDrop — it does not care how you moved the files, only whether they arrived intact.

Join the waitlist for the Pro report export. No account needed, no spam — one email when it ships.

Why File Transfer Verification Matters Right Now

When Syq launched on Hacker News as a faster alternative to rsync, it collected 41 points and 49 comments — a comment-to-point ratio of 1.20. That ratio is the tell. People were not simply upvoting a neat tool; they were arguing about whether it could be trusted. The thread filled with the same question over and over: how do I know it did not silently corrupt my files? Speed claims are easy to make and hard to disprove, and every new transfer utility inherits that skepticism on day one.

Existing tools do not close that gap. rsync --checksum verifies while it copies, but its output is a scrolling terminal log that disappears when you close the window. It gives you no artifact you can hand to a client, attach to a delivery ticket, or reopen six months later when someone asks whether the archive was intact. hashdeep and md5deep produce raw hash dumps with no comparison, no transfer semantics, and no readable report. TeraCopy bundles verification into the copy action itself, so it cannot check files you already moved, and it is Windows-only. GoodSync is heavier and priced for enterprise backup, not for the photographer who just finished a shoot.

The timing is what makes this worth building now. Every new transfer tool — Syq today, something else next month — creates a fresh wave of users who need independent proof that their data survived the trip. Verification is the layer nobody wants to own because it is unglamorous, yet it is the one thing that turns a fast copy into a defensible delivery. xfercheck does not compete with your transfer tool. It sits after it, hashes both directory trees, and hands you the evidence.

How It Works

Three steps, no configuration files, no accounts, no cloud upload.

1

Move your files with whatever tool you already use

Run rsync, Syq, scp, rclone, or drag files onto a mounted drive. xfercheck never touches the transfer itself, so it adds no risk and no speed penalty to the copy you already trust.

2

Point xfercheck at both directories

Run xfercheck src/ dst/ and it walks both trees in parallel, computing SHA256 hashes for every file and comparing size, path, and digest to find missing, truncated, or silently corrupted entries.

3

Read, archive, or forward the report

You get a single self-contained HTML file plus a JSON manifest listing matched files, mismatches, and files modified mid-transfer. Open it in any browser, email it to a client, or store it as delivery evidence.

What You Get

Tool-agnostic verification

xfercheck does not replace your transfer tool and does not require it to support checksums