BYTETOOLS

Video Compression Tips, Settings and Mistakes to Avoid

The single biggest win in video compression is picking the right CRF: stay around 23–28 for files that look identical to most viewers but are dramatically smaller, and only push higher when a hard size limit forces your hand. Beyond that one setting, a handful of habits separate a clean result from a blurry, oversized or painfully slow one.

These tips assume you are using a local, in-browser tool like the ByteTools Compress Video tool, where the CRF slider and output-size readout are the two controls that matter most.

Best practices for clean, small files

  • Trim before you compress. Cut dead footage at the start and end first. Re-encoding fewer seconds is faster and produces a smaller file than compressing the whole clip and trimming later.
  • Start conservative, then push. Compress at CRF 28, preview it, and only raise the value if you still need it smaller. It is easier to add compression than to recover lost detail.
  • Watch the output-size readout. The tool shows the new size, so treat compression as a target-and-check loop instead of a one-shot guess.
  • Resize when detail is not the point. A 4K screen recording that will only be watched at 720p shrinks far more if you reduce dimensions before compressing.
  • Keep the source file. Always compress a copy so you can go back if you overshoot.

Common mistakes to avoid

MistakeWhy it hurtsDo this instead
Pushing CRF to 40 for everythingBlocky, smeared footage that looks worse than the size saving is worthMatch CRF to the goal; 23–28 for most uses
Re-compressing an already compressed exportEach pass throws away more detail with little size benefitCompress once from the highest-quality source you have
Compressing a huge raw clip you will trim anywayWastes time re-encoding footage you deleteTrim first, then compress
Expecting big savings from a tiny clipShort or already-lean files have little to giveAccept modest gains or resize instead

Troubleshooting slow or disappointing results

Compression feels slow. Re-encoding runs on your own CPU, not a server, so long or high-resolution videos take real time. Close other heavy tabs, use a desktop browser for big files, and trim the clip down first to speed things up.

The file barely got smaller. The source was probably already heavily compressed. Raise the CRF a little or reduce the resolution, but do not expect a lightly-encoded social clip to shrink like a raw camera recording.

Quality dropped more than expected. You likely combined a high CRF with a downscale, stacking two quality losses. Lower the CRF, or keep the original dimensions and let CRF alone do the work.

It looks fine on your laptop but bad on a TV. Larger screens reveal compression artifacts. If the video will be shown on a big display, choose a lower CRF than you would for a phone.

Try the Compress Video — free and 100% in your browser.

FAQ

What CRF gives the best quality-to-size balance?

For most everyday footage, CRF 23–28 is the sweet spot: a clearly smaller file with quality most viewers cannot tell apart from the original. Go lower for archival clarity, higher only when you must hit a size cap.

Is it better to lower the resolution or raise the CRF?

If the video will be watched small, lowering resolution saves more than CRF alone. If it needs to stay full-size, use CRF. Doing both at once can degrade quality quickly, so change one at a time and check the preview.

Why does compressing twice make it look bad?

Every re-encode discards detail permanently. Compressing an already-compressed file stacks that loss with almost no extra size benefit. Always start from the best-quality source you have.

How do I compress without losing audio quality?

The tool focuses on the video stream, so most of your savings come from the picture rather than the sound. Keep CRF moderate and your audio will stay perfectly usable.

Related free tools

Built by ByteVancer

ByteTools is a free product of ByteVancer, a software and web development studio building web apps, SaaS and custom software. If you have a product idea that needs real engineering behind it, explore what ByteVancer can do.