HandBrake Black Bars Not Removed: How to Fix Cropping

If HandBrake finishes an encode but the output still contains letterbox bars at the top and bottom or pillarbox bars on the sides, cropping either was not detected, was not applied as expected, or was never part of the picture problem. The most common causes are automatic crop detection sampling an unrepresentative section, borders that change between scenes, conservative cropping intended to protect real picture content, subtitles placed inside the bars, or a video player adding its own bars during playback. The steps below help Windows, macOS, and Linux users identify which cause applies without changing unrelated settings.

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

Before changing multiple settings, confirm that the bars are encoded into the video rather than being added by the player or display. This distinction matters because HandBrake can crop pixels stored in the source frame, but it cannot prevent every player, television, or monitor from filling unused screen space with black.

1.1 Identify Letterbox and Pillarbox Bars

Letterbox bars appear above and below a wider image stored inside a taller frame. Pillarbox bars appear on the left and right when a narrower image is stored inside a wider frame. Some sources contain both, producing a black border on all four sides.

Do not assume that every black area is removable padding. A dark scene, a fade to black, or intentional negative space can resemble a border. Cropping too aggressively can remove titles, heads, signs, or other real picture content.

1.2 Test a Representative Scene

Open the source in HandBrake and inspect a preview image from a scene that clearly shows normal picture content and the unwanted bars. Avoid testing only an opening logo, a fade, credits, or a scene surrounded by darkness. Those frames may not represent the main program.

If the bars change during the video, inspect several points, including the beginning, middle, and end. Movies and edited recordings sometimes switch aspect ratios between scenes. Music videos, presentations, compilations, and camera exports can also mix footage with different borders.

Create a short test encode around a representative scene if your HandBrake interface and source allow range selection. A small test is faster and provides stronger evidence than repeatedly encoding the entire file.

Success means the test output fills the expected encoded frame without cutting into visible content. Once that result is achieved, stop changing crop and dimension settings and run the full encode with the tested configuration.

1.3 Compare the File in More Than One Player

Play the test file in two applications, ideally with each player in a normal window rather than full-screen mode. If one player shows bars and another does not, HandBrake may already have removed the encoded borders. The first player, operating system, television, or streaming device may be adding black space to preserve the video aspect ratio.

Resize the playback window. Bars that grow, shrink, or move as the window changes are usually part of the playback presentation. Bars encoded into the video remain proportional to the video picture itself.

2. Check the HandBrake Settings Directly Related to Cropping

The relevant controls are in HandBrake's Dimensions settings. Video quality, audio bitrate, filters unrelated to geometry, and chapter options do not normally determine whether stored black borders are removed.

2.1 Review Automatic Crop Detection

HandBrake can automatically estimate cropping by analyzing sampled frames. This works well for stable, clearly defined borders, but automatic detection has limits. It may preserve bars when the border is inconsistent, the edge is noisy, subtitles overlap the bar, or sampled frames contain dark picture content. It may also choose conservative values to avoid removing legitimate image pixels.

In the Dimensions area, check the displayed crop values rather than merely assuming automatic cropping is active. Top and bottom values correspond to horizontal letterbox borders. Left and right values correspond to vertical pillarbox borders. Values of zero mean no pixels are being removed from that edge.

If the automatic values match the visible border, generate a preview or short test encode. Success means the stored bars disappear while the outermost real image remains intact. If the values are zero or obviously too small, proceed to manual cropping.

2.2 Set Manual Crop Values Carefully

Switch from automatic cropping to a custom or manual crop mode. Increase one edge at a time while checking the preview. For letterboxing, adjust the top and bottom values. For pillarboxing, adjust the left and right values. Borders are not always perfectly symmetrical, so do not force matching values unless the source actually requires them.

1. Choose a bright, representative frame where the boundary is easy to see.
2. Increase the crop value for one affected edge in small increments.
3. Refresh or regenerate the preview after each adjustment.
4. Stop when the black border is gone but no real image detail has been removed.
5. Check at least two additional scenes before encoding the full source.

A thin dark line at the edge may be part of analog noise, a soft transition, or the encoded picture. Cropping a few additional pixels can remove it, but only if those pixels are consistently non-picture material.

Success means the preview shows no unwanted encoded border across representative scenes, and captions, titles, faces, and edge details remain visible. At that point, do not keep increasing the crop merely to make the frame mathematically symmetrical.

2.3 Check the Resulting Dimensions

Cropping changes the available picture area. Review the displayed storage dimensions after setting crop values. This article focuses on bars that remain, not on correcting a picture distorted by excessive cropping, but the output dimensions still provide a useful sanity check.

If the crop values are nonzero but the resulting dimensions appear unchanged in a way you did not expect, review whether dimension limits, anamorphic behavior, or scaling settings are affecting the final frame. Avoid adding padding, because padding deliberately creates pixels around the image and can look like the black bars you intended to remove.

Success means HandBrake reports dimensions consistent with the cropped picture, and the short output file visually matches the preview.

3. Check Source and Playback Factors That Apply

If correct manual crop values still seem ineffective, determine whether the apparent bars come from the source, selected tracks, encode path, or playback environment.

3.1 Borders Burned Into the Source

A burned-in border is physically stored as part of every video frame. HandBrake can remove a stable border by cropping those edge pixels. However, if the source was edited onto a larger black canvas, the visible program may move, resize, or change shape. One fixed crop cannot perfectly follow a moving boundary.

Screen recordings are a common example. A video player may have been captured inside a desktop canvas, leaving uneven black space around it. Phone videos and social-media exports may also place footage inside a fixed landscape or portrait frame.

Choose crop values that are safe for the entire recording. If removing every bar in one scene would cut content in another, retain some border or edit the changing sections separately in a video editor.

3.2 Bars That Change Between Scenes

Automatic cropping is not dynamic scene-by-scene reframing. HandBrake applies the chosen geometry to the encode rather than tracking every composition change as an editor might. If one scene is letterboxed and another fills the frame, a crop large enough for the first scene can cut the second.

In this situation, the safest choices are to keep the bars, crop only the amount safe across all scenes, or split the source into sections with different crop settings. Keeping bars is better when aspect-ratio changes are intentional or when any fixed crop would remove meaningful content.

3.3 Subtitles Positioned Inside the Bars

Some sources place subtitles or captions in the lower letterbox area. Cropping that region removes those visible subtitle pixels if they are already burned into the picture. A separately selectable subtitle track is different, but its rendered position should still be checked in a test encode.

Preview a scene containing subtitles before committing to a crop. If the text occupies the black border, choose between retaining enough border for readability, selecting an appropriate separate subtitle track, or using a legitimate editing workflow that repositions text. Do not crop first and discover after a full encode that dialogue has disappeared.

3.4 Player, Display, and Device Added Bars

A correctly cropped video can still show bars when its shape does not match the playback window or screen. For example, a wide film shown on a 16:9 television normally requires space above and below unless the player zooms or cuts the sides. A vertical phone video shown on a landscape monitor normally has space on the sides.

Check the player's fit, zoom, aspect-ratio, and full-screen options. Reset forced aspect-ratio settings to automatic or original. If the bars exist only in full-screen playback, they are probably preserving the picture rather than remaining from HandBrake's crop.

Success means the encoded frame has no stored border when viewed in a fitting window, even though a mismatched display may still add external black space.

3.5 Source Selection, Tracks, and Hardware Encoding

For disc structures or files with multiple titles, angles, or video streams, confirm that you opened the intended source and selected a representative title. Use only media you own or have permission to process. A preview from one title does not prove that another title has the same borders.

Audio tracks do not control video cropping. Subtitle selection can matter when text is burned into the output or occupies the border, but changing an audio codec or bitrate will not remove bars. Likewise, a hardware video encoder normally compresses the frame produced by HandBrake's processing pipeline; it is not the first setting to blame when crop values are zero or incorrect.

Operating-system and graphics-driver differences can affect preview display or hardware encoding reliability, but they are less likely to explain a consistent border that is visible in the encoded frame. Test with a software encoder only if the preview is correctly cropped while a hardware-encoded output unexpectedly is not. If both outputs retain identical bars, return to the crop and source analysis rather than repeatedly changing drivers.

4. Use the Activity Log to Separate Guesswork From Evidence

HandBrake's Activity Log records information about the scanned source and encode job. Open it after a test encode and look for the selected title, source dimensions, crop values, output dimensions, filters, and encoder. Exact wording can vary, so focus on whether the logged values match the settings you intended to use.

• Confirm that the correct source title or file was scanned.
• Verify that cropping was applied and did not remain zero on every edge.
• Compare input dimensions with the final encoded dimensions.
• Check whether padding or scaling produced a larger output canvas.
• Confirm that the test used the preset and encoder you expected.

If the log shows zero cropping, the bars remained because no pixels were removed. If it shows the intended crop and smaller dimensions, inspect the output in another player because the remaining bars may be player-generated. If the log shows unexpected values, create a new job instead of continuing to modify a possibly confusing queue entry.

When requesting help, preserve the complete log from a short test encode and remove personal file paths if necessary. A screenshot of the bars alone cannot show whether they are in the encoded frame or added during playback.

5. Run a Clean Temporary Encode With Minimal Settings

A clean test helps when a saved preset, queued job, padding option, or unusual filter makes HandBrake appear not to be working. Use a short, noncritical output file and avoid overwriting the source.

1. Open the original source again rather than re-encoding a previous failed output.
2. Select the correct title, range, and a representative scene.
3. Start from a standard built-in preset appropriate for the source resolution.
4. Open Dimensions and set verified manual crop values.
5. Leave padding disabled unless it is intentionally required.
6. Choose one necessary audio track and disable optional subtitle burning for the first geometry test.
7. Use a software video encoder if you are specifically testing whether hardware encoding affects the result.
8. Encode a short segment to a new destination filename.
9. Inspect the file in two players and review the Activity Log.

This test succeeds when the output dimensions and visible image match the manual crop. Reintroduce required subtitles, additional audio tracks, and preferred encoder settings one at a time. Stop as soon as the needed configuration works. There is no benefit to changing audio, quality, frame-rate, or driver settings after the crop has been confirmed.

If the clean test still contains a stable encoded border despite logged nonzero crop values, compare the number of cropped pixels with the actual border thickness. The crop may simply be too small. If the remaining space changes with the player window, it is not an encoded border.

6. Quick Fix Checklist

• Inspect a bright, representative scene instead of an intro, fade, or credits sequence.
• Determine whether the source has letterbox, pillarbox, or four-sided borders.
• Check the actual crop values in Dimensions rather than relying on the automatic label.
• Use manual cropping when automatic detection preserves a consistent visible border.
• Preview several scenes before accepting fixed crop values.
• Keep some border if scenes change shape or content reaches the frame edge.
• Check whether burned-in subtitles occupy the area you plan to remove.
• Disable unintended padding and verify the resulting output dimensions.
• Test the output in another player and outside full-screen mode.
• Read the Activity Log to confirm the selected source, crop, and dimensions.
• Run a short clean encode before processing a full movie or long recording.
• Stop changing settings once the encoded border is gone without lost content.

7. Frequently Asked Questions

7.1 Why Does HandBrake Auto Crop Leave Black Bars?

Automatic crop detection samples the source and makes a cautious estimate. It can miss borders when scenes are dark, edges are noisy, subtitles overlap the border, or aspect ratios change. Inspect multiple previews and set manual crop values when the border is stable and clearly separate from the picture.

7.2 Can HandBrake Remove Bars That Appear Only During Full-Screen Playback?

Not necessarily. Full-screen bars may be added by the player or display because the video's aspect ratio does not match the screen. Cropping cannot make every video fill every screen without either distorting the image or cutting picture content. Test in a normal window and compare another player.

7.3 Why Do the Bars Disappear in Preview but Remain in the Output?

First confirm that the queued job used the same crop settings shown in the preview. Then inspect the Activity Log and encoded dimensions. If those are correct, the playback software may be adding the visible space. A clean encode to a new filename can also prevent confusion with an older output.

7.4 Should I Crop Every Black Pixel From the Edges?

No. Crop only pixels that are consistently border material. Dark image content, soft edges, subtitles, titles, and intentional framing should remain. If a fixed crop would damage any important scene, preserve some or all of the bars.

7.5 Does Changing the Hardware Encoder Fix Cropping?

Usually not. Cropping is determined by the geometry settings before final compression. Try a software encoder only as a controlled test when the preview and logged crop are correct but the hardware-encoded result differs. Otherwise, focus on crop values, source variation, padding, and playback behavior.

7.6 When Is Keeping the Black Bars the Better Choice?

Keep the bars when aspect ratios intentionally change, subtitles sit within them, the picture boundary moves, or removing them would cut meaningful content. Bars added by a display to preserve aspect ratio are also normal. The correct result is not always a screen filled edge to edge; it is a complete, undistorted picture with no unnecessary encoded border.