The short version
This tool repairs MOV files whose structure broke — a damaged or truncated index that leaves real footage no player can navigate — by rebuilding the container around the video that survived, without re-encoding. It runs entirely in your browser: the file is read on your machine and 0 bytes are uploaded, which you can confirm in the Network tab. It can't bring back footage that isn't in the file — an iCloud placeholder stub or a 0-byte file needs a re-download or recovery, not repair.
Fix your MOV now
- Drop the file
- Repair runs locally
- Download the result
Drop the MOV above. The tool reads it on your machine, tells you what it actually is and whether the structure is intact, then rebuilds the damaged container around the footage that survived. No .exe to download, no app to install, which matters on a Mac, where most repair tools are Windows software.
Full MOV repair is rolling out in stages: the structural remux repair (rebuilding a damaged but readable container) runs today, and deeper reconstruction for files whose index was never written is in development. The diagnosis always tells you which case your file is first.
"QuickTime Player can't open this file"
The file isn't compatible with QuickTime Player.Apple's wording is different, but the failure underneath is the same one MP4 users hit. MOV and MP4 are siblings: the MP4 format was standardized from Apple's QuickTime container, so both store your footage as one large block of compressed data plus an index that tells the player where every frame lives. That index is written when a recording or transfer finishes. Interrupt the ending (a dead battery, a dropped AirDrop, a crash) and you get a file full of real footage that no player can navigate.
QuickTime is also the strictest mainstream player: it refuses files that VLC will attempt to play. That makes VLC a useful test: if the MOV plays there but not in QuickTime, you have a codec gap, not corruption. If it plays nowhere, the structure is damaged, and that's the repairable case: rebuilding an index is routine work when the footage behind it survived.
iPhone and Mac scenarios
Recording interrupted on the phone
A call coming in mid-recording, a battery dying, the Camera app crashing — anything that stops a recording before the phone finalizes it leaves the index unwritten. The footage up to the interruption is on the phone; the file just has no map to it.
Partial transfers
AirDrop that didn't finish, an iCloud download cut short, a copy off an SD card interrupted midway: the result is a truncated file. Because the index sits at one end of the file, a truncated MOV often loses its entire index while keeping most of the footage.
HEVC (H.265) from newer iPhones
iPhones record HEVC by default, inside the same MOV container. Structural repair doesn't care: it rebuilds the container without re-encoding the video, so HEVC footage passes through untouched, at original quality.
What this can and can't fix
Can fix
- Structural MOV damage — broken or truncated index, bad offsets
- Recordings interrupted before the phone or camera finalized them
- Files cut short by failed AirDrop, iCloud, or SD-card transfers
- iPhone HEVC footage — repaired without re-encoding
Can't fix
- iCloud placeholder stubs — a few KB standing in for the real file; re-download the original instead
- DRM-protected video (iTunes/Apple TV purchases)
- Footage whose bytes were overwritten — data that isn't in the file can't be regenerated
- Files that read as 0 bytes — that's a recovery problem, not a repair problem
A quick sanity check before anything else: a healthy-sized file is a repair candidate; a file far smaller than the footage it should hold usually isn't. The diagnosis above tells you which you have, and a failed repair is never charged.