By Lucas, founder of FixMyVideos · Updated
iPhone Video (MOV) Won't Open: What Broke Inside the File and How to Get It Back
An iPhone 15 Pro, 16 Pro or 17 Pro records into a QuickTime .mov file: HEVC (H.265) video in 10-bit with Dolby Vision HDR by default, H.264 if you chose "Most Compatible", ProRes on the Pro models if you asked for it, and AAC sound.
These are failures we have repaired on real iPhone files, starting with what you can check yourself.
How an iPhone MOV is put together
The file has two parts that matter. The mdat is the body: compressed pictures, audio frames and a few small metadata records, written one after another while you film. The moov is the index. It lists where every picture and every audio frame sits, how long each one lasts, which way up the picture should be shown, and which codec reads it. The phone writes the final index only when recording stops cleanly, either after the body or into space it set aside at the start.
Without the index, QuickTime says the file cannot be opened and ffprobe prints "moov atom not found", even when every picture is there untouched.
Most of the cases below come down to the index going missing, the index no longer matching the body, or the body losing bytes.
Check these yourself first
Find the original. If the broken file is a copy on a computer, look at the same clip in Photos on the phone. If it plays there, copy it again by a different route (cable instead of AirDrop, or a fresh iCloud download) and compare. In one case we repaired, a 99.7 MB iPhone HEVC clip had its first 852 KB overwritten by a later part of the same file and a 1.4 MB stretch written twice. Two separate uploads of it were byte-identical, so the damage was already in the copy we were sent, not in the transfer to us. A clean copy from the phone would have kept the opening seconds that no repair could bring back.
Try VLC. It is free and more tolerant than QuickTime or the Windows players. If VLC plays it cleanly from start to finish, the index is readable and the player or a missing codec is the likelier problem. On an older Mac or PC, HEVC files can refuse to play while being perfectly healthy; Cannot decode H.265 on Mac covers that side.
Look at the size. A clip that weighs a few kilobytes, or one a hex viewer shows as nothing but zeros, holds no video (see the last section).
Work on a copy. Some repair tools write straight into the file they are given, so keep the original untouched.
What we found inside broken iPhone files
An index left over from the previous clip
This case came from a camera rather than an iPhone, and we include it because it shows how a file can carry an index every tool accepts and still be wrong. Three HEVC 4:2:2 10-bit clips at 59.94 fps, written into MP4, reached us after card-recovery software had pulled them back. Each opened its header with a 512 KB block reserved for the index, to be filled in when recording stopped. Recording never stopped cleanly, so the block still held the index of the clip recorded before, and that stale index matched the layout of another of the three byte for byte.
The interrupted write also left short abandoned stubs of 1 to 7 bytes in front of about one sample in six, each a copy of the start of the sample written after it. A naive scan reads a stub as part of the picture before it, loses track and skips the real picture behind it; an earlier engine build delivered one clip with only 175 of 459 pictures decoding and no sound, with its pictures also marked for playback in the wrong order. The audio sat about 4 KB into each interleaved block, behind a stretch of device metadata and a small table listing the size of every AAC frame that followed.
After the fixes, the clip we could check against a reconstructed original came back with 610 of 610 pictures byte-identical, decoded in the original order with the original frame timing and the audio at zero offset. The other two decode every picture but the last, which the interrupted write cut in half. Those bytes were never written, so nothing can restore that frame.
One extra record per picture under Dolby Vision
With HDR Video on, which is the default from the iPhone 12 onward, Apple attaches a Dolby Vision metadata record to every picture. In HEVC terms it is a NAL unit of type 62, from a range the standard leaves to vendors. Our scanner used to reject that range, so on an iPhone 13 Pro test recording it carved 294 of 314 pictures, each one exactly 426 bytes short: the size of the Dolby Vision record. It now accepts the record as part of the picture it follows. The same recording carves 314 of 314, byte-identical to the original's own sample table, and the other four iPhone HEVC test recordings we measured also came back with every picture. On one of those recordings it also closed an audio drift of about one second.
Video with no sound
On iPhone files that have lost their index, the sound is the hard part. On the iPhone 13 Pro H.264 files we measured, audio came in blocks of 22 to 25 AAC frames, with per-frame metadata records of 144 bytes each slipped into those same blocks. An index-less AAC stream does not state its own sample rate either, so it has to be inferred from how long the audio lasts against the picture. Label 48 kHz audio as 44.1 kHz and it plays 8.8% slow and low, which is worse than silence. On iPhone 13 Pro H.264 test files with the index stripped, the engine now recovers the audio at 48 kHz. In the isolated audio check its length came within a few hundredths of a second of the picture; in the full delivered file the gap was about a third of a second. When the length cannot separate the two rates, it uses the rate that passed the silent-decode check instead of guessing.
Black, sideways and silent
The 99.7 MB clip above had an intact index and a body that had moved. Before our copy-damage repair existed, the engine treated it as index-less and produced a preview that was 81% black, lying on its side, with no audio. Portrait iPhone video is stored as landscape pixels plus a rotation flag in the index, so a rebuild that throws the old index away also throws away "which way up".
The repair finds the duplicated stretch by searching for where the same bytes repeat, removes it, and uses the phone's own index to rebuild the file. The delivered file decodes 1,838 of 1,838 frames with no decoder errors, stands upright, carries its AAC stereo track, and runs 61.67 s of a 64.67 s recording. About 2.5 s at the start were overwritten in the copy, so the repaired file begins at the first clean keyframe, 3 s in.
Nothing is broken, the picture just stops
An iPhone 17 Pro Max 4K H.264 clip of 3:55 seemed broken because the image froze, once for more than three minutes. Every byte of the body was accounted for in the index and every picture decoded. Two pictures were simply held on screen for 23.9 s and 195 s while the sound kept running; across the whole clip, the picture moved for about 16 seconds. Everything pointed to a copy the phone re-encoded when the clip was shared, so whatever froze the picture happened at or before that export. Our diagnosis now tells you the file is not damaged and for how long the picture actually moves, because no rebuild can add pictures that were never in it. If your clip stalls, check whether the original on the phone stalls in the same places.
When a file cannot be recovered
Some uploads contain no video at all, and the diagnosis says so:
- All zeros. We have had a 30 MB camera file in which every byte was
0x00, with no container, picture or sound anywhere in it. - A header and nothing after it. A 24-byte upload holding only the opening
ftypbox looks like a video to the file system, but there is no recording behind it. - A few sectors repeated. When a card, reader or cable keeps handing back the block it already read, the copy fills up with the same 512 bytes. One 20 MB file we received held 24 distinct blocks, each repeated about 1,706 times. A second copy through a different reader or slot is the move most likely to produce a real file.
In all three cases the recording may still exist somewhere else: on the phone, in iCloud, or on the drive before the recovery tool touched it. That is where to look next.
Trying it on your file
Upload the clip as it is, without converting it. The diagnosis tells you which of the shapes above your file has, and if there is something to recover you get a free 5-second preview, once you have left an email address, of what the engine recovered from your file. Files up to 150 GB are accepted. Repair costs €6 under 2 GB, €18 from 2 to 20 GB, €35 from 20 to 50 GB and €59 above that, VAT included, and only if the preview shows your footage.
FAQ
Does this apply to the iPhone 16 Pro, 17 Pro and older models? Yes. The iPhone 15 Pro, 16 Pro and 17 Pro and the earlier models write the same QuickTime structure, with HEVC or H.264 video and AAC audio, so the iPhone failures above apply to all of them. The test recordings we measured the Dolby Vision fix on come from an iPhone 13 Pro, and the frozen-picture case was an iPhone 17 Pro Max file.
The clip plays on the phone but not on my computer. Is it damaged? Probably not the original. Copy it off the phone again by another route and try the new copy in VLC. If it plays, the first copy was the broken one.
Why does my video play lying on its side? The rotation flag in the index was lost, which happens when something rebuilds the file without carrying it over, or the player ignores it. The pixels are fine. Our repairs carry the phone's rotation flag over, and in the copy-damage case above the delivered file came back upright.
The repaired video has no sound. Can that be fixed? The engine separates the AAC frames from the metadata records mixed into the same blocks on the iPhone files we measured. On iPhone 13 Pro test files with the index stripped it recovered the audio at the true 48 kHz, and when the duration cannot tell 48 kHz from 44.1 kHz it keeps the rate its decode check validated rather than guessing.
Can you recover a video I deleted? No. We repair damaged files that still exist; we do not undelete. Check the Recently Deleted album in Photos first.
Is my footage safe? Uploads go over HTTPS, are processed on our servers, and are deleted automatically after 48 hours. Nothing is used for training or shared. Privacy policy.
Related
- moov atom not found
- QuickTime error -2048
- Video plays but no audio
- Recover HEVC / H.265 files
- Recover MOV files
- How our recovery engine works
Free preview · No commitment
Ready to recover your video?
Upload your file and get a free 5-second preview in about a minute. Pay only if the preview looks right.
Upload your file →