A MOV file is a sequence of atoms, also called boxes. Each atom starts with a 4-byte size and a 4-byte type code. The mov atom structure determines how a player reads your video. If the index atom is missing or in the wrong place, playback fails even though the actual video data is still intact. Learn the key atoms, ftyp, moov, and mdat, and how moving the index to the front (faststart) fixes streaming problems.
What is a MOV Container Structure?
The QuickTime file format atoms are like building blocks stacked in order. Each block announces its own size and type, so a player can skip unknown atoms and still parse the file. The MOV container structure is simple: a header atom, then one or more data atoms, then a metadata atom, or the metadata can come first. The three atoms you need to know are ftyp, mdat, and moov.
Ftyp the File Type Atom
The ftyp atom identifies the file type. It is always near the start of the file. For QuickTime files, the brand is set to "qt ". This atom tells software that the file is a valid MOV or MP4 container. Without it, a player may not recognize the file at all.
The MP4 format is based on the QuickTime file format and uses the same atom structure, so ftyp works the same way in both.
Mdat Where the Video and Audio Live
The mdat atom holds the actual audio and video data. It makes up almost all of the file size. This is the footage itself, the compressed frames, the sound samples, everything that makes up your video.
If you lose the moov atom but the mdat is still present, the raw data is still there. You just need a way to rebuild the index so a player knows where each frame starts and ends.
Moov the Index That Makes Playback Possible
The moov atom holds metadata: the movie header (mvhd), and one trak atom per track with timing and sample tables. Players need the moov atom before they can play. Think of it as a table of contents. Without it, the player does not know the duration, the codec, or where each sample is located inside the mdat atom.
When Moov Is Missing
If the moov atom is missing or corrupted, the player cannot find the start of each frame. You may see a black screen, an error message, or a file that opens but does not play. The footage in the mdat atom is still there, but without the index, the player cannot locate it. Repair tools scan the mdat for recognizable patterns to rebuild the moov.
When Moov Is at the End
Many cameras and encoders write the moov atom at the end of the file. This is fine for local playback because the player reads the whole file before playing. For streaming or online use, the player waits until the entire file downloads before it can start. That delay is inconvenient for large files.
Faststart Moving Moov to the Beginning
Faststart moov at beginning means the moov atom is placed at the start of the file, right after the ftyp atom. This lets playback begin before the whole file downloads. FFmpeg does this with the flag -movflags +faststart. The process rewrites the file so the index comes first, without moving the actual video data.
The result is a file that streams immediately, even over slow connections.
Check if a File Is Faststart
- Open the file in a hex viewer or a tool that shows atom positions.
- Look at the first few bytes: after the ftyp atom, the next atom should be moov.
- If you see a large mdat atom instead, the moov is at the end and the file is not faststart.
Why a Misplaced Moov Breaks Playback While the Footage Survives
The moov atom is a small metadata block, often just a few kilobytes. The mdat atom is the bulk of the file. If the moov is missing, corrupted, or placed in a location the player cannot find, the player gives up. But the mdat remains untouched.
This is why repair is possible: the raw frames are still in the file. A repair tool can scan the mdat, identify sample boundaries, and generate a new moov atom. The recovered file will then play normally.
Practical Takeaways for MOV Repair
Understanding the mov atom structure helps you diagnose playback problems. If a file does not play, the moov atom is likely missing or damaged. The footage is probably still in the mdat atom.
Use a tool like mov.repair to recover the file by rebuilding the index from the existing data. No watermark is added, and the process is free.