Why your MOV file won't play on Windows (and how to fix it)

A MOV that will not open on Windows has one of two causes, and they need different fixes. Either the file contains HEVC or ProRes video, which Windows cannot decode on its own, or it contains ordinary H.264 and only the .mov wrapper is confusing the player. Drop the file on the MOV to MP4 converter and it reads the codec back to you before you convert anything.

If it says H.264, the fix is a stream copy into an MP4: a few seconds, no re-encode, no quality loss, nothing uploaded. If it says HEVC or ProRes, the picture has to be re-encoded to H.264, which takes longer but produces a file Windows will open anywhere.

The two causes, and how to tell them apart

A .mov file is a container — a box. What matters for playback is the codec inside it, and Windows treats those two things separately, which is why the error messages are so useless.

MOV and MP4 are close relatives: both are built on the ISO base media file format, and MP4 was standardised from Apple's QuickTime container. That is why a MOV holding H.264 video and AAC audio can usually become an MP4 without touching a single frame of picture. The bytes are already in the right shape. Only the wrapper changes.

So the question is never "does Windows support MOV". It is "does Windows support what is inside this MOV". Three answers are common:

• H.264 + AAC. Windows can decode both. Playback problems here are the container, the player, or a missing file association — not the codec.
• HEVC (H.265) + AAC. This is what a modern iPhone records by default. Windows does not ship an HEVC decoder; Microsoft's own codec FAQ points you at a Store extension for HEVC, VP9, AV1 and MPEG-2.
• ProRes. From professional cameras, Final Cut, and iPhones in ProRes mode. Windows has no consumer decoder for it at all, and the files are enormous.

You cannot tell these apart from the file name or the Explorer icon. You have to read the header, which our in-browser codec checker does locally: container, video codec and profile, resolution, frame rate, audio codec.

Case one: it is H.264, and the container is the whole problem

This is the good outcome, and more common than people expect — files off an older iPhone, a screen recorder, or a camera set to compatibility mode all land here. Windows will often play them once you point them at the right player, but the file still causes trouble elsewhere: web forms, PowerPoint, a colleague's machine. Changing the wrapper solves all of it at once.

A remux — a stream copy — writes the existing video and audio streams into an MP4 container untouched. No frames are decoded, and no quality decision is made, because there is nothing to decide. The output is bit-for-bit identical picture in a box Windows, Android, PowerPoint and every upload form recognise, and it finishes in seconds even for a long clip, because the work is plumbing rather than encoding.

Case two: it is HEVC or ProRes, and Windows genuinely cannot decode it

If your iPhone is set to High Efficiency — the default for several generations now — it records HEVC inside a .mov. That file plays perfectly on the phone and on a Mac, then lands on a Windows PC as a black rectangle, a frozen first frame, or a "can't play" dialogue. Nothing is wrong with the file. You have two routes.

Install the decoder

Microsoft publishes HEVC Video Extensions in the Store, and some machines ship with a manufacturer-supplied version already installed — which is why an HEVC file plays on one Windows PC and fails on the next one in the same office. Installing it fixes that machine and only that machine. The file is unchanged, so it fails again on the next PC, in PowerPoint, and on plenty of Android phones and TVs. Fuller account: HEVC video that will not play on Windows 11.

Convert the file to H.264

This fixes the file rather than the computer. Every Windows install since the Windows 7 era decodes H.264, usually in hardware, and our HEVC to H.264 converter does the job in the page with nothing uploaded.

Be realistic about the time. This is a genuine re-encode and the browser build is single-threaded, so expect roughly real-time for 720p and slower for 1080p. A three-minute clip is fine; a forty-minute 4K recording is not a browser job. Files over 2 GB are refused outright — a 32-bit WebAssembly heap cannot address them — and past about 300 MB the page warns that it needs roughly three times the file size in free memory.

Fixing it, step by step, with nothing installed

1. Open the MOV to MP4 converter. The FFmpeg engine is compiled to WebAssembly and runs inside the tab, so the file never leaves your machine and there is no account.
2. Drag the MOV in and read the codec line it prints. That single line decides everything else.
3. If it says H.264, the page offers a stream copy and says so in words. Take it — that is the lossless, near-instant path.
4. If it says HEVC or ProRes, the page tells you it has to re-encode. Leave quality on High unless the file is long, press Convert, and keep the tab in the foreground.
5. Save the MP4 and double-click it. If it opens in the built-in player, it will open everywhere else too.

One caveat, which the tool states up front: subtitle tracks and extra audio tracks are dropped, and only the first video and first audio stream survive. Irrelevant for a phone clip; not irrelevant for a film with a commentary track.

Symptoms that look like "won't play" but are something else

Picture but no sound. The video decoded and the audio did not. MOV files from screen recorders and some cameras carry uncompressed PCM or AC-3 audio that a stock Windows player will not touch; re-encoding the audio to AAC fixes it, as the guide on video that plays with no sound explains.

Sound but a black screen. Almost always HEVC: the audio decoder works, the video decoder does not exist.

It plays sideways. iPhones record in one physical orientation and store a rotation flag. Good players honour it; some Windows players and editors ignore it. A re-encode bakes the correct orientation into the picture; a stream copy carries the flag across intact, which is usually what you want.

No thumbnail in Explorer. The thumbnail generator needs the same missing decoder. A symptom of case two, not a separate fault.

Why "just install VLC" is not really the answer

VLC carries its own decoders and will play almost any MOV you throw at it. If you only need to watch the clip once, on your own machine, and you are allowed to install software, that is reasonable.

It stops being the answer the moment the file has to go anywhere. VLC does not change the file, so the same MOV will still refuse to embed in a PowerPoint slide, still fail on the recipient's phone, and still be rejected by upload forms that accept only MP4. It is also no help on a locked-down work laptop, a school machine, or a Chromebook, which is why we wrote a separate guide on converting video on a Chromebook. Converting once fixes the file for every device it will ever reach; installing a player fixes one computer.

Stopping it happening again

If MOV files keep arriving from the same iPhone, the sender can fix it at source. On the phone, Settings → Camera → Formats → Most Compatible switches recording from HEVC to H.264. New recordings are still .mov, but the codec inside is one Windows understands, so every future file falls into case one. The trade is size: H.264 recordings are noticeably larger for the same footage.

Existing recordings are unaffected by that setting. For a backlog still on the phone, converting there beats moving it to a PC first: our iPhone video converter app uses the device's hardware encoder, so it is far faster than any browser on long or 4K footage and has no file-size ceiling. It always re-encodes, so it has no equivalent of the lossless remux, and on iPhone the first conversion is free while further ones need the paid upgrade (on Android it is free and unlimited). The walk-through is in converting MOV to MP4 on an iPhone, and if the file is bound for an Android handset rather than a PC, iPhone video that will not play on Android covers that close cousin of the same problem.