Best HandBrake Settings for Compressing Video Without Losing Quality
Best HandBrake Settings for Compressing Video Without Losing Quality
HandBrake exposes a genuinely intimidating number of controls. Video tab, audio tab, filters, chapters, dimensions, and a preset list running to dozens of entries. Most guides respond by explaining every checkbox, which is thorough and almost useless — because in practice four settings determine the overwhelming majority of your output quality and file size, and the rest are edge cases.
This guide covers those four, the values worth using for each resolution, and the specific configurations for the jobs people actually do.
The Four Settings That Matter
| Setting | Where | What it controls |
|---|---|---|
| Constant Quality (RF) | Video tab | Quality target — the single biggest lever on file size |
| Video Encoder | Video tab | H.264 vs H.265 — roughly a 30–50% efficiency difference |
| Encoder Preset | Video tab | Speed vs compression efficiency trade |
| Resolution | Dimensions tab | Downscaling, when the source is larger than you need |
Everything else — audio bitrate, filters, chapter markers, web optimisation — adjusts the result at the margins. Get these four right and the rest rarely matters.
1. Constant Quality (RF): The One That Counts
HandBrake gives you two rate control modes. Use Constant Quality, not Average Bitrate, for essentially every job that is not targeting an exact file size.
The difference matters. Average bitrate mode spends the same bits per second on a static talking head as on a fast pan through foliage — it wastes bits on the easy parts and starves the hard ones. Constant Quality mode instead holds perceived quality steady and lets the bitrate move: simple scenes get fewer bits, complex scenes get more. The output is better looking at the same size.
The RF slider is inverted from what you might expect: lower numbers mean higher quality and bigger files. RF 0 is lossless. RF 51 is unwatchable.
RF values by resolution
| Source | RF range | Notes |
|---|---|---|
| 4K / 2160p | 24–28 | Start at 26. High pixel density hides artefacts well |
| 1080p | 20–22 | RF 22 is the best general-purpose default |
| 720p | 22–24 | |
| 480p / SD | 18–20 | Fewer pixels means each one is more visible |
Higher resolutions tolerate higher RF values because artefacts occupy proportionally less of the screen. This is why a 4K file at RF 26 can look better than a 480p file at RF 26.
A practical calibration method: take a 60-second clip from the most complex part of your video — the most motion, the most fine texture — and encode it at RF 20, 22 and 24. Compare them full-screen at normal viewing distance, not zoomed to 400%. Whichever one you cannot distinguish from the source is your setting for that content type. This takes five minutes and saves you from either shipping mush or hauling around files twice the size they need to be.
Content type shifts the answer
Grainy film, confetti, water, foliage, and smoke are expensive to encode and show artefacts early — bias toward lower RF. Screen recordings, animation, and static interviews are cheap — you can often push RF 24–26 at 1080p with no visible loss. See reduce screen recording file size for the specifics of that case.
2. Video Encoder: H.264 vs H.265
HandBrake's encoder dropdown includes x264, x265, and hardware options (VideoToolbox on Mac, NVENC and QSV on other platforms).
x264 (H.264) is the compatibility default. It plays everywhere — old TVs, old phones, browsers, every editing tool. Slightly less efficient, entirely dependable.
x265 (H.265/HEVC) produces roughly 30–50% smaller files at the same visual quality. The trade is compatibility and encoding time: x265 is meaningfully slower than x264 at equivalent presets, and older devices may not play it at all.
The rule of thumb: if you know what will play the file, use H.265. If you do not, use H.264. Archiving your own library on modern hardware is the H.265 case. Sending a file to a client whose setup you have never seen is the H.264 case. Deeper comparison in HEVC vs H.264 and x264 vs x265.
On hardware encoders: VideoToolbox, NVENC and Quick Sync are dramatically faster — often 10–50× real time versus well under real time for a slow software preset. They need roughly 20–40% more bitrate to match software quality, which is frequently a fine trade for the time saved. Use them for batch jobs and anything time-sensitive; use software encoding for archival masters. The full picture is in hardware vs software encoding.
3. Encoder Preset: Where the Diminishing Returns Live
The preset slider runs from Ultrafast to Placebo and controls how thoroughly the encoder searches for efficient ways to represent each frame. Slower presets produce smaller files at the same RF value — they do not produce better looking files, they produce equally good looking, smaller files.
The returns fall off sharply:
| Preset | Relative time | Relative size vs Medium |
|---|---|---|
| Very Fast | ~0.3× | ~+15–20% |
| Fast | ~0.6× | ~+5–8% |
| Medium | 1× | baseline |
| Slow | ~2× | ~−5% |
| Very Slow | ~4× | ~−8% |
| Placebo | ~10×+ | ~−9% |
Medium is the correct default. Use Slow when the file will be stored long-term and the encoding time is paid once. Skip Very Slow and Placebo unless you are encoding a small number of files you will keep for years — you are paying quadruple the time for a few percent.
4. Resolution: The Underrated Lever
This is the setting people forget, and it is often the largest single reduction available.
Encoding cost scales roughly with pixel count. Downscaling 4K to 1080p removes 75% of the pixels before the encoder ever sees them. If the video will be watched on a phone, in a Slack thread, or embedded on a web page, the 4K resolution is doing nothing except costing you bandwidth.
In HandBrake's Dimensions tab, set the width you actually need. 1920 for general use, 1280 for web embeds and messaging apps. Leave "Optimal size" and anamorphic settings alone unless you have a specific reason.
Frame rate is the sibling lever: Same as source with Constant Framerate is right for almost everything, but halving 60fps to 30fps for a screen recording or a talking head is a legitimate saving. Do not do it for anything with real motion — the result looks stuttery in a way viewers notice immediately.
Ready-Made Configurations
Archiving a video library (smallest files, quality preserved)
- Encoder: x265
- RF: 22 (1080p) / 26 (4K)
- Preset: Slow
- Resolution: same as source
- Audio: AAC 160 kbps, or passthrough if the source audio is already efficient
Uploading to YouTube
- Encoder: x264
- RF: 18–20
- Preset: Slow
- Resolution and frame rate: same as source
Counterintuitive but correct: do not compress hard for YouTube. YouTube re-encodes every upload, so your file is an intermediate. Compress it aggressively and YouTube re-compresses already-degraded video, and the loss compounds. See best video format for YouTube.
Email or messaging attachment (hard size limit)
This is the one case where Average Bitrate beats Constant Quality, because you have an exact target. Use the video file size calculator to work out the bitrate, switch to Avg Bitrate with 2-pass encoding enabled, and downscale to 1280 wide.
Relevant limits are collected in email attachment size limits.
Screen recordings and tutorials
- Encoder: x264
- RF: 24–26 (screen content compresses extremely well)
- Preset: Medium
- Frame rate: 30fps is usually plenty
Phone footage for messaging
- Encoder: x264
- RF: 23
- Resolution: 1280 wide
- Preset: Medium
Platform-specific targets are covered in compress video for Telegram, compress video for WhatsApp, and compress video for Discord.
Settings That Waste Your Time
Two-pass with Constant Quality. Not available, and not needed — CQ already allocates bits by scene complexity. Two-pass exists to help average-bitrate mode hit a target intelligently.
Deinterlace and Decomb filters on progressive footage. Anything shot in the last fifteen years is progressive. Running deinterlacing on it softens the image for no benefit. Leave filters off unless you are working with genuine interlaced material such as old DVDs or broadcast captures.
Denoise, at default settings. NLMeans and hqdn3d do reduce file size, sometimes substantially, because grain is expensive to encode. They also smear fine detail. If your source is genuinely noisy, use the lightest setting available and check the result. Otherwise leave it off.
Audio bitrate obsession. AAC at 160 kbps stereo is transparent for practically all content. Dropping to 96 kbps saves a few megabytes on a file measured in hundreds and audibly degrades music.
Why Output Files Come Out Larger Than the Source
A recurring frustration, and the cause is nearly always the same: the RF value is set higher-quality than the source actually is.
If someone hands you a heavily compressed 1080p file and you re-encode at RF 18, the encoder faithfully preserves every compression artefact in the original — because as far as it is concerned, those blocks and that banding are detail worth keeping. Preserving ugly detail is expensive.
Two fixes. Raise the RF number until the output is smaller, or recognise that the source is already efficiently encoded and leave it alone. Re-encoding an efficient file is lossy work with nothing to gain.
When HandBrake Is More Machine Than the Job Needs
Everything above assumes you want to reason about encoders. HandBrake rewards that — it exposes real control, and for a one-off archival encode the control is worth having.
It is a poor fit for routine work. Dragging a folder of clips into HandBrake, setting up a queue, choosing RF values per file, and waiting is a lot of process for "make these smaller before I send them."
Compresto is the shorter path on macOS. Drop in videos, images or PDFs, pick a target size or quality level, and it selects the encoder, RF equivalent and resolution per file — using Apple's media engine where that is the right trade and software encoding where it is not. Batch processing is the default rather than a queue you configure. Everything runs locally; nothing is uploaded.
If you want the dials, HandBrake is excellent and free. If you want the output, this takes about ten seconds. Alternatives worth knowing about are compared in best HandBrake alternatives.
Frequently Asked Questions
What is the best RF value in HandBrake?
RF 20–22 for 1080p, 22–24 for 720p, 24–28 for 4K, 18–20 for standard definition. RF 22 at 1080p is the most useful single default. Calibrate on a complex 60-second clip rather than trusting any number blindly — content type shifts the answer by two or three points in either direction.
Should I use H.264 or H.265?
H.265 for files you will store or play on current hardware, since it is 30–50% more efficient. H.264 for anything going to an unknown device. The trade is purely compatibility versus size.
Does a slower preset make files smaller?
Yes, with sharply diminishing returns. Very Fast to Medium is worth it. Medium to Very Slow costs roughly four times the encoding time for around 8% file size. Medium or Slow covers almost every case.
Is two-pass encoding better?
Only in Average Bitrate mode, where it lets the encoder plan bit distribution across the file. With Constant Quality it is neither available nor needed.
Which HandBrake preset should I start from?
"Fast 1080p30" under General is a reasonable base for web video, and the Apple and Android device presets under Devices are sensible when targeting specific hardware. Start there, then override the RF value and encoder using the guidance above — presets are starting points, not answers.
How do I compress a video to an exact file size in HandBrake?
Switch from Constant Quality to Average Bitrate, calculate the required bitrate from your target size and duration (target megabytes × 8192 ÷ duration in seconds ≈ total kbps, minus your audio bitrate), and enable 2-pass encoding. The file size calculator does the arithmetic for you.
Do these settings apply to HandBrake on Mac and Windows?
Yes. HandBrake's interface differs slightly across platforms but the encoders, RF slider and presets are identical. The only platform-specific item is the hardware encoder available: VideoToolbox on Mac, NVENC or Quick Sync elsewhere.