To convert MOV to MP4, first check which codecs are inside the MOV. If the video is H.264 or HEVC with AAC audio (as it is in most iPhone and camera clips), you can simply remux it into an MP4. That takes seconds and loses no quality. If it holds ProRes, DNxHD, uncompressed video or PCM audio, you have to re-encode to an MP4-friendly codec such as H.264 or HEVC, ideally with a constant quality setting.
This guide explains why MOV and MP4 are so closely related, how to tell which route you need, and the exact settings for each one. It also covers the snags that catch people out, such as HEVC files that won't play on Apple devices and timecode tracks that make the conversion fail.
MOV and MP4: close relatives
MOV is Apple's QuickTime File Format. MP4 (MPEG-4 Part 14) was standardised from the ISO Base Media File Format, which was itself based on QuickTime. Both use the same "atom" or "box" structure, so they are close cousins. They are not the same, though. MOV can carry a much wider range of codecs, including Apple ProRes, along with timecode tracks and other professional extras. MP4 is the format nearly every phone, browser, smart TV, social platform and video editor can open.
Keep in mind that the file extension only names the container. Whether a conversion is quick and lossless or slow and lossy depends on the codecs inside it. If that distinction is new to you, our guide to codecs versus containers explains it in a few minutes.
Step 1: find out what is inside the MOV
Open the file in a media info tool, or run ffprobe -hide_banner input.mov, and read the stream list. Look for these details:
- Video codec - h264, hevc, prores, dnxhd, mjpeg, rawvideo and so on.
- Audio codec - aac, alac, pcm_s16le, pcm_s24le and similar.
- Extra streams - timecode (tmcd), metadata or a second audio track.
Then use this table to choose a route:
| What is in the MOV | Typical source | Best route to MP4 |
|---|---|---|
| H.264 + AAC | Older iPhones, "Most Compatible" mode, many cameras, screen recordings | Remux (stream copy) |
| HEVC + AAC | iPhones set to "High Efficiency", recent cameras | Remux, adding the hvc1 tag |
| Apple ProRes | Editing exports, recent iPhone Pro models, Atomos recorders | Re-encode to H.264 or HEVC |
| DNxHD/DNxHR, MJPEG, uncompressed | Editing intermediates, older cameras | Re-encode |
| Any video + PCM audio | Cameras, audio-first exports | Copy the video, convert the audio to AAC |
Route A: remux without re-encoding
When the codecs are already MP4-compatible, a remux copies the compressed streams into a new container byte for byte. Quality is identical and speed is limited only by your disk:
ffmpeg -i input.mov -c copy -movflags +faststart output.mp4
The +faststart flag moves the index (the "moov" atom) to the start of the file, so the video can start playing in a browser before it has fully downloaded.
HEVC files and the hvc1 tag
FFmpeg labels HEVC in MP4 as hev1 by default. Apple's players (QuickTime, Safari, iOS) generally expect hvc1 and may refuse to play a hev1 file even though the video data is fine. Add the tag when you copy:
ffmpeg -i input.mov -c copy -tag:v hvc1 -movflags +faststart output.mp4
When a remux fails
Two errors come up often. A MOV with a timecode track can fail with "codec not currently supported in container" if you used -map 0 to copy every stream. In that case, map just the video and audio (-map 0:v -map 0:a). An unsupported codec, such as ProRes, produces the same error, and the only fix is Route B.
Route B: re-encode to H.264 or HEVC
ProRes and other editing codecs are built for quality and fast editing, not small files. A ProRes 422 clip can be several times larger than an H.264 version that looks the same on screen. For MP4 delivery, re-encode with a constant quality setting so the encoder spends bits only where the picture needs them:
ffmpeg -i input.mov -c:v libx264 -crf 20 -preset slow -pix_fmt yuv420p -c:a aac -b:a 192k -movflags +faststart output.mp4
What each part does:
-crf 20sets constant quality. Lower values mean higher quality and bigger files. For x264, values from about 18 to 23 suit most uses. Our guide to what CRF means covers this in detail.-preset slowtrades encoding speed for better compression at the same quality.-pix_fmt yuv420pmatters for ProRes sources, which are 4:2:2 or 4:4:4. Most phones, browsers and TVs only decode 8-bit 4:2:0 H.264, so without this flag you may get a High 4:2:2 file that many devices won't play.-c:a aac -b:a 192kconverts PCM or ALAC audio to AAC, which every MP4 player supports.
For smaller files, use HEVC: -c:v libx265 -crf 24 -tag:v hvc1. HEVC typically needs noticeably less bitrate than H.264 for similar quality, but it encodes more slowly and some older devices can't decode it. Our H.264 vs H.265 comparison can help you choose.
Video fine, audio not
Some camera MOVs hold H.264 video with PCM audio. You don't have to re-encode the picture. Copy the video and convert only the audio: ffmpeg -i input.mov -c:v copy -c:a aac -b:a 192k output.mp4. FFmpeg can write PCM into MP4, but many players and editors won't play it, so AAC is the safe choice.
Things to check after converting
- HDR and Dolby Vision. iPhone HDR footage is HEVC with HLG and, on recent models, Dolby Vision metadata. A plain remux keeps the HEVC stream intact, but how much Dolby Vision metadata survives depends on the tool and its version. Test playback on your target device.
- Rotation. Phones often store rotation as metadata rather than rotating the pixels. Remuxing keeps that flag. Re-encoding with FFmpeg applies the rotation automatically by default.
- Variable frame rate. Phone recordings are often variable frame rate. That is fine for playback, but some editors handle it poorly. Converting to a constant frame rate during the re-encode solves this.
- Metadata. Creation date and location tags may not all transfer. Add
-map_metadata 0to copy global metadata if you need it.
Which route should you choose?
If the MOV already holds H.264 or HEVC, remux it. You get a perfect copy in seconds, and re-encoding would only cost quality and time. Re-encode only when the codec isn't supported in MP4, when the file is too big, or when the target device needs a different profile or pixel format. If you have a whole folder of mixed clips, see our guide to batch converting videos on Windows.
Doing it with Movie Encoder
Movie Encoder opens MOV files and shows full media info for each one: video codec, bit depth, chroma subsampling, colour and HDR details, audio tracks and metadata. You can see at a glance whether a file can be remuxed or needs re-encoding. Stream copy is built in. Movie Encoder also warns you about codec and container combinations that won't work, so you won't end up with a ProRes-in-MP4 error.
For files that do need re-encoding, choose H.264, HEVC or AV1 with constant quality, check the exact FFmpeg arguments in the command preview, and drag in a whole folder to convert in the batch queue. Your original MOVs are never overwritten or deleted.
Frequently asked questions
Does converting MOV to MP4 reduce quality?
Not if the MOV already contains H.264 or HEVC with AAC audio, because those streams can be copied into MP4 untouched. Quality is only affected when the video has to be re-encoded, for example from ProRes.
Why won't my converted HEVC MP4 play on my iPhone or Mac?
Apple players usually expect HEVC in MP4 to be tagged hvc1 rather than hev1. Remuxing again with the hvc1 tag normally fixes it without re-encoding.
Can I put ProRes in an MP4 file?
Not reliably. ProRes belongs in MOV, so to get an MP4 you need to re-encode to a delivery codec such as H.264 or HEVC.
