At a glance
| Input | MP4, MOV and other video the browser can open |
|---|---|
| Output | MP4 |
| Bitrate | 1, 2.5 or 5 Mbps |
| Optional resize | 1080p, 720p, 480p or 360p |
| Where it runs | Entirely in your browser — no file is uploaded to a server |
| Price | Free, with no account and no sign-up |
| Offline | Works with no connection after the first visit |
The three settings that actually matter
Resolution first: 1080p to 720p removes more than half the pixels and is invisible on a phone. Bitrate second — it is the direct control on file size, and the point where quality starts to break down depends entirely on how much movement the footage contains. Frame rate last: 60fps to 30fps halves the frames, which matters for gameplay and not for a talking head.
Footage with a lot of motion — sport, handheld walking shots — needs substantially more bitrate than a static interview to look the same.
Why it takes as long as it does
Every frame is decoded, resized and re-encoded on your own machine. There is no server farm doing it in parallel, which is the same reason nothing is uploaded. Hardware encoding helps where the browser exposes it; an older laptop will be noticeably slower than a recent one.
The tab has to stay open and the machine awake. Closing it stops the work.
Frequently asked questions
How small can it get?
Commonly 50–80% with no visible difference on a phone screen, mostly from dropping the resolution. Footage with heavy motion compresses less.
Why is it slow?
Every frame is re-encoded on your processor rather than on a server. That is the trade for the file never being uploaded.
Which setting should I change first?
Resolution. Going from 1080p to 720p removes more than half the pixels and is invisible on a phone.
Something wrong with this tool, or an idea for it? Tell us