Production · wedding film production cards and drives
wedding film production: check a backup size mismatch
Why is the backup from the wedding film production smaller than the source?
Short answer
Not necessarily a loss: folder totals report size on disk, which depends on each drive's cluster size, so a wedding backup can look smaller while every clip is complete. Compare file counts and exact byte sizes per clip instead. A clip over 4 GB missing from a FAT32 backup drive, however, is a real copy failure.
The situation
A copy exists, but byte totals or file counts do not match the recorded cards.
A smaller backup folder is not proof that footage is missing. Folder totals report space used on disk, which depends on the cluster size of each volume, so the same wedding clips can occupy noticeably different totals on card and backup drive.
01 / Diagnose
Work out what actually disappeared
Three causes explain almost every mismatch here. Allocation differences shift the total without touching a single clip. Hidden files, camera sidecars and macOS resource files are counted on one side and not the other. And a drive still formatted FAT32 refuses any file of 4 GB or more, which quietly skips the long ceremony chapters while everything shorter copies fine.
Hidden sidecars, failed large files, filters and allocation errors can all change totals. For wedding film production, this matters because the wedding film production combines several sources, takes and handoff steps that must be reconciled as a set
Check the last known path, trash and backups without writing to the original device.
02 / Protect the source
Preserve the best recovery chance
- 1
Leave both sides untouched: no deleting at the destination, no reformatting of the wedding cards until the comparison has an answer.
- 2
Produce a file list of each card and of the backup with names and exact byte sizes, including hidden files, then compare the two lists.
- 3
Check the backup drive's file system; if it is FAT32, move the backup to an exFAT or NTFS volume before copying the large chapters again.
- 4
Copy the clips that the comparison flagged straight from the card again, and verify each one by byte size after the copy finishes.
Do not accept a matching folder total as proof and format the cards on the strength of it. Equally, do not delete the existing backup to start over; while it exists, you still have two partial copies of a day nobody can shoot again.
03 / Choose the method
Match the tool to the source
For stable, readable exFAT, NTFS and FAT16/FAT32 or uncompressed IMG, DD, RAW and BIN images.
Unconfirmed exports are marked .UNVERIFIED.
Comparing and copying again needs no recovery software at all. File Recovery Hero only becomes relevant if clips were deleted from a card or drive formatted exFAT, NTFS or FAT16/FAT32; it reads no APFS or HFS+ volume and repairs no truncated clip.
04 / Verify
Check the recovered content, not just its name
The backup is sound when clip counts match per card and each clip has the identical byte size on both sides. Spot-check the longest files, usually ceremony and speeches, by playing the last seconds; a copy that stopped early ends in the middle of a sentence.
Keep the source until two verified copies exist. One working preview is not enough.
Sources and technical references
FAQ
Questions about this recovery case
Can wedding film production cards and drives be recovered in this situation?+
A smaller backup folder is not proof that footage is missing. Folder totals report space used on disk, which depends on the cluster size of each volume, so the same wedding clips can occupy noticeably different totals on card and backup drive. The result still depends on what remains readable on the source.
What should I avoid before scanning?+
Do not accept a matching folder total as proof and format the cards on the strength of it.
Does scanning write to my memory card?+
Your memory card is only read. Nothing is saved to it.
How do I know whether the result is complete?+
The backup is sound when clip counts match per card and each clip has the identical byte size on both sides.