MOV to MP4 Converter
Convert QuickTime MOV videos into MP4 files that play everywhere. iPhone and camera footage is remuxed without re-encoding, and editing formats like ProRes are re-encoded automatically. Free, private, and nothing leaves your browser.
Runs on ffmpeg.wasm inside your browser. Nothing is uploaded, no account, no watermark.
How the MOV to MP4 converter works
MOV is Apple's QuickTime container, and MP4 is its more universal cousin. Most MOV files from iPhones, cameras and editing apps already hold H.264 or HEVC video with AAC audio, exactly what an MP4 holds. For those files this converter remuxes: the streams are copied bit-for-bit into an MP4 wrapper with no re-encoding, so the result is lossless and finishes in seconds.
Files from professional editing tools sometimes use codecs like ProRes that MP4 players, browsers and TVs cannot handle. When a plain remux is not possible, the converter automatically re-encodes the video to H.264 at CRF 23 and the audio to AAC at 192k, producing an MP4 that plays virtually anywhere. Once it finishes, the result panel names the path it took, so you know whether the file was copied or re-encoded.
The conversion runs locally in your browser with ffmpeg.wasm, a WebAssembly build of FFmpeg. The engine (about 32MB) downloads once and is cached afterwards. Nothing is uploaded: a useful property when the footage is large or private.
Tips for best results
| Situation | What to do |
|---|---|
| MOV from an iPhone, iPad or most cameras | Nothing: these already use H.264/HEVC + AAC, so the remux path converts them losslessly in seconds |
| ProRes or other editing-codec MOV | Expect the re-encode path; the output is far smaller and plays everywhere |
| MOV will not play on Windows or Android | Convert it: the MP4 output works across devices and browsers |
| File much larger than 200MB | Remuxing large files is fine, but re-encoding them is slow on low-end devices; keep the tab in the foreground |
Frequently asked questions
Is MOV to MP4 conversion lossless?
Yes, when the stream-copy remux works, which covers most iPhone, iPad and camera MOVs because they already contain H.264 or HEVC video with AAC audio. The streams are copied unchanged into the MP4 container. Editing-codec files like ProRes are re-encoded to H.264 + AAC at CRF 23 instead, and the result panel tells you which path was used.
Why does one MOV convert in seconds and another take minutes?
A remux only rewrites the container around the existing streams, so even a long clip finishes in a few seconds. A re-encode has to decode and recompress every frame using your device's CPU, so expect it to run for about the length of the video, longer on an older laptop or phone. The converter attempts the remux first and only falls back to re-encoding when the MOV holds a codec that MP4 cannot carry.
Why convert MOV to MP4 at all?
MP4 is the most widely supported video container: it plays natively on Windows, Android, smart TVs, browsers and messaging apps, while MOV playback outside the Apple ecosystem is hit and miss. Converting also tends to make sharing and uploading smoother.
Is there a file size limit?
The converter has no fixed cap, but everything happens in browser memory, so a MOV much over 2GB will run out of room. Anything up to a few hundred megabytes remuxes comfortably. Larger camera files usually remux fine too, but if they need the re-encode path on a low-powered device, expect a long wait and keep the tab in the foreground.
Is my MOV file uploaded to a server?
No. The whole conversion happens in your browser using ffmpeg.wasm, a WebAssembly build of FFmpeg. The engine is fetched once and cached, so the page keeps working offline afterwards, and the MOV itself is never sent anywhere.