How Video Files Get Corrupted (And What Actually Happens)
Interrupted writes, filesystem errors, hardware failure — learn the science behind video corruption and what makes recovery possible.
Video File Anatomy
To understand corruption, you need to understand how video files work.
MP4 and MOV files are containers that hold encoded video and audio data:
┌─────────────────────────────────┐
│ MP4 Container │
├─────────────────────────────────┤
│ FTYP │ File type info │
│ MOOV │ Metadata/index │
│ MDAT │ Video + audio data │
│ ... │ Other optional atoms │
└─────────────────────────────────┘
- FTYP — Identifies the file type and version
- MOOV — The index (metadata, timestamps, frame locations)
- MDAT — The actual video and audio data
Key insight: The MOOV atom is written last. If writing stops before it completes, you get a large file with no way to play it.
Interruption During Recording
Most common cause of corruption.
What happens:
- Camera starts recording → writes to MDAT
- Recording stops → writes the MOOV index
- Interrupted here → MOOV never completes
The video data is there. The index isn't. This is why files often appear normal size but won't play.
Triggers:
- Battery dies mid-recording
- Storage fills up
- Camera overheats and shuts down
- Accidental stop
- Computer crash during capture
Storage Media Failure
Bad Sectors
Hard drives and SSDs develop bad sectors over time. When video data lands on a bad sector:
- Partial data loss — Some frames missing
- CRC errors — Data corrupted during read
- Unrecoverable sectors — Data completely lost
SD Card Failures
SD cards are particularly vulnerable:
- Wear leveling failure — Controller loses track of data location
- Factory defects — Budget cards fail more often
- Physical damage — Bent card, broken contacts
- Counterfeit cards — Fake capacity cards lose data randomly
Signs of failing storage:
- Files suddenly appear corrupted
- Slow read/write speeds
- Camera shows errors
- Files disappear or rename randomly
Transfer Errors
Copying files incorrectly causes corruption:
- Interrupted copy — Connection drops mid-transfer
- Eject during transfer — USB drive removed too early
- Network interruption — Network share disconnects
- Software crash — Copy utility fails
Safe transfer tips:
- Always use "Safely Remove Hardware"
- Verify file sizes match after transfer
- Don't transfer during system updates
- Use quality cables and ports
Filesystem Corruption
The filesystem (NTFS, exFAT, APFS) tracks where files are stored. When it corrupts:
- Lost cluster pointers — File location unknown
- Directory errors — Files appear missing or inaccessible
- Cross-linked files — Two files claim same space
Causes:
- Power loss during write
- Disk errors not addressed
- Software bugs
- Malware
Codec Mismatches
Not corruption per se, but files become "unplayable":
- Missing codec — Player doesn't understand encoding
- Corrupt codec install — System codec damaged
- Wrong extension — File renamed incorrectly
This is often fixable by:
- Installing correct codec (K-Lite, Perian)
- Renaming to correct extension
- Using VLC (plays almost anything)
What's Recoverable?
| Scenario | Recovery Chance |
|---|---|
| Interrupted recording (MOOV missing) | 70-90% |
| Partial file transfer | 40-60% |
| Bad sector damage | 20-50% |
| Filesystem corruption | 60-80% |
| Codec mismatch | 95%+ |
| Overwritten data | 0-10% |
| Physical media failure | 10-30% |
Prevention
- Quality storage — Don't skimp on SD cards
- Backup strategy — 3-2-1 rule (3 copies, 2 media, 1 offsite)
- Safe ejection — Always properly remove drives
- Monitor health — Check SMART data, test SD cards
- Record short clips — Less exposure to interruption