Offload

Standalone offload

Plug in a card, pick destinations, get verified copies and a transfer report. No project setup required.

Use Standalone Offload when you want a card or drive copied to one or more backups, every file verified, and a CSV or PDF transfer report, without creating a project or keeping those files under ongoing tracking. It is the sidebar Offload pillar.

Same fan-out engine and BLAKE3 verification as project Offload. Different ending: a result page and Export CSV / Export PDF, not a lasting project file table.

Overview

Open Offload in the sidebar. The overview lists recent and in-progress runs under Recent offloads. Statuses you will see:

Offloading
Verified
Failed
Source disconnected
Backup disconnected
Dismissed

Start a run with New offload (or Start an offload when the list is empty). The overview blurb matches the product: copy a card or drive to one or more backups; every file is verified at each destination, then left alone.

Wizard: Select Source → Destinations → Review & Start

Select Source

Breadcrumb shows Offload → New offload. On Select Source, pick where the files are (connected drive or SD chips, or This Mac). Choose the Source folder, then Continue.

Destinations

Add one or more backups: external drives, S3-compatible storage, Google Drive, and Dropbox. You need at least one. Continue when the set looks right.

Review & Start

Confirm Source and Backups, then click Start offload.

Live run

The run page shows byte-based progress, speed, ETA, and parallel progress per destination. You can pause and resume. If the source disappears, the run moves to Source disconnected until you plug the same source back in. If a backup destination drops, you may see Backup disconnected; reconnecting resumes. Full detail on Pause, resume, retry.

What happens after a standalone Offload finishes?

When the run finishes, the result page summarizes verification. Headlines include All copies verified, Offload cancelled, or that some files need attention. Per-file badges show Verified or Failed. Failed files can use Retry failed files.

Under Report available, use Export CSV or Export PDF. The report includes file names, sizes, and BLAKE3 checksums per destination. That is the record for a DIT handoff, a client, or your own archive.

What standalone does not do

After a successful standalone offload, Tusk does not keep a project that watches those files, syncs new changes, or supports restore / delete-local for them. The copies on your destinations are real files; the transfer report is your ledger. If you want ongoing tracking, offload into a project instead (From project creation or Into an existing project).

Reformat only after Verified

Wait for Verified (or All copies verified on the result page) before you wipe the card. A failed or disconnected run is not done.

The offload concept →

Standalone vs project Offload, fan-out, BLAKE3.

Into an existing project →

When you want files tracked in a project.

Pause, resume, retry →

Disconnects and retries on both Offload modes.

From project creation →