Encoding presets don’t get a lot of attention, but they decide whether your stream looks sharp or like a mosaic made of Lego bricks. They control how hard the encoder works, how long it chews on each frame, and how much data ends up in the pipe. I’m Priya Mehta, and most of my week is spent staring at bitrate curves and VMAF logs. Pick a preset that’s too fast, and you’re broadcasting macroblocks. Pick one that’s too slow for a live event, and you’ve got a slideshow. The trick is knowing where the elbow is—where the extra compute stops paying you back in better picture. This article walks through what presets actually do, what they cost you in real money, and how to pick the right one without overthinking it.
What Encoding Presets Actually Are
A preset is a bundle of knobs the encoder turns for you—motion estimation range, partition depth, reference frame count, rate-control behavior. In software encoders like x264 and x265, these bundles get names that tell you how patient the encoder is: ultrafast, superfast, veryfast, faster, fast, medium, slow, slower, veryslow, placebo. The faster the preset, the fewer corners the encoder checks. The slower the preset, the more analysis it runs per frame, trying to squeeze the same visual punch into fewer bits.
Here’s the basic deal: CPU cycles for compression efficiency. Crank out a 10-minute clip at ultrafast on a decent box and you might be done in 30 seconds. The file will be fat. Switch to veryslow and that same clip could take 15 minutes, but the file might be half the size and look identical to a viewer. That’s not a rounding error—it’s the whole job.
How the Preset Scales Look
Software encoders follow a speed ladder. x264 gives you: ultrafast, superfast, veryfast, faster, fast, medium, slow, slower, veryslow, placebo. x265 uses the same labels. Hardware encoders from NVIDIA (NVENC) or Intel (Quick Sync) don’t use those words—they lean on things like p1 through p7 or a “target usage” integer—but the idea holds: higher number or lower target usage means more work per frame, better compression, slower throughput.
What Presets Do to Picture Quality
We measure quality with numbers (PSNR, SSIM, VMAF) and with our eyes. A slower preset at a fixed bitrate makes the encoder try harder. It checks more motion vectors, tests more block partitions, keeps more reference frames around. You get less ringing around sharp edges, fewer flat areas dissolving into blocky mush, and gradients that don’t look like contour maps.
Take a 1080p clip at 4 Mbps. Encode it with veryfast and you might land a VMAF around 80. Push it through medium and you’re suddenly at 85—same bitrate, visibly cleaner motion, skin that doesn’t crawl. But the quality jump shrinks when the content is simple. A talking head with a locked-off camera doesn’t give the encoder much to think about. Veryfast might look nearly the same as slow there, so don’t waste the CPU.
Bitrate Savings That Actually Matter
Slower presets wring more quality out of fewer bits, so you can hit your quality floor at a lower bitrate. That’s a direct line to your CDN bill. If moving from fast to slow lets you drop from 3 Mbps to 2 Mbps while keeping VMAF at 93, you just shaved a third off your delivery cost. Multiply that across a library getting millions of views a month and it’s real money—enough to make your CFO stop asking why you need so many cloud instances.
Where the Costs Land
Cost shows up twice: the compute that runs the encoder, and the bandwidth that pushes bits to viewers. Faster presets keep your instance bill low but make your files big. Slower presets burn more CPU time but shrink the bits you ship. The right answer depends on whether you’re encoding live or for a catalog that sits around getting streamed for years.
On-Demand Encoding
VOD is a one-time pain, repeated reward. You pay the encoding tax once, then serve the result a million times. Throwing more compute at a preset today can pay for itself within a couple of months of reduced egress. Say you’re processing a 90-minute film. Veryfast gives you a 4 GB file at your quality target. Veryslow drops it to 2.2 GB. If that film gets 10,000 streams a month, you’re saving 18 TB of transfer monthly. At a typical CDN price of two cents per gig, that’s $360 back in your pocket every month—over four grand a year. The extra encoding time? Maybe 50 cents on spot instances. The math is not close.
Live Encoding
Live video flips the equation. You’re paying for compute every second the stream is up, and latency means you can’t let the encoder daydream. A preset that needs two seconds per frame is a non-starter when your glass-to-glass budget is under a second. Most live setups stick to veryfast or faster on software, or hand the work to a hardware encoder. The bitrate will be higher for the same quality, but the compute cost stays predictable and the frames stay on time.
Hardware encoders like NVENC on modern NVIDIA cards have gotten genuinely good. They can match x264 medium quality while running at speeds that embarrass veryfast. They use fixed-function silicon, so the CPU is barely involved. For a live pipeline at scale, a rack of GPUs can beat a room full of general-purpose cores on both cost and latency.
Picking a Preset Without Losing Your Mind
There’s no best preset—only the one that fits your content, your delivery pipe, and your budget. Start by benchmarking a few clips that look like your typical input. Encode them at a range of presets, keeping CRF or bitrate fixed. Record encoding time and file size. Run VMAF or at least SSIM against the source. Plot the results and look for the spot where the line bends—where slower presets stop giving you noticeable quality or bitrate returns.
Content Complexity
High-motion material—sports, action movies, gameplay—makes the encoder work, so slower presets earn their keep. Static content like lecture captures or software demos doesn’t benefit much. For a webinar platform, veryfast is probably fine. For a film-focused streaming service, slow or slower is worth the compute burn.
Bitrate Ladders
Presets and bitrate ladders are coupled. At the bottom of the ladder—low-bitrate, small-screen renditions—a slow preset can rescue a stream that would otherwise be a blocky mess. At the top, 25 Mbps for a 4K mezzanine, fast and placebo probably look the same, but one finishes in time for lunch. Don’t pay for placebo-level work at high bitrates.
Hardware vs. Software
Software encoders (x264, x265, libaom-av1) give you the widest preset range and the tightest compression. Hardware encoders (NVENC, QSV, AMF) trade some efficiency for fixed, low-power throughput. A sensible cloud pipeline mixes both: hardware for live and quick-turnaround jobs, software for premium VOD where bitrate savings compound.
A Testing Routine That Won’t Waste Your Time
Don’t just trust the preset name—measure. Use FFmpeg with everything locked except the preset. Keep the same CRF or bitrate, same profile, same level. Track encoding fps and output file size. For quality, pipe the result through libvmaf against the source. Run this on a handful of clips that represent your library and you’ll have real numbers, not guesses.
Here’s a quick FFmpeg snippet to test a preset:
ffmpeg -i input.mov -c:v libx264 -preset medium -crf 23 -an output.mp4Swap medium for each preset you’re evaluating. Note the wall-clock time and file size. For VMAF:
ffmpeg -i encoded.mp4 -i original.mov -lavfi libvmaf -f null -You’ll get a mean VMAF score. Stack those numbers in a spreadsheet and you’ll see exactly where the trade-off stops making sense for your content.
Cost Optimization That Goes Beyond the Obvious
Once you’ve mapped the preset landscape, you can get clever with your pipeline. For VOD, per-title encoding is a proven play. Analyze each video’s complexity and assign a preset accordingly—veryfast for an interview, slow for a sequence with confetti and quick pans. Netflix built a whole workflow around this idea. You can build a basic version with FFmpeg and a shot-detection script without a research team.
For live channels, think about adaptive preset switching. If CPU headroom is healthy, nudge the preset toward medium to clean up the stream. If load spikes, drop back to fast so you don’t drop frames. OBS does a mild version of this already; a custom pipeline can be more aggressive and tuned to your hardware.
Cloud encoding services charge by the input minute. A slower preset doesn’t change the per-minute rate, but it keeps your instance running longer. Spot instances and reserved capacity can cut that compute rate by 60–70%. Pair cheap compute with presets tuned to your content, and you’re serving high-quality video for a fraction of the on-demand sticker price.
FAQ
What’s the best x264 preset for decent quality without giant files?
Start with medium. It’s the factory setting for a reason—balanced speed and compression. If you’ve got CPU to spare and file size matters, step to slow. The jump from medium to slow typically trims bitrate by 10–15% at the same quality, with encoding time roughly doubling. Skip placebo—it burns cycles for gains you’d need a magnifying glass to see against veryslow.
Do hardware encoders have something like presets?
They do, but the dial is coarser. NVENC uses p1 (fastest) through p7 (slowest), with p6 and p7 enabling two-pass and deeper lookahead. Intel Quick Sync maps target usage from 1 (best quality) to 7 (fastest). The pattern holds—more work, better compression—but hardware encoders can’t match the bitrate efficiency of a well-tuned software encoder at the same throughput. Their win is fixed performance and lower power draw.
Can I change presets on the fly during a live stream?
Technically yes, but you’ll have to restart the encoder session, which usually means dropped frames. Most live setups sidestep this by running two encoder instances in parallel—one at veryfast for the main feed, another at a slower preset as a backup—and switching at the ingest point if needed. It adds some plumbing but gives you a safety net when the CPU gets hammered.
Wrapping Up
Presets are a trade-off lever, not a magic wand. The right one depends on your content, your viewers, and how much you’re willing to spend on compute versus bandwidth. Test with your own footage, measure the real bitrate and quality differences, and let the numbers tell you where to stop. At scale, even small preset shifts add up—fewer artifacts on screen and fewer dollars flying out the door.