Troubleshooting AutoOffload

My card or drive doesn't appear

• Make sure the card or drive is fully seated in the reader and the reader is connected directly (try a different port or a powered hub).
• Confirm the volume is mounted by your operating system: it should show up in Finder (macOS) or File Explorer (Windows). If the OS can't see it, AutoOffload can't either — the card or reader may be faulty.
• AutoOffload treats very large volumes (roughly 1 TB and up) as fixed drives rather than cards, so a big external drive may show as a destination instead of a card.
• Try ejecting and reinserting the card. AutoOffload re-detects cards automatically.

"Permission denied" or AutoOffload can't read/write

This almost always means the operating system hasn't granted file access yet.

• macOS: open System Settings → Privacy & Security → Files and Folders (and Removable Volumes) and make sure AutoOffload is allowed. The first offload triggers these prompts — click Allow. You may need to re-launch the app after granting access.
• Windows: open Settings → Privacy & security → File system and confirm AutoOffload may access your drives and folders.
• Make sure your destination isn't a read-only or locked location. Pick a folder you own (an external drive, Desktop, Documents, etc.).

The offload stopped, failed, or was interrupted

Your files are safe — AutoOffload never leaves a half-written file posing as a good one.

• Check the on-screen summary: failed files are listed individually, and your cards stay mounted.
• Just run the offload again. AutoOffload recognizes files already copied (by checksum) and copies only what's missing — so re-running resumes where it left off.
• If a specific file keeps failing to copy or verify, the source card may have a bad read on that file. Keep the original card until you've recovered that file, and try a different card reader or port.
• Do not format the card until you get a clean, fully verified run.

"Files already exist" at the destination

AutoOffload never overwrites your files by accident. When a file with the same name is already there, it follows the duplicate-handling setting you chose:

• Skip — if the existing file is byte-for-byte identical (same checksum), it's recognized and skipped. This is what makes re-running an interrupted offload safe.
• Keep both — a differing file is copied alongside the existing one with a new, numbered name, so nothing is lost.

If two cameras produced the same filename (e.g. two DSC0001.ARW), AutoOffload detects the collision and numbers them apart automatically — neither is overwritten.

The destination drive is full

AutoOffload runs a free-space check across every destination before it copies a single byte, so a run won't fill a disk halfway through — it tells you up front if there isn't room. If you hit this:

• Free up space, or choose a different / additional destination, then start again.
• Remember each destination needs room for the whole selection.

The transfer is slow

• Offload speed is limited by the slowest link: the card reader, the cards themselves, and the destination drive (and its connection). A slow USB hub, an old reader, or a nearly-full mechanical drive will all cap throughput.
• Connect the reader and destination drive directly rather than through a chain of hubs or adapters.
• Copying to multiple destinations is pipelined so total time tracks your slowest disk, not the sum of them — but a slow backup drive still sets the pace.
• The optional final verification pass (a full re-read of the destination after copying) roughly doubles read time on large offloads. It's off by default; leave it off unless you specifically want that extra proof before wiping cards.

macOS says the app is "from an unidentified developer"

AutoOffload is notarized by Apple, so this is rare. If you see it:

1. Right-click (or Control-click) the AutoOffload app and choose Open, then confirm in the dialog; or
2. Open System Settings → Privacy & Security, find the AutoOffload message, and click Open Anyway.

You only need to do this once.

Windows blocks the install or asks for confirmation

Installing from the Microsoft Store means Windows has already vetted the app, so you shouldn't see a SmartScreen warning. If a non-Store copy triggers "Windows protected your PC," prefer the Store version. If you must proceed with a trusted build, click More info → Run anyway.

Where are the logs?

AutoOffload writes local log files (they never leave your machine). Include them when you contact support:

• macOS: ~/Library/Logs/AutoOffload/
• Windows: %LOCALAPPDATA%\AutoOffload\Logs\

In addition, every offload writes a CSV manifest and an HTML report inside a hidden _autooffload folder next to your copied files — these show exactly what copied and what verified for that run.