HandBrake Aspect Ratio or Crop Is Wrong: How to Fix It

If a HandBrake encode looks stretched, squished, unusually narrow, too wide, or clipped around the edges, the problem usually comes from one of four areas: incorrect crop detection, unsuitable dimension settings, anamorphic or display-aspect metadata, or a player interpreting that metadata incorrectly. The fastest solution is not to change every setting at once. Instead, create a short test encode, inspect the source and output dimensions, and isolate whether HandBrake removed pixels, reshaped the image, or merely produced a file that one player displays incorrectly.

This guide explains how to troubleshoot the problem on Windows, macOS, and Linux without requiring advanced video-engineering knowledge. It applies to ordinary video files, screen recordings, phone footage, camera footage, and unprotected disc sources you have the right to convert. The focus is the visible picture shape and framing, not simply whether black bars appear.

1. Confirm the Symptom With a Small Test Encode or Preview

Before changing dimensions or crop values, identify exactly what is wrong. A stretched picture, a cropped picture, and a correctly encoded picture displayed incorrectly by one player can look similar at first glance, but they require different fixes.

1.1 Identify the visible failure

Open the source and encoded output and compare the same frame. Choose a frame containing recognizable circles, faces, text, or objects near the edges. Then classify the problem:

• Stretched horizontally: People and objects look too wide.
• Squished horizontally: People and objects look unusually thin or tall.
• Top or bottom clipped: Crop values may be removing actual image content.
• Left or right clipped: Automatic crop detection may have mistaken a dark edge for a border.
• Framing is correct but the player window has the wrong shape: The player may be ignoring display-aspect metadata.
• Only one section of the video is clipped: Borders or framing may change during the source.

This classification matters because crop removes stored pixels, while anamorphic signaling changes how stored pixels should be displayed. If content is missing, investigate crop first. If all content remains but its shape is distorted, investigate dimensions, anamorphic behavior, source metadata, and playback.

1.2 Use HandBrake Preview before a full encode

Load the source, select the intended title and preset, and open HandBrake's Preview window. Examine several positions rather than relying on the opening frame. Disc sources, edited recordings, and broadcasts can contain dark introductions that do not represent the rest of the program.

If the preview already shows missing edges, the problem is in the selected title, crop, or dimension configuration. If the preview looks correct but the completed file looks wrong, playback interpretation, metadata, or an encode-specific setting becomes more likely.

When available in your HandBrake interface, create a short preview encode. A representative 20 to 60 second sample is usually enough to test shape and framing. Use a scene with motion, edge detail, and recognizable geometry.

Success looks like this: The sample retains the intended frame, circles remain circular, and people have natural proportions. Once the sample is correct in more than one player, stop changing geometry settings and proceed with the full encode.

2. Check the HandBrake Settings Directly Related to This Problem

HandBrake's Dimensions controls determine which pixels are removed, how many pixels are stored, and how the picture should be displayed. Review these controls methodically instead of moving width and height values until the preview looks approximately right.

2.1 Review automatic crop detection

Automatic crop detection attempts to identify black or near-black borders and remove them. It is useful for many sources, but it can make the wrong decision when real picture content is dark, when borders vary during the program, or when analog captures contain irregular edge noise.

Inspect the top, bottom, left, and right crop values shown in the Dimensions section. A value of zero means no pixels are removed from that edge. A positive value removes that many source pixels before resizing or encoding.

If important content is missing, change cropping to a custom or manual mode and set all four values to zero for a test. Do not immediately assume that zero crop must be the final setting. The purpose of this test is to determine whether cropping caused the loss.

Success looks like this: Previously missing text, heads, borders, or edge details return. If they do, restore only the crop that clearly removes unwanted border pixels while preserving the actual image.

2.2 Check manual crop values carefully

Manual cropping is easy to misread because each number refers to pixels removed from a specific edge. A large left value does not shift the picture to the left. It discards pixels from the left side.

Use the following process:

1. Set top, bottom, left, and right crop values to zero.
2. Preview a frame with visible details near every edge.
3. Add crop in small increments only where an unwanted border exists.
4. Check several scenes because borders may vary over time.
5. Run another short encode before committing to the entire file.

A few uneven pixels at an analog or captured edge may be less distracting than cutting off subtitles, scoreboards, camera timestamps, or composition details. Cropping is partly a content decision, not merely a mathematical one.

2.3 Understand storage resolution and display aspect ratio

Storage resolution is the encoded pixel grid, such as 720 by 480 or 1920 by 1080. Display aspect ratio describes the shape in which those pixels should appear during playback. These are related, but they are not always identical.

Some video uses non-square pixels. In that situation, a stored frame can have one numerical width-to-height ratio while metadata tells the player to display it at another ratio. This is common in certain DVD, standard-definition broadcast, and older camera workflows. It is called anamorphic video.

For example, simply dividing the stored width by the stored height may suggest a shape that differs from the intended display. A compatible player uses pixel-aspect or sample-aspect metadata to reconstruct the correct display width. A player that ignores this signaling can make the same file look stretched or squished.

Do not force the storage dimensions to match a familiar ratio unless you understand what HandBrake is already preserving. Unnecessary manual resizing can distort a source that would otherwise display correctly.

2.4 Check anamorphic behavior

HandBrake can preserve or calculate anamorphic information so that non-square-pixel sources retain their intended display shape. The exact controls visible in the interface can depend on the selected preset and source, but the practical decision is consistent: either preserve the intended display aspect with metadata, or convert the image to square-pixel dimensions that represent the same visible shape.

If the output looks correct in a standards-compliant desktop player but wrong on a television, hardware box, browser workflow, editor, or older application, that destination may not handle anamorphic metadata as expected. In that case, test a clean preset that produces conventional square-pixel output while preserving the intended display aspect.

Avoid changing both anamorphic behavior and width or height independently during the same test. Change one geometry decision at a time so the result remains understandable.

Success looks like this: The same file has the same natural proportions in your intended playback device and a second known-good player. Stop when the destination displays it correctly and no image content is missing.

2.5 Use strict and loose dimensions practically

Dimension constraints can require HandBrake to adjust a calculated width or height to values acceptable to a codec, preset, or playback target. In practical terms, stricter constraints preserve tighter relationships among crop, scaling, and anamorphic calculations. Looser behavior allows dimensions to be adjusted to suitable modulus values while maintaining the intended display shape as closely as possible.

Small numerical differences in stored width do not automatically mean the picture is wrong. The critical test is whether the display aspect is preserved and recognizable geometry remains undistorted. Do not fight a harmless one-pixel or few-pixel adjustment by entering arbitrary dimensions.

If you previously customized resolution limits, modulus, or anamorphic options, begin again with an official preset suitable for the destination. Then adjust only the resolution limit you actually need. This is safer than trying to reconstruct a web of dependent dimension settings.

3. Check Source, Destination, and Playback Factors

Not every apparent HandBrake failure originates in HandBrake. A source can contain incorrect metadata, and a player can disregard correct metadata. The target device can also impose limitations that are absent on a desktop computer.

3.1 Compare the output in two players

Open the encoded file in at least two independent players. Include a well-maintained desktop player if possible, then compare it with the application or device where the problem first appeared.

If one player displays the file correctly and another stretches it, the encoded picture is probably intact. The second player may be ignoring the pixel-aspect or display-aspect information, applying a forced zoom mode, or using a manual aspect-ratio override.

Check the player's video menu for options such as aspect ratio, zoom, crop to fill, stretch, fit, or original size. Return these to an automatic or original mode. On televisions and streaming devices, also disable display modes that enlarge the picture to fill the screen.

Success looks like this: The output appears correctly when the player uses its automatic or original aspect mode. In that case, do not re-encode unless the actual destination cannot interpret the file correctly.

3.2 Test whether the source metadata is wrong

A source may itself declare the wrong display shape. This can happen with malformed captures, incorrectly exported editing projects, concatenated clips, or files produced by unusual recording software. If several players show the source incorrectly before HandBrake touches it, HandBrake may simply be following bad metadata.

Look for a stable reference. A known physical object, embedded title card, calibration pattern, or expected screen-recording canvas can reveal the intended ratio. If the source is genuinely mislabeled, use HandBrake's dimension controls to create the correct visible shape, but verify it with a short sample rather than relying solely on the source's reported values.

Phone videos can also contain rotation metadata. A player that handles rotation differently may appear to swap the intended geometry. Confirm that the source orientation is correct in HandBrake's preview before diagnosing it as an aspect-ratio failure.

3.3 Separate hardware encoding from geometry

Hardware encoders primarily affect video compression, speed, and supported codec features. Crop and scaling generally occur elsewhere in the processing pipeline. Therefore, changing from a hardware encoder to a software encoder is not the first fix for a stretched or clipped picture.

However, a software-encoder test can still be useful when output differs only with a particular hardware path, driver, or device. Use the same preset and geometry settings, change only the video encoder, and create a short sample. Update the operating system, graphics driver, and HandBrake from their official sources if the behavior is repeatable only with hardware encoding.

Success looks like this: Both hardware and software samples have identical framing and proportions. If only one path fails consistently, keep the working encoder while investigating driver or compatibility issues.

3.4 Treat audio and subtitles as targeted checks

Audio tracks do not determine picture aspect ratio. Do not spend time changing audio codecs or bitrates to solve stretching. Audio selection matters only if the wrong title or program was selected, which can indicate that you are encoding a different source segment than expected.

Subtitle tracks also do not normally reshape the video, but burned-in subtitles become part of the picture after positioning and scaling. If subtitles are clipped, first determine whether the underlying video edge is also clipped. If only the subtitles are affected, inspect subtitle burn-in and positioning rather than altering the entire aspect ratio.

For disc sources, confirm that the selected title, angle, and chapter range match the content you previewed. Only process material you own or are authorized to copy, and do not use this guidance to bypass access controls.

4. Use the Activity Log to Separate Guesswork From Evidence

HandBrake's Activity Log records how it interpreted the source and what it did during the encode. It can reveal the detected source geometry, crop values, output dimensions, filters, encoder selection, and warnings. Interface labels can summarize settings, while the log shows what the job actually used.

4.1 What to look for in the log

Open the log for the affected encode and search for information related to:

• Source width and height
• Pixel or sample aspect ratio
• Display aspect ratio
• Top, bottom, left, and right crop values
• Scaling or output dimensions
• Rotation or geometry filters
• The selected title and angle
• Warnings, failures, or unsupported settings

Compare those values with the source and with the settings you expected. If the log shows significant cropping when you intended none, return to Dimensions and disable or correct crop. If the stored output dimensions look unusual but the log also contains non-square-pixel signaling, test playback before declaring the output malformed.

4.2 Compare a failing and successful job

If an older encode worked, compare its Activity Log with the failing job. Focus on crop, scale, anamorphic, rotation, title selection, and preset differences. Ignore unrelated bitrate and audio changes unless the job selected a different source title.

Save the complete log before resetting settings if you may need support. A screenshot of the visible output rarely identifies whether pixels were cropped, resized, or merely displayed incorrectly. The log provides reproducible evidence.

Success looks like this: The log reports the crop and output geometry you intentionally selected, and the sample displays correctly. Once the evidence and visible result agree, further random changes are more likely to create a new problem than solve one.

5. Run a Clean Temporary Encode With Minimal Settings

If the cause remains unclear, create a controlled test. This removes old preset modifications and prevents several interacting changes from hiding the real cause.

5.1 Build the clean test

1. Reload the source in HandBrake.
2. Select a built-in general-purpose preset appropriate for the source resolution.
3. Reset cropping to zero temporarily.
4. Leave width and height under the preset's normal automatic handling.
5. Avoid custom anamorphic, modulus, rotation, padding, and upscaling changes.
6. Select one ordinary audio track and disable optional subtitle burn-in for the test.
7. Encode a short, representative section.
8. Play the result in two players.

If the clean sample is correct, the source and basic HandBrake pipeline are functioning. The problem is probably in the previous preset's crop, resolution, anamorphic, or player-specific configuration.

Restore custom requirements one at a time. Start with crop because it changes framing directly. Next apply any resolution limit. Then test destination-specific format or encoder requirements. Preview after each geometry change.

5.2 Know when to stop changing settings

Stop when the output preserves all intended image content, displays circles and faces naturally, and works in the actual destination player. The encoded storage dimensions do not need to match the source if you intentionally resized it, and they do not need to form the visible display ratio when valid anamorphic signaling is in use.

Do not keep adjusting dimensions merely to obtain round numbers. A technically neat resolution is not an improvement if it distorts the image or removes useful content.

6. Quick Fix Checklist

• Compare the source and output using the same representative frame.
• Use Preview and a short sample instead of repeatedly encoding the whole video.
• Set crop to zero to test whether automatic or manual cropping removed content.
• Restore only crop values that remove genuine unwanted borders.
• Do not confuse stored resolution with intended display aspect ratio.
• Test anamorphic output in the actual destination player.
• Return the player's zoom, stretch, and aspect overrides to automatic.
• Try a second player before re-encoding a file that may already be correct.
• Start from a clean built-in preset if dimension settings have been heavily modified.
• Check the Activity Log for actual crop, scale, and aspect calculations.
• Change only one geometry-related setting between tests.
• Stop when framing and proportions are correct on the target device.

7. Frequently Asked Questions

7.1 Why does HandBrake crop part of my video automatically?

HandBrake's automatic crop detection may interpret dark image areas as removable borders. This is more likely with dim scenes, irregular analog edges, changing borders, or content framed against black. Set crop to zero for a test. If the missing content returns, use carefully chosen manual values or retain the full frame.

7.2 Why is my HandBrake output stretched even though the resolution looks correct?

The stored resolution may not describe the intended display shape by itself. Anamorphic video can rely on pixel-aspect metadata. The output may also be correct while a player ignores that metadata or forces a stretch mode. Compare two players and inspect both the display-aspect information and stored dimensions.

7.3 Should I enter 16:9 dimensions manually?

Usually not. A 16:9 presentation does not mean every source must be manually resized to one particular pixel grid. Cropping, resolution limits, and anamorphic behavior affect the correct calculation. Start with an appropriate built-in preset and let HandBrake preserve the aspect ratio unless you have a specific delivery requirement.

7.4 Why does the preview look correct but the final file looks wrong?

If Preview is correct, the completed file may be interpreted differently by the playback application or device. Check for player zoom and aspect overrides, compare another player, and review the Activity Log. Also confirm that the final job used the same title, preset, crop, and dimensions shown during preview.

7.5 Can a hardware encoder cause the wrong aspect ratio?

It is not the most likely cause because cropping and scaling are generally separate from compression. Still, a short software-encoder comparison is worthwhile if the failure occurs only with one hardware encoder. Keep all geometry settings identical so the test isolates the encoder and driver path.

7.6 What should I do if the source itself has the wrong aspect ratio?

First confirm the source is genuinely mislabeled by checking it in multiple players and using recognizable objects as a visual reference. Then create a short HandBrake test that corrects the visible shape, preferably using conventional square-pixel output for broad compatibility. Do not rely only on reported dimensions when the source metadata is known to be wrong.

The safest HandBrake aspect ratio or crop fix is a controlled one: verify the symptom, disable crop temporarily, distinguish stored pixels from display shape, test playback interpretation, and use the Activity Log to confirm what happened. Once a short sample has correct framing and natural proportions on the destination device, preserve those settings and run the full encode.