The download finished and the file won't play. It isn't corrupt.

Three symptoms, one cause

Audio plays, picture stays black. Player opens the file then quits. One app refuses the file while another plays it perfectly. Every one of those is a decoder saying no, and none of them is a truncated download.

A genuinely incomplete file behaves differently — it plays correctly until the point where the bytes stop, then ends. If your file fails at frame zero but reports a sane duration, the container parsed fine and the video track inside it is the problem.

That distinction saves you from re-downloading a file that was never broken.

What changed underneath you

Instagram spent years serving H.264 to essentially everyone. H.264 High Profile plays on anything with a screen manufactured this decade, which is why downloading Reels was boring for so long.

That's shifting. We caught a single Reel being re-encoded from H.264 to VP9 between two parses eight hours apart on 2026-04-23 — same shortcode, same post, different vencode_tag in the signed URL. The full observation is in watching Instagram roll VP9 across Reels, and Meta has since rolled parts of it back, which is its own kind of signal.

VP9 is a fine codec. It's also the reason your file won't open in QuickTime, because Apple's default player has never shipped VP9 support and shows no sign of starting.

So the same download flow that worked all last year can hand you a file your usual player rejects, without anything in the pipeline breaking. The platform changed its encoder, not your tool.

Find out what you actually have

Thirty seconds with ffprobe settles it:

ffprobe -v error -show_entries stream=codec_name,width,height -of default=noprint_wrappers=1 yourfile.mp4

You get the codec name and dimensions and nothing else to wade through. h264 means any player will handle it and your problem is elsewhere. vp9 or vp09 explains the black screen immediately. av01 means AV1, rarer still and supported by even fewer desktop players.

No ffmpeg installed and no desire to install it? Open the file in VLC and press Ctrl+J on Windows or Cmd+I on macOS. Same information, worse ergonomics, zero setup.

The fix, in order of how much you should want it

Change players. VLC decodes VP9, AV1, H.264, HEVC and most things you'll encounter, on every desktop platform, for free. This costs you one install and no quality, which makes every option below it a worse trade.

Re-encode to H.264 if some other tool in your chain demands it — an old editor, a TV that plays from USB, a client who wants an mp4 and won't discuss it. ffmpeg -i input.mp4 -c:v libx264 -crf 18 -c:a copy output.mp4 keeps the audio untouched and re-encodes only the video. CRF 18 is visually transparent for most content.

Understand what that second option costs. You are decoding a lossy stream and re-encoding it lossily. Even at CRF 18 you're spending quality you can't get back, on a file whose source was already compressed by Instagram. Do it because a downstream tool forces you, never as routine hygiene.

Grab a different quality tier. Instagram doesn't always re-encode every rendition at once, so the 720p variant of a post can still be H.264 while the 1080p one has moved to VP9. If our result card offers both, the lower tier is worth a try before you re-encode anything.

When it really is the file

Two cases where the download genuinely is at fault, and both look distinct from the codec symptom.

Truncation: the file plays normally and then stops early, or the duration reported by the player is shorter than the post. Usually a download interrupted mid-stream — network drop, tab closed, sleep. Re-download it.

Video with no audio track at all, where ffprobe shows a single stream. That's not a playback problem, it's a muxing one, and it has its own writeup in why your downloaded Reel has no sound.

Anything else that fails at frame zero with a full-length duration is a decoder problem. Check the codec before you check anything else.

For anyone building on top of this

The lesson we took from the VP9 episode is that codec is not a property you get to assume and cache. It's a property of the specific rendition you fetched, at the moment you fetched it, and Meta will change it under you without telling anyone.

Read the codec from the manifest rather than inferring it from the file extension or the URL path. An .mp4 container tells you nothing about what's inside — MP4 happily carries H.264, HEVC, AV1 and VP9. The container is a box; the codec is the contents.

MDN keeps the definitive compatibility table at developer.mozilla.org, and it's the reference worth checking before you promise a user their file will play anywhere.