Why Convert MOV to MP4?
iPhone Video Compatibility Guide

Why iPhones Use MOV

The story begins in 1991 when Apple released QuickTime — a multimedia framework designed to handle video, audio, and animation on early Macintosh computers. QuickTime introduced the .mov container format, which became the standard way Apple devices stored and played back video for the next three decades.

When Apple launched the original iPhone in 2007, it naturally used QuickTime's MOV container for video recording. Every iPhone since has continued this tradition. The MOV format was later formalized as the basis for the MPEG-4 Part 12 standard (ISO 14496-12), which means MOV and MP4 are actually closely related — MP4 is essentially a subset of the QuickTime file format specification.

The codec inside the container matters more than the container itself. Early iPhones recorded using H.264 (AVC) video with AAC audio. This combination worked fairly well across devices because H.264 decoders were widespread. The compatibility situation changed significantly in September 2017.

With iOS 11 and the iPhone 7, Apple switched the default video codec to HEVC (H.265). HEVC offers roughly 40–50% better compression than H.264 at the same visual quality — a critical advantage for 4K video, which would otherwise consume enormous amounts of storage. A 1-minute 4K clip at 30fps takes about 170 MB with HEVC compared to roughly 350 MB with H.264.

The problem is that HEVC is covered by complex patent licensing from multiple patent pools (MPEG-LA, HEVC Advance, Velos Media), and many software vendors — including Microsoft — chose not to bundle HEVC decoders by default. So while your iPhone happily records HEVC/MOV video, the receiving device may not be able to decode it.

Where MOV Files Do Not Work

MOV compatibility issues fall into two categories: container problems (the device or platform does not recognize the .mov file at all) and codec problems (the device recognizes MOV but lacks the HEVC decoder to play the video inside). Here is a breakdown of where you will encounter issues.

The pattern is clear: Apple devices handle MOV natively, but everything else has varying degrees of trouble. The HEVC codec compounds the issue — even platforms that accept the MOV container may not be able to decode the video stream inside it.

The Rename Trick — .mov to .mp4

Because MOV and MP4 share the same underlying MPEG-4 container specification, you might wonder: can I just rename video.mov to video.mp4? The answer is sometimes yes, sometimes no, and it depends entirely on the codecs inside the file.

When Renaming Works

If your MOV file contains H.264 video + AAC audio, renaming the file extension from .mov to .mp4 will work in most players. Both container formats use the same ISO Base Media File Format structure, and the internal codec streams are identical to what an MP4 file would contain. The player reads the file, finds H.264/AAC streams, and plays them normally regardless of the extension.

You can check what codecs a MOV file contains using FFmpeg's probe tool:

ffprobe -v error -show_entries stream=codec_name input.mov

If the output shows h264 and aac, renaming is safe. If it shows hevc, prores, or any other codec, renaming will likely not solve your playback problem.

When Renaming Fails

Renaming fails in the following cases:

• HEVC (H.265) video — The file extension changes to .mp4, but the video stream is still HEVC. Any device that lacked the HEVC decoder before will still lack it after the rename. The fundamental problem was never the container — it was the codec.
• ProRes video — iPhone 13 Pro and later models can record in ProRes mode. ProRes is a professional editing codec that most consumer devices cannot decode at all, regardless of the container format.
• LPCM audio — Some MOV files contain uncompressed PCM audio instead of AAC. While many MP4 players can handle this, some strict MP4 parsers reject it because LPCM is not a standard audio codec for the MP4 container.
• QuickTime-specific metadata — Some MOV files contain QuickTime-specific atom structures that are valid in MOV but technically invalid in MP4. Most modern players are lenient about this, but some strict validators will flag the file as corrupt.

When Re-encoding Is Needed

Re-encoding means decoding the original video stream and then encoding it again using a different codec. This is a lossy process — each generation of encoding introduces some compression artifacts. However, with modern encoders and appropriate settings, the quality loss is imperceptible.

You need re-encoding when:

• The MOV contains HEVC and the target device lacks HEVC support — This is the most common scenario. You re-encode from HEVC to H.264, which is universally supported.
• The MOV contains ProRes — ProRes files are massive (up to 6 GB per minute for ProRes 422 HQ at 4K). Re-encoding to H.264 at CRF 18–20 reduces file size by 95% or more while preserving excellent visual quality.
• You need to change resolution or frame rate — If you want to downscale 4K to 1080p or reduce 60fps to 30fps, re-encoding is required.

The standard approach is to re-encode with libx264 (the open-source H.264 encoder) at CRF 18–20 for near-lossless quality, or CRF 23 for a good balance of quality and file size. CRF stands for Constant Rate Factor — lower values mean higher quality and larger files.

Lossless Stream Copy

If your MOV file already contains H.264 video and AAC audio, there is a much better option than re-encoding: stream copy (also called remuxing). This operation extracts the video and audio streams from the MOV container and places them into an MP4 container without decoding or re-encoding anything. The result is a bit-identical copy of the original video in a universally compatible MP4 wrapper.

The FFmpeg command for lossless stream copy is:

ffmpeg -i input.mov -c copy -movflags +faststart output.mp4

This command does three things:

• -c copy — Copies both video and audio streams without re-encoding. Zero quality loss.
• -movflags +faststart — Moves the MP4 metadata (moov atom) to the beginning of the file, enabling instant playback in web browsers and streaming players. Without this flag, the player must download the entire file before it can start playing.
• The entire operation takes under 5 seconds regardless of video length, because no encoding is performed — it is simply rewriting the container structure around the existing streams.

Stream copy is the ideal solution when possible because it is instant, lossless, and produces a file that is byte-for-byte identical in video quality to the original. The output file will be approximately the same size as the input (a few kilobytes smaller due to the simpler MP4 container header).

Optimal Settings for MOV to MP4

When stream copy is not an option and you need to re-encode, here is the full FFmpeg pipeline that produces the best results for iPhone HEVC/MOV to H.264/MP4 conversion:

ffmpeg -i input.mov \
  -codec:v libx264 -crf 23 -preset medium \
  -pix_fmt yuv420p \
  -codec:a aac -b:a 192k \
  -movflags +faststart \
  output.mp4

Here is what each parameter does:

• -codec:v libx264 — Uses the x264 encoder, the most widely compatible H.264 implementation. The output plays on virtually every device made in the last 15 years.
• -crf 23 — Constant Rate Factor of 23 is the x264 default and provides an excellent balance between quality and file size. VMAF scores typically range from 93 to 96, meaning the visual quality is indistinguishable from the original for most viewers. Lower values (18–20) produce higher quality at larger file sizes.
• -preset medium — Controls encoding speed vs. compression efficiency. medium is a good default. Use slow or slower if you want smaller files (at the cost of 2–5x longer encoding time). Use fast or veryfast if encoding speed matters more than file size.
• -pix_fmt yuv420p — Forces 4:2:0 chroma subsampling, which is required for playback on most devices. iPhone HEVC can record in 4:2:0 or 4:2:2 depending on the mode; some players choke on 4:2:2 H.264.
• -codec:a aac -b:a 192k — Re-encodes audio to AAC at 192 kbps, which is transparent quality for stereo audio. iPhone video typically records at 44.1 or 48 kHz stereo, so 192k is more than sufficient.
• -movflags +faststart — Enables instant web playback by relocating the moov atom to the file start.

Encoding Speed Estimate

Re-encoding time depends on your CPU, the video resolution, and the preset. As a rough guide for a modern desktop CPU (Intel i7 / AMD Ryzen 7):

A 5-minute 4K 30fps iPhone video with -preset medium takes approximately 10 minutes to re-encode. Stream copy, by contrast, finishes the same file in under 5 seconds.

Change iPhone Camera Settings

If you frequently share videos with Windows and Android users, you can configure your iPhone to record in H.264 instead of HEVC. This makes the resulting MOV files compatible with virtually all devices (and trivially remuxable to MP4 via stream copy).

1. Open Settings on your iPhone.
2. Tap Camera.
3. Tap Formats.
4. Select "Most Compatible" instead of "High Efficiency".

This changes the video codec from HEVC to H.264 and the photo format from HEIC to JPEG. The trade-off is significant: H.264 files are roughly twice the size of HEVC files. A 1-minute 4K video at 30fps goes from about 170 MB (HEVC) to about 350 MB (H.264). If you record a lot of video, this adds up quickly.

An alternative approach is to keep "High Efficiency" enabled for the storage savings and simply convert to MP4 when you need to share. This gives you the best of both worlds: compact HEVC recordings on your phone and universally compatible MP4 files when you share. Convertio's online converter makes this easy — upload the MOV, download the MP4, done.