"moov atom not found" — what it means, and how to fix it

If you've seen "moov atom not found", "could not find codec parameters", or a video that opens to a black screen with the correct duration — your file has almost certainly lost its moov atom. The good news: this is the single most recoverable kind of video damage there is, because the media itself is usually still sitting on disk, intact.

What is a moov atom?

An MP4 or MOV file is a container. It holds two main parts:

• mdat — the actual compressed video and audio samples. This is the bulk of the file.
• moov — the index. It records where each sample lives, how long it lasts, its resolution, codec, and timing.

A player cannot show a single frame without the moov. It's like a book with all the pages but no table of contents and no page numbers — the content exists, but nothing can navigate it.

Why does the moov atom go missing?

Most cameras and recorders write moov last, when you stop recording cleanly. That means any interruption before the stop leaves the file without an index:

• Battery died, or the device shut down from low power
• The app, camera, or recorder crashed mid-recording
• A drone crashed or lost power ("flyaway")
• The SD card was pulled, or the device was switched off while still writing
• A file transfer was interrupted and the tail of the file never arrived

Some tools report this as "moov atom not found" (the atom is absent entirely) and others as a truncated moov (the index started but was cut off). Both are container-level problems.

How to confirm it's really the moov atom

Before spending time on recovery, check these four things:

1. File size is not zero. A file with real size (say, tens of MB) almost certainly contains media. A file that is truly 0 bytes contains nothing to rebuild — see the limits below.
2. The player knows the file exists but shows nothing. Many players will list the file, sometimes even a duration, but render a black frame.
3. The error names the atom. Messages containing moov atom not found, moov atom is missing, or could not find codec parameters all point at the index.
4. It is an MP4 or MOV. This matters — see the format limit below.

What can be rebuilt — and what cannot

Usually recoverable

• Recording interrupted by crash, freeze, or power loss, where the file still has real data
• Camera or phone battery died mid-record (GoPro, DJI, Sony, dashcams, phones)
• Drone crash or flyaway leaving an unreadable MOV
• OBS or streaming crash producing a headless MP4
• A moov atom that is present but truncated

Usually not recoverable

• A file that is truly 0 bytes. Nothing was ever written to disk. No container repair can invent media that does not exist.
• Media overwritten by later recordings. If the card was reused, the bytes are gone.
• Physically damaged storage with bad sectors. Run a data-recovery tool first, then repair the recovered file.
• Formats outside the ISO-BMFF family. FixFile rebuilds MP4 and MOV containers. WebM, MKV, AVI, and audio-only formats use different structures and are not supported.

How to repair a file with a missing moov atom

1. Keep an untouched copy

Work on a copy. Never let anything write to the original card or file until you have recovered what you need.

2. Get a reference clip from the same device

This is the step that decides whether the repair succeeds. Because the index is what's missing, the tool needs a healthy index to use as a template. Record a short clip on the same camera, same resolution, same frame rate, same codec settings as the broken file. Full details are in how to prepare a reference clip.

3. Rebuild the container locally

Open the FixFile repair tool, add the damaged file, optionally add the reference clip, and run the repair. Everything happens inside your browser — the file is never uploaded, which matters when the footage is private (a dashcam incident, a client shoot, a family event).

4. Confirm with the free preview

You'll get a low-resolution preview. If your footage appears, you pay $4.99 once to download the full HD file. If it doesn't, you pay nothing and you've lost only the few minutes it took to try.

Why not just use a desktop repair utility?

Desktop tools can work well, but they usually mean installing software, and the paid ones commonly cost far more than a single $4.99 download. The other common option — a "free online repair" site — asks you to upload the file, which for private footage is a real privacy trade-off. A browser-local repair avoids both: nothing leaves your device, and you only pay after you have seen the result.

Preventing it next time

• Always stop the recording with the device's own stop button before removing power or the card.
• Where the app allows it, enable faststart (moov at the front) so the index is written early.
• Carry spare batteries — low-power shutdowns are the top cause of headless files.
• For OBS and similar recorders, consider recording to MKV and remuxing afterwards; it survives crashes far better. See OBS MP4 won't open.

FAQ