How to compress a video without wrecking the picture
Shrink an MP4, MOV or WebM by bitrate, resolution and frame rate — and know when a target file size is a better ask than a quality slider.
Updated 2026-09-21
A phone clip that looked fine in the camera roll is often too large for email, a form upload or a messaging app. Compression is not one slider. File size is bitrate times duration, so you get a smaller file by spending fewer bits per second, fewer pixels, or fewer frames — or by dropping the soundtrack if nobody needs it.
On Batonbox the Compress Video tool lets you keep about 70, 50 or 30 percent of the original size, cap the longest side, drop the frame rate, mute the audio, or aim at an exact megabyte target. Common formats stay in the browser; a few older containers go through the server encoder.
Size is bitrate, not magic
A three-minute 1080p clip at 12 Mbps is about 270 MB. The same clip at 4 Mbps is about 90 MB. Viewers on a phone rarely see the difference until you also shrink the picture or crush the shadows. Start by cutting bitrate, then resolution, then frame rate. That order keeps motion looking like the original for longer.
A hard file-size cap is useful when a site rejects anything over 25 MB or 100 MB. The encoder then spends the allowed bits across the whole duration. Short clips survive a tight cap; a twenty-minute lecture at 8 MB will look blocky no matter which tool you use.
Resolution and frame rate
Most sharing destinations display 720p or smaller. Dropping 4K to 1280 on the long side removes most of the bulk with little visible loss on a laptop. Going to 640 is for chat previews and GIFs, not a film you still want to watch.
30 fps is enough for talking heads and screen recordings. 24 fps suits cinema-like motion. 15 fps is a last resort for a tiny file. Do not raise the frame rate above the source — extra frames are invented, not recovered.
What you should not expect
Compression cannot add detail that is not in the file. A 480p source will not become a crisp 1080p export. HDR to SDR, vertical to horizontal, and burned-in subtitles are separate jobs.
If the tool has to re-encode, you pay a generation of loss. That is normal. A second pass on an already-tiny file usually looks worse than one careful pass from the original camera file.
Step by step
- 1
Pick the destination
Email and forms: start at keep 50 percent and 1280 on the long side. Chat: 854 or 640. A site with a megabyte limit: type that number as the target size.
- 2
Mute if the picture is the point
Screen recordings without speech, or clips you will add a new soundtrack to later, can drop the audio track and save a useful chunk.
- 3
Watch the estimate
The workbench shows the original size next to an estimate before you run. If the estimate is still too large, drop resolution before you drop quality to low.
- 4
Play the result
Check a face in close-up and a fast pan. Blockiness on a still face means bitrate is too low; stutter on a pan means the frame rate is too low.
Questions
- Will compressing a video upload it?
- MP4, MOV and WebM usually stay in your browser tab. Older containers such as AVI or WMV, or a request the browser cannot write, go to the server encoder. The tool tells you which path it used.
- Why is the file still large after I chose 30 percent?
- The encoder still has to store every second of picture. A long 4K clip at 30 percent can still be hundreds of megabytes. Cap the longest side or set a target size.
- Is WebM smaller than MP4?
- Sometimes, at the same visual quality. MP4 plays in more apps and editors. Keep MP4 unless you know the destination wants WebM.