Skip to content

Compress video

  • Runs on your device
  • Works offline once loaded

Make a video small enough to send. Choose a limit like 10 MB for Discord, 16 MB for WhatsApp or 20 MB for email, and each video is encoded to fit under it. Lower the resolution or frame rate for tighter limits. Your device encoder does the work, so nothing is uploaded.

How it works

  1. Drop your videos.
  2. Pick a size limit, or choose a quality level.
  3. Download the compressed MP4 or WebM.

Why use it

  • Target size mode with common presets.
  • Resolution, frame rate and audio bitrate controls.
  • MP4 with H.264 or WebM with VP9.
  • No watermark and no length limit.

Compressing a video to fit a size limit

How the size target works

A video file is its bitrate, the amount of data per second, multiplied by its length. So when you set a limit, the compressor works out a bitrate: it takes 93 percent of the limit as a safety margin, sets aside room for the sound, and divides the rest by the length of the video. Hardware encoders do not always hit a bitrate exactly, so it checks the finished file and, if it came out too large, encodes again with a corrected bitrate, up to three passes in all.

The length of the video therefore decides the quality you can get. These are the video bitrates the compressor aims for with 128 kbps sound:

LengthLimit 10 MBLimit 25 MB
30 seconds2.5 Mbit/s6.4 Mbit/s
1 minute1.2 Mbit/s3.1 Mbit/s
2 minutes0.52 Mbit/s1.5 Mbit/s
5 minutes0.13 Mbit/s0.52 Mbit/s
Worked out with the formula the compressor uses. Removing the sound adds about 0.13 Mbit/s to every figure.

What those bitrates look like

In our tests a 10 second clip of full HD camera footage used about 3.6 Mbit/s at the Balanced setting. Squeezed to 1.5 Mbit/s with a size target, it scored exactly the same as the 720p version, and fine texture such as trees went soft. A full HD screen recording of an app needed less than 0.8 Mbit/s at every setting, because most of a screen does not change from one frame to the next.

As a rough guide for camera footage: around 3.5 Mbit/s looks like Balanced at 1080p. Near 1.5 Mbit/s, 1080p and 720p look the same, so choose 720p if the video is for phones. Well below 1 Mbit/s detail suffers whatever you choose, and cutting the video shorter with the video trimmer helps more than any setting. Screen recordings, slides and talking heads in front of a plain wall get away with much less. All the measurements are in how to compress a video.

Resolution, frame rate and sound

  • Resolution helps when the bitrate is low: fewer pixels share the same data. At 720p a video is meant for phones and small windows; keep 1080p when text on screen must stay readable.
  • Frame rate barely changes the size, since the budget is set per second. Halving 30 frames per second to 15 saved only 4 percent in our test. Lower it for slides or very small targets.
  • Sound at 128 kbps takes about 1 MB per minute. For speech, 64 kbps is plenty, and for a screen recording without narration, remove the audio and give its share to the picture.

MP4 or WebM

MP4 with H.264 plays on every phone, computer, television and messaging app, so it is the right choice for anything you send. WebM with VP9 came out about a quarter smaller than MP4 at the same quality setting in our test, with slightly lower scores, and plays in every current browser. Use it for video on a web page you control.

If something goes wrong

  • The result says it is above the target. The limit is too small for the length at this resolution. Choose 720p or 480p, remove the sound, or trim the video.
  • It is slow. Encoding runs on your own computer or phone, and it stops if the tab is closed. Our 10 second full HD clip took about 17 seconds at 1080p and 8 seconds at 720p, so a lower resolution also makes it faster.
  • The browser says it cannot do this. The compressor needs WebCodecs, the video encoders that Chrome, Edge, Safari 16.4 or newer and Firefox 130 or newer provide. Update the browser or try another one.
  • The file came back unchanged. It was already under the limit, or, with a quality setting, the original was smaller than anything the compressor could make. The original is the better file then.

How we tested. Bitrates in the table come from the compressor's own formula. Quality figures are from our video compression tests: 10 second clips at 1920 by 1080 and 30 fps, encoded with this tool in Chrome and scored with SSIM against the original frames.

Popular ways to use this tool

Questions and answers

How do I get a video under 10 MB?

Choose the 10 MB preset and add your video. The tool sets the bitrate from the length so the result fits, and retries with a lower bitrate if it lands slightly over.

Will quality drop a lot?

That depends on how much you need to shrink. Lower resolutions leave more bitrate for each pixel and often look better than a big picture at a starved bitrate.

Why does it need my browser to support WebCodecs?

It uses the hardware encoder built into your device. Current Chrome, Edge, Safari and Firefox support it.

Related guides

Video and audio6 min read

GIF vs MP4 vs WebM: the same clip in each format

We turned a camera clip and a screen recording into a GIF, an MP4 and a WebM at the same size. The GIF was up to 16 times larger and still looked worse. Here is why, and when a GIF is still the right choice.

Video and audio7 min read

How to compress a video: what each setting really does

A video's size is its bitrate times its length, and every setting works through that. We compressed two full HD clips at every setting and measured the size and quality of each result, including the usual advice to lower the resolution.

Esc