If HandBrake removes only unwanted black borders, automatic cropping may be appropriate. If it cuts picture content—or you need every edge of the source—disable cropping. Use Custom when you have checked exactly how much to remove. A smaller output height alone does not establish that useful picture detail was lost.
This guide is for readable videos, home recordings and Blu-ray backups you own or are authorized to process. Make a separate viewing copy and keep the source. HandBrake always converts the video; turning cropping off does not make the operation lossless.
First identify what changed
A video that looks wrong can involve three different things:
| What you observe | Check first | Appropriate next step |
|---|---|---|
| Borders present in the source are absent in the output; picture edges remain intact | Crop values and several source scenes | Accept the crop only if those borders are unwanted throughout the title. |
| Heads, dates or picture edges are missing | Source versus output at the same moment | Disable cropping and make a new preview from the original source. |
| The file contains the full picture, but the player shows empty space around it | Playback fit/zoom and the picture’s shape relative to the screen | Do not guess crop values just to fill the display. |
| Cropping is off, but the stored dimensions are smaller | Resolution Limit and scaling settings | Review output size separately; disabling crop does not disable resizing. |
Start with the Blu-ray-to-MP4 decision guide if you have not yet selected a format for the destination. This page deals with the picture area, not disc reading or copy protection.
What HandBrake’s automatic cropping actually promises
The official resizing guide says HandBrake tries to detect black borders and remove them. It also acknowledges that its estimate can be wrong. Treat the proposed crop as something to inspect, rather than proof that every scene has the same border.
For example, a title could contain both wide and taller picture sections. A crop that looks harmless in one section needs checking in the others. Home footage may also have a recording date or other important detail near an edge. These are reasons to inspect your own source, not claims that we tested a particular film or camcorder.
Do not assume that a setting named Conservative guarantees preservation. The current CLI reference lists that mode but does not offer such a guarantee.
Keep the full frame, or adjust four edges deliberately
Choose your intended preset first. Once the source has been scanned, inspect the picture or dimensions settings; labels vary with the HandBrake version and platform.
- To preserve all source edges: choose None for cropping where available, or select Custom and set Top, Bottom, Left and Right to 0.
- To remove a known border: use Custom values established from the source and preview. Do not copy someone else’s pixel numbers.
- To accept automatic cropping: check several representative moments before keeping the proposed values.
The current CLI reference documents --crop-mode none. It also documents --crop 0:0:0:0, with the order top:bottom:left:right; explicitly setting crop values selects custom mode by default. These are option fragments, not a complete encoding command. Run HandBrakeCLI --help locally to check the options in your installed version.
After changing a preset or selecting another title, inspect the resulting values again. Before adding a batch, confirm the settings that will actually be used for each job. A successful preview of one title is not evidence for the rest.
Why a 1080-high source can become 800-high
Consider a hypothetical square-pixel 1920 × 1080 source with an unwanted 140-pixel border at both the top and bottom. With cropping only—no further scaling or padding—the remaining image is:
1080 − 140 − 140 = 800, so 1920 × 800.
That calculation describes the remaining pixel rectangle. It is not a recommendation to crop every video by 140 pixels, a measured file-size saving, or proof that no content was removed. You still need to check that those rows really are expendable across the title.
Nor does entering 1920 × 1080 as the output size undo a crop. Resizing cannot restore picture that was excluded from the new encode. Return to the retained source to make another copy.
Stored width and height also do not always equal display geometry: the CLI has separate pixel-aspect and display-aspect controls. Do not apply this square-pixel example blindly to anamorphic DVD material. For quality and file-size settings, use Constant Quality vs Average Bitrate.
Preview the scenes that could invalidate your choice
HandBrake’s Preview workflow lets you select a short section and its duration. Use it before committing to a long encode:
- Compare source and preview at matching moments, including an ordinary bright scene, a dark scene, titles or credits, and any change in picture shape.
- Check all four edges for meaningful content. Text already embedded in the source picture is part of that picture. Separately selected subtitle tracks still need their own check.
- Review the cropped and final output dimensions. If the image looks squeezed or stretched, check sizing and display-aspect settings instead of removing more picture.
- Play a short encoded preview on the intended destination. Check the finished full-length copy afterward as well.
A wide picture can still have space above and below it on a differently shaped screen even after encoded black borders are removed. Filling the screen is a separate display decision; it should not silently become permission to discard picture edges.
For subtitle selection, continue with keeping audio and subtitle tracks. For timing, use the frame-rate decision guide. Keep the original alongside the viewing copy using the personal media archiving workflow.
For an intact picture that looks stretched or squashed, use the display aspect and pixel aspect diagnosis before changing crop values.
Evidence and limits
Official sources were read on October 30, 2026. The resizing guide is marked as a draft in the documentation navigation, so the available modes and pixel order were cross-checked against the current CLI reference. Installed versions can differ. This article provides documented controls and an editorial checking method; it does not report an encoding benchmark, hardware test or guaranteed space saving.