AutoOffload Documentation

Start here

• Quick Start — your first offload, step by step.
• Safe Use Guide — how to use AutoOffload without ever risking your media. Read this before you format a card.
• Installation — macOS and Windows setup.
• Troubleshooting — fixes for the most common issues.
• FAQ — quick answers to common questions.
• Support — how to reach us and report a bug.

What AutoOffload does

• Verifies every copy. Each file is hashed (BLAKE3) as it's copied and re-read and checked at the destination. A copy that doesn't match is deleted and reported — it never passes as good.
• Never touches your card. Source cards are treated as strictly read-only, enforced in code. AutoOffload only reads from them; it never renames, moves, or deletes anything on the source.
• Organizes as it copies. Files are sorted by the time they were actually shot (from the photo's own metadata) into folders you control — by date, by event, or by a custom template.
• Handles many cards and destinations at once. Offload several cards in parallel, and copy to a working drive and a backup drive in a single pass.
• Lets you re-check the archive later. A manifest is written alongside your files, so weeks or months later AutoOffload can re-read the archive and prove it's still intact — or flag exactly what changed.
• Works offline. No account, no cloud, no telemetry — the only server contact is a one-time license activation. Your media never leaves your machine.

What AutoOffload does not do

So you know what to expect:

• It does not transcode, generate proxies, or play back / cull your media — it offloads, organizes, and verifies, by design.
• It does not copy to cloud storage, NAS-as-a-service, or LTO tape.
• It does not delete or format your cards for you. You verify the copy and format the card yourself, when you're ready.

Platforms

• macOS on Apple Silicon (M1 or newer) or Intel.
• Windows (installed from the Microsoft Store).