A video file is two things: an index and a stream
Every MP4, MOV, or similar video is really two things sharing one file. The first is the stream: the compressed audio and video frames, in one long block that makes up almost the entire file size. The second is the index: a small table that tells the player where every frame starts, how long it lasts, and how the audio lines up with the picture. The wrapper that holds both is called the container. For MP4 files, the index is a block named the moov atom.
The usual shape of a “corrupted” video: the big block of footage survived; the small index didn't.
This split explains almost everything about video corruption. A player that can't find a valid index refuses to open the file at all, even when 99% of the bytes (the footage itself) sit there intact. Repair is possible because a map can be rebuilt; territory that was never written cannot. Damage to the stream itself, the actual frames, is the rarer and more serious case. For a byte-level tour of how the container and index work, see MP4 anatomy: the moov atom.
The five real causes
Lists of "reasons your video is corrupted" tend to pad out to fifteen entries. In practice there are five mechanisms, each with a recognizable fingerprint.
1. The recording was interrupted
A camera battery dies mid-clip. A drone hits a tree. OBS crashes two hours into a stream recording. Each time, the same thing happens: the index of an MP4 is written only when the recording is finalized, at the moment you press stop. Interrupt the recording, and the footage is on the card but the index never gets written. The file won't open anywhere, and tools like ffmpeg report "moov atom not found". This is the single most common cause of unplayable video, and the most repairable one: the data survived, and only the map is missing.
2. The transfer was interrupted
Copying files off an SD card and pulling the card early. A download that silently stopped at 80%. A cloud sync that gave up on a hotel Wi-Fi connection. The result is a truncated file: the front is intact, the tail is simply absent. A 4 GB clip that arrives as 2.9 GB is the fingerprint. What's salvageable is exactly what arrived: a repaired file plays up to the cut and no further, because the remaining footage isn't damaged, it's elsewhere. Always check the source device first.
3. The storage is failing
Flash memory wears out; hard drives develop bad sectors. When storage starts failing, bytes read back wrong or not at all. Unlike the first two causes, the damage can land anywhere in the file, including the middle of the stream. The fingerprint: a video that opens but glitches, freezes, or dissolves into blocky artifacts at a specific point, or a card where several files went bad at once. Repair can rebuild structure around the damaged region, but frames stored on dead sectors are gone. Multiple corrupted files on one card is a hardware symptom, so stop writing to that card.
4. The file came out of data recovery
Files that recovery software "got back" from a formatted card or deleted folder are a category of their own. Recovery tools often reassemble files by pattern-matching raw storage, and on a fragmented drive they can stitch together pieces that never belonged to the same file: right name, right size, wrong bytes. Some recovered videos repair beautifully; some contain another file's data entirely. This case is common enough that we wrote a separate guide on why recovered files won't open.
5. The software wrote it wrong
The least common cause, but real: bugs in the program that created the file. An encoder writes timestamps that drift, a muxer miscounts frame offsets, an editing app exports a container that technically violates the spec. The fingerprint is a file that plays in one player but not another (VLC copes, your editor refuses), or audio that slowly slides out of sync. Because the underlying frames are healthy, these files usually respond well to a rebuild of the container, or a remux.
The repairability map
This is the table we wish had existed every time someone asked us "is it fixable?" One row per cause, the symptom you'll actually see, and a straight answer. No repair tool, ours included, beats this table.
| Cause | Typical symptom | Repairable? |
|---|---|---|
| Interrupted recording | File won't open in any player; healthy file size; ffmpeg says moov atom not found | Yes, usually. The footage is on disk; the index can be rebuilt. The last seconds before the interruption (still in the camera's memory buffer) are gone. |
| Interrupted transfer | File is smaller than the original; plays partway then stops, or won't open at all | Yes, up to the cut. Everything that arrived can be made playable. The missing tail isn't damaged, it's absent, so recheck the source device for the full original. |
| Failing storage / bad sectors | Glitches, freezes, or blocky artifacts at a specific point; often several files affected on the same card or drive | Partially. Structure can be rebuilt around the damage; frames that lived on the dead sectors are unrecoverable. Expect a clean file with a gap. |
| Recovery-tool output | Right extension and plausible size, but the file won't open, or opens showing the wrong content | It depends. If the recovery tool found the right clusters, repair finishes the job. If it stitched fragments of different files together, there is no video in there to fix. |
| Software bug / bad muxing | Plays in some players but not others; audio drifts out of sync; editors reject the file | Yes, usually. The frames are healthy; rebuilding the container into a spec-correct file resolves most of these. |
| Data overwritten or never written | File reads 0 bytes, opens as nothing, or is a small fraction of its expected size; contents are all zeros | No. There is no footage in the file to rebuild around. No tool can repair data that doesn't exist; anyone claiming otherwise is selling you a scan result. |
"Repairable" here means a tool can rebuild the file's structure around the footage that physically survived on disk. It never means regenerating lost frames.
What "repair" actually does
A video repair tool does structural work. It reads what's left of the file, identifies the surviving stream data, and rebuilds the container around it: reconstructing the index frame by frame, correcting offsets and timestamps, and writing out a new, spec-correct file. When the index is missing entirely, the tool scans the raw stream for frame boundaries and rebuilds the map from what it measures. That's the whole honest job description.
What repair never does is create footage. It doesn't interpolate missing frames, doesn't guess at content, doesn't "enhance" anything. A repaired file contains exactly the video that survived in the original, which is why the repairability map above has "no" rows. Repair is also non-destructive when done right: it reads your original and writes a new file, so a failed attempt costs you nothing. If you have a video showing one of the symptoms above, the video repair page will tell you which case yours is.
Red flags a file is beyond repair
Before spending time (or money) on any repair tool, check these. Each one means the data itself is missing, and structural repair can't help:
- The file is 0 bytes. There's nothing in it: a data-recovery problem, not a repair problem.
- The file is full of zeros. Open it in a hex viewer (or scroll it in any text editor): if you see endless runs of nothing, the camera allocated space it never filled. Common when an SD card died mid-write.
- The size is wildly wrong. A "two-hour recording" that's 40 MB doesn't contain two hours of footage. Compare against a healthy clip of similar length from the same device.
- The storage device itself is failing. If the card won't mount, files vanish, or copying throws I/O errors, stop. Do data recovery first, then repair whatever the recovery produces.
FAQ
Can a corrupted video file be fixed?
Often yes, though it depends on which part is damaged. If the file's structure (its container or index) is broken but the compressed footage inside survived, a repair tool can rebuild the structure and the video plays again. If the footage data itself was overwritten or never written to disk, no tool can restore it, because there is nothing left in the file to rebuild from. The repairability map above matches each cause to its prognosis.
What causes video file corruption?
Five things, in practice: a recording interrupted before the camera could finalize the file; a transfer or download that stopped partway; failing storage returning wrong or unreadable bytes; data-recovery software reassembling a file from the wrong pieces; and, less often, bugs in the software that wrote the file. Everyday playback doesn't corrupt videos. Corruption happens when a file is written, moved, or stored, not when it's watched.
Why do videos corrupt when transferring?
Because a transfer that stops early leaves a truncated copy: the front of the file arrived, the tail didn't. Pulling a USB drive or SD card mid-copy is the classic trigger, because the operating system often hasn't finished flushing data to the device when the icon disappears. The original, if it still exists, is usually fine, so check the source before repairing the copy.
Are corrupted videos ever partially recoverable?
Yes, and partial results are common. A truncated file can be rebuilt into a playable video that simply ends where the data ends. A file with a band of damaged bytes in the middle can play cleanly before and after the bad region. Repair returns the footage that physically survived (often most of it), but it cannot fill gaps with footage that no longer exists.
Next in this series: MP4 anatomy — what the moov atom is and why your video won't play.