Video · MOV to MP4
MOV to MP4, without re-encoding.
Most iPhone and camera MOV files already hold H.264 or HEVC video. This copies those streams into an MP4 in seconds, with no quality loss, on your device. Your file is not uploaded.
How to convert a MOV to MP4
- Choose the MOV file. The tool reads its track list (video, audio, and any camera metadata tracks) and shows each one with what will happen to it.
- Leave Method on Auto. If the video is H.264 or HEVC and the audio is AAC, everything is copied and the job takes seconds even for a large clip.
- Press Convert to MP4, then download the result. A preview player appears so you can check it plays.
Why MOV and MP4 are so close
MP4 was derived from Apple's QuickTime file format, so the two share the same box structure. An iPhone MOV is usually H.264 or HEVC video with AAC audio, which MP4 is happy to hold. Converting is therefore a matter of re-wrapping the same compressed data, not recompressing it. That is why the picture is bit-for-bit what the camera recorded, and why a 1 GB MOV becomes a 1 GB MP4 rather than something smaller.
The tool tags copied HEVC as hvc1, the code Apple players expect inside MP4. Without that tag some Apple software refuses an otherwise valid HEVC MP4.
iPhone clips: HDR, Live Photos and data tracks
Recent iPhones record HDR video as 10-bit HEVC. Copying keeps that colour data exactly. If you force a re-encode to H.264 the tool must convert to 8-bit, and HDR footage can look flat or washed out afterwards because the colour range is not tone-mapped; the tool warns you when it detects 10-bit input. For HDR, remux and keep HEVC.
Phone MOV files often carry extra data tracks (timecode, motion or camera metadata, and the second stream of a Live Photo). MP4 players ignore them and the MP4 muxer cannot store most of them, so they are left out. The result table lists every track dropped. Your video and sound are never affected by this. Portrait clips keep their rotation flag when copied.
When it has to re-encode
Some MOV files do not fit MP4: ProRes video (common from pro cameras and some iPhones in ProRes mode), uncompressed PCM audio, or Motion JPEG. For those the tool re-encodes the offending track to H.264 or AAC. ProRes is enormous and the in-browser encoder is slow: in our own test runs a 1080p H.264 encode in this WebAssembly build ran at roughly 2 frames per second, so a minute of 30 fps video could take around 15 minutes. If your clip is ProRes, pick the smaller-size option or use desktop software for long footage. Remux-only mode refuses with a clear message instead of silently re-encoding.
Worked example
A 38-second iPhone clip, 1920x1080, HEVC at about 17 Mbps with AAC stereo, is about 80 MB as a MOV. In Auto mode both tracks are marked Copied, the two metadata tracks are marked Left out, and the MP4 is a few kilobytes larger or smaller than the original, because only the wrapper changed.
Common mistakes
- Expecting a smaller file. A remux changes the wrapper, not the compression. To shrink it use the video compressor.
- Converting HDR video to H.264 and then wondering why it looks dull. Keep HEVC.
- Choosing Remux only for a ProRes file. It will stop with an explanation; switch to Auto.
- Renaming .mov to .mp4. Sometimes works because the containers are close, but the box layout and codec tags can differ, and some players still reject it.
Your file never leaves your browser
This page does not contain a file upload to any server. The converter runs in an isolated frame with a content security policy that blocks all network connections except to local blob and data URLs, and it has no analytics or ads inside it. The file you choose is handed to FFmpeg, compiled to WebAssembly, which reads it directly from your disk and writes the result into your browser's memory; the download is created locally. You can confirm by opening your browser's network panel while converting, or by switching to airplane mode after the engine has loaded.
Limits and what this does not do
- One file at a time, up to 2 GB. Above 500 MB the output is built in memory, so a low-memory device may stop with an out-of-memory message; nothing on disk is changed either way.
- It does not edit, trim, stabilise or colour-correct. Use the trimmer for cuts.
- It cannot open DRM-protected or encrypted video.
- It does not tone-map HDR to SDR.
Common mix-ups
-
Often assumedA .mov file plays in any modern browser.
What the source saysMDN lists QuickTime (MOV) as supported only in older versions of Safari plus browsers that had the QuickTime plugin, while MP4 is listed for all browsers. That gap is why iPhone clips are often wrapped as MP4. [1]
-
Often assumedMOV and MP4 differ so much that the video must be re-encoded.
What the source saysMDN describes both as containers that wrap streams, and lists H.264 (AVC) among the video codecs MP4 supports. When the video inside a MOV is H.264, it can be wrapped in an MP4 as it is. [1]
Checked against these sources on .
Frequently asked questions
Is converting MOV to MP4 lossless?
Yes when the tool reports every track as Copied. The compressed video and audio data is moved into the MP4 container unchanged. If a track is marked Re-encoded, that track loses a small amount of quality; the result table shows which.
Why is my MP4 the same size as the MOV?
Because nothing was recompressed. A remux only swaps the wrapper, so the size stays within a few kilobytes. Use a compressor if you need a smaller file.
Will the MP4 play on Windows or Android?
H.264 plays almost everywhere. HEVC (the iPhone default) needs a hardware decoder or the HEVC extension on some Windows PCs and older Android phones. If you need maximum compatibility, choose Always re-encode, accepting a slower job and some quality cost.
Does it keep the rotation of portrait videos?
Yes when copying. The rotation flag travels with the video track. When a re-encode happens FFmpeg applies the rotation to the pixels.
What happens to the extra tracks in an iPhone MOV?
Data tracks such as timecode and Live Photo metadata are left out because MP4 cannot store them. The result table lists each one. The video and audio are unaffected.
Why did Remux only refuse my file?
One of its tracks (for example ProRes video or PCM audio) cannot be stored in MP4 as it is. Switch Method to Auto and that track is re-encoded.
Is the file uploaded anywhere?
No. It is read and processed on your device by FFmpeg running as WebAssembly in a sandboxed frame without network access. The only download is the converter engine itself, which happens after you pick a file.
How big a file can it handle?
Up to 2 GB, with a warning above 500 MB. The practical limit is your browser tab memory, because the result is assembled in memory before you save it.
Sources
Last checked
- Apple QuickTime File Format specification — the MOV atom structure that MP4 was derived from
- FFmpeg formats documentation — the MP4, Matroska, WebM and Ogg muxers and their options (movflags faststart)
- FFmpeg command-line documentation — stream selection with -map and stream copy with -c copy
- MDN: video codecs used on the web — H.264, HEVC, VP8, VP9, AV1 and MPEG-4 Part 2 support and licensing notes
- ffmpeg.wasm project — FFmpeg compiled to WebAssembly, the engine this page runs in your browser
- Emscripten file system API — WORKERFS, which lets the converter read your file without copying it into memory first
Runs entirely in your browser. Your file is read on your device and is never uploaded.