Make a video small enough to send, with no watermark, no signup and no 20 MB wall. It runs on our server, so your phone does not have to.
Drag & drop a video or click to browse
MP4, MOV, AVI, MKV, WEBM and anything else ffmpeg reads — up to 500 MB and 30 minutes
Upload a video and get a smaller MP4 back. The work is done with ffmpeg and x264 on our server rather than in your browser, because a real encode is minutes of sustained CPU and no phone is going to do that quietly.
A compressor cannot always help. Compression works by spending fewer bits on detail you are unlikely to notice — so if whatever encoded your file last already did that, there is nothing left to take. Measured on our own server: a clip that had already been through an efficient encoder came back at 98.3% of its original size, and re-encoding it at a higher quality setting made it 18% larger. Most tools will hand that back and call it compressed. This one tells you it could not help and gives you your original file instead, because a 1.7% saving reported as a success is a claim you have no way to check.
In order of how much they matter:
| Lever | Effect | Worth knowing |
|---|---|---|
| Frame size | Very large | Halving the height removes three quarters of the pixels. 1080p to 720p is usually invisible on a phone. |
| Quality setting | Large | Measured on a 63 MB minute of 1080p: balanced took it to 54% of the source, smallest to 26%. |
| Audio | Small | Re-encoded to 128 kbps AAC, which is transparent for speech and fine for music. Rarely the problem. |
| Length | Proportional | Half the video is half the file. If you only need part of it, trim first — that beats any setting here. |
On four pinned cores, a minute of 1080p30 encodes in roughly 18 to 20 seconds — about three times faster than real time. A ten-minute video is therefore around three minutes of work, plus however long the upload takes. The progress bar is read from ffmpeg itself, so it reflects the encode rather than a timer.
Free use is one file a day, up to 100 MB and 10 minutes. Beyond that a credit pack raises it to 500 MB and 30 minutes per file. The 500 MB is the largest body the server accepts; the 30 minutes is set from how long a job may hold its slot before the queue assumes it has died, so a legitimate encode can never be cut off half way. Your upload is deleted the moment the encode finishes, and the result six hours later.
It depends entirely on how your file was encoded, and any tool that gives you a single number before looking at it is guessing. Measured here on a 63 MB minute of 1080p: the balanced setting brought it under half, and the smallest setting brought it to about a quarter. A video straight off a phone or a camera usually has a lot to give, because those encoders are tuned for speed rather than size. A file that has already been through YouTube, WhatsApp or another compressor has much less, and sometimes nothing at all.
Because it was already efficiently encoded, and that is a real answer rather than a failure. Compression works by spending fewer bits on detail you are unlikely to notice; if a previous encoder already did that, there is nothing left to take. When the result comes out no smaller than what you uploaded, this page says so and hands back your original file rather than a re-encode that is the same size and slightly worse. If you genuinely need it smaller at that point, lowering the resolution is the lever that still works.
Yes. Every setting here re-encodes the video, and re-encoding always costs something — there is no lossless way to make an H.264 file meaningfully smaller. The question is whether you can see it. At the balanced setting most people cannot on normal viewing; at the smallest setting you will see it on detailed or fast-moving footage, which is the trade you are choosing. Keep your original if it matters: the file you get back is a copy, and nothing here changes the one you uploaded.
Often, yes, and it is the most effective thing on this page. Quality settings shave bits off each frame; halving the frame height removes three quarters of the pixels. If the video is going to be watched on a phone, in a chat app, or in a small embed, 720p is usually indistinguishable from 1080p and much smaller. The resolution control never enlarges anything — asking a 720p file for 1080p leaves it at 720p.
Upload anything ffmpeg reads, which in practice means MP4, MOV, AVI, MKV, WEBM, FLV, WMV and most things a camera or a screen recorder produces. You always get back MP4 with H.264 video and AAC audio, because that is the file that plays everywhere without explanation. If you need a different container or codec, that is a conversion rather than a compression and it is a different job.
No to all three. The file you download has nothing added to it, you do not need an account, and the limit is a real technical limit rather than a sales tactic: 500 MB and 30 minutes per file, with the free allowance at 100 MB and 10 minutes. The reason most compressors put a wall at 10 or 20 MB is that they want you to pay to pass it; the reason there is a wall here at all is that the encode has to run on a real server with other people's work queued behind it.
About a third of the video's own length, plus the upload. Measured on our server, a minute of 1080p takes roughly 18 to 20 seconds on four pinned cores, so a ten-minute video is around three minutes of encoding. The page shows a live progress bar read from ffmpeg itself rather than an animation, and if something is queued ahead of you it tells you how many.
The upload is deleted as soon as the encode finishes, and the compressed file is deleted six hours later — that window exists only so the download link still works if you close the tab and come back. Nothing is kept after that, nothing is looked at, and nothing is passed to anyone else. If you would rather not upload a video at all, that is a fair position, and for trimming or converting there are tools on kliptools.com that run entirely in your browser.