Offload from project creation

When you come back from a shoot and there's nothing on your Mac yet, the cleanest path is to create the project and run the offload as the same operation. The new-project wizard handles both.

Local file conflicts during create-project offload

If the primary folder you picked already contains files with the same names as files on the source, Tusk catches the conflict before starting:

• Skip conflicting files: leaves the existing local files alone and skips those names from the offload (they don't go to your destinations either).
• Replace with source files: deletes the local copies first, then offloads everything from the source. Use this when the source is the canonical version. Tusk warns you before doing the deletion.

The summary at the end of the wizard shows your chosen resolution before the offload starts.

What you see while it runs

Tusk lands you on the project page. The active offload card at the top shows:

• Overall progress as a percentage of bytes copied (not files), so a single 60 GB raw clip counts correctly.
• Per-destination progress bars.
• EMA-smoothed transfer speed and ETA.
• The current file being processed.
• Pause and Cancel controls.

Files appear in the file table immediately, even before their offload completes. Each row shows In progress, then flips to Synced (copyLocally on) or Remote only (copyLocally off) once verified.

What if my Mac sleeps or restarts?

The session is fully persisted to disk. If your Mac sleeps, the offload pauses; on wake, it resumes. If you restart your Mac, the offload state is restored on Tusk's next launch and the session picks up where it stopped. No bytes re-read, no files redone.