Why a MOV File Won't Play on Windows (and How to Fix It)

By Andrew Butson · July 2, 2026 · 7 min read

Someone sends you a .mov, whether from an iPhone, a Mac, or a video call recording, and Windows Media Player or the default Movies & TV app either refuses it outright or plays the audio with a black or frozen video. The file isn't corrupted, and this isn't a rare edge case: it's one of the most common cross-platform video complaints there is, because "MOV" describes the box the video is shipped in, not what's actually inside it.

The fix depends on knowing which of two different problems you've actually hit: a genuinely dead piece of software, or a codec Windows was never taught to decode. Either way, there's a reliable answer.

Container vs codec: why one .mov plays fine and another doesn't

.mov is a container format, Apple's QuickTime File Format, and a container is just a box: it defines how video, audio and metadata are packaged together, but it says nothing about how the video itself is encoded. The actual video data inside a MOV is usually compressed with either H.264, a codec so widely supported it plays almost everywhere without a second thought, or HEVC (H.265), the newer, more efficient codec Apple has defaulted to on iPhones for several years now for 4K and slow-motion recording. Two .mov files can look identical by extension and behave completely differently on the same PC, because one holds H.264 and the other holds HEVC.

That's why the problem often isn't consistent: an older MOV, or one exported from software that still defaults to H.264, opens fine, while a MOV straight off a recent iPhone in 4K sometimes doesn't. That's not because the container changed, but because what's packed inside it did.

Why QuickTime for Windows isn't the answer anymore

The obvious-looking fix, installing QuickTime since that's the software the format is named after, doesn't actually work, and hasn't for years. Apple stopped updating QuickTime for Windows back in 2016, and shortly after, security researchers found unpatched vulnerabilities in it; the guidance at the time was to uninstall it rather than keep using it, and it has had no updates since. It also never gained HEVC support even while it was maintained, so installing it wouldn't fix a modern iPhone MOV even if it were still safe to run.

Every fix that actually works

Skip QuickTime entirely. These are the routes that hold up:

• Install VLC: it's free, plays essentially every container and codec combination in circulation including HEVC-in-MOV, and needs no configuration. It's the single most reliable universal fix for a MOV that Windows' own apps reject.
• Add the HEVC extension to Windows' built-in apps: if you specifically want Movies & TV or the Photos app to handle it rather than a separate player, Windows offers an "HEVC Video Extensions" app in the Microsoft Store, the same one, and the same licensing situation, that HEIC photos run into on Windows. Some PCs, especially from major manufacturers, ship with a free manufacturer-licensed version already installed.
• Change the capture setting at the source, for iPhone footage you control: Settings → Camera → Formats → "Most Compatible" records H.264 video (and JPEG photos) instead of HEVC/HEIC from then on, trading a larger file for zero playback problems anywhere. It only affects video shot after the change.
• Convert the file you already have to MP4: the most direct fix for a MOV someone's already sent you, since it re-encodes the video into H.264 inside an MP4 container, the combination the fewest devices and apps have trouble with.

Where converting locally actually helps

Morphr transcodes MOV to MP4 entirely in your browser, using a real video engine rather than just relabelling the file. That matters, because a MOV holding HEVC genuinely needs re-encoding, not just repackaging, to become the H.264 MP4 that plays everywhere. That's exactly the fix a compatibility problem like this needs: the output plays on Windows, older phones, upload forms and video call platforms that choke on HEVC or MOV specifically.

The honest trade-off is time, not just quality: transcoding a whole video file, frame by frame, inside a browser tab is genuinely heavier work than the format conversions Morphr does for images or documents, so a large or long clip can take real minutes rather than seconds, running on your own device's processor rather than a server's. For a short clip it's barely noticeable; for a lengthy 4K recording, expect to wait. Nothing is uploaded either way; the trade for that privacy is that your own machine does the work.

Frequently asked questions

Should I still install QuickTime to play a MOV on Windows?

No. Apple stopped updating QuickTime for Windows in 2016 and the guidance since has been to uninstall it over unpatched security issues, and it never supported HEVC even while it was maintained. VLC is the safer, more capable, actively maintained alternative for the same job.

Why does one MOV from my iPhone play fine and another one doesn't?

It almost always comes down to which codec is packed inside: H.264, which is broadly supported, or HEVC, which iPhones default to for 4K and slow-motion footage and which plenty of Windows software still can't decode without an extra codec. The container extension, .mov, is the same either way; what's inside it differs.

Will converting MOV to MP4 lose quality?

There's some quality cost because the video is being fully re-encoded rather than just repackaged, but at a reasonable bitrate it's not something you'd notice by eye. What you gain is universal playback: MP4 with H.264 is the format the widest range of devices, players and upload forms handle without issue.

Is there a faster fix than converting the whole file?

If you have access to the iPhone that shot the footage, switching Settings → Camera → Formats to "Most Compatible" prevents the problem for anything filmed from then on, which is faster than converting after the fact, but it does nothing for video you've already been sent.