QuickTime Movie

Atom structure and what MP4 leaves out

The shared ISOBMFF skeleton means most tools that parse MP4 can partially read MOV. The divergence lives in features MP4 never adopted. MOV supports edit lists — instructions that remap, offset, or repeat segments of a track without duplicating media data. A single edit list entry can add an initial delay, trim frames from the start, or loop a section, all without touching mdat. MP4 technically allows edit lists too, but many players ignore them, producing audio sync drift on files that depend on the feature.

Timecode tracks are another MOV-specific strength. These carry SMPTE timecode (HH:MM:SS:FF) embedded as a dedicated track type, giving NLEs frame-accurate references that survive re-wraps, partial exports, and conform workflows. Drop-frame and non-drop-frame variants are both supported. MP4 has no equivalent mechanism; timecode in MP4 workflows typically requires sidecar files or proprietary metadata.

ProRes: why MOV persists in production

The ProRes codec family is the primary reason MOV remains mandatory in professional post-production. ProRes ships in five profiles: 422 Proxy (~45 Mbps for 1080p24), 422 LT (~102 Mbps), 422 (~147 Mbps), 422 HQ (~220 Mbps), and 4444 XQ (~500 Mbps for 1080p24 with alpha). Each doubles the data rate of the tier below it, trading file size for reduced quantization error. ProRes 4444 and 4444 XQ carry full alpha channel transparency — critical for compositing and motion graphics.

A one-hour 1080p24 ProRes 422 HQ file runs approximately 100 GB. ProRes 4444 XQ at the same resolution pushes past 225 GB per hour. These sizes are intentional. ProRes prioritizes decode speed and edit performance over storage efficiency; every frame decodes independently with no inter-frame prediction, so scrubbing and random access are instantaneous.

Apple restricted ProRes encoding to MOV containers. You can remux ProRes into MKV, but most professional tools expect the MOV wrapper and may reject or misinterpret ProRes in other containers. FFmpeg added ProRes encoding support on Linux and Windows, but the output must still target a MOV container for broad NLE compatibility.

iPhone recording and the HDR problem

Modern iPhones shoot video in MOV by default, but the codec inside has changed significantly. iPhone records HEVC in MOV with 10-bit HLG HDR by default since iPhone 12; most Windows and web players silently drop the HDR metadata, shifting colors toward magenta. This happens because HLG (Hybrid Log-Gamma) tone mapping requires explicit support in the decoder and display pipeline. Windows Media Player, many browser-based players, and older versions of VLC either ignore the mdcv and coll atoms carrying the HDR signaling or apply an incorrect transfer function.

The result is footage that looks correct on Apple devices and washed-out or magenta-tinted everywhere else. Converting to SDR with a proper tone-map pass (using tools like FFmpeg's zscale filter or DaVinci Resolve's color management) fixes the color but discards the extended dynamic range. Shooting in "Most Compatible" mode on iPhone forces H.264 in an SDR color space, side-stepping the issue at the cost of larger files and no HDR.

Audio in MOV

MOV supports AAC (lossy, small files), ALAC (Apple's lossless codec), and linear PCM (uncompressed). Professional workflows lean toward PCM-in-MOV because it avoids any decode step during editing and preserves sample-accurate audio without generational loss. A stereo 48 kHz 24-bit PCM track adds roughly 500 MB per hour — negligible next to ProRes video data rates. AAC makes sense for delivery and distribution; PCM makes sense for everything before that.

Limitations

Windows support for MOV has improved but remains inconsistent. Codecs like ProRes require Apple's codec pack or third-party decoders. HEVC in MOV requires the HEVC Video Extensions from the Microsoft Store (paid on some Windows 10 installations, free on Windows 11). Web browsers cannot play MOV files containing ProRes at all; browser HEVC support varies by platform and is absent entirely in Firefox as of early 2026.

File sizes in production workflows are substantial. A feature-length film in ProRes 4444 at 4K can exceed 10 TB. This is manageable on fast NVMe storage but creates real problems for backup, transfer, and archive.

MOV lacks native support for certain codec combinations that MKV handles freely. You cannot put VP9 or AV1 video in a MOV container through any standard mechanism. Subtitle tracks in MOV are limited compared to MKV's support for ASS/SSA and other complex subtitle formats.

When to choose MOV

Use MOV when your workflow is Apple-centric or ProRes-based. Final Cut Pro, DaVinci Resolve, and Premiere Pro all handle MOV natively. If you need timecode tracks, alpha channel video, or edit lists, MOV is the correct container.

Use MP4 for web delivery, streaming, and cross-platform distribution. MP4 with H.264 or H.265 plays on virtually every device and browser.

Use MKV when you need maximum codec flexibility — multiple audio tracks in different formats, complex subtitle support, or open-source codecs like AV1 and Opus. MKV is not supported by Apple's ecosystem without third-party players, which limits its use in mixed-platform professional environments.