How to Repair an MP4 With a Missing moov Atom Error

You press play on an important phone recording and get a cold, unhelpful error: “moov atom not found.” The video was there when you filmed it. The file size looks right — hundreds of megabytes of something. Yet every player refuses to open it, all because of one small missing piece with a strange name.

This error is one of the most fixable problems in video repair. Your footage is almost certainly still inside the file. What is missing is the index that tells players how to read it. This guide explains what the moov atom is, why interrupted recordings lose it, and the proven ways to rebuild it safely.

Quick Answer

The moov atom is the index at the end of an MP4 file that lists every frame’s position, size, and timing. When a recording is interrupted, the phone never writes this index, so players report “moov atom not found” even though the video data is complete. You fix it by rebuilding the index: use a repair tool such as Untrunc with a healthy video from the same phone and settings as a reference, and save the result as a new file. Always repair a copy, never the original.

Understanding the Parts of an MP4 File

An MP4 file is a container made of sections called atoms or boxes. Three matter for this repair:

• ftyp — a tiny label at the start saying “this is an MP4-style file” and which variant it follows.
• mdat — the big section holding the actual compressed video and audio, written live while you record.
• moov — the index: frame positions, durations, resolution, codec details, and track layout. Players read this first to understand everything else.

Most phones write the mdat first and the moov last, the moment you tap stop. That design is efficient for recording but fragile: a crash, a dead battery, a forced restart, or the app being killed mid-recording leaves a file with data but no index. Some cameras offer a “fast start” layout with the moov at the front, but that version can only be written after recording ends too.

Before You Repair: Safety Steps

1. Copy the broken MP4 to your computer and put the original somewhere safe. Every repair attempt happens on a copy.
2. Record or find a healthy reference video: same phone, same camera app, same resolution and frame rate, even a five-second clip of the wall will do.
3. Check the broken file’s size. A size close to what you would expect for the recording length means the data survived. A tiny file means the recording itself failed early.
4. Do not keep using the phone storage heavily if the file was deleted as well as damaged; deleted data can be overwritten. If deletion is part of the problem, our overview of the best free file recovery software options explains how carving tools pull raw data back from a drive.

Method 1: Rebuild the Index With Untrunc

Untrunc is a free, open-source tool created specifically for moov-missing files. It reads the reference file’s index structure, then scans the broken file’s raw data and builds a matching index for it.

1. Download Untrunc from its official project page and extract it.
2. Load the healthy reference video first.
3. Load the broken MP4 as the file to repair.
4. Start the repair and save the output with a new name, such as video-repaired.mp4.
5. Test the result in more than one player and scrub through the whole timeline, not just the first seconds.

When it works — and for phone recordings it works often — the repaired video plays with its original quality, because Untrunc does not re-encode anything. It simply writes the missing map for the data that was already there.

Method 2: Let VLC or FFmpeg Attempt a Recovery

For lightly damaged files, general tools sometimes succeed faster:

1. Open the file in VLC. If VLC can decode the stream, use Media > Convert/Save to write a fresh, properly indexed copy.
2. With FFmpeg, a stream copy command can rebuild container structure without re-encoding: ffmpeg -i broken.mp4 -c copy fixed.mp4. If the moov is fully absent, FFmpeg will fail — that result tells you to go back to Method 1.
3. If only part of the video matters, some tools let you extract the playable portion. A partial clip with the key moment beats a perfect repair that never finishes.

The official FFmpeg documentation covers its container and stream-copy options in detail if you want to understand exactly what each command does before running it on your only copy — another reason copies come first.

How to Judge the Result Honestly

A repair is only finished when the whole file has been checked, not when the first frame appears. Play the repaired video at normal speed from beginning to end and watch for frozen frames, jumps, or places where the picture breaks into blocks. Drag the position slider to several points — the start, the middle, and near the end — and confirm playback resumes cleanly each time. Check that the sound, if the recording has any, stays in step with the picture. If the last few seconds are missing, that is expected: they were still being written when the recording stopped. Everything before that point should be complete and watchable.

Method 3: When the File Also Has a Damaged Header

Sometimes the ftyp label or the start of the mdat section is damaged too, and index tools refuse the file outright. Advanced repair tools and hex-editor techniques can transplant a healthy header from the reference file, but this is delicate work where one wrong byte shifts everything after it. If the recording is truly irreplaceable — a wedding, a legal record, a one-time event — this is the point to hand a copy (never the only original) to a data recovery specialist and let them work on it with professional tools.

Common Mistakes During moov Repair

• Using a reference video with different settings. A 4K reference will not correctly index a 1080p broken file. Match resolution, frame rate, and camera app.
• Repairing the only copy. A failed tool run can alter the file. Copies are free; originals are not replaceable.
• Assuming a successful start means full success. Always play the repaired file to the end. Damage near the end of the recording is common.
• Re-recording over the phone’s storage. If the broken file was also deleted, new photos and videos can overwrite its data before you copy it out.
• Uploading private recordings to random online repair sites. Your video passes through a stranger’s server. Desktop tools keep it on your machine.

Conclusion

“Moov atom not found” sounds terminal, but it is really just a missing table of contents. The book itself — your video — is usually intact inside the file. Protect the original, grab a matching reference clip from the same phone, rebuild the index with Untrunc or a similar tool, and verify the whole result. Most interrupted phone recordings come back fully watchable with this approach, at their original quality.

Frequently Asked Questions

Can a moov atom be repaired without a reference file?

Some commercial tools guess standard settings and attempt a repair blind, and they sometimes succeed. A matching reference file is still the most reliable input and dramatically improves the result.

Does repairing the moov atom reduce video quality?

No. Index-rebuilding tools do not re-encode the video; they write a new index for the existing data. The repaired file keeps its original resolution and quality.

Why do players show the error instantly instead of trying to play?

Players rely on the moov atom to locate frames before decoding anything. Without it they cannot even begin, which is why the error appears immediately and in every player.

My repaired video has picture but the length looks wrong. What now?

The tail of the recording may be incomplete, so the rebuilt index is slightly short. This is normal for interrupted recordings — the footage up to the interruption is what survives, and the final seconds may be lost.

Which phones are most affected by this error?

Any phone can produce it when recording is cut off suddenly, but it appears most with long recordings, low battery, overheating, or a camera app crash — anything that stops the app before it writes the finishing index.