How to reduce video file size without losing quality
Most videos are far bigger than they need to be, carrying detail no screen shows and bitrate no eye notices. Here is how to cut a file down while keeping the picture that actually matters.
"Without losing quality" is doing a lot of work in that phrase, so let us be precise: you cannot remove data and keep every bit, but you can remove data the eye never registered in the first place. Most video files are padded with exactly that — resolution beyond what the screen shows, and bitrate beyond what motion needs. Strip those and the picture looks identical while the file gets much smaller.
This guide explains the three settings that control video size — CRF, resolution and bitrate — what each one really does, and the order to change them in so you cut the most weight for the least visible cost.
What actually makes a video file big?
A video's size is its bitrate multiplied by its duration, and the bitrate is driven by two things: how many pixels are in each frame (resolution) and how much data the encoder spends describing them (quality). A phone recording a slow talking-head scene at 4K and a high bitrate is spending enormous amounts of data on a picture that barely moves — that waste is exactly what compression reclaims.
Before you change anything, it helps to see what you have. Drop the file into video file info to read its resolution, bitrate and codec. A 1080p clip at 20Mbps, for instance, is carrying roughly four times the bitrate it needs — the headroom you are about to reclaim.
What is CRF and why does it help?
CRF, or Constant Rate Factor, is the smartest way to compress. Instead of forcing a fixed bitrate on every second, you set a quality target and let the encoder spend bits where they matter — lots on complex, fast-moving frames, few on simple, still ones. The result is a smaller file at the same perceived quality, because no bits are wasted on scenes that did not need them.
| CRF | Quality | Use for |
|---|---|---|
| 18 | Visually lossless | Archival, when size barely matters |
| 23 | The default sweet spot | Most videos, no visible loss |
| 26 | Good, slightly softer | Sharing, web, smaller files |
| 30 | Visibly compressed | When size is the priority |
Lower CRF means higher quality and a bigger file; higher CRF means more compression. The scale is roughly logarithmic — every increase of about six halves the file size. For most people, sitting at CRF 23 to 26 gives a large size cut with no change anyone would notice.
When should you lower the resolution?
Resolution is the biggest lever of all, because pixels multiply. A 4K frame holds four times the pixels of 1080p, and 1080p holds more than double 720p. If a video will only ever be watched on a phone or embedded small on a web page, its 4K resolution is pure waste — the screen cannot show that detail regardless.
- Match resolution to the destination: 1080p for a full-screen desktop or TV, 720p for most web and social embeds, 480p for a small inline player.
- Halving each dimension quarters the pixel count, which is a dramatic size saving before CRF even applies.
- Use the resize video tool to set the output dimensions, then compress the smaller frame.
How is bitrate different from CRF?
Bitrate control and CRF are two ways to reach a file size, and they suit different goals. CRF aims for a consistent quality and lets the size fall where it may. Bitrate control does the opposite: you fix the size and let quality vary to hit it. Use CRF when quality is the priority and any file size is acceptable; use a target bitrate when you must land under a hard size ceiling — an email limit, an upload cap.
For the "keep it looking good" goal in this article, CRF is the right tool, and the compress video workbench exposes it directly. When instead you need an exact figure — under 25MB for email, say — switch to compress video to a target size, which works backwards from the size you type to the bitrate needed.
Compress a video by qualityWhat order should you do it in?
Doing these steps in the right sequence gets the smallest file for the least visible loss. Work from the changes that remove invisible data to the ones that start to cost quality.
- Trim off anything you do not need — a slow intro or a trailing pause — with the trim video tool. Fewer seconds is a direct size cut with zero quality cost.
- Lower the resolution to match where the video will play, removing pixels the screen cannot show.
- Re-encode with CRF around 23, and nudge higher toward 26 if the file is still bigger than you want.
- Only if you have a hard size limit, switch to a target bitrate to land precisely under it.
Switching to a more efficient codec is a fifth option — H.265 packs the same quality into a smaller file than H.264 — but it plays on fewer devices, so weigh compatibility before choosing it in the video converter. If in doubt, keep H.264 and lean on resolution and CRF instead.
Frequently asked questions
Can you really compress video with no quality loss?
Not literally — some data is always discarded. But you can discard data the eye never noticed: resolution beyond the screen and bitrate beyond what motion needs. At CRF 23 and a sensible resolution, the result looks identical to almost everyone while being much smaller.
What is a good CRF value?
For H.264, CRF 23 is the default and looks visually lossless to most viewers. Move up to 26 for smaller files with only a slight softening, or down to 18 when you want archival quality and size is no concern.
Does lowering resolution hurt quality?
Only if you drop below the resolution the video is actually watched at. Reducing a 4K clip to 1080p for phone playback removes detail the phone could never display, so there is no visible cost — just a much smaller file.
Is the video uploaded when I compress it here?
No. Compression runs in your browser with ffmpeg compiled to WebAssembly. The file is read from your disk, re-encoded on your device, and never sent to a server, so even unreleased footage stays private.