The resolution label on your downloaded video is probably wrong

5 min read

If you have ever saved a video and felt the quality didn't match the number attached to it, you were probably right, but not for the reason you'd assume. The file usually isn't the problem. The label is.

Instagram's page metadata can describe a display box rather than the dimensions of the delivered video. A portrait file at 720×1280 and a page display box at 640×1136 are different measurements, even though both look like a plausible resolution.

Check it yourself in ten seconds

This is worth verifying rather than believing, and it takes no tools you don't already have. Find any short video you've saved from a social platform and open its properties.

  • Windows: right-click, Properties, Details tab. Look at Frame width and Frame height.
  • macOS: select the file and press Command-I, or open it in QuickTime and press Command-I.
  • Any platform: VLC's Media Information window shows the decoded stream size.

Now compare that against whatever the tool told you when you saved it. If the file says 720 and the tool said 640, or the tool said "SD" for something that is plainly HD, you have found a mismatch between the label and the file.

What Instagram actually hands over

Some post responses include a dimensions field next to a media URL. Depending on the response shape, it can describe the post's display area rather than the encoded stream. Proximity to a URL does not establish what was measured.

It describes the post's display box, the space the post occupies in a feed layout. That figure is derived from the aspect ratio the creator uploaded and the size the interface wants to render it at. It is a layout number that happens to be expressed in pixels, which makes it easy to mistake for a resolution.

The file being served is produced separately, by a transcoding pipeline that has its own opinion about what size to encode at. Nothing forces those two numbers to agree, and frequently they don't.

Where the real number is hidden

Some media URLs carry another useful clue: a transcode tag identifying a rendition. It is metadata, not a substitute for inspecting the file.

Instagram's CDN links include a parameter named efg, whose value is a base64-encoded JSON object. Decoded, it describes the asset the CDN is about to serve, including a transcode tag that looks roughly like this:

The 720 is a rendition label. A label alone does not specify both dimensions, especially for portrait video. Tags can vary or be absent, and they should not be treated as a promise that a file has been inspected.

Platforms commonly produce several renditions at different sizes and bitrates. Which one is exposed can depend on the endpoint and request. Do not assume that a listed rung proves every post has that rendition, or that the platform retains the upload unchanged.

Where the number comes fromWhat it actually describes
The dimensions field in the page dataMay describe the display box rather than the encoded stream
The transcode tag inside the media URLA rendition hint; not necessarily both encoded dimensions
Your file's properties dialogGround truth: what you actually received

These sources answer different questions. A robust label should acknowledge missing metadata rather than inventing dimensions from an HD badge.

Why a real 1080p video can still look soft

Correcting the label doesn't make anyone's video sharper, and it's worth being honest about that. There is a second, separate reason uploads come back looking worse than they left, and it has nothing to do with metadata.

Resolution is a count of pixels. It says nothing about how much data was spent describing them. Every upload is re-encoded on arrival, and that re-encode targets a bitrate, a data budget per second of video. A 1080p file at a generous bitrate and a 1080p file at a thin one have identical dimensions and visibly different quality.

This is why the footage that suffers most is the footage that's hardest to compress: fast motion, confetti and rain, water, fine fabric texture, film grain, smoke, and gradients in dark scenes. A static talking head survives compression almost untouched. A drone shot over trees falls apart. Same resolution, same platform, wildly different outcome.

So there are two independent things going on, and conflating them is the usual source of confusion. The label is often wrong, which is a reporting problem and fixable. The encode discarded detail on upload, which is a physics-of-compression problem and is not recoverable by anyone, using any tool, at any price. Detail that was thrown away during transcoding does not exist to be downloaded.

Images have their own variants

Image posts can expose several versions too, but their delivery does not require combining video and audio tracks.

An image response may include a list of sizes. Choosing a larger available variant can avoid a small preview, but list order and metadata are not guarantees. Instagram can resize or recompress an image before making those variants available.

When saving a photo, inspect the downloaded image's dimensions just as you would a video. A platform-served original variant should not be confused with a photographer's camera original.

What you can actually control

If you're the one publishing, the decisions that matter happen before upload. After that, the platform controls the processing.

  1. Export at the platform's native size rather than above it. Uploading a 4K master to a service that serves 1080p just means the downscale happens on their encoder instead of yours, and yours is the one you can tune.
  2. Spend your bitrate before upload, not after. A generously encoded source gives the re-encoder better material to work from. A file that's already been squeezed once gets squeezed again, and the damage compounds.
  3. Shoot with compression in mind. If a shot is all motion and fine texture, expect it to suffer, and consider whether a slower shot carries the same idea.
  4. Keep your masters. The version on the platform is a lossy copy that you cannot recover the original from. This is the one that people only learn the hard way.

Keep your own original. A platform copy has already been re-encoded, so it may have lost detail you cannot recover. A deleted post or closed account could also make that remaining copy unavailable.

The short version

Page dimensions, rendition tags and file properties are different sources of information. Use the first two as clues, and inspect the saved file when exact width, height or bitrate matters.

If you want to see the difference, save a reel and check the file against what you were told. Whatever it says, believe the file.

More reading