Compress a video to 100 MB
100 MB comfortably clears most upload forms, shared-drive policies and messaging apps, while being a fraction of what cameras and screen recorders actually produce.
It is the most generous preset here: a 1080p clip keeps full resolution for the first few minutes, and a 4K phone clip under a minute keeps all 3840×2160. Everything runs locally, with your hardware encoder and no upload step at all.
Drop a video here
or browse files
MP4 · MOV · WebM · MKV. Any length, any size. Nothing is uploaded.
What you get, by clip length
| Clip length | Resolution | Video bitrate |
|---|---|---|
| 1 min | 1920×1080 | 12.87 Mbit/s |
| 3 min | 1920×1080 | 4.21 Mbit/s |
| 5 min | 1280×720 | 2.47 Mbit/s |
| 10 min | 960×540 | 1.17 Mbit/s |
| 20 min | 640×360 | 0.52 Mbit/s |
| 1 hour | 426×240 | 0.15 Mbit/s |
Longest clip this target accepts: about 90 minutes with sound, or about 120 with the audio removed. Past that SqueezeVid declines the target and says why, rather than producing a file you would not send.
The economics of 100 MB
Three minutes is the practical edge of full resolution here, and ten minutes still gives you a perfectly legible half-frame — the table above has the exact steps. That makes this the preset for anything you would actually sit and watch.
The ceiling runs to well over an hour, and to two hours with the audio removed. So an hour-long screen recording does fit under 100 MB — but it arrives at a quarter-frame, which is fine for a talking head and useless for anything with small text on screen. Length and legibility are the trade, and the planner shows you which side of it you are on before you download.
When 100 MB is the wrong target
Two cases. If the file is already modest — a 40 MB phone clip, say — this preset has nothing to do: the planner refuses to inflate a light source to fill a budget, caps the bitrate near the source’s own quality and tells you it did. You would be re-encoding for no gain, and a re-encode is always a small quality loss.
And if what you actually need is an upload that fits a specific limit, pick that limit instead. Compressing to 100 MB and hoping is how you discover a 50 MB cap the slow way; the presets exist so the target is the constraint rather than a guess.
Frequently asked
- Can I compress a very large file, say 2 GB, in the browser?
- Yes. SqueezeVid streams the file from disk rather than loading it into memory at once, so multi-gigabyte inputs work. Only the compressed output is held in memory, and at a 100 MB target that’s trivial.
- Why use this instead of a desktop app like HandBrake?
- HandBrake is excellent, if you want to install software and pick codecs, profiles and rate-control modes yourself. SqueezeVid answers a narrower question: “make this file fit under X” with zero installation and zero settings, using the same hardware encoder a native app would.
- Will a 4K video stay in 4K at 100 MB?
- For about the first minute, yes — a 4K phone clip keeps all 3840×2160. Past that the planner steps down, because 4K needs more bitrate than this budget can hold for long. If 4K matters more than length, trim first; if length matters more, let it downscale.
Read next
How to compress a video to an exact file size
File size is bitrate × duration; everything else is detail. The actual math SqueezeVid runs, budgets and safety margins included.
Why in-browser video compression beats uploading to the cloud
The math of upload time, what WebCodecs actually is, and why a browser tab with access to your hardware encoder outruns a server farm for this job.