Drag the DCIM folder onto the desktop, wait for the progress bar, eject, hope for the best — most photographers and filmmakers have offloaded a card this way at least once. For a handful of vacation photos it's fine. For a paid shoot with no reshoot possible, it's a bet you don't need to be making.
Finder was never built to verify a copy
Finder's copy dialog tells you a transfer finished. It does not tell you the destination file is bit-for-bit identical to the one on the card. Silent corruption on card readers, USB hubs and long cables is rare but real, and a truncated or bit-flipped file usually looks completely normal in the Finder — same name, plausible file size, thumbnail that may even render. You only find out it's broken when you try to open it in your NLE or RAW converter, days or weeks later.
What "verified" actually means: ShotGrab computes a SHA-256 checksum of
every file while it copies — one read of the card, not two — then confirms the
destination matches before the file counts as safe. Nothing is renamed out of its
.shotgrab-partial holding folder until that check passes.
A pulled cable behaves differently in each tool
Unplug a card reader mid-transfer in the Finder and you're left with a partial file sitting under its final name, indistinguishable from a good one until you open it. ShotGrab copies into a temporary, clearly-marked location first and only promotes a file to its real name after verification — so an interrupted copy leaves you with nothing misleading, and reconnecting the card in an armed project mops up exactly what's missing.
Finder doesn't know what a duplicate is
Copy the same card twice — easy to do on a long day with several similar-looking cards — and Finder either overwrites silently or appends "copy" to the filename, doubling your storage for no reason. ShotGrab tracks a dedup key (filename, size, capture date and camera model) per project, so the same shot connected twice doesn't get re-copied or duplicated, and a file you deleted by hand from the archive is copied again next time instead of being silently skipped forever.
And then there's the folder you get at the end
A Finder copy is a flat dump: everything from the card lands in one folder, exactly as the camera named it. After a twelve-hour multi-camera day that's several thousand files with no separation by camera, date or client, waiting to be sorted before you can even start editing. ShotGrab places every file where it belongs — by date, camera model, project, whatever pattern you set up once — so the folder is ready the moment the copy finishes.
Where Finder is genuinely still fine
This isn't a case that Finder is broken — for a small, low-stakes transfer where you have time to manually double-check a few files afterward, it's perfectly adequate, and it's already installed. The problem shows up specifically when the volume is high, the stakes are high, or both: a wedding, a multi-camera shoot, a shoot day with a client watching over your shoulder. That's the situation ShotGrab was built for.
The short version
- ShotGrab verifies every file with a live SHA-256 checksum; Finder verifies nothing.
- An interrupted ShotGrab copy leaves a clearly-marked partial, never a silently broken "final" file.
- ShotGrab knows what it already copied; Finder duplicates or overwrites.
- Files land already organized, not in a flat dump you sort later.