HandBrake Video Looks Stretched? Check Display Aspect and Pixel Shape

Diagnose stretched or squashed HandBrake output. Separate stored size, display aspect and PAR, check the source, and preview a correctly proportioned viewing copy.

If a HandBrake output keeps the whole picture but makes people look wider or thinner, compare its display aspect and pixel aspect ratio with the source. Do not start by cropping the image or forcing it to fill your screen. If only one player shows the distortion, investigate that player’s display settings before re-encoding the whole collection.

This guide covers readable videos and backups you own or are authorized to process. Keep the source and write any trial output to a separate file. It does not cover disc reading or copy protection.

Decide whether the problem is shape, missing edges or empty space

What you can see Check next
Heads or edges disappear, while the remaining image has normal proportions Compare the source and output at the same moment; follow the cropping guide.
The whole picture is present, but faces or familiar objects look stretched Compare stored dimensions, display aspect and pixel aspect ratio.
Shapes look correct, with black space around the picture Check whether the image and display have different proportions. Empty space alone is not an encoding fault.
The same output looks right in one player and distorted in another Check the affected player’s fit, zoom and aspect override, and whether it handles the file’s display information. This observation does not identify the cause by itself.

Do the comparison with the same scene, with any manually forced aspect ratio or zoom disabled where possible. A screen-filling image is not necessarily a correctly shaped one.

Storage size and display size answer different questions

Storage width and height describe the encoded pixel grid. Display aspect ratio describes the intended width-to-height relationship when the picture is shown. Pixel aspect ratio (PAR) describes the shape assigned to each pixel: 1:1 means square pixels.

These values need not describe the same rectangle. HandBrake’s anamorphic explanation discusses storing a picture at one shape and signalling how it should be displayed. Its historical examples are useful context, but that page is marked as a draft; do not use its old interface and command examples as a current recipe.

The current CLI reference separately defines storage width/height, display width and pixel aspect. A stored frame that is not 16:9 therefore is not, by itself, proof of a bad widescreen encode. Nor should every DVD be assigned the same numbers. See the DVD output decision guide for the wider workflow.

Check the source before changing the output

Open the source and check that its displayed proportions are credible. Note the selected title, the source’s dimensions and any reported display or pixel aspect. If the source already looks wrong, confirm its intended shape from the recording or its provider; copying a mistaken source interpretation is not a correction.

Save the Activity Log for the relevant job. It records the source scan and encoding activity, including settings and problems. Compare the source information and job settings instead of relying only on what you remember selecting in the interface.

Then inspect the output geometry in your installed version’s picture or dimensions controls. Labels can vary. Recheck the values after choosing a preset, especially if you have manually entered width or height.

When a square-pixel copy may help

If the destination’s requirements call for square pixels, or a comparison suggests trouble with non-square-pixel display, a square-pixel viewing copy is a candidate to test. It still needs the correct display shape. Merely changing the PAR label to 1:1 while keeping an inappropriate storage rectangle can change the picture’s proportions.

The current CLI calls this option --non-anamorphic. Its custom controls also distinguish --display-width from --pixel-aspect; those two options are mutually exclusive. --keep-display-aspect preserves the source display aspect when using custom anamorphic. These are descriptions of controls, not a complete command or a recommendation to set custom values blindly. Use HandBrakeCLI --help for the options available in your installed build.

Do not choose a universal output resolution from a tutorial. Keep the intended proportions, review the resulting dimensions, and test the destination. Turning anamorphic off is not a universal fix or a promise of lossless output.

Prove the change on a short section

Use HandBrake’s Preview to select a representative starting point and duration. Pick familiar shapes and visible edges; compare them with the source at the same moment. Check another section if the source changes picture format.

First inspect the result inside HandBrake’s Preview window. For external playback, make a separate short test encode: the current CLI provides --start-at for the starting offset and --stop-at for duration relative to that start, using matching units. These are option names, not a complete command. Play that test file in the destination application or device as well as your comparison player. If the result is correct only in the latter, retain both observations rather than declaring compatibility. Where requirements are unclear, consult the destination’s documentation before another full encode.

Once the preview is satisfactory, encode to a new file and repeat the check on the finished result. Keep the version, preset, source/output geometry and log with your notes. Use the backup verification checklist for broader file checks. Motion cadence or audio timing is a separate problem; changing frame-rate mode does not establish that picture geometry is correct.

Evidence and limits

Official guidance was checked on November 2, 2026. The diagnostic order is editorial guidance based on the sources linked above; we did not run HandBrake or test a disc, drive, television or player. The draft anamorphic page supplies conceptual context only, with controls checked against the current CLI. No particular resolution, PAR value or device compatibility is guaranteed.