Pixel aspect ratio: why stored dimensions can mislead
Stored width divided by height describes the frame grid, but it describes the displayed picture only when pixels are square and no other display transform applies. Non-square samples can make a legacy recording's intended shape differ from its numerical dimensions. Check sample and display aspect information before resizing an authorized copy.
Open the relevant downloader · Platform tools and access limits
Distinguish the grid from the intended display
Pixel aspect ratio describes the intended width of one displayed sample relative to its height. Square pixels have a ratio of 1:1. A display aspect ratio describes the complete picture's width relative to its height. These are separate measurements, even though modern square-pixel sources often make the distinction easy to overlook.
For an ordinary unrotated picture, display aspect ratio is frame width divided by frame height, multiplied by pixel aspect ratio. FFmpeg commonly calls the pixel measurement sample aspect ratio, or SAR, and the whole-picture measurement DAR. Other software can use different labels, so verify terminology in the receiving application's documentation.
This relationship explains why an older file's stored dimensions need not imply the intended visible shape. It does not establish which metadata value is correct when a source has been edited incorrectly. Use the original production context or a trustworthy reference to resolve that uncertainty.
Calculate a simple non-square example
Consider a hypothetical frame grid that is 720 samples wide and 576 high. With square pixels, its grid ratio is 5:4. If the intended sample aspect ratio is 16:15, multiplying 5:4 by 16:15 yields a 4:3 displayed picture. The display can therefore look correct at 4:3 without having a stored 4:3 grid.
The arithmetic is a teaching example, not an instruction to assign 16:15 to every 720×576 file. Production formats can have additional conventions and intended picture regions. A copied file may already have been resampled to square pixels, making the old signaling inappropriate.
Check a known circular object or a reliable source reference when judging the result. A person looking wider after a change suggests that the transformation needs review, but appearance alone cannot reconstruct uncertain source geometry. Keep the original and record which assumptions led to a test derivative.
Check conflicting receiver interpretations
Inspect the file's reported sample and display aspect values using a media-information tool. FFprobe can report stream geometry alongside codec information. If a player honors a non-square sample ratio while an editor treats the same samples as square, their previews can differ even though both read the file successfully.
Look for an import interpretation setting in the receiving editor's documentation. For a legacy editing project, correct source interpretation can be preferable to permanently resizing every retained original. A player window's fit or stretch setting can also distort the picture, so eliminate that simpler presentation issue before changing source geometry.
If container and stream signaling disagree, gather both reports and ask an experienced editor or the owner to inspect the export. Do not choose a ratio solely because it fills your screen. Filling a receiving rectangle is a layout goal, not evidence of the source's intended proportions.
Make a square-pixel derivative without silently changing shape
A receiving workflow may require square pixels. In that case, a permitted conversion can resample the source to an appropriate frame grid while preserving the intended display shape. Merely deleting the sample-aspect metadata can change how the same stored values are shown, rather than producing a correctly resampled picture.
FFmpeg's aspect-ratio guidance distinguishes stored sample shape from displayed shape. If you use an external processing tool, understand whether a setting changes signaling or actually scales the picture. SocialVidDownloader does not expose custom pixel-aspect correction, and changing a file extension does not perform that operation.
Label the derivative with its intended delivery use and keep the source for archive purposes. Compare the new file in the target receiver, checking proportions, captions and cropping. If intended geometry remains uncertain, preserve that uncertainty in the record instead of describing a guessed resize as a verified restoration.
Worked example
Worked calculation: width 720 divided by height 576 is 1.25. Multiply by a verified sample-aspect value of 16/15 to obtain about 1.333, or 4:3. A square-pixel derivative must preserve that displayed shape. Applying the same assumption to an unrelated 720×576 file without checking its source would be an unjustified correction.
Related guidance
Sources and verification
Reviewed 2026-10-08. Product behavior is limited to available source formats and provider access; it is not a promise that every public link works.