Account

What new tool do you want?

Video & Audio

Video Compressor (Reduce MP4 Size)

Compress videos to share by email, WhatsApp or Discord — choose a quality level or a target size in MB, and optionally lower the resolution. Runs in your browser.

How to use

  1. 1Add a video and choose a quality preset or a target size (e.g. 25 MB).
  2. 2Optionally lower the resolution, then press Compress.

How it's calculated

Quality mode uses H.264 with a constant rate factor (CRF). Target size calculates the video bitrate: (MB × 8,000 ÷ seconds) − audio bitrate.

Frequently asked questions

How small can I make it?

Lowering resolution to 720p or 480p plus a higher CRF typically cuts size by 60–90% with acceptable quality.

Why is compression slow?

Encoding runs on your CPU in the browser without hardware acceleration. A few minutes of 1080p video can take several minutes.

Is my video uploaded?

No — it's compressed on your device. Only the video engine is downloaded once from a CDN.

A worked example of the target-size math

For a 60-second video with a 25MB target and 96kbps audio, the tool computes the video bitrate as floor((25 × 8000 × 0.97) ÷ 60 − 96) = 3137 kbps. Breaking that down: megabytes × 8000 converts to kilobits (×8 for bits, ×1000 for the mega- prefix, using round decimal units rather than binary ones), dividing by the duration in seconds gives the total combined bitrate budget, the 0.97 factor leaves a 3% safety margin since container overhead and encoder variance mean a precisely-targeted bitrate often slightly overshoots, and finally subtracting the audio bitrate leaves exactly what's left over for video. If that leftover number drops below 50kbps, the tool refuses outright rather than producing a technically-compliant but unwatchably blocky result — at that point the honest fix is a smaller target or a lower resolution, not a smaller number silently fed to the encoder.

Why quality mode and size mode use fundamentally different encoder settings

Quality mode uses CRF (Constant Rate Factor) — a single number telling the encoder 'maintain this visual quality level, and let the resulting bitrate and file size vary scene by scene' (CRF 23 for high quality down to CRF 33 for smallest, since higher CRF means more compression). Target-size mode does the opposite: it fixes the bitrate to hit an exact file size and lets visual quality be whatever that bitrate produces, with -maxrate and -bufsize constraining how much the bitrate can spike during complex scenes so the overall average stays on target. These are genuinely different encoding philosophies — one optimizes for consistent quality with a variable file size, the other for a guaranteed file size with variable quality — which is exactly why the tool offers both as separate modes rather than picking one.

Why this can take noticeably longer than a desktop video editor

The compression runs entirely through FFmpeg compiled to WebAssembly, executing on your CPU through the browser's JavaScript engine rather than using your graphics card's dedicated hardware video encoder (which most desktop software and even your phone's OS use by default for speed). Software-only, CPU-bound encoding is simply slower — the tradeoff for that slowdown is that the video never has to leave your device at all, with only the roughly 32MB FFmpeg engine itself fetched once from a CDN and cached for later use, not your actual video content.

Related tools

More: Video & Audio