Compress Video to Fit

Why your video is too big, and what actually shrinks it

A one-minute clip from a recent phone can easily be 150 MB. The same minute, compressed sensibly, can look almost identical at 12 MB. Understanding where that difference comes from makes it much easier to get the result you want.

The four things that determine file size

Bitrate is the amount of data used per second of video, and it is by far the biggest factor. Phones record at generous bitrates — often 40 to 100 megabits per second — because storage is cheap and they would rather not throw away detail during capture. For sending a clip to a friend, a fraction of that is enough.

Resolution is the pixel dimensions. 4K has four times the pixels of 1080p, and needs roughly four times the data to look equally sharp. Dropping a 4K clip to 1080p is often the single most effective size reduction available, and on a phone screen nobody will notice.

Frame rate matters less than people expect. Halving 60fps to 30fps saves considerably less than half the size, because consecutive frames are very similar and modern codecs already exploit that.

Duration is the one nobody wants to hear. If your video is well over the limit, trimming the boring first ten seconds often does more than any amount of clever encoding.

How this tool decides

Most compressors ask you to choose a quality percentage or a bitrate, which requires knowing what those numbers mean for your particular clip. This one works the other way round.

You tell it the size you need to hit. It reads the video's duration, subtracts what the audio track will need, divides the remaining budget across the running time, and encodes at that bitrate. If the resulting bitrate would be too low for the video's resolution to still look acceptable, it reduces the resolution rather than producing something blocky — a sharp 720p clip beats a smeared 1080p one every time.

The result lands close to your target rather than exactly on it, because compression is not perfectly predictable — a static talking head compresses far better than a handheld shot of moving trees. The tool aims slightly under the limit to leave room for that variation.

Common platform limits

These change from time to time and vary by region and account tier, so treat them as a guide rather than gospel. When in doubt, aim a little under.

Doing the work in your browser: the honest trade-off

This compressor runs a complete video encoder inside the page. That has one large advantage and one real cost, and it is worth being straight about both.

The advantage is that your video never leaves your computer. There is no upload, no server storing your footage, no account, and no size cap imposed by somebody else's bandwidth bill. For anything personal — family video, a clip from a private event, footage for work under an NDA — that difference is the entire point.

The cost is speed. A browser cannot use your graphics card for video encoding the way a desktop application can, so it works on the processor alone and is several times slower than a native program. A two-minute clip typically takes one to three minutes.

In practice the maths still favours doing it here. An online compressor has to upload your whole file first, compress it on a server, then send it back. On a typical home connection, uploading a 200 MB video alone takes several minutes — before any compression starts. Doing the work locally is frequently the faster route in wall-clock time, and always the more private one.

Where it genuinely does not make sense is very large files. Compression needs roughly two to three times the file size available in memory, so a 2 GB recording will exhaust the browser and fail. For those, desktop software is the right tool, and this page will tell you so rather than letting you wait twenty minutes for a crash.