“Without losing quality” isn’t literally true of any video compression, and understanding why changes how you should actually approach this. Every compression method removes some information from the original file. The real goal, and the one HandBrake and ffmpeg are both built around, is removing information in a way the human eye can’t detect at normal viewing distance and resolution, while shrinking the file substantially. Once you understand that distinction, picking the right settings gets a lot more straightforward.
Why “Constant Quality” Is the Setting That Actually Matters
Both HandBrake and ffmpeg default to a mode called Constant Quality, controlled by a value most commonly called CRF (Constant Rate Factor) or RF depending on which tool and encoder you’re using. The scale runs from 0, essentially lossless and enormous, to 51, badly degraded and tiny. Lower values mean higher quality and larger files. Higher values mean smaller files with more visible compression artifacts.
The number that actually matters isn’t a universal constant, it depends on your source footage, the encoder you’re using, and your own tolerance for compression artifacts. HandBrake’s own documentation suggests roughly CRF 20 for standard-definition video and CRF 22 for HD video as reasonable starting points with the x264 encoder, not fixed rules. Grainy, high-motion footage needs a lower CRF to look clean than smooth, low-motion footage does at the same setting, which is why testing against your specific source matters more than copying a number from a guide.
Setting Up HandBrake for the First Time
Download HandBrake from its official website only, handbrake.fr, since it’s free and open source but frequently gets bundled into shady download wrappers on third-party sites. On Windows, it requires the Microsoft .NET Desktop Runtime, which HandBrake will prompt you to install on first launch if it’s missing.
Start with one of HandBrake’s built-in presets rather than building settings from scratch. The Production Standard preset is a reasonable general-purpose starting point that preserves your source’s original resolution and frame rate rather than changing them unexpectedly. From there, the two settings actually worth adjusting are the video codec and the CRF value, everything else in the default preset is reasonable for most use cases.
Choosing a Codec: H.264 vs. HEVC vs. AV1
Codec choice affects both compression efficiency and compatibility, and the tradeoff is real in both directions. H.264 (x264) remains the most universally compatible codec, playable on essentially any device or platform without issue, making it the safe default if you’re unsure where the compressed file will end up. HEVC (H.265) achieves meaningfully better compression at the same visual quality, commonly cutting file size by around 50 percent compared to H.264 at an equivalent quality level, but it demands more processing power to encode and can hit compatibility issues on older devices or some web platforms that don’t fully support it.
AV1 is the newest option in HandBrake’s official presets, offering compression efficiency that can exceed even HEVC’s, with hardware-accelerated encoding available on newer Intel chips specifically. It’s the right choice if your priority is squeezing out the smallest possible file and your playback destination supports it, but broader compatibility and encoding speed both lag behind the more established codecs, so verify your target platform actually supports AV1 playback before standardizing on it.
Practical HandBrake Settings by Use Case
For a general-purpose compression where you want a meaningfully smaller file with no visible quality loss on a typical screen, start with the x264 encoder at CRF 20 to 22, using the Production Standard preset as your base. For sharing a compressed video by email or a platform with a strict size limit, dropping to CRF 26 to 28 with the “Very Fast” or “Fast” encoder speed setting trades a small amount of visible quality for a dramatically smaller file, useful when the alternative is not being able to send the file at all. For archival purposes where quality matters more than size, staying in the CRF 18 to 20 range with a slower encoder preset (Slow or Slower) produces a noticeably better result at the cost of longer encoding time, since slower encoder presets spend more computational effort finding efficient ways to compress each frame.
Avoid extremely low CRF values, 0 through 5, unless you specifically want a near-lossless file that’s barely smaller than your source. There’s no meaningful visual benefit for normal viewing at that range, and you may end up with a larger file than expected for the modest quality gain.
Using ffmpeg for More Control and Batch Processing
ffmpeg accomplishes the same core compression as HandBrake through command-line syntax rather than a graphical interface, and it’s the better choice specifically for batch processing multiple files or automating a repeatable workflow. A basic ffmpeg compression command using the same Constant Quality approach looks like this: specifying the H.264 codec, a CRF value, and an encoding preset that controls the speed-versus-efficiency tradeoff, then the output filename. The core concepts, CRF for quality and codec choice for compatibility, transfer directly from HandBrake’s graphical settings, since HandBrake actually uses ffmpeg’s underlying encoding libraries behind its own interface.
The practical advantage of ffmpeg over HandBrake shows up specifically when you need to compress many files identically rather than adjusting settings one file at a time through a GUI. A single ffmpeg script can process an entire folder of videos overnight with consistent settings, something HandBrake’s interface makes considerably more tedious for anyone working with more than a handful of files.
How to Actually Judge Whether You’ve Lost Visible Quality
Don’t trust a CRF number in isolation. Encode a short test clip, thirty seconds is usually enough, at your candidate CRF value, then compare it directly against the original at normal viewing size and distance, not zoomed in at 400 percent looking for pixel-level differences nobody will notice during actual playback. If you can’t tell the difference in that realistic comparison, that CRF value is a genuine “no visible quality loss” setting for that specific source. If compression artifacts are visible, blocking in dark scenes, blurring on fast motion, lower the CRF value by two or three points and test again rather than guessing at a bigger jump.
This per-source testing habit matters more than any specific number in this guide, because the right CRF value for a slow-panning nature documentary and a fast-motion gaming clip can differ by five or more points on the same scale, even though both might reasonably be called “high quality” source footage.
Common Mistakes That Actually Hurt Quality
Re-encoding an already-compressed file repeatedly compounds quality loss each time, since every encoding pass discards some information regardless of how conservative the settings are. If you have the original, uncompressed or lightly compressed source available, always encode from that rather than from a file that’s already been through a lossy compression pass, even if the original file is larger and less convenient to work with.
Changing resolution unnecessarily is another common mistake. Downscaling a video’s resolution does reduce file size, but it’s a separate lever from CRF and shouldn’t be your first move if quality preservation is the goal. Adjust CRF first, and only reduce resolution if you need more size reduction than CRF adjustment alone can reasonably provide without visible quality loss, since resolution changes are more immediately noticeable to a viewer than a moderate CRF increase.
Don’t Forget the Audio Track
Video compression guides overwhelmingly focus on the video stream and skip the audio track entirely, but audio can be a meaningful chunk of a file’s total size, especially in an uncompressed or lightly compressed source. HandBrake’s default audio settings usually re-encode to a reasonable AAC bitrate automatically, but for a video where dialogue or music quality genuinely matters, check the audio bitrate setting directly rather than assuming the default is appropriate. A bitrate around 128 to 160 kbps is typically sufficient for stereo dialogue and general content without noticeable quality loss, while music-heavy content benefits from staying closer to 192 kbps or above.
If your source audio is already compressed and you’re just changing the video codec or resolution, consider passing the audio through without re-encoding at all, an option both HandBrake and ffmpeg support, since re-encoding audio that’s already been compressed once introduces the same kind of compounding quality loss that affects re-encoded video.
Hardware Acceleration: Faster, But With a Real Tradeoff
Both HandBrake and ffmpeg support hardware-accelerated encoding through your GPU, Intel Quick Sync, NVIDIA NVENC, or AMD’s equivalent, which can cut encoding time dramatically compared to software-only encoding. The tradeoff worth knowing before defaulting to it: hardware encoders generally produce a slightly larger file for the same visual quality compared to software encoding at an equivalent CRF-like setting, because they’re optimized for speed rather than maximum compression efficiency.
For a quick compression where encoding time matters more than squeezing out the absolute smallest file, hardware acceleration is a reasonable tradeoff. For archival compression where you’re encoding once and want the best possible size-to-quality ratio, software encoding through x264, x265, or AV1’s software encoder will typically outperform the hardware-accelerated equivalent, at the cost of a longer encoding time you only pay once.
Common Questions About Compressing Video for Free
What’s the actual difference between HandBrake and ffmpeg?
HandBrake is a graphical application built on top of ffmpeg’s underlying encoding engine, making it more approachable for a single file or occasional use. ffmpeg is the command-line tool itself, offering more granular control and being significantly better suited to batch processing many files with identical settings.
Is HEVC always better than H.264 for compression?
HEVC achieves better compression efficiency at the same quality level, often cutting file size by around half compared to H.264. The tradeoff is compatibility: some older devices and platforms don’t fully support HEVC playback, so confirm your target destination supports it before making it your default.
What CRF value should I actually use?
There’s no single correct number since it depends on your source footage and encoder. HandBrake’s own documentation suggests roughly 20 for standard-definition and 22 for HD video with x264 as reasonable starting points, but test a short clip at your chosen value and compare it directly against the original before committing to it for a full file.
Why does my compressed video still look worse than expected?
Check whether you’re encoding from an already-compressed source rather than the original, since repeated lossy encoding compounds quality loss. Also confirm you’re not using an unnecessarily high CRF value or an overly aggressive encoder speed preset, both of which sacrifice more quality than the file-size benefit usually justifies.
The Bottom Line
Genuine “no visible quality loss” compression is achievable for free with either HandBrake or ffmpeg, but it depends on testing your specific source at a reasonable CRF value rather than trusting a single universal number from any guide, including this one. Start around CRF 20 to 22 with the x264 encoder, compare a short test clip against your original at normal viewing size, and adjust from there based on what you actually see rather than what a preset assumes about your footage.
References and Sources
VideoProc, “HandBrake Video Compression: Settings and Troubleshooting”: https://www.videoproc.com/video-editor/handbrake-compress-video.htm
WinXDVD, “How to Compress Video with HandBrake and Keep Good Quality”: https://www.winxdvd.com/handbrake-troubleshoot-tips/handbrake-compress-video.htm
MundoBytes, “HandBrake: How to Convert and Compress Video Without Losing Quality”: https://mundobytes.com/en/Handbrake-convert-and-compress-video/
ClipGenie, “Which Is Better for Video Compression (No Quality Loss)?”: https://clipgenie.io/post/ffmpeg-vs-handbrake-which-is-better-for-video-compression-no-quality-loss/
About The Author
