You download a Reel at 1080p, move it to your phone, and it will not play. The thumbnail shows, the file is clearly there, and the player either shows a black screen or refuses to open it. The resolution is fine. The problem is the codec — the format the video pixels are actually compressed in — and it is a trap that catches downloads specifically, because a downloaded file is opened outside the browser that made it look fine.
Two codecs, very different reach
Almost every video you have ever played was encoded with one of two codecs.
H.264 (also called AVC) is the old, universal one. It is nearly twenty years old, it is hardware-decoded by effectively every phone, television, browser and media player made this century, and it is the format QuickTime, the iOS photo viewer and the Windows built-in player expect without complaint.
VP9 is Google's newer, royalty-free codec. It compresses better than H.264 — smaller files for the same quality — which is exactly why platforms like it. But its reach is narrower. VP9 plays reliably in Chrome and Chromium-based browsers. Wrapped in an MP4 container and handed to Safari, the iOS system player, QuickTime or Windows' default player, it frequently will not open at all.
That gap is invisible while the video stays in a browser. It becomes the entire problem the moment the file is downloaded.
Instagram serves more VP9 than people realise
This is not a rare edge case. Instagram increasingly delivers public Reels as VP9-only DASH — a manifest listing several VP9 renditions and no H.264 fallback whatsoever.
A concrete example from a live Reel: the DASH manifest offered eight VP9 renditions, topping out at 1080p, and not a single H.264 rendition anywhere in the document. If your downloader simply picks the highest resolution it can find, it hands you a 1080p VP9 file — technically the best rendition available, and one that will not open on an iPhone, in QuickTime, or in the default Windows player.
The browser preview worked because you were in Chrome. The download failed because you were not opening it in Chrome any more.
Why playability has to beat resolution
Faced with a VP9-only manifest, a downloader has to make a choice, and the honest one runs against instinct. It is tempting to always serve the highest resolution — bigger number, better download. That is the wrong rule.
The right rule is playability first, resolution second. A 720p H.264 file that opens on every device is a finished download. A 1080p VP9 file that will not open on the recipient's phone is a support ticket. Where a manifest is VP9-only but a pre-muxed H.264 progressive rendition exists lower down — commonly at 720p — the H.264 file is the better download for most people, because "it opens" outweighs "it is 360 more pixels tall".
Among renditions that are equally playable, more pixels wins. The ranking only demotes resolution when the higher-resolution option is one a lot of devices cannot decode. This is a deliberate trade, not a limitation, and it is worth stating plainly rather than quietly serving a file that fails.
How to tell what you actually downloaded
If a file will not play, or you just want to know what you have, three tools will tell you the codec:
- ffprobe (part of ffmpeg), from a terminal:
`` ffprobe -v error -select_streams v:0 -show_entries stream=codec_name yourfile.mp4 ``
This prints h264, vp9 or av1 and nothing else.
- VLC: open the file, then Tools → Codec Information (or Window → Media Information on macOS). The codec name is listed per stream. VLC is also the practical rescue player — see below.
- MediaInfo: a free cross-platform app that shows the codec, profile, bitrate and container in one panel, which is the friendliest option if you do not live in a terminal.
If the video stream reads vp9 and the file will not open in your system player, you have found your answer.
What to do if you already have a VP9 file
You have two realistic options.
- Play it in VLC. VLC bundles its own decoders and plays VP9 on every platform, including iOS and Windows, without touching the system codecs. If your only goal is to watch the file, this is the fastest fix and it costs nothing in quality.
- Transcode it to H.264. If you need a file that opens everywhere — to send to someone, to import into an editor, to play in the system viewer — re-encode it:
`` ffmpeg -i input-vp9.mp4 -c:v libx264 -crf 18 -c:a aac output-h264.mp4 ``
Be honest with yourself about the cost: this is a generation loss. You are decoding an already-compressed video and compressing it again, so the H.264 output is very slightly softer than the VP9 source even at a high quality setting. A low -crf (18 is visually near-transparent) keeps the loss small, but it is never zero. Transcode when you need compatibility, not as a default.
The cleaner path is to have the download decision made correctly in the first place, which is why the Reels downloader prefers a playable rendition over a marginally larger unplayable one.
Why "we support 4K" is usually a story
Since resolution is the headline number, some tools advertise 4K downloads. Treat that with suspicion. Instagram generally re-encodes uploads to a 1080-pixel width, so a genuine 4K rendition rarely exists to be served regardless of what the creator's camera shot. A tool that produces a 4K file from a 1080p source is upscaling — interpolating extra pixels — which increases the file size and the pixel count without adding any real detail. It is a bigger file of the same picture. The honest ceiling for most Instagram video is 1080p, and a tool that claims to beat it is usually inventing pixels.
Where this is heading: AV1
The direction of travel is AV1, the successor to VP9 from the same alliance. It compresses better still, it is royalty-free, and platforms are rolling it out for the same bandwidth reasons they adopted VP9. Its compatibility story today looks a lot like VP9's did a few years ago: strong in modern Chrome, patchy in system players, increasingly hardware-decoded on new phones but absent on older ones. The same rule applies — check the codec before you trust the resolution, and prefer the file that will actually open on the device you are sending it to.
A note on scope and rights: download videos you made, own, or have the creator's explicit permission to save. Compatibility does not change permission — a file that opens everywhere still needs to be one you are allowed to keep. And none of this is legal advice; the rules on copying other people's content vary by country, so check what applies where you are. If you want the audio side of the same story, the companion post on silent downloads covers why some files arrive with no sound at all.