Tusk Logo

Tusk

Always know your files are backed up

C0001.MP4

C0002.MP4

C0003.MP4

C0004.MP4

Back up files to multiple destinations at once and always know what's where — so you can free up space on your Mac without the anxiety.

I have a whole sports bag of SSDs. Finding a past shoot used to mean plugging them in one by one. Now I just open Tusk.

Why Tusk

Backup you can actually trust.

Tusk

  • Always know where every file is — even when drives are unplugged

  • See backup status per file and per destination, in real time

  • Automatically syncs every file change in the background

  • Free up local space confidently — Tusk blocks deletion until files are fully backed up

  • Restore any file with one click from any destination

Traditional backup tools

  • No idea what's on a drive until you plug it in

  • No visibility until something goes wrong

  • Manual triggers — easy to forget, easy to skip

  • Delete locally and hope for the best

  • Dig through folders on a plugged-in drive to find anything

SEE IT IN ACTION

Watch how it works.

Tusk works with almost any workflow — it watches your folder and propagates every change forward automatically.

Tusk - See it in action
Tusk demo walkthrough. This video shows how a user creates a project from a local folder, selects backup destinations such as local storage, Google Drive, or S3, starts syncing immediately, sees file-level backup and verification status, safely deletes local files only after backup, and restores files later on demand. The workflow is designed for large media projects such as video production.

Every workflow is different.

See guides for your setup →

Quick facts

FAQ

Questions worth asking.

Time Machine backs up your whole system. Backblaze runs in the background but gives you no per-file visibility. ChronoSync can't tell you where a file is when the drive is unplugged. Tusk is purpose-built for project files — per-file, per-destination status, automatic background sync, and full drive tracking whether your drives are connected or not.

One-time purchase. You pay once and own it — no monthly fees. The regular price is $79. We're currently running a launch offer at $49, which includes one year of updates. Try it free for 14 days, no credit card required.

Yes. Once you set up a project, Tusk watches your folder and syncs every change automatically — no manual triggers, no scheduled runs. You just work. Tusk keeps up. If you shut Tusk down, it will automatically resume syncing when you start it back up.

Tusk supports external drives (SSDs, HDDs, and SD cards mounted as volumes), Google Drive, and Amazon S3-compatible object storage — including Backblaze B2, Wasabi, and AWS S3. You can connect multiple destinations to the same project and Tusk syncs to all of them in parallel. Every file transfer is verified with a BLAKE3 checksum before the source is considered safe.

Your files are always just files — stored on your drives and cloud accounts in their original format. Tusk doesn't lock anything up in a proprietary format. If you stop using Tusk, your backups are still there exactly where you left them.

Yes — that's one of the things Tusk was built for. Every file's location is indexed, so you can always see which drive or cloud destination holds a copy, even when nothing is plugged in. When you're ready to restore, connect the drive or pull from the cloud and Tusk handles the rest.

If you delete a file through Tusk, it checks that the file is fully verified on all backup destinations first — and blocks the deletion if it isn't. Tusk also watches your project folder directly, so any rename, move, or edit you make in Finder or your app is automatically picked up and propagated to your backup locations. The one thing Tusk never does is delete files from your backups — even if you delete them locally. Your backup destinations are always additive.

Tusk syncs in the background and throttles automatically when your Mac is under load. It runs as a menu bar app and stays quiet during active editing sessions. Background jobs pause automatically during SD card ingest so transfers finish as fast as possible, then resume when ingest is done.