moov atom not found — what it means and how to get your video back

Your MP4/MOV is missing its index — not its frames. In most cases the footage is still inside the file and can be rebuilt.

What this error actually means

MP4 and MOV files have two key parts: the mdat box (the actual video/audio frames, written continuously while you record) and the moov box (the index that tells players where every frame lives — written once, at the very end, when the camera finalizes the file).

If the camera lost power, the battery died, the SD card filled up, or the recording app crashed before finalizing, the moov index was never written. Every player — VLC, QuickTime, editors — fails with moov atom not found, even though the frames are sitting right there in the file.

How recovery works

The fix is to scan the raw stream, find the frames, and rebuild the index. That's exactly what ClipMend's rescue mode does, locally on your Mac:

1. Drop the broken file into ClipMend → press Analyze. The free diagnosis reads the container and tells you whether the frames are present.
2. ClipMend scans the stream and reconstructs the moov index. It needs the codec parameters, which it gets one of two ways:
   • Reference clip — a short healthy video from the same camera at the same settings (even a fresh 5-second clip you record now works), or
   • Self-rescue — some cameras (GoPro and others) embed codec parameters in the stream itself, so no reference is needed at all. Exact fps is read from the stream when the camera recorded it.
3. You get a normal playable .mp4 — audio recovered, frame order (B-frames) restored. Frames are copied 1:1, not re-encoded, so there's no quality loss.

When it can't be fixed

Honesty matters here: if the file is zero-filled, empty, or contains only a header, the frames were never written to disk and no software on Earth can recover them. ClipMend's analysis tells you which case you're in before you commit to anything.

FAQ