About SqueezeVid
Last updated: October 15, 2026
SqueezeVid compresses a video so the file lands under a size you pick, and it does it entirely inside your browser tab. No upload, no account, no watermark, no paid tier. It is built and maintained by Damien Yvert, an independent developer.
Why it runs in your browser
Every other free video compressor works the same way: you upload the file, it waits in a queue on someone’s server, and you download the result. That design loses on its own terms. Home connections upload far slower than they download, so a 2 GB phone video can spend twenty minutes going up before any work starts — and the work itself is often the fast part.
It is also the wrong place to send a lot of video. Screen recordings carry whatever was on the screen, including email and account numbers. Family video is family video. Handing either to a free service whose business model you have not read is a decision most people would rather not make for a file-size problem.
So SqueezeVid does neither. It uses WebCodecs, the browser’s access to your machine’s own hardware video encoder, which means compression usually runs several times faster than real time and starts the moment you pick a file. There is no upload endpoint on this site — not a policy we could quietly change, but how the thing is built.
Why it hits the number instead of guessing
Most compressors give you a quality slider and let you find out afterwards whether the file fits. SqueezeVid works backwards from the limit: it computes the bitrate budget from your target and the clip’s duration, reserves room for audio and container overhead, and steps the resolution down when the bits-per-pixel budget would turn the picture to mush. Then it checks the real output size and re-encodes tighter if a pass overshot, so the download button only ever offers a file that actually fits.
The honest consequence: it cannot beat arithmetic. A tight limit divided by a long duration leaves too few bits for watchable video, and no encoder changes that. When that happens it says so and suggests trimming, a larger target, or dropping the audio track — rather than handing you a smear and calling it done.
Because the work happens on your device, your device sets the ceiling. It needs an up-to-date Chrome, Edge, Brave, Opera or Firefox, ideally on desktop; Safari’s WebCodecs support is still partial. That trade-off is the price of not uploading anything.
What it deliberately does not do
Being clear about the edges is more useful than pretending there are none. SqueezeVid does no editing — no trimming, cropping, filters, subtitles or merging. It changes a file’s size, nothing else. It always outputs MP4 with H.264 video and AAC audio, the most universally playable combination, and will not produce WebM, GIF, AV1, HEVC or audio-only files. It handles one file at a time, and there is no API and no CLI.
If you need batch processing, two-pass AV1 archival quality or fine codec control, HandBrake is free, excellent, and the right answer. If you need to cut the clip rather than shrink it, use an editor.
How the articles are written
The articles exist because the question behind most of this traffic is arithmetic, not software: people want to know what the limit actually is and why their file will not fit. Two rules govern them.
First, every platform limit carries a date, because these numbers move — Discord’s free ceiling went from 8 MB to 25 MB to 10 MB to 20 MB within a few years, and an undated figure is a figure that will quietly become wrong. Where an article states a limit, it says when it was checked.
Second, the quality figures are not written by hand. Each size-target page publishes a table of what you actually get at a given duration, and a test regenerates every row from the same planner the tool runs and fails the build if the two disagree. This is not a precaution in the abstract: those pages once advertised “clean 1080p” where the planner really produced 960×540, and six claims across three pages overstated the output before anything checked them. The prose is now forbidden from restating a bare figure, because a sentence is exactly where a number goes to stop being checkable.
That is the same instinct behind writing Gmail’s “25 MB” as ~18 MB throughout: base64 encoding inflates an attachment by about a third, so the message limit and the file limit are not the same number, and quoting the advertised one would be repeating a mistake rather than reporting a limit.
Contact
Corrections, bug reports and feature requests are all welcome. A report that names your browser, OS and the source file’s codec is worth ten that don’t. Write to damienyvert.dev@gmail.com.
For exactly what is and is not collected, see the privacy policy. The short version is that your video is never part of it.