I’m trying to encode videos with HandBrake, but the preset options and quality settings are confusing. I need help choosing the right HandBrake settings for good video quality, smaller file sizes, and reliable playback.
Your playback target matters more than the preset name. For broad compatibility with TVs, phones, browsers, and older hardware, start with an H.264 preset matching the source resolution, such as a 1080p preset for 1080p video. Presets are starting configurations, not fixed quality levels. H.265 can produce smaller files, but it encodes more slowly and some older devices struggle with it.
For quality, use Constant Quality rather than targeting an arbitrary file size. With H.264, RF 20 to 22 is a sensible starting range for 1080p. Lower RF means better quality and a larger file. Higher RF means a smaller file and more visible compression. The encoder speed setting is separate: slower settings usually save some space at the same RF, but take longer to encode.
Keep the resolution at or below the source, select “Same as Source” for frame rate, and avoid forcing 30 fps if the original is 60 fps. AAC audio is the safest general choice, while passthrough preserves compatible original audio without re-encoding. A good basic setup is H.264, MP4, RF 21, Same as Source frame rate, and AAC audio. Test a short scene with motion, shadows, and fine detail before committing to an entire movie.
A clean animated video and a grainy live-action movie can use the same preset and RF yet produce very different file sizes. Don’t treat RF as a size control; make a short test encode, and avoid removing grain unless you actually want the softer look that filtering can create.
Start with Fast 1080p30, keep H.264 video, AAC audio, and MP4 if reliable playback matters more than maximum compression. Set Constant Quality around RF 20 to 22, and treat the preset as a starting bundle of settings rather than a required choice.
Changing the main preset after tweaking individual tabs reloads its saved settings, so choose the preset first. Otherwise HandBrake may quietly undo your work.
The naming is needlessly confusing. The large preset menu selects the whole recipe: codec, resolution limits, frame rate behavior, audio defaults, and so on. The encoder preset inside the Video tab only controls encoding speed versus compression efficiency. RF controls visual quality. Those are three separate decisions.
The suggestions above are reasonable, but check the Audio and Subtitles tabs before starting. A preset may include only the first audio track, omit commentary or another language, and skip subtitles depending on its selection rules. Auto-cropping can remove edges too. RF 21 is irrelevant if the track or picture area you wanted never reaches the output.
Pick a compatible preset, adjust RF, inspect every track, then save your own custom preset once it behaves correctly. Avoid the Advanced tab unless you can explain why a specific setting needs changing.
Don’t compare RF numbers across different codecs or encoders. RF 21 in x264 does not mean the same quality as RF 21 in x265, NVENC, or Intel Quick Sync, so copying a number from a guide can give you a very different result.
Hardware encoding is useful when speed matters, but it often needs a larger file to match a good software encode. For a library where size matters, use software H.264 or H.265 and accept the longer encode. For quick conversions, hardware encoding is perfectly reasonable.
Pick the playback format first, then judge quality with a short sample. Treat every encoder change as a fresh starting point rather than carrying the same RF value across.
Check whether the source is interlaced before copying settings from a typical Blu-ray or streaming guide. Old DVDs, camcorder footage, and some broadcast recordings may need Decomb or Deinterlace. Progressive video usually does not. Applying those filters unnecessarily can soften detail or alter motion, while leaving real interlacing untreated produces comb-like lines during movement.
I agree with @zeronode4729node about saving a custom preset, but don’t treat that preset as universal. Save the codec, quality range, audio defaults, and container. Recheck cropping, scaling, frame rate, and filters for every source. Those settings depend on the input more than on your preferred output format.
A practical workflow is to encode a 30 to 60 second section containing movement and dark detail, then view it on the actual playback device. If it looks rough, lower RF slightly. If it looks fine but encoding is too slow, move the encoder preset one step faster rather than changing several controls at once. Leave advanced encoder options alone unless you are solving a specific problem.
For general use, H.264 in MP4 remains the least troublesome choice. H.265 is worth considering when storage matters and all your devices support it. Just remember that a smaller encode is not automatically a better encode, especially if HandBrake removed needed detail through filtering before the codec even got involved.
Don’t burn a full movie encode before you’ve watched the test clip on the actual TV, not your computer monitor. What looks clean on a laptop can show banding in dark scenes on a big panel, and that’s exactly where @silent_fuzzy_socket’s 30 second dark sample earns its keep.
Everyone keeps landing on MP4, and for playback that’s fine, but MKV deserves a mention since nobody brought it up. If your source has soft subtitles, multiple audio tracks, or chapters, MP4 will quietly drop or mangle some of that while MKV just keeps it. And here’s the practical bit: if you ever change your mind, you can remux MKV to MP4 later in seconds with no re-encoding, so you’re not locked in. I’d only default to MP4 when the target device is picky, like an older TV or a car headunit. Otherwise MKV saves you from redoing an encode just because a track didn’t survive the container.
@zeronode4729node’s warning about the preset reloading and wiping your tabs is the one people actually get burned by, so that’s worth repeating over anything about RF numbers.
Testing on your TV is smart, especially for dark scenes. For a simpler setup, pick Fast 1080p30, choose MP4, H.264, and set Constant Quality to RF 22. Leave filters, frame rate, and audio on preset defaults. Encode the whole file once. If it looks rough, use RF 20. If the file is too big, try RF 24. This keeps playback reliable and avoids endless setting tweaks. Save the setup as your own preset for next tiem.
Check whether you actually need to encode before choosing a preset. HandBrake always re-encodes the video, so it cannot move an existing H.264 or H.265 stream into a different container without some quality loss. If the video already looks good and your only problem is the container, audio tracks, or subtitles, remuxing is the safer and much faster job.
Be careful with heavily compressed sources too. A small streaming download encoded again at RF 21 will not recover detail, and the output can even end up larger while looking slightly worse. HandBrake works best when you start from a reasonably clean source and accept that smaller files require some compromise.
There is another frame-rate detail hidden behind “Same as Source.” Variable frame rate is usually fine for ordinary playback, but it can cause timing or audio-sync trouble in some editors and older devices. If the file will be edited, use a constant frame rate that matches the actual source rate. Don’t convert 23.976 to 30 or 60 unless the target device specifically requires it, since that can create uneven motion.
I’d keep the original file until the completed encode has been checked from beginning to end. Test clips catch picture-quality problems, but they may miss a subtitle that appears late, a commentary track selected by mistake, or audio drift that builds over a long recording. A preset saves time, but it is not a substitute for verifying the final file.