Fix 'Unsupported format or damaged file' for iPhone MOVs in Premiere Pro

You've just shot something on your iPhone, dragged the MOV into Premiere Pro, and got slapped with Unsupported format or damaged file — Error code: 0xc00d5213. Annoying as hell. Let's fix it.

The Real Fix: Re-wrap to H.264

What's actually happening here is that modern iPhones (from the iPhone 7 onward, but especially the 12/13/14/15 series) default to recording video in HEVC/H.265 — a newer, more compressed codec. Premiere Pro's native importer doesn't always handle H.265 wrapped in MOV correctly, particularly on Windows. The 0xc00d5213 error is Windows Media Foundation's way of saying "I can't decode this."

1. Download Shutter Encoder (free, no watermark, actively maintained).
2. Open it, drop in your problematic MOV file.
3. Under Choose function, select Rewrap — not convert, just rewrap.
4. Set Output extension to .mp4 with H.264 codec (the default).
5. Click Start function. Takes seconds, not minutes.
6. Import the new MP4 into Premiere Pro.

The reason step 3 works is that we're not re-encoding the video stream — we're only changing the container from MOV to MP4 and keeping the video as-is. But here's the trick: if the source is H.265, Shutter Encoder's rewrap does force transcode to H.264.

When Rewrap Fails (True H.265 Files)

If you shot in 4K 60fps or ProRes, the rewrap-to-H.264 approach might still give you errors. In that case, you need a full transcode. Use Shutter Encoder > Choose function > H.264, set quality to Intermediate, and check Hardware encoding if your GPU supports it. This will re-encode the whole thing — slower, but bulletproof.

Alternative: Change iPhone Recording Format

Skip the problem at the source. On your iPhone, go to Settings > Camera > Formats. Under Video Capture, select Most Compatible instead of High Efficiency. This makes the iPhone record in H.264 + AAC in a MOV wrapper. You'll still get the error sometimes, but far less often.

Why Does This Happen on Windows but Not Mac?

Premiere Pro on macOS uses Apple's native VideoToolbox decoder for H.265 — it's baked into the OS. On Windows, it relies on Media Foundation, and Microsoft's HEVC decoder is a separate purchase (some PCs don't have it at all). So the same file works on a Mac and fails on Windows. That's the root cause — not a damaged file, not a bad card, just a missing decoder.

Less Common Variations

1. iPhone 15 Pro with Log or ProRes — Those files are actually .mov with ProRes 422 or 4444 codec. Premiere Pro can handle them, but needs a specific QuickTime decoder. Install Apple's QuickTime 7 (still works on Windows 10/11) or use Shutter Encoder to transcode to DNxHR.
2. HDR video from iPhone — If the file has Dolby Vision metadata, Premiere Pro may choke even after rewrap. Use ffmpeg to strip HDR metadata: ffmpeg -i input.mov -c copy -bsf:v hevc_metadata -map_metadata 0 output.mp4.
3. Corrupted file header — Rare but possible if you interrupted a transfer. Use ffmpeg -err_detect ignore_err -i input.mov -c copy output.mov to salvage it.

Preventing This Going Forward

Set your iPhone to Most Compatible (as above). If you're shooting professionally, buy the HEVC Video Extensions from the Microsoft Store ($0.99) — it gives Windows the decoder it's missing. For team workflows, standardize on DNxHR LB for delivery: transcode all iPhone footage on ingest using Media Encoder with a preset.

Bottom line: The error is never the file being "damaged." It's always a codec mismatch. Rewrap to H.264 or install the HEVC decoder. You'll never see 0xc00d5213 again.