video/quicktime QuickTime (MOV) Common
Identifies QuickTime container files (.mov) — Apple's video format, common in professional editing and iPhone-recorded video.
What it's for
video/quicktime identifies QuickTime container files (.mov) — Apple's video container format, historically the foundation that MP4's own container design was actually based on (MP4 and MOV share significant underlying structural similarity). It remains extremely common today primarily because it's the default video format produced by iPhone camera recordings, making it something nearly every web application accepting user-uploaded video needs to handle gracefully, even if MOV isn't the format you'd choose for actual web delivery.
Format & syntax
Content-Type: video/quicktime
No parameters. Like MP4, a MOV file's actual video codec (commonly H.264 or, on newer iPhones, HEVC/H.265) matters more for playback compatibility than the container format alone — and this codec distinction is a frequent, very real source of "why won't my uploaded iPhone video play on the web" support issues.
How it's used in practice
- iPhone-recorded video uploads — by far the most common practical encounter with this MIME type today: any web application accepting video uploads from iPhone users will regularly receive
.movfiles, since it's the iPhone camera app's native recording format. - Professional video editing workflows — QuickTime/MOV remains common in professional video editing and production pipelines, particularly within Apple-centric workflows (Final Cut Pro and related tooling).
- Screen recording on macOS — macOS's built-in screen recording functionality outputs MOV files by default, making it another common source of MOV files needing to be handled by upload/processing pipelines.
- Video requiring transcoding before web delivery — because of MOV's mixed browser support (particularly with newer HEVC-encoded content), a very common practical pattern is transcoding uploaded MOV files to MP4/H.264 server-side before serving them for web playback.
Common mistakes & gotchas
- Assuming MOV plays reliably in all browsers the way MP4 does — browser support for MOV playback, especially with certain codec combinations (HEVC in particular), is meaningfully less consistent than MP4/H.264 — a common real-world gotcha for applications accepting direct video uploads that then try to play them back web-side without transcoding.
- Not transcoding uploaded iPhone video before web playback — given how common iPhone-sourced MOV uploads are, applications that don't include a transcoding step (converting to MP4/H.264 server-side) frequently run into playback issues for a meaningful share of their user-uploaded video content.
- HEVC codec compatibility varying significantly across playback contexts — newer iPhones increasingly default to HEVC (H.265) encoding even within a MOV container, and HEVC playback support varies more across browsers/devices than the more universally supported H.264, compounding MOV's general web compatibility challenges.
- Large file sizes from high-resolution/high-frame-rate iPhone recordings — modern iPhone video recording (especially 4K, high frame rate, or ProRes options) can produce very large MOV files, which is worth accounting for in upload size limits and processing/transcoding time expectations.
Comparison & FAQ
| Type | Purpose | Key difference from video/quicktime |
|---|---|---|
| video/mp4 | The most universally web-compatible video container | Much more consistent browser playback support; MOV often needs transcoding to MP4 for reliable web delivery |
Why won't the MOV video my user uploaded play in the browser?
Likely a codec compatibility issue, particularly if it's HEVC-encoded (increasingly common on newer iPhones) — browser support for MOV playback, especially with HEVC, is meaningfully less consistent than MP4/H.264, making server-side transcoding a common necessary step.
Should I accept MOV uploads directly, or convert them?
Accepting MOV uploads (since they're extremely common from iPhone users) while transcoding to MP4/H.264 server-side before web playback is the typical, more reliable approach for ensuring consistent playback across all your users' browsers.
Is MOV related to MP4?
Yes, closely — MP4's container design was based significantly on Apple's original QuickTime container format, which is part of why the two formats share meaningful underlying structural similarity despite being distinct formats with different MIME types today.
Why are iPhone-recorded videos sometimes very large?
Modern iPhone recording options (4K resolution, high frame rates, or ProRes) can produce substantially larger files than typical web video — worth factoring into upload size limits and expected processing/transcoding time for applications handling iPhone video uploads.