MOV File Won't Open? How to Tell If It's Broken or Just the Wrong Player

A MOV file that will not open is frustrating in a specific way: it often plays perfectly well somewhere else. It runs on the phone but not the laptop. It opens on a Mac but not on Windows. It previews fine but your editing software refuses to import it.

That pattern matters, because it usually means the file is not damaged at all. Before you go looking for repair tools, it is worth spending five minutes working out which problem you actually have.

Start here: is it the file, or is it your computer?

MOV is Apple's video format. It is very close to MP4 under the hood, but the video inside it can be encoded in a lot of different ways, and not every computer can read every one of them. So "my MOV will not open" splits into two completely separate problems with completely separate answers.

Before you try anything, make a copy of the file and work on the copy. Some of the steps below rewrite the file. If one goes wrong, you want the original untouched. And if the file is still on a camera card, stop recording to that card right now — overwriting is the one kind of damage nobody can undo.

The simple fixes, in the order worth trying

1. Open it in VLC

VLC is free, it runs on Windows, Mac and Linux, and it carries its own decoders instead of relying on what your operating system happens to have installed. It also tolerates messy files that other players give up on.

If VLC plays your file, you never had a broken file. You had a player problem. Either keep using VLC, or convert the file to something your other software understands with Media → Convert/Save.

2. If it came from an iPhone, it is probably HEVC

Since iOS 11, iPhones record in HEVC (also written H.265) by default because it saves space. Plenty of Windows machines cannot play it without an extra decoder. Nothing is wrong with your video.

Two ways around it. Either play it in VLC, which handles HEVC on its own. Or, on the iPhone, go to Settings → Camera → Formats and choose Most Compatible so future recordings are saved in the older, more widely supported format.

3. Try renaming a copy to .mp4

MOV and MP4 are close relatives. Some apps look at the file extension before they look at the contents, and refuse a MOV out of habit. Renaming a copy to .mp4 takes five seconds and occasionally solves the whole thing.

To be clear about what this does and does not do: it changes the label on the file, not what is inside. It will never repair genuine damage.

4. Rebuild the container with FFmpeg

If you are comfortable with a command line, FFmpeg can rewrite the file's structure without re-encoding or degrading the video:

ffmpeg -i broken.mov -c copy fixed.mov

If that finishes and the new file plays, you are done. If FFmpeg stops with moov atom not found, that is the specific failure explained below, and free tools generally cannot get past it on their own.

5. Try an automated repair service

There are online services that repair damaged video automatically for a small fee, and most let you preview the result before you pay anything. If your file has a common, simple fault, they work well and cost very little. It is genuinely worth trying one before going further.

What "moov atom not found" actually means

This is worth understanding, because it explains most unopenable MOV files.

A MOV file has two parts: the video and audio data itself, and a small index that tells a player where everything is — how many frames, how long, where each one starts. That index is called the moov atom. Cameras normally write it last, when you press stop.

So if a camera loses power, crashes, overheats, or the card is pulled while recording, you end up with a file full of perfectly good video and no index at all. Nothing can play it, because nothing knows how to read it. The footage is not gone. The table of contents is.

That is the most repairable situation there is, and it is also the one that makes automated tools fail.

Why automated repair tools give up

If two or three tools have already told you the file is unrecoverable, you have not done anything wrong. There are specific reasons they stop.

• They need a reference file and you do not have one. Most automated repair works by copying the index from a healthy clip shot on the same camera with the same settings, then attaching it to your broken file. No matching reference clip, no repair.
• The damage is in the video data, not the index. Rebuilding an index is a structural job. Damage inside the encoded frames has to be worked through frame by frame, which automated tools are not built to do.
• The footage is scattered across the card. When power is lost mid-write, the remaining data is often left in non-sequential blocks that have to be put back in the correct order by hand.
• The format is outside what consumer tools support. ProRes, high-bitrate 10-bit footage, multi-track audio and professional camera formats are common examples.
• There is more than one fault at once. Real damaged files often have two or three of the above together. Automated tools test for one thing and exit.

What manual repair does instead

Manual repair means a person opens the file in a hex editor, reads the actual byte structure, and rebuilds what is missing based on what the surrounding data shows should be there.

• Rebuilding a missing index by reading frame boundaries straight out of the video stream, with no reference file needed
• Finding the exact point where a recording was cut off and building a valid file that ends cleanly there
• Putting fragmented data back into the right order
• Handling formats that consumer tools do not recognise
• Saving partial results — if most of the footage is intact, recovering that rather than reporting failure

It is slower than an automated service and it costs more. It is also what is left once automation has failed, and it recovers a real number of files that tools have already given up on.

What cannot be recovered

Being straight about this saves everybody time.

• Anything that was overwritten. If new footage was recorded over the file, it is gone. No tool and no person can bring it back.
• A file that never held any video. If the camera failed before writing a single frame, there is nothing inside to recover.
• A physically broken card or drive. Cracked, bent or water-damaged media needs a data recovery lab with a cleanroom. That is a different trade from file repair.
• DRM-protected content. Outside the scope of file repair.

How it works

1. Upload the file and send us the link. Google Drive, Dropbox or WeTransfer are all fine. Email the link to cornmonster2018@gmail.com and tell us what camera or phone it came from and what happened when the recording stopped.
2. We assess it at no charge. We open the file, look at its actual structure, and work out what is wrong and how much of it is recoverable.
3. You get a straight answer within 48 hours. Either it is recoverable and we send you a quote, or it is not and we tell you exactly why. If we cannot recover it, you pay nothing.
4. You decide. Nothing happens until you approve the quote.

Your files are never shared with anyone, and our working copies are deleted after the job is finished. Our privacy policy has the full detail.

Frequently asked questions

Why does my MOV file play on my phone but not on my computer?

Almost always a codec problem, not a damaged file. Newer iPhones record in HEVC, also called H.265, and many Windows computers cannot decode it out of the box. The file is fine. Try opening it in VLC, which brings its own decoders and does not rely on what Windows has installed.

Can I just rename a MOV file to MP4?

Sometimes it works, because MOV and MP4 are closely related container formats. It costs nothing to try on a copy of the file. It will not fix a file that is genuinely damaged, though, because renaming changes only the label, not the contents.

My editing software says the MOV file is unsupported or offline. Is it broken?

Not necessarily. Premiere Pro, Final Cut and DaVinci Resolve all refuse files whose index is damaged, even when a player can still show the picture. If VLC plays it but your editor will not import it, the container needs rebuilding rather than the footage being lost.

What does it mean if my MOV file is 0 KB?

It means the file entry exists but no data was written to it, usually because the camera lost power or the card was removed while recording. The footage may still be physically present on the memory card, so stop using that card immediately and recover from the card rather than the file.

Can a MOV file be repaired without the original camera?

Automated tools usually cannot, because they need a healthy reference clip from the same camera and settings. Working through the file by hand does not need a reference, because the structure can be rebuilt by reading the frame boundaries out of the video data itself.

How do I send you a MOV file for assessment?

Upload it to Google Drive, Dropbox or WeTransfer and email us the link at cornmonster2018@gmail.com. We reply within 48 hours with an honest answer about whether it can be recovered. If it can, we send a quote and you decide whether to go ahead. If it cannot, you pay nothing.

Stopping it happening again

• Format cards in the camera before a shoot, not on a computer
• Never pull a card or a battery while the record light is on
• Let the camera finish writing after you press stop — give it a couple of seconds
• Copy footage off the card before you review or delete anything
• Retire a card the day it starts producing odd glitches. They rarely get better