Damaged MP4 repair: files that play partway or glitch

Truncated files (cut off at the end)

A download that stopped early, a copy that got interrupted, or a cloud sync that gave up all leave you with the first part of the file and nothing after. If the index was at the start, the file opens and then stops or hangs at the point where the data ends. If the index was at the end, it won’t open at all.

Either way, you can usually save everything up to the cut. Remux with FFmpeg to get a clean file, or rebuild the index from a reference clip if it won’t open. The missing part isn’t in the file, so re-download it if you can.

Glitches in the middle

Grey smears, green blocks or frozen frames for a few seconds, then normal playback, mean some of the data was damaged, usually by a failing card or a bad transfer. That data is gone. What you can fix is how the file behaves: a re-encode will play smoothly through the damaged section instead of stalling, so you can still edit and share the clip. The visible damage stays.

Audio drifts out of sync

If the sound slowly drifts after a glitch, the timestamps got confused. Regenerating them (ffmpeg -fflags +genpts -i in.mp4 -c copy out.mp4) often fixes it. See also our audio out of sync page.

What our tool does here

FixCorruptVideo checks the whole file, not just the start, and picks the least destructive fix that gets you a file that plays and seeks all the way through. The free preview lets you check the result before paying.

Grading the damage before you repair

Not all damage is equal, and the right repair depends on how badly the file is hurt. A simple grading scale helps you choose quickly and set expectations.

Grade 1, cosmetic: the file plays in VLC but not in stricter players, or has a wrong duration, missing thumbnail, or seeking problems. The index exists but has errors. A lossless remux fixes it completely.

Grade 2, structural: the file won’t open anywhere. The index is missing or unreadable, but the video data is intact. An index rebuild recovers everything that was recorded.

Grade 3, partial: the file opens after repair but has glitches, freezes, or silent gaps in places. Some frames are damaged. You keep most of the clip, with visible defects where the damage is.

Grade 4, severe: large parts of the file are zeros, overwritten, or missing. Only fragments can be saved, if any.

Most damaged MP4s we see are grade 1 or 2. Grade 3 usually traces back to a failing card. Grade 4 is rare and usually involves formatting, overwriting, or physical drive failure.

Measuring the damage yourself

Compare the file size with what you’d expect. A rough estimate is bitrate times duration: a 1080p phone clip is around 15 to 20 megabits per second, so a minute is about 110 to 150 MB. 4K is roughly three times that. A file far smaller than expected is missing data.

Run ffmpeg -v error -i damaged.mp4 -f null - 2>&1 | wc -l after any repair. The number of error lines gives a quick sense of how much damage remains. Zero is perfect, a handful is minor, thousands mean extensive frame damage.

Open the file in a hex viewer and scroll through. Long runs of 00 or FF bytes in the middle of the data are areas that were never written or were wiped. Their position, as a percentage of the file, tells you roughly where in the clip the damage sits.

Repairing grade 1 damage

A remux rewrites the container from scratch and fixes most cosmetic issues: ffmpeg -i damaged.mp4 -c copy -movflags +faststart repaired.mp4. It takes seconds and doesn’t touch the video data.

If the duration is still wrong, add -fflags +genpts to rebuild timestamps. If seeking is still slow, the file may lack a keyframe index; remuxing to MKV and back to MP4 often regenerates it.

Repairing grade 2 damage

A missing index needs a rebuild. The repair tool walks through the raw mdat data and identifies each video frame and audio packet. For H.264 and HEVC this is reliable, because each frame has a length prefix and a recognisable header. For AAC audio, the tool infers packet boundaries from the gaps between video data.

A reference file from the same device helps in two ways: it supplies the codec setup data (needed to decode anything at all if the camera didn’t repeat it in the stream) and it shows the interleaving pattern of audio and video, which makes audio recovery far more accurate.

Our repair runs a native frame scanner first and falls back to reference-based rebuilding when needed. Open the repair page and judge the free 15-second preview before unlocking the full file for $9/month or $29/year.

Repairing grade 3 damage

After rebuilding the index, the file plays, but some sections show grey or green blocks that spread across the picture until the next keyframe, or freeze briefly, or have audio dropouts.

Damaged video frames affect every frame that depends on them, up to the next keyframe. Phones and cameras usually place keyframes every one or two seconds, so a single damaged frame causes up to two seconds of visible artefacts.

Two strategies help. Cutting removes the affected seconds cleanly at keyframe boundaries with -c copy. Re-encoding makes the decoder conceal errors by copying neighbouring image areas, which often looks better than you’d expect for small damage but costs some quality overall.

For audio dropouts, replacing the damaged seconds with silence or room tone in an editor is usually less noticeable than leaving clicks.

Repairing grade 4 damage

When large parts of the file are gone, the goal is to save whatever fragments remain. A frame scanner can still find valid frames between the damaged regions, but the codec setup data is often in the missing part, so a reference file becomes essential.

Expect a result with jumps and gaps. The saved parts will look normal; the missing parts are simply absent. For important footage this is still worthwhile, since a few seconds of a key moment may be exactly what you need.

If the damage came from a formatted or overwritten card, try recovery tools on the card image before repairing; they may find a more complete copy of the file elsewhere on the card.

Physical damage to the storage

Cards that were bent, cracked, soaked, or burnt, and drives that were dropped, are physically damaged. File repair can’t help until the data has been read off the device.

Dry water-damaged cards thoroughly before trying them. Don’t force a cracked card into a reader. For high-value footage on a physically damaged device, a recovery lab can often read chips or platters directly.

See how to recover corrupted video files for imaging and recovery steps before repair.

Damage patterns by cause

The cause of damage leaves a recognisable fingerprint in the file, which helps predict how much can be repaired.

Power loss while recording: full-size mdat, no moov, end of the data cut mid-frame. Grade 2. Expect a near-complete repair.

Card removed during transfer: file shorter than expected, end missing, sometimes the directory entry shows the full size with zeros at the end. Grade 2 or 4 depending on how much was copied.

Failing card: correct size, index present or missing, small damaged regions scattered through the data. Grade 3.

Fake-capacity card: the first part of the file is fine, later parts contain data from other files or repeating patterns. Grade 3 or 4.

Overwritten after deletion: random chunks belong to newer files. Grade 4.

Bad editor export: index present but inconsistent, e.g. wrong durations or sample counts. Grade 1.

Damaged audio, intact video (and the reverse)

Audio and video in an MP4 are stored in separate chunks, so damage can hit one and not the other. Damaged audio shows up as clicks, gaps, robotic tones, or total silence; damaged video as blocks, freezes, or black frames.

If only the audio is damaged and you have another recording of the same event, such as a second phone or an external recorder, replace the audio entirely in an editor and sync it by a clap or visible action.

If only the video is damaged, the audio may still be valuable. Extract it with ffmpeg -i damaged.mp4 -vn -c:a copy audio.m4a.

Repairing damaged MP4 files from editing projects

If a damaged MP4 is a source clip inside a Premiere, Resolve, or Final Cut project, repair it, save the repaired file with the same name in the same folder, and the project should relink automatically. If the repaired clip is a different length, edits after the end of the recovered footage show as offline media.

If the damaged MP4 is an export, re-export from the project. That is faster and gives a perfect file. Repair exports only when the project is gone.

Trying a repair with no risk

Repair is non-destructive when done properly: the tool reads the damaged file and writes a new one. Your original stays exactly as it was, so you can try several approaches.

Open the damaged file on the repair page. It grades the damage, chooses a strategy, and shows a free 15-second preview so you can judge the result yourself. Unlock the full file for $9/month or $29/year if it is what you need. For more on the structure being repaired, see what the moov atom is and corrupted MP4 files.

How repair tools decide what is a valid frame

When a repair tool scans damaged data, it needs to tell real frames from garbage. For H.264 and HEVC, each frame in an MP4 starts with a length field followed by a NAL unit header. The header has a fixed structure: a forbidden bit that must be zero, a type field with a limited set of valid values, and for HEVC a layer and temporal ID. A candidate that breaks these rules is rejected.

The tool then checks that the claimed length makes sense: not larger than the remaining data, not absurdly small, and followed by another plausible frame or audio data. Several consecutive valid frames give high confidence that the scanner is in sync with the stream.

When damage throws the scanner out of sync, it searches forward byte by byte for the next position where a valid sequence begins. Everything between the last good frame and the resynchronisation point is dropped. This is why damaged regions turn into clean jumps rather than garbled noise after a good repair.

Damaged MP4s from security and body cameras

Security cameras, body cameras, and doorbells often record continuously and finalise files every few minutes. A power cut damages only the file in progress. These devices sometimes use unusual audio such as G.711 or ADPCM, which mainstream repair tools may not understand. A reference clip from the same device is especially important.

If the footage may be evidence, keep the original untouched and document every step. Courts and insurers care about an unbroken chain of custody. Repair a copy, and record the tool, version, and settings used.

Setting expectations for heavily damaged files

For grade 3 and 4 damage, measure success by whether the important moments survive, not by whether the file is perfect. A two-minute clip with three seconds of glitching is usually a good outcome. A ten-minute clip that yields four minutes of usable footage may still contain the moment you need.

Use the free 15-second preview on the repair page to check before you unlock ($9/month or $29/year), and see how to recover corrupted video files if more complete copies may exist on the original media.

Physical damage versus logical damage

Damage to an MP4 can come from two very different places. Logical damage means the data on the storage is readable but the file structure is wrong, for example a missing index or a truncated header. Physical damage means the storage itself is failing, so some blocks cannot be read at all. Logical damage is a software problem that repair tools handle well. Physical damage must be addressed by imaging the storage first, often with tools that retry unreadable sectors.

If your computer slows to a crawl, makes clicking sounds, or reports read errors while copying, assume physical damage and stop using that device for anything other than one careful copy. Repair the copy, never the failing original.