MOV vs MP4: why your iPhone video plays on the phone but not on your PC

MOV and MP4 are near-identical twins

The extension is a red herring. When the ISO standardized the MP4 format, it started from Apple's QuickTime container, the one that uses the .mov extension. Both are built the same way, out of nested boxes (the older name, atoms, is the one that survives in error messages): a big block holding your compressed audio and video frames, and a small index that records where every frame sits, how long it lasts, and how the picture and sound line up.

A MOV and an MP4 have the same anatomy: a large block of footage plus a small index. The extension mostly says which ecosystem wrote the file.

Because the layouts are so close, the container itself is almost never why a clip won't open. The two things that actually decide whether a video plays are the codec (the language the frames are compressed in, which sits inside the container) and whether the file is structurally intact. Confusing those two with each other, or with the extension, is what sends people down the wrong path. For the full anatomy of the container and its index, seeMP4 anatomy: the moov atom.

What actually trips up your PC: HEVC

Since the iPhone 7, Apple's default capture format has beenHEVC (also called H.265), a newer codec that packs the same quality into roughly half the bytes of the older H.264. Your iPhone has a hardware HEVC decoder, so it plays those files instantly. A typical Windows PC does not: Windows ships without an HEVC decoder, and until you add one, players that rely on the system codec show a black frame, play the audio with no picture, or throw an error likethis item was encoded in a format that's not supported.

This is the crucial distinction: the file is perfectly healthy. Nothing is broken and nothing needs repairing. The PC simply can't read the language the frames are written in. That's why the same clip plays on the phone and stalls on the laptop, and why a repair tool is the wrong instrument here entirely. The right fixes are a decoder or a converter, covered below.

The container plays a bit part. Windows' built-in Media Player has historically been lukewarm about the .mov extension even for H.264 video, which is where the "rename it to .mp4" folk remedy comes from. Sometimes that nudge is enough for a fussy player to accept a healthy file. But it does nothing about the codec inside and nothing about damage, so treat it as a quirk, not a fix. The distinction between "install a codec" and "repair the file" is worth understanding on its own; we pull it apart incodec vs container.

If it plays on the phone, the file isn't broken

Here is the single most useful rule for this whole situation, and it keeps people from wasting time on the wrong tool: a file that plays anywhere is not corrupted. When your iPhone plays the clip back cleanly, it has already decoded every frame; the footage and the index are demonstrably intact. Whatever is stopping your PC is happening on the PC's side, not in the file.

So resist the urge to "repair" a video that still plays on the phone. There is nothing structurally wrong to rebuild, and running repair on a healthy file accomplishes nothing. The problem is a gap between what your phone can decode and what your PC can, and you close that gap on the PC.

When it plays nowhere: that's the repairable case

The other scenario looks similar from the outside but is a different animal. The clip won't open on the PC and it won't open on the phone, or the Photos app shows an exclamation mark where the thumbnail should be. Now the file itself is damaged, and repair is exactly the right tool.

The usual cause is an interrupted ending. A MOV's index is written only when the recording or transfer finishes. A call interrupting a recording, the battery dying, the Camera app crashing, or an AirDrop that dropped partway all stop the file before that finalizing step, leaving the footage on disk with no map to it:

An interrupted MOV: the footage survived, but the index that was due to be written at the end never was, so no player can navigate the file.

ffmpeg names this bluntly: moov atom not found. A truncated AirDrop or iCloud download produces a close cousin, a file cut short so its index is missing along with the tail. Both are structural damage, both leave the surviving footage intact, and both are whatindex rebuilding exists to fix. One honest caveat: the last seconds still sitting in the camera's memory buffer when it was interrupted were never flushed to storage, so they're genuinely gone, not merely stranded.

Fixing each case, in the right order

Sort your clip into one of the two cases first, then apply the matching fix. A ten-second test settles it: try the file inVLC, which bundles its own decoders and tolerates damage other players refuse.

It plays in VLC (or on the phone): a codec gap

The file is healthy; your PC just lacks the decoder. On Windows, install Microsoft's HEVC Video Extensions from the Store so system players can read H.265, or simply keep using VLC, which needs nothing extra. If you want a file that opens everywhere without fuss, convert it to H.264 MP4 once with a tool like HandBrake, accepting the small quality and file-size cost that re-encoding always carries. None of this is repair, and none of it should touch a repair tool.

It plays nowhere: structural repair

If VLC also refuses it, the structure is damaged, and now repair is the job. A repair tool reads what's left of the file, finds the surviving frames, and rebuilds the container and index around them, without re-encoding, so HEVC footage comes back at full quality. Because the files involved are often multi-gigabyte and frequently personal, doing this without uploading anything is the sane default. Point a MOV at MOV repair or an MP4 at MP4 repair; the diagnosis will also tell you if you're in the "plays fine, wrong codec" case and repair isn't what you needed after all.