Preset · 25 MB target
Compress a video to 25 MB
25 MB is the cap on Gmail and Outlook attachments and Discord's classic Nitro limit. It holds roughly a minute of full-HD video, or about twenty minutes if you accept a small, soft picture. Drop your video below and it's compressed to just under 25 MB on your own device — no upload, no account, no watermark.
How long is 25 MB of video?
There's no single answer, because it's a trade between length and picture quality: the longer the clip, the less detail fits in the same 25 MB. The table below is what this compressor actually produces from a typical phone recording — full HD, 30 frames a second, with sound.
| Video length | What 25 MB gives you |
|---|---|
| 30 seconds | Full HD — hard to tell from the original |
| 1 minute | Full HD, still sharp |
| 5 minutes | Clearly reduced — fine on a phone, soft on a laptop |
| 10 minutes | Small picture; watchable, but blocky on a big screen |
| 20 minutes | Heavily reduced, and the frame rate drops to keep it watchable |
Past about 20 minutes, 25 MB stops being enough for a picture worth watching. Rather than hand you mush, the compressor refuses and tells you the smallest size that would actually work for your clip. For an exact figure before you start, the bitrate calculator does the sum for your own video's length and resolution.
Why 25 MB, and what to expect
Gmail and Outlook both cap attachments at 25 MB, and Discord's Nitro Basic tier uses the same limit. Most services check the exact byte count, so a "25.1 MB" file bounces. This tool always lands under the limit: it works out exactly how much to compress so the video fits, leaves room for the audio, then checks the result and compresses again if the first pass came out a touch too big. You'll typically get a file between 22 and 25 MB — never over.
Where the quality goes is worth knowing in advance. Rather than smearing every frame equally, the compressor keeps the picture sharp and shrinks its dimensions instead — so a long video comes back clear but physically smaller, not blurry at full size. Below a certain point it also drops the frame rate. That's why the table above talks about picture size rather than a quality percentage. All of it runs locally in your browser, so a 300 MB source doesn't need a 300 MB upload before work even starts.