Reduce a video’s file size
Every video’s size is just bitrate × duration. Reducing it means lowering the bitrate, and doing that well means knowing how low you can go before the picture falls apart, and when to trade resolution instead.
SqueezeVid does that math for you, backwards: you say what the file must weigh, it works out the best bitrate and resolution that fit, then encodes locally in your browser. No upload, no queue, no watermark, no account.
Drop a video here
or browse files
MP4 · MOV · WebM · MKV. Any length, any size. Nothing is uploaded.
The three levers
Bitrate is the direct lever: halve it, halve the file. H.264 tolerates a surprising amount of squeezing before artifacts show, especially on static content like screen recordings.
Resolution is the rescue lever: when the bitrate budget per pixel gets too thin, a 720p image encoded properly beats a 1080p image starved of bits. SqueezeVid switches rungs automatically when the budget demands it.
Duration is the lever nobody wants to hear about: trimming a clip to the part that matters does more than any encoder setting. If a target seems impossible, cut first, compress second.
Common targets
Sharing on Discord? The free limit is 20 MB. Emailing? Gmail’s 25 MB really means ~18 MB after encoding overhead. Posting through a form or helpdesk? 10 MB and 25 MB caps are everywhere. SqueezeVid ships presets for each: pick one, or type any number of megabytes.
Frequently asked
- How do I reduce a video’s file size without losing quality?
- Strictly, any re-encode trades some quality, but most videos carry far more bitrate than their content needs, so the loss is often invisible. The key is matching the bitrate to the content and stepping resolution down when the budget is tight, which is exactly the planning SqueezeVid automates.
- What’s the best format for small video files?
- For compatibility, MP4 with H.264 video and AAC audio: it plays on effectively every device and platform. Newer codecs like AV1 compress better but still hit playback and upload-form compatibility issues; when the goal is “send this anywhere”, H.264 remains the right answer.
- Why trust a browser tool with no upload over a cloud compressor?
- Two reasons: time and privacy. Uploading a 1 GB file to a cloud compressor takes minutes before work even starts; local compression starts instantly and uses your own hardware encoder. And a file that never leaves your device can’t be retained, scanned or leaked by anyone’s server.