HandBrake Cropped Too Much Video: How to Restore the Edges

If HandBrake cropped too much video, the missing picture area was usually removed during encoding rather than hidden by the player. Automatic cropping may have mistaken a dark edge for a black border, a manual crop value may have been carried over from an earlier job, or a custom preset may be applying unwanted geometry settings. Less commonly, subtitles, playback zoom, source-file damage, or hardware-specific behavior can make the output look cropped. The safest troubleshooting method is to confirm the symptom with a short preview, set cropping to zero as a diagnostic, and change only one relevant setting at a time.

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

Do not begin by repeatedly encoding the entire video. First, identify exactly what is missing and determine whether HandBrake removed it. Choose a frame where the lost area is easy to recognize, such as a title card, subtitle near the bottom, screen-recording toolbar, game interface, camera timestamp, or a person standing close to the edge.

Open the source in a trusted player and compare the same scene with HandBrake's preview and encoded output. Check all four sides. Write down whether the loss affects the top, bottom, left, right, or several edges. This distinction matters because crop settings are stored as separate values for each side.

1.1 Preview Several Different Scenes

Automatic crop detection can be misled by the frames it analyzes. A dark opening, fade from black, letterboxed title sequence, or scene with naturally black surroundings may appear to contain removable borders even when later scenes use that area for real content.

Inspect several positions across the running time:

• The opening title or first bright scene
• A bright scene with visible detail at every edge
• A scene containing subtitles, captions, or interface elements
• A scene near the middle of the program
• A late scene or end-credit sequence

If one crop setting protects all meaningful picture content, you have a reliable target. If the apparent borders change between scenes, cropping aggressively is risky. In that situation, retaining a small border is usually preferable to permanently deleting titles, subtitles, or picture detail.

1.2 Run a Short Comparison Encode

Create a short test containing the revealing scene, or use HandBrake's preview feature to generate a brief sample. Make one test with the current settings and another with cropping set to zero on all four sides. Keep the resolution limit and other geometry controls consistent so that cropping is the only meaningful difference.

Success means the zero-crop sample contains the missing edges visible in the source. At that point, stop investigating unrelated settings. You have established that cropping caused the loss, and you can concentrate on automatic detection, manual values, or preset carryover.

If the zero-crop encode is still missing the same area, verify whether the source actually contains it. The selected title, angle, or video track may differ from the one previously viewed. The player may also be zooming or scaling one version differently.

2. Check the HandBrake Settings Directly Related to This Problem

The settings most directly connected to lost edges are found in HandBrake's Dimensions controls. Labels and layout can vary somewhat across operating systems and releases, but the relevant concepts are crop mode, crop values, storage dimensions, display dimensions, aspect ratio, and scaling.

2.1 Disable Automatic Cropping as a Diagnostic

Automatic cropping is convenient for sources with stable black borders, but it cannot understand the artistic or informational importance of every dark pixel. It may interpret dark scenery, black slide backgrounds, screen-recording margins, or inconsistent analog-video edges as disposable borders.

Change the crop mode from automatic to a custom or manual mode that allows explicit values. Enter zero for top, bottom, left, and right. Then inspect a preview or make another short test encode.

If all missing content returns, automatic detection was the cause. You can leave every value at zero or introduce small manual values only after checking multiple scenes. Stop changing settings once the entire intended image is visible and its proportions look correct.

2.2 Inspect Every Manual Crop Value

A crop value represents pixels removed from a particular edge. Even a modest number can cut off subtitles, phone-camera overlays, presentation controls, or a thin line of desktop UI. Check all four fields rather than assuming only the visibly affected side matters.

For example, a bottom crop can remove burned-in subtitles, while a top crop can delete a window title bar. Left and right cropping is particularly noticeable in screen recordings, security footage, gameplay, and camera material where important objects reach the frame boundary.

Set suspicious values to zero and test again. If you later decide to remove genuine black borders, increase values gradually while watching representative frames. Success means borders are reduced without losing any content that appears elsewhere in the video.

2.3 Check for Preset Carryover

A previous encode may have used custom crop values appropriate for one source but harmful to another. If those values were saved in a custom preset, every new job based on that preset can inherit the mistake.

Load a built-in preset suitable for the source and check the Dimensions settings again. If the built-in preset produces a correct zero-crop test while your custom preset does not, recreate or update the custom preset without the unwanted crop values.

Before saving the corrected preset, confirm that cropping is configured the way you intend. If your sources vary, avoid baking source-specific manual crop numbers into a general-purpose preset. A preset for mixed phone videos, recordings, and camera footage should not assume that every file has identical borders.

2.4 Review Scaling and Aspect-Ratio Controls

Scaling does not normally remove source edges in the same way as cropping, but an unexpected output size can make diagnosis confusing. Review the displayed storage and output dimensions after changing crop values. If the aspect ratio is being preserved, HandBrake may adjust one dimension to keep the image from stretching.

Do not compensate for over-cropping by stretching the remaining picture. That does not restore deleted pixels. First restore the edges by correcting the crop, and then choose an appropriate output resolution.

Success means the preview contains the complete intended frame, circles and faces do not look unnaturally wide or narrow, and the reported output dimensions are appropriate for the source and preset.

3. Check Source, Subtitle, Playback, and Encoder Factors

When zero cropping does not resolve the symptom, determine whether the apparent loss comes from the selected source, a subtitle issue, or playback behavior. Audio settings are not responsible for cutting picture edges, so changing codecs, bitrates, or audio tracks is not a useful response to this symptom unless the wrong title or program was selected.

3.1 Verify the Source Title, Angle, and File

Disc structures and multi-program files can contain several titles, angles, or video streams. Make sure HandBrake loaded the same one that you inspected in another player. Work only with media you own or are authorized to process, and do not use these steps to bypass access controls.

For a file source, compare its native frame dimensions in a player or media-information tool with the source dimensions reported by HandBrake. If the original file itself lacks the edges, HandBrake cannot reconstruct them. You will need a different or intact source copy.

For a screen recording or phone video, remember that the recording application may have captured only a region of the display. If the source never included the taskbar, status area, or outer pixels, disabling HandBrake's crop will not bring them back.

3.2 Distinguish Burned-In and Selectable Subtitles

Burned-in subtitles are part of the video image. Cropping the bottom edge can permanently cut through them. Selectable subtitle tracks are separate and may be rendered differently by different players.

If subtitles are missing rather than visibly sliced, confirm that the desired subtitle track was added and that the player has it enabled. If subtitle text appears cut off exactly at the picture boundary, test with zero cropping and inspect the subtitle placement. Also compare playback in another application to rule out a player-specific subtitle renderer.

Success means burned-in text is fully visible in the encoded pixels, or the intended selectable track appears completely when enabled. Once that happens, do not alter audio or video quality settings in an attempt to improve subtitle placement.

3.3 Disable Player Zoom and Overscan

A correctly encoded file can look cropped if the playback application is set to zoom, fill, pan and scan, or crop-to-screen mode. Televisions and some display chains may also apply overscan, which hides a narrow area around the image.

Play the output in a second desktop player at its default aspect ratio and with zoom disabled. If possible, inspect a still frame or screenshot. When the edges appear in one player but not another, the encode is intact and the playback configuration is responsible.

Success means the same encoded file displays its full edges in a neutral player. Stop re-encoding at this point. Correct the player's scaling mode or the television's picture-size setting instead.

3.4 Test Software Encoding if the Result Is Inconsistent

Crop geometry is generally determined before video compression, so switching encoders is not the first fix for a consistent crop error. However, if previews look correct but a hardware-encoded file is corrupted, shifted, or displayed with unusual dimensions, make a short software-encoder test using the same zero-crop dimensions.

Also try a different player before blaming the encoder. If only the hardware-encoded sample is abnormal across multiple players, update the operating system and graphics driver from the hardware vendor's official channel, or use a software encoder for the affected job.

Success means the software sample preserves the expected frame and plays consistently. If both hardware and software outputs lose identical edges, return to the source and crop settings because the encoder itself is unlikely to be the cause.

4. Use the Activity Log to Separate Guesswork From Evidence

HandBrake's Activity Log records details about the scanned source, selected title, filters, dimensions, crop values, encoder, and processing result. It is the best place to confirm what HandBrake actually did rather than relying only on what the interface appears to show.

Open the Activity Log for the affected job and look for source dimensions, crop information, scaling, output dimensions, and filter configuration. The exact wording can differ, but you are looking for evidence that nonzero pixels were removed from specific edges.

4.1 Compare a Bad and Good Test Log

Save or copy the log from the over-cropped encode. Then run the short zero-crop test and compare the two logs. Focus on these differences:

• Selected source title or video stream
• Top, bottom, left, and right crop values
• Input and output frame dimensions
• Geometry or scaling filters
• Preset and encoder selection
• Warnings, read errors, or filter failures

If the bad job reports nonzero cropping and the good job reports zero, the evidence confirms the diagnosis. If both jobs report zero crop but only one looks wrong, investigate player zoom, different source selection, unusual scaling, or decode errors.

Keep the log when asking for support. Include a description of which edge is missing and whether the source shows that content. Remove file paths or other personal information before posting it publicly.

5. Run a Clean Temporary Encode With Minimal Settings

A clean test prevents several unrelated customizations from obscuring the cause. Open the source again, select a standard built-in preset, and avoid importing settings from the failed queue item. Choose a short range containing visible edge details.

1. Confirm the correct source title, angle, or file.
2. Set all four crop values to zero.
3. Keep aspect-ratio preservation enabled unless you have a specific reason not to.
4. Use a normal output resolution that does not intentionally reduce the frame unexpectedly.
5. Disable optional filters that are not needed for the test.
6. Choose a software video encoder if you are isolating hardware behavior.
7. Add only the audio and subtitle tracks needed to verify the sample.
8. Encode the short range and play it in two applications.

If the clean encode restores the edges, add your required settings back one group at a time. Check Dimensions first, then subtitles and filters, and finally encoder-specific options. Make a short sample after each meaningful change.

Stop when you identify the setting that reintroduces the loss. Correct that setting rather than continuing to modify unrelated quality, frame-rate, or audio controls. If the clean zero-crop encode still lacks pixels visible in the original, compare logs and verify that both applications are reading the same source video stream.

6. Quick Fix Checklist

• Compare the source and output at the same bright, edge-revealing scene.
• Preview the opening, middle, ending, subtitles, and UI-heavy scenes.
• Set top, bottom, left, and right crop values to zero.
• Run a short test instead of encoding the complete video.
• Check whether a custom preset retained manual crop values.
• Use a built-in preset to create a clean baseline.
• Verify the selected source title, angle, and video stream.
• Check whether subtitles are burned in or separately selectable.
• Disable zoom, fill, crop, and overscan in the playback chain.
• Compare the failed and successful Activity Logs.
• Try software encoding only if the preview and final output disagree.
• Accept a small black border when removing it would risk real content.

The safest successful result is not necessarily a frame with every dark pixel removed. Success means all intended picture content, titles, subtitles, overlays, and interface elements survive the encode. A narrow border is reversible during playback; cropped-away source pixels are not.

7. Frequently Asked Questions

7.1 Can HandBrake Restore Edges Already Removed From an Encoded File?

No. If HandBrake cropped pixels during encoding, those pixels are not stored in the resulting video and cannot be recovered from that file. Re-encode from the original source with corrected crop values. Upscaling or adding borders can change the frame size, but it cannot recreate the missing image accurately.

7.2 Why Did Automatic Crop Work on One Video but Fail on Another?

Sources differ. One may have stable, sharply defined black bars, while another begins with darkness, contains changing borders, or uses near-black content at the edges. Automatic detection makes a geometric judgment and cannot know that a dark area will later contain subtitles or important action. Preview multiple scenes before accepting its result.

7.3 Should I Always Set Cropping to Zero?

Zero is the best diagnostic setting because it shows whether cropping caused the loss. It is also a safe final choice when edge content varies or must be preserved. You can use nonzero values when a source has consistent unwanted borders, but verify them throughout the video first.

7.4 Why Are Only My Subtitles Cut Off?

Burned-in subtitles near the bottom may have been included in the cropped picture area. Set the bottom crop to zero and test again. If the subtitles are a separate track, confirm that the correct track is enabled and compare players because subtitle rendering may occur during playback.

7.5 Does Changing the Video Encoder Fix Over-Cropping?

Usually not. Crop and geometry processing generally happen independently of the final compression choice. Switching from hardware to software encoding is useful only when the preview is correct but the produced file is corrupted or behaves differently across players. Consistent missing edges point back to crop settings or the source.

7.6 Is It Better to Keep a Small Black Border?

Yes, when the alternative is cutting meaningful content. Small borders can be hidden by a player's display options if desired, while lost titles, subtitles, UI, and edge detail cannot be restored without re-encoding from the source. Preserve uncertain pixels and crop only borders that remain consistently empty across representative scenes.