Why does QuickTime say my MOV file isn't compatible even though it played before?

The file may have been re-saved or converted by another app, changing the codec. QuickTime only supports H.264, HEVC, ProRes and AAC. If the new file uses a different codec, QuickTime will reject it.

Can I open a damaged MOV file with VLC?

Sometimes VLC can play a damaged file because it tries to repair the index on the fly. If VLC also fails, the file likely needs a repair tool that can rebuild the moov atom.

Will re-encoding a MOV file lose quality?

Yes, re-encoding always loses some quality, even if you use a high bitrate. Re-wrapping with -c copy does not re-encode and preserves quality, but it only works if the codec is already supported by QuickTime.

Is there a way to play a MOV file on a Mac without QuickTime?

Yes, VLC is free and plays many MOV files that QuickTime cannot. You can also use the command line with ffplay, but VLC is the simplest option for most users.

QuickTime "The File Isn't Compatible": MOV Fixes on Mac

QuickTime Player shows "The document 'name.mov' could not be opened. The file isn't compatible with QuickTime Player" and you assume the file is broken. It probably is not. QuickTime supports a narrow set of codecs. Many MOV files use video or audio formats it cannot decode, even though the file itself is intact. The fix depends on one thing: whether the codec is unsupported or the file is genuinely damaged. Both are diagnosable with free tools already on your Mac or available without cost.

Why QuickTime Rejects Some MOV Files

QuickTime Player X supports H.264, HEVC (H.265), ProRes and AAC. If your MOV file uses something else, the compatibility error appears even when the file opens fine in other players. The .mov extension only tells you the container, not the codec inside. A MOV file can be perfectly valid and still get rejected.

The file is not corrupt. It is encoded in a way Apple's player does not support. Find out what codec is actually inside before you try anything else.

Check the Codec with Free Tools

Use ffprobe to Inspect the Streams

Confirm whether the problem is a codec issue or a file structure issue before you attempt a repair. Install ffprobe, part of the FFmpeg suite, via Homebrew or download a static build. Open Terminal and run:

Type ffprobe file.mov and press Return.
Look for the Stream lines. They show the video and audio codecs, for example h264 or hevc.
If you see mjpeg or vp9, that is why QuickTime rejects the file.

When ffprobe reports the file's duration and streams normally, the file is not damaged. When it reports 'moov atom not found', the file is missing its index and needs repair, not a different player.

Test with VLC to Separate Codec from Damage

Let VLC Be the Judge

Open the MOV file in VLC. VLC uses its own decoders and plays many MOV files QuickTime rejects. If VLC plays the file without issues, the codec is unsupported by QuickTime but the file is fine. If VLC also fails or shows a black screen, the file is damaged or incomplete.

Drag the file onto the VLC icon, or open VLC and use File > Open. If it plays, you have two choices: convert the file to a QuickTime-compatible format, or re-wrap it without losing quality.

Fix an Unsupported Codec by Re-wrapping

If the codec is unsupported but the file plays in VLC, re-wrap the container. This does not re-encode the video. You lose no quality. Use ffmpeg with the -c copy flag:

Open Terminal.
Run ffmpeg -i in.mov -c copy out.mov.
Wait for the process to finish. The output file has the same video and audio streams but a new container.

When the original file uses a codec QuickTime supports, such as H.264 or HEVC, this re-wrap makes QuickTime open it. When the codec is truly unsupported, re-wrapping will not help. Re-encode instead with ffmpeg -i in.mov -c:v libx264 -c:a aac out.mp4. That changes the file and reduces quality. Only do it if you must have the file in QuickTime.

When the MOV File is Damaged or Incomplete

Diagnose a Missing or Broken Index

If ffprobe reports a missing moov atom, or if VLC cannot play the file, the problem is not the codec. A MOV file needs a moov atom (the index) at the beginning or end of the file. When that index is missing or damaged, QuickTime cannot open the file even if all the video data (the mdat atom) is present.

This happens when a screen or camera app is force-quit or loses power while recording. The file may be large and contain all the video data. Without the index, QuickTime has no way to locate the frames. No player will open it until the file is repaired.

Rebuild the Index

You need a repair tool that can reconstruct the moov atom. These are not built into macOS. The mov.repair website offers an online repair option that handles this kind of damage without requiring you to install software.

HEVC and Hardware Limitations on Mac

Check Your Mac's HEVC Support

If your MOV file uses HEVC (H.265), QuickTime may reject it on older Macs. Apple lists HEVC support from macOS High Sierra (10.13) onward. Even with a supported codec, the Mac's hardware must be able to decode it in real time. On an older Mac or a macOS version before High Sierra, QuickTime shows the compatibility error.

Check your macOS version by clicking the Apple menu and choosing About This Mac. If you are on High Sierra or later, HEVC should work, provided your Mac's processor or GPU supports it.

Work Around the Limitation

Use VLC to play the file. VLC does not depend on Apple's hardware acceleration. Or re-encode the file to H.264, which is more universally supported. Upgrade your macOS if your hardware allows it.

Preventing Future MOV Compatibility Problems

Stop the Error Before It Happens

Always stop the recording app properly before closing it or shutting down your Mac.
Make sure your screen recorder has enough free disk space before you start.
Keep your macOS updated to get the latest codec support.
For important files, keep a backup in a second format, such as MP4 with H.264.
If you share a MOV file with someone who uses QuickTime, check the codec first with ffprobe.

Separate an unsupported codec from a damaged file and you can decide fast whether to re-wrap, re-encode, or repair. Most of the time, the fix is simple and free.