When you plug in a camera card and drag the footage to your drive, the operating system does not guarantee that every byte arrived intact. It copies the files, reports success, and moves on. If a handful of bytes got corrupted during the transfer, you will not find out until you open the clip in your NLE and see a green frame where the hero shot should be.
Checksum verification exists to catch this before it becomes your problem.
What a Checksum Actually Does
A checksum is a mathematical fingerprint of a file. The transfer tool reads the original file, generates a hash value, copies the file to the destination, then reads the copy and generates another hash. If the two match, the file is identical. If they do not, the transfer was corrupted.
Think of it like a script supervisor checking continuity. The shot was set up a certain way, and someone verifies it matches when you cut back to it. Without that check, you might not notice the mismatch until the edit is locked and the client is watching.
The most common hash algorithms you will see are MD5, XXHash, and SHA-256. MD5 is fast but older. XXHash is extremely fast and increasingly the default in professional tools. SHA-256 is slower but cryptographically secure, which matters more for legal chain-of-custody than everyday editing work.
What Happens Without Verification
File corruption during transfer is not common, but it is not rare either. USB connections can be flaky. Card readers degrade over time. Cables get bent. Bus-powered drives can brown out during large copies. Network transfers over Wi-Fi are particularly susceptible.
When a file corrupts during transfer, the damage is usually invisible at the file system level. The file exists. It has the right name. It might even be the right size. But some frames are wrong. Maybe a few seconds of footage have blocky artifacts. Maybe the file will not play past a certain timecode. Maybe it plays fine in your media player but causes Premiere to crash when it tries to decode a specific frame.
The worst part is that by the time you notice, you may have already formatted the camera card. The original is gone, and your only copy is the broken one.
Tools That Get This Right
Professional on-set data wranglers use dedicated copy-and-verify tools for exactly this reason. The most common options:
Silverstack is the industry standard for DIT work. It copies media with full checksum verification, generates detailed reports, and handles multiple destinations simultaneously. It is expensive and overkill for a solo editor, but if you are doing on-set data management, this is what productions trust.
Hedge is the tool most freelance editors should look at. It verifies every file with XXHash, supports copying to multiple destinations in a single pass, and has a clean interface that does not require DIT training. It runs on Mac and is the sweet spot between professional rigor and practical usability.
rsync with checksum flag is the free option. Running rsync -c forces checksum comparison rather than just checking file size and timestamp. It is command-line only, which is not for everyone, but it works on Mac and Linux out of the box and is scriptable for automated backup workflows.
TeraCopy is a Windows option that integrates with Explorer and verifies file integrity during copy operations. Not as full-featured as Hedge or Silverstack, but better than a raw drag-and-drop.
Building the Habit
The overhead of verified transfers is minimal. On modern hardware, the bottleneck is the drive speed, not the hash computation. A checksum-verified copy takes maybe 10-15% longer than a raw copy. On a 256 GB camera card, that is an extra minute or two.
The workflow is simple. Plug in the card. Copy through your verification tool. Wait for the green checkmark. Only then format the card. No exceptions. Not when you are in a hurry. Not when the director is asking for a rough cut in an hour.
Make it the default behavior, and you will never lose footage to a silent transfer error.
What Comes After the Transfer
Verified transfers solve the ingest problem. But once that footage is on your drive and in your project, the next question is what happens to it over time. Projects accumulate unused clips, orphaned media, and intermediate files that were never cleaned up.
Clip Sweeper traces the chain from your timeline back to the original media files, showing you exactly what is in use and what is dead weight. Keeping your projects clean after ingest is just as important as getting the files there safely in the first place.