AntiUpload// browser-resident file tools
ENESFRPTDE
SESSION · 
← Back to home

Free · No file size limit · No watermark · Quality or target size

Compress Video

Shrink a video without obvious quality loss — CRF presets from "Best" to "Smallest", optional resolution downscale.

100% freeNo file size limitNo watermarkNo sign-up
  1. 1Pick file
  2. 2Configure
  3. 3Download
For platform caps: pick "Smaller" + 720p downscale to comfortably fit Discord's 25 MB, WhatsApp's 16 MB, or email's 25 MB limits. "Balanced" default is the libx264 reference quality.
  • Files never leave your browser — processed entirely on your device
  • No upload, no queue, no waiting for a worker to free up
  • No file-size cap from us — limit is your device's RAM

About Compress Video

AntiUpload's Video Compressor reduces the file size of any video without uploading it anywhere. It's the flagship in the video toolkit because compression is the highest-volume request: people record 1080p phone clips that are 100+ MB and then can't email them, share them on Discord's free tier (25 MB cap), or fit them under WhatsApp's 16 MB global limit. We use libx264 in WebAssembly with CRF (Constant Rate Factor) quality presets — same encoder Handbrake desktop uses, same quality settings the professional FFmpeg tutorials recommend, just running inside your browser instead of on a server.

Four CRF presets cover the dominant tradeoffs: Best (CRF 20, near-visually-lossless, ~40% size reduction on typical phone clips), Balanced (CRF 23, the libx264 default — works for 90% of users, ~60% size reduction), Smaller (CRF 28, noticeable but acceptable compression artifacts, ~75% reduction), and Smallest (CRF 32, obvious artifacts but the smallest file). Pair with optional resolution downscale (1080p / 720p / 480p / 360p) for compounding size savings — a 4K source compressed to Balanced + downscaled to 720p is typically 90%+ smaller than the original.

Cloud video compressors (Veed, FreeConvert, CloudConvert, VideoSmaller, Clideo) all charge for the big-file case: free tiers are 100-500 MB max, watermarked, queued, or paywalled. The economics make sense for them — server CPU isn't free. For us they don't apply: the entire encode runs on your CPU/GPU. On Chromium / Safari 17+ the upcoming WebCodecs path will route encoding through your device's hardware H.264 encoder for 5-20× speedup; for now we use FFmpeg WASM libx264 with the `ultrafast` preset and `medium` effort level as a quality-vs-speed compromise tuned for the WASM build's lack of x86 ASM acceleration.

How it works

  1. Drop your videoAccepts MP4, MOV, WebM, MKV, AVI, M4V, FLV. No file-size limit from us — multi-gigabyte 4K recordings work fine. The constraint is your device's available RAM.
  2. Pick a quality presetBest (CRF 20) preserves detail aggressively, modest savings. Balanced (CRF 23, default) — the libx264 standard, fine for 90% of uses. Smaller (CRF 28) is the sweet spot when fitting platform caps. Smallest (CRF 32) for last-resort space savings.
  3. Optionally downscale resolutionResolution downscale compounds with CRF for bigger savings. A 4K source at Balanced + 1080p downscale typically shrinks 70-85%. 720p downscale produces ~90% savings on 4K source.
  4. Optionally pick encoder effortMedium effort (default) is bench-tuned — produces smaller files at the same CRF target compared to ultrafast, at 1.4× encode time. For long clips on slow devices, switch to ultrafast and accept slightly larger output.
  5. Click Compress videoOutput is always MP4 (universally playable). Progress bar shows live frame= updates so you can confirm encoding is alive. Result panel shows the % size reduction.

When to use Compress Video

Compressing phone video for email attachment
Gmail caps attachments at 25 MB. iPhone 4K video runs ~400 MB/min — way over. Compress to Balanced + 720p downscale and a 5-minute clip lands well under 25 MB.
Fitting under Discord's 25 MB free upload limit
Discord's free tier rejects uploads > 25 MB. Most phone gameplay / reaction recordings exceed this. Smaller preset at 720p typically lands a 1-minute clip at 12-20 MB — fits with room to spare.
Compressing for WhatsApp's 16 MB cap
WhatsApp's global video cap is 16 MB. For longer content try Smallest CRF + 480p downscale + audio-only consideration via our Mute Video tool if the visuals carry less than the audio.
Reducing storage / cloud-sync cost on large clips
A 1-hour 4K recording is ~24 GB. Compress at Balanced + 1080p and the same content is 1-2 GB while remaining sharp on phone / laptop playback. Dropbox / Google Drive quota stretches further.
Web-optimising clips for blog / portfolio sites
Embedding 4K source on a portfolio page is bad UX — mobile users load several hundred MB unnecessarily. Compress to Balanced 720p for fast playback at acceptable visual quality.

Frequently asked questions

How to compress a 1GB video to under 100MB for free?
Drop it into our Video Compressor, pick Smaller (CRF 28), and add 720p downscale. A 1 GB source typically lands at 60-90 MB. If you need to go smaller, try Smallest (CRF 32) + 480p — accept visible quality drop. There's no upload involved; the compression runs in your browser. Veed / CloudConvert / VideoSmaller all cap free users at 500 MB or less and watermark above.
What CRF should I pick?
CRF 23 (Balanced) is the libx264 default and the right choice for 90% of users — visually-clean output at ~60% smaller than source. CRF 20 (Best) when the source is for editing / archival / printing. CRF 28 (Smaller) when you need to fit a platform cap. CRF 32 (Smallest) for last-resort space savings; expect visible compression artifacts.
Best free no-watermark video compressor online?
AntiUpload Video Compressor — no watermark, no signup, no size cap, no upload. Compare to Veed (watermarks free tier, paywall above 250 MB), FreeConvert (1 GB free + watermark), VideoSmaller (limits), Clideo (watermark on free). All of them upload your video to their servers; we don't need to.
Why is compression slower than the cloud services?
Because we use your CPU, not a beefy server. Cloud services run on multi-core Xeon CPUs with hardware H.264 encoders. Your laptop encodes via FFmpeg WASM (libx264) at a fraction of that speed (~1× realtime on a recent Apple M-series, slower on Intel laptops or phones). The trade-off is: their speed costs $9-25/month + uploading 1 GB of your data first. Our slowness is fully free with no data leaving your device. For typical phone clips < 5 minutes the difference is minutes vs seconds, not hours vs minutes.
Does compressing reduce quality?
Yes — that's how it works. Lower CRF = higher quality + bigger file. CRF 20 is near-visually-lossless on most content. CRF 28 is "noticeable on close inspection but fine for casual viewing." CRF 32 is "compression artifacts visible on motion / fine detail." Resolution downscale also drops quality (visibly so on >= 1080p source viewed full-screen). For "smaller file at the same visual quality" there's no magic — you have to drop CRF and live with the artifacts.
Can I compress without losing any quality?
Lossless video compression exists (libx264 `-qp 0` or codecs like FFV1) but produces files only marginally smaller than the source — usually 90%+ of the original size. For practical "make the file smaller" use cases, you're always trading some quality for size. Our Best preset (CRF 20) is the closest thing to "lossless to the human eye" and saves ~40% on typical phone source.
How long does compressing a 5-minute 1080p clip take?
On a modern laptop (Apple M-series, recent Intel) at Balanced + medium effort: 3-10 minutes. On older devices or phones: longer. The WebCodecs hardware-encode path (coming in a follow-up PR) will cut these times by 5-20×. For now, close other browser tabs to free up CPU for the encode.

Related tools