An iPhone video that won't play on Windows is usually an HEVC file the PC can't decode — not a corrupt file. Apple names the codec plainly: "HEVC (High Efficiency Video Coding), also known as H.265, for videos." That is what the camera records while your iPhone's Formats setting is on High Efficiency.
The file itself arrived intact. The player simply has nothing it is willing to use to decode that stream.
What Windows is actually choking on
Apple's reason for shipping HEVC is storage: "HEIF and HEVC offer better compression than JPEG and H.264, so they use less storage space on your devices and iCloud Photos, while preserving the same visual quality."
The cost is compatibility, and Apple says as much. It describes the older formats — JPEG and H.264 — as the ones that "are more broadly compatible with other devices and operating systems."
Read that phrasing carefully: more broadly compatible, not universally compatible. Apple is describing a spectrum, not a switch.
And the single most useful sentence Apple publishes on this is the one most articles skip, because it tells you which of your clips are the risky ones:
"On some older devices, support for HEVC is affected by the resolution and frame rate (fps) of the video. Resolutions of 1080p or lower and frame rates of 60 fps or lower are more broadly compatible with older devices."
That is a much better model than "just switch to H.264." Apple frames HEVC compatibility as a function of resolution multiplied by frame rate. The sentence's own scope is "some older devices" rather than Windows specifically — but it still gives you a ranking of what to suspect first.
Apple's manual says iPhone "records video at 30 frames per second (fps)" by default, and that "depending on your iPhone model, you can change the fps rates to 24, 25, 30, 60, or 120," with formats "like HD, 4K, HD (PAL), and 4K (PAL)." So if a 1080p clip plays and a 4K clip from the same phone doesn't, you haven't found a mystery — you've found the boundary Apple describes. Apple also notes that "faster frame rates and higher resolutions result in larger video files," which is the same axis seen from the storage side.
The fastest fix: re-encode the clip you already have
For a file already sitting on your desktop, the settings on your phone are irrelevant — that file is already HEVC. Re-encoding it to H.264 puts it in the format Apple itself calls the compatible one: switching the camera to Most Compatible means, verbatim, "your camera will capture photos and videos in JPEG and H.264 formats."
Try it right here
Runs in your browser. Your file is not uploaded anywhere.
This runs inside your browser tab — the video is read from disk and re-encoded locally, so nothing is uploaded. That matters here because the files people are trying to open on a PC are typically the long ones they didn't want to hand to a random website. If your file carries a .mov extension, MOV to MP4 is the same job with the container named up front; the rest of the Clapr toolbox covers the neighbouring cases.
One trap worth naming: Apple's spec sheets describe what the camera records in terms of codecs, not filenames — the iPhone 17 spec page lists "Video formats recorded: HEVC and H.264." The extension on your file doesn't tell you which of those you got, so judge by what plays, not by what it's called.
Stop it happening on the next shoot
If you keep hitting this, change what the camera captures. Apple's own Windows-oriented guidance is to tap Most Compatible under Settings → Camera → Formats.
Three conditions Apple attaches to that setting, none of which you should skip:
- It only applies going forward. "All new photos and videos will now use JPEG or H.264 format." Everything already in your library stays as it was.
- It only appears on capable hardware. "This setting is available only on iPhone and iPad devices that can capture media in HEIF or HEVC format" — Apple lists that as "iPhone 7 or iPhone 7 Plus or later."
- It's reversible. "To return to using the space-saving HEIF and HEVC formats, choose High Efficiency."
Other causes, in order of likelihood
The transfer path didn't convert anything. Apple documents that importing over USB may handle this for you: "When you import HEIF or HEVC media from an attached iPhone or iPad into Photos, Image Capture, or a PC, the media might be converted to JPEG or H.264. If you don't want it to be converted, open Settings, tap Apps, tap Photos, then scroll down and tap Keep Originals." Note the word might — Apple does not promise conversion, and Keep Originals is documented as the switch that prevents it. For the PC side of that import, Apple's instruction is to "install the Apple Devices app from the Microsoft Store."
The file came from iCloud Photos. That path is explicitly not a conversion path: "If sharing this media via iCloud Photos, the media is preserved in its original format, resolution, and frame rate." An HEVC clip synced through iCloud stays HEVC. Apple adds a related snag for imports: "if you have iCloud Photos turned on, you must download the original, full resolution versions of your photos to your iPhone or iPad before you import to your PC."
It came over AirDrop, Messages or email and still didn't convert. Apple's wording here is conditional on the receiver: "if sharing this media using other methods, such as AirDrop, Messages, or email, and the receiving device doesn't support the newer media formats, the media might automatically be shared in a more compatible format, such as JPEG or H.264." Conditional, and might.
You changed the wrong "Most Compatible." There are two settings with that name and they do different things. The one in the share sheet is documented as: "Tap Automatic for the best file format for the destination, tap Current to prevent a file format conversion, or tap Most Compatible and files may convert to JPEG or MOV." That is the share-time output format. The capture-time one lives in Settings → Camera → Formats and produces JPEG and H.264. Setting one does not set the other.
It's ProRes, not HEVC. On Pro models the recorded list is longer — "HEVC, H.264, ProRes, and ProRes RAW" — and Apple notes that "apps might transcode a ProRes video to a smaller H.264 format if ProRes isn't supported." For the RAW variants specifically, Apple publishes a Windows component: "to enable playback of ProRes RAW and ProRes RAW HQ video files in compatible applications on Windows systems, install Apple ProRes RAW for Windows." That statement covers ProRes RAW and ProRes RAW HQ only.
It plays, but the colour looks off. Apple documents an HDR fallback: "On supported models, iPhone records video in HDR and shares HDR videos with devices using iOS 13.4, iPadOS 13.4, macOS 10.15.4, or later; other devices receive an SDR version of the same video."
How to tell it worked
Play the converted file in whatever refused the original — the same app, not a different one, or you've tested nothing. If you switched the camera setting, shoot a fresh five-second test clip and move that across; older clips in your library are unaffected by the change.
FAQ
Why does the video play on my iPhone but not on my PC? Because the codec differs from what the PC can decode. Apple records in HEVC (H.265) under High Efficiency and describes JPEG/H.264 as the formats that are "more broadly compatible with other devices and operating systems."
Does switching to Most Compatible convert my existing videos? No. Apple's wording is "all new photos and videos will now use JPEG or H.264 format." Clips already shot stay in their original format.
Why does my 1080p clip play and my 4K one doesn't? Apple ties HEVC support on some older devices to resolution and frame rate, stating that "resolutions of 1080p or lower and frame rates of 60 fps or lower are more broadly compatible with older devices." Higher-spec captures sit outside that band.
Will importing over USB fix it automatically? Sometimes. Apple says media "might be converted to JPEG or H.264" on import into Photos, Image Capture, or a PC — and that Keep Originals is the setting that stops that conversion.
Is there a way to check the codec before converting? Apple's spec pages describe recorded formats as codecs, not extensions, so the filename won't tell you. For anything beyond that, check the official documentation. Practically, re-encoding to H.264 settles the question either way.
More playback and export troubleshooting in the fix guides; for the closely related cloud case, see Google Drive not playing HEVC/H.265. Apple quotes checked 19 September 2026 — verify against Apple's official documentation before relying on them.
