
Two-destination camera card offload
Make two copies.
Prove every byte.
Confirm a camera-card folder, copy every regular file to two genuinely distinct destination volumes, re-read both copies with SHA-256, and export a receipt that keeps partial outcomes honest.
Inside the actual app
The offload state stays visible.
The native workspace separates the source inventory, destination preflight and file-level evidence. It never turns a partial copy into a green badge just because most files arrived.
Built for the real handoff
One focused app.
Four jobs done.
Solo photographers
Create two checked copies before leaving a location without adopting a production-management suite.
Photo assistants
Hand the photographer or producer a file-level receipt that explains exactly what completed.
Small creative teams
Standardize a local ingest step while keeping source media and copy destinations under team control.
Interrupted field work
Cancel deliberately and resume from re-hashed existing files instead of restarting every completed copy.
offload-receipt.pdfoffload-receipt.jsonoffload-manifest.jsonMANIFEST.sha256Private by defaultA clear workflow
From first record
to finished handoff.
Select and confirm the source
Choose the mounted-card folder, inspect its regular-file inventory and type the source name exactly before OffloadProof can start.
Prove both destinations
Select two writable locations. OffloadProof checks volume identities, source overlap, capacity, path collisions and a safety reserve.
Copy, re-read and resume safely
Files move into product-owned job folders. Cancellation leaves completed files available, but a resume only trusts an existing file after a fresh size and SHA-256 check.
Export the handoff evidence
A job is verified only when both destinations contain every expected hash. Export PDF, Markdown, JSON and portable manifest evidence for verified or partial work.
Focused by design
Useful depth.
No account clutter.
Immutable source inventory
Inventory regular files and record SHA-256, size and relative path without modifying the selected source folder.
Real volume independence
Compare source and destination volume identities so two folders on the same drive cannot masquerade as redundant copies.
Capacity and path preflight
Check available space, writability, source overlap and case-folded path collisions before creating a product-owned job folder.
Verified resume
Reuse a completed destination file only after re-reading its size and hash; replace corrupt existing bytes instead of assuming they are good.
Per-destination failure states
Keep missing, mismatched, failed and source-changed outcomes visible for each destination. Partial never means verified.
Portable receipt bundle
Write readable and structured receipts, a per-file two-copy manifest and hashes for every generated artifact into a new folder.
Practical guides
Start with the job
you need to finish.
Questions, answered
OffloadProof FAQ
What does OffloadProof copy?+
You choose a camera-card folder and manually confirm its name. OffloadProof inventories regular files, records skipped symbolic links, hashes each file with SHA-256 and leaves the selected source untouched.
Are two folders on the same drive considered two copies?+
No. Both destinations must report different volume identities, and neither may match the source volume. Two paths on one volume never pass the independence preflight.
When does a job become verified?+
Only after every inventoried regular file has been copied to both destinations, re-read there and matched to the source SHA-256. A missing, failed, changed or mismatched file keeps the job NOT VERIFIED.
Can an interrupted offload resume?+
Yes. OffloadProof keeps completed files inside its product-owned job folders. On the next run it counts a file as resumed only after re-reading its size and SHA-256; a corrupt existing file is replaced and verified again.
What is included in the handoff receipt?+
The export bundle contains PDF, Markdown and JSON receipts, a portable per-file manifest, an export receipt and a SHA-256 manifest for the generated artifacts. Partial runs can be exported, but remain clearly NOT VERIFIED.
Does OffloadProof erase cards, format drives or upload files?+
No. It does not delete or format the source, upload files or promise protection from underlying hardware failure. It writes only to product-owned job folders on destinations you select and to the receipt folder you choose.
Is OffloadProof right for every production shoot?+
Not yet. The current native MVP has deterministic fixture coverage and a verified local workflow. Physical camera cards, independent destination drives, Developer ID signing, notarization and broader release QA remain launch gates.
How much will OffloadProof cost?+
The price is US$39 as a one-time purchase for one Mac, with no subscription. Secure checkout and DMG delivery are handled by Polar.

OffloadProof for macOS
Make two copies.
Prove every byte.
A focused local ingest desk for photographers who need evidence of two matching copies—not card erasure, cloud storage or an unsupported hardware guarantee.
- macOS 14+
- One Mac
- Launch updates included
Signed with Developer ID and notarized by Apple.