Tusk is a Mac app that automatically backs up your project folders to multiple locations and tracks where every file lives — even when your drives aren't connected.
On a large production, a Digital Imaging Technician (digital imaging technician) sits at a cart and makes sure every frame shot that day exists in at least two verified places before anyone touches a card. On your shoot, that job belongs to you. Same responsibility, no cart, and usually a MacBook balanced on a road case.
The workflow itself is short: offload every card to at least two destinations, verify every file with a checksum, export a record of what you copied, and wipe nothing until verification passes. Everything else about data wrangling is detail on top of those four steps.
This guide walks through the shoot-day workflow and the software that runs it on a Mac, from full DIT stations like Silverstack down to what a solo shooter actually needs.
TL;DR: Shoot-day data wrangling means offloading every card to at least two destinations, verifying every file with a checksum, and wiping nothing until verification passes. Tusk streams a card to all destinations in one read, verifies each file with BLAKE3, and exports a CSV or PDF checksum report you can hand to a client or editor. It does not do MHL reports or LTO tape, so it's built for solo shooters and small crews, not enterprise DIT carts.
What Does a Data Wrangler Actually Do?
Data wrangling is the custody chain for footage between the camera and the edit. The data wrangler offloads camera cards to backup storage, verifies that every copy is intact, logs what was copied where, and clears cards for reuse. On set, this person is the reason a wiped card is never a catastrophe.
A DIT does that plus image work: monitoring exposure, applying LUTs, generating proxies, prepping dailies. On productions with budget, these are separate roles with dedicated software. On a two-person shoot, both jobs collapse into whoever owns the laptop.
That distinction matters when you pick software. Most "DIT software" is priced and designed for the full cart role. If your actual job is the custody chain (copy, verify, log, wipe), you need a much smaller tool than the category suggests.
The Shoot-Day Workflow: Offload, Verify, Report, Wipe
Step 1: Offload Every Card to Two Destinations
One copy is not custody. Right after a shoot, your footage exists only on the card, and the moment you copy it to a single drive you've moved the risk instead of removing it. Backblaze's drive statistics put the average annual failure rate across nearly 300,000 monitored drives at 1.57% in 2024, under data-center conditions. A drive in a backpack on a shoot day does not live under data-center conditions.
Two destinations before the card gets wiped is the floor. Two SSDs, or one SSD plus cloud storage if the venue has real upload bandwidth. Your Mac's internal drive can be one of them, but it doesn't have to be: good offload software streams from the card directly to external destinations, reading the card once and writing everywhere at the same time.
For the full picture of copies and locations beyond shoot day, the 3-2-1 rule for video projects covers where those copies should eventually live.
Step 2: Verify Every File With a Checksum
A checksum is a fingerprint of a file's exact contents. Offload software computes it while reading the card and again for each written copy. Matching fingerprints prove the copy is intact. A mismatch means the transfer failed somewhere, and you find out now, on set, while the card still exists.
This is the step Finder skips, and it's the whole reason dedicated offload tools exist. A corrupted transfer looks identical to a successful one in Finder: right file name, right file size, unplayable clip. You'd discover it in the edit, weeks after the card was reformatted.
Tools differ in which algorithm they use (xxHash, MD5, and BLAKE3 are all common), but any of them catches silent corruption. What matters is that verification runs on every file, on every destination, every time. Not as an option you enable for important shoots. Every time.
Step 3: Export a Transfer Report
The report is the artifact that makes your work provable. It lists every file, its size, and its checksum per destination, so the editor, the client, or you in six months can confirm the footage that arrived is the footage that left the card.
On productions, this is a formal deliverable, often as an MHL file (Media Hash List), a manifest format that post-production software can re-verify against. If a client contract says "MHL deliverables," that word choice decides your software for you.
For small crews, the report matters for a more ordinary reason: handoffs. Sending a client a PDF listing every clip with verified checksums answers "did you get everything?" before it gets asked. It also settles the six-months-later question of which card a clip came from.
Step 4: Wipe Cards Only After Verification Passes
The card gets reformatted only when every destination reports verified copies. Not when the progress bar hits 100%, not when the folder sizes match. Verified.
The same rule applies later to your Mac. When you clear local copies to free up space after the shoot, the check should be identical: is every file confirmed on every backup destination? If your software can't answer that question, you're deleting on faith.
What DIT Software Runs on a Mac?
Four tools cover most of the Mac DIT and offload space in 2026, at very different sizes:
Silverstack is the full DIT station: cascade copies, proxy generation, audio sync, metadata handling, and ASC MHL support. Silverstack XT runs 799 EUR per year as a subscription. It earns that on carts managing dozens of cards a day. It is a lot of software for one person with two cameras.
ShotPut Pro ($169 one-time) is the offload specialist productions have used for years. Its signature feature is automatic reporting: enable PDF in preferences and every offload produces a report with a file manifest, timecodes, and thumbnails, no extra step. It also generates MHL files.
OffShoot (formerly Hedge, $169 one-time) is the fast, minimal option: drag source, pick destinations, go, with checksum verification on every transfer and production reports you generate from transfer logs at handoff.
Tusk ($79 one-time, or $49 during the current launch offer) does the verified multi-destination offload with CSV and PDF checksum reports, then keeps tracking your footage after the shoot. The next section covers where it fits and where it doesn't.
We compared the first three in depth in OffShoot vs ShotPut Pro vs Silverstack if the choice is between those.
Where Tusk Fits (and Where It Doesn't)
Tusk's offload is built around the same shoot-day loop. In the sidebar, open Offload and start a new offload: pick the card as the source, pick your destinations (external drives, S3, Google Drive, or Dropbox), review, and start. Tusk reads the card exactly once and streams to all destinations in parallel, computing a BLAKE3 checksum for every file during the transfer. Nothing has to touch your Mac's internal drive unless you add it as a destination.
When the run finishes, the result page shows per-file verification and tells you plainly: all copies verified, you can safely remove the files from your card or drive. From there, Export CSV and Export PDF produce the transfer report: every file name, size, and BLAKE3 checksum, per destination. The PDF is the one you send to a client or editor as the handoff record. The CSV is the one you keep, grep, or archive with the project.
Later, when the job is delivered and you want the footage off your Mac, Tusk's delete preflight runs the same logic in reverse: it physically re-verifies that every file exists on every connected backup destination and blocks the delete if anything is missing or unverified. Clearing space stops being a judgment call.
Now the honest part. Tusk does not generate MHL files. Its CSV and PDF reports carry the same core information (files, sizes, checksums per destination), but they are not a manifest format that Silverstack or post-production tools can automatically re-verify. Tusk also has no LTO tape support, and none of the image-side DIT work: no proxies, no LUTs, no audio sync, no metadata handling.
So the line is easy to draw. If your productions contractually require ASC MHL deliverables or archive to LTO, you need Silverstack (or a dedicated tape tool like YoYotta or Canister), and Tusk is not a substitute. If you're a solo shooter or a small crew doing your own data wrangling, and the job is verified copies plus a report a human reads, Tusk covers the shoot-day loop at half the price of the offload specialists.
After the Shoot: The Part Offload Tools Skip
Every tool above gets footage off the card safely. Then the card comes out, and most of them are done. What no offload report tells you is where that footage is eight months later, when the client asks for a re-export and you're staring at a shelf of unlabeled SSDs.
This is the part Tusk is actually built around. It tracks every file by content across all your destinations, whether the drives are plugged in or not. Open the project and the file table shows each file's status per destination: which drive holds it, whether the cloud copy is verified, what's safe to delete locally. The shoot-day offload becomes the first entry in a record that persists for the life of the project.
If your Mac is perpetually full of last month's shoots, freeing up space without losing footage shows that side of the workflow.
A Data Wrangler's End-of-Day Checklist
Before you leave the location or go to sleep, every card should pass this list:
- Every card is offloaded to at least two destinations.
- Every file shows verified checksums on every destination, not just a finished progress bar.
- The transfer report is exported and stored with the project (and sent, if someone is waiting on a handoff).
- Cards are physically separated from the drives holding their copies. One bag should never contain the only two copies of anything.
- Cards get reformatted in the camera, and only the ones whose verification passed.
If a step fails, the card stays untouched until it's resolved. A full card is an inconvenience. An unverified wipe is permanent.
FAQ
Data wrangling is managing the custody chain for footage between camera and edit: offloading camera cards to backup storage, verifying every copy with checksums, logging what was copied where, and clearing cards for reuse. On large productions it's a dedicated role. On small shoots, it's whoever owns the laptop.
A data wrangler handles data custody: offloading, verifying, logging, and wiping cards. A DIT (digital imaging technician) does that plus image work such as exposure monitoring, LUTs, proxy generation, and dailies. On small crews one person usually covers both, which is why lighter tools can be a better fit than full DIT software.
It depends on the size of the job. Silverstack XT (799 EUR/year) is a full DIT station with proxies, metadata, and ASC MHL support. ShotPut Pro and OffShoot (both $169) are offload specialists with checksum verification and reporting. Tusk ($79) does verified multi-destination offloads with CSV and PDF checksum reports, and additionally tracks your footage across drives and cloud after the shoot.
No. Tusk exports transfer reports as CSV and PDF, listing every file with its size and BLAKE3 checksum per destination. Those reports are for humans (clients, editors, your own records), not a machine-readable manifest that post-production software can automatically re-verify. If a production contractually requires ASC MHL deliverables, use Silverstack or ShotPut Pro.
Only after every file has verified checksums on at least two separate destinations. A finished copy is not the same as a verified copy: a transfer can fail silently and still show the right file names and sizes. Checksum verification is the only confirmation that the copies are intact, and until it passes, the card is the only trustworthy copy you have.
No. Offload software like Tusk streams directly from the card to multiple destinations at once, reading the card a single time. Your Mac coordinates the transfer but doesn't need to store the footage. That matters on shoot days, since a laptop's internal drive is usually the smallest disk you're carrying.