100% on-device
Compress a MOV in your browser
The .mov files an iPhone, a Mac or an editor produces are the biggest files most people ever have to send. This is where they shrink the most — on your own device, with no upload.
How it works
- Drop your .mov. QuickTime files from iPhone, Final Cut, Premiere or OBS all read the same way.
- Name a size. Email 25 MB · WhatsApp 16 MB · Discord 10 MB are one tap, or type your own limit and the tool solves the bitrate that lands under it.
- Download an MP4. Same footage, H.264 — the format every phone, browser and chat app plays.
In our own test, an 81-second 798 MB .mov came out at 23.6 MB — 97% smaller — and that is typical for a .mov straight out of an editor.
Intermediate codecs are enormous by design, because editing is not delivery
ProRes, DNxHR and the camera-native formats behind most .mov files encode every frame whole, with no reference to its neighbours. That is deliberate: an editor can cut to any frame and decode it without reconstructing a chain of predictions, so scrubbing and rendering stay responsive. A delivery codec does the opposite, describing most frames as differences from the ones around them. The gap between those two ideas is the file size.
It also means the first encode to H.264 is barely a re-encode at all - nothing has been thrown away yet, so the reduction is unusually large and unusually cheap in visible quality. Check what you have first, though: .mov is only a container, and a .mov that already holds H.264 has had that saving taken.
A .mov from an iPhone is not the same problem as one from an edit suite
An iPhone records HEVC, a modern delivery codec that is already efficient; those files are large because they are 4K, long, or both. Converting HEVC to H.264 at matched quality tends to need more bits rather than fewer, so any saving comes entirely from naming a smaller size - from lowering the bitrate and the resolution, not from the change of codec.
Two things do not survive the encode. H.264 has no alpha channel, so a ProRes 4444 export with transparency flattens against a background instead of keeping it, and timecode tracks go the same way. If the .mov is an intermediate you still have to edit, keep it and treat the MP4 as the copy you send.
Questions
Is my video really not uploaded?
Yes — and not as a policy, as a fact of how it is built. There is no upload endpoint: the file is read straight into this browser tab and compressed by code running on your own machine. You can watch the Network tab while it works, or pull your Wi-Fi out mid-compression and it will still finish. Nothing is stored, nothing is queued, and there is no account.
Why is my .mov so enormous?
Because it is usually barely compressed at all. A .mov out of Final Cut or Premiere is often ProRes — an editing format that deliberately keeps quality over size and can run near 80 megabits per second, which is where an 800 MB file for eighty seconds of video comes from. It was never meant to be sent anywhere; it was meant to be edited. Re-encoding it to H.264 typically takes 90–97% of the file away with no visible difference on a phone or a laptop.
Will the result still play on my iPhone and Mac?
Yes — better than the original does elsewhere. You get an MP4 with H.264 video and AAC audio, which is the most widely supported combination there is: iPhone, Mac, Android, Windows, every browser, and every chat app. A .mov that only opens in QuickTime is exactly the problem this solves.
Does it get a .mov from an iPhone (HEVC)?
Yes. iPhones record HEVC (H.265) inside a .mov container, and the engine decodes it and re-encodes to H.264. One quirk you may notice: your browser sometimes cannot decode HEVC well enough to report the video's dimensions, so the tool shows the duration but not the resolution. The compression itself is unaffected — that work is done by FFmpeg, not by the browser.
Will it fit exactly under my limit?
Yes. The size you type is a hard ceiling: the bitrate is solved from your byte budget and the clip's duration, and if the encoder overshoots the tool rescales and re-encodes rather than missing the cap.
Other formats
The same workbench handles all of them — pick a tab above, or start from its own page: