How to fix “moov atom not found” in MP4 or MOV

What the moov atom does

The moov box describes tracks, codecs, timing and the sample tables that locate compressed video and audio inside the file. The large mdat box normally carries those media samples. A player needs a usable index to interpret the payload correctly.

If the recording stops before the container is finalized, the mdat payload may exist while the metadata needed to map frames, timestamps and tracks is absent or incomplete.

Typical symptoms

• FFmpeg reports moov atom not found or cannot parse any streams.
• The file has a plausible size but shows no duration or thumbnail.
• The last recording made before a crash, power loss or battery removal is the only damaged clip.
• QuickTime, VLC or an editor refuses to open the file.
• Copying or renaming the file does not make it playable.
• A neighboring recording from the same device and settings works normally.

Why the moov atom is missing

Many devices finalize movie metadata when recording stops cleanly. If power disappears first, the device may never write the final index. A camera crash, forced shutdown, battery removal or storage error can leave the same pattern.

A partial transfer can look similar. If the original still exists on the camera, phone or memory card, first make a fresh byte-for-byte copy before assuming the recording itself is structurally damaged.

Missing moov, damaged moov, or truncated file?

These are related but not identical problems. A parser may report that the moov atom is missing because it was never written, because the end of the file is absent, or because the metadata is present but unreadable.

• Interrupted recording: media data may have been written while final metadata was never completed.
• Truncated file: the tail of the file may be missing because copying, downloading or storage stopped early.
• Damaged metadata: a moov structure may exist but contain inconsistent or unusable tables.

The repair strategy depends on which of these actually happened. For interrupted MP4 cases, see repair a truncated MP4 recording.

Why normal FFmpeg commands may fail

ffmpeg -i broken.mp4 -c copy fixed.mp4 first has to parse packets from the input. With no usable index, there may be no streams or packets for FFmpeg to copy. Likewise, faststart moves an existing moov box toward the beginning; it cannot recreate one that was never written.

This is why remuxing is useful for many playable-but-inconvenient files but not a universal solution for an unfinalized recording.

What not to do first

• Do not overwrite or repeatedly edit the only copy of the damaged recording.
• Do not keep recording onto the same memory card if the original may need storage-level recovery later.
• Do not assume renaming .mov to .mp4 reconstructs missing metadata.
• Do not transcode the only original before preserving an untouched copy.

A safe repair procedure

1. Preserve the original. Work from a copy whenever possible.
2. Confirm the failure point. Determine whether the problem happened during recording or during transfer.
3. Keep a healthy reference when available. A short clip from the same device, recording mode, resolution and frame rate can reveal useful structural information.
4. Use structural repair. Reconstruct container metadata around surviving media data instead of merely renaming or remuxing.
5. Validate the output. Check duration, decodability, seeking, video continuity and audio synchronization before treating the result as repaired.

How a healthy reference can help

A reference clip does not donate missing footage. Its value is structural: it can show how the same camera or application normally describes codecs, tracks, timescales and sample layout.

The best reference is usually recorded by the same device with matching recording settings. An edited export or social-media download may have a different container structure and can be a poor substitute.

FrameRescue can also test compatible validated structural profiles and available reference assets when the user has no reference of their own.

What FrameRescue does differently

FrameRescue can compare the damaged structure with validated profiles or a compatible reference, build candidate containers and check outputs independently. It will not label a file successful merely because a new container was written.

The repair path can use multiple compatible hypotheses rather than relying on one guessed reference. Candidate results are validated before a best available result is presented.

Recovery is not guaranteed. Media that was never written, has been overwritten, is encrypted, or is otherwise absent cannot be recreated by rebuilding container metadata.

How to verify a repaired file

Opening the first frame is not enough. Check the beginning, middle and end of the recovered recording. Verify duration, seeking, picture continuity and audio synchronization. If the clip matters for editing, test it in the software where you intend to use it.

A container can be readable yet still contain gaps, damaged sections or timing problems, which is why validation must be treated as a separate step.

“Moov atom not found” FAQ

Can FFmpeg recreate a missing moov atom?

Not with a simple copy or faststart command when the required index does not exist. Structural reconstruction may be necessary before normal remuxing or decoding becomes possible.

Does a large file mean the video can be recovered?

No. A plausible size suggests that data exists, but it does not prove that all expected samples are present or that the surviving payload can be mapped correctly.

Do I need a healthy reference file?

Not always. A matching reference can be useful, but whether it is necessary depends on the damaged recording and on what compatible structural information is available.

Can changing .mov to .mp4 fix the error?

No. Renaming the extension does not create missing track tables, timestamps or sample indexes.

What if the file was damaged during copying rather than recording?

Re-copy the original source first if it still exists. A transfer problem should be corrected at the source before attempting container reconstruction.

Related repair guides

• Repair a truncated MP4

  Recording interrupted or copy cut off? How to tell, and when a reference-based repair is needed.

• Repair a corrupted MP4

  Phones, action cameras, drones and dashcams: what “corrupted” usually means and what can be recovered.

• Repair a corrupted MOV file

  Symptoms, safe first steps and the structural repair path for unplayable MOV recordings.

• Phone died while recording

  Does the video save? Where to look on iPhone, Android and cameras, and how to repair the unfinished file.