MPEG-4 Video (Apple)
M4V is Apple's 2006 file format for iTunes Store video — byte-for-byte identical to MP4 except for four bytes at offset 8. Those four bytes are a brand label Apple's apps pay attention to and every other player ignores. That difference is why renaming `.m4v` to `.mp4` plays the file on Windows.
Common questions
How do I convert M4V to MP4?
FileDex converts M4V to MP4 in your browser — drop the file into the converter above. Most M4V files use the same compression as MP4: H.264 video and AAC audio. Only one small label inside the file differs. FileDex re-packs the file into MP4 in seconds without re-compressing the video — fully lossless. Files protected by Apple's iTunes DRM cannot be converted because the lock is inside the file.
What is an M4V file?
M4V is Apple's brand of the MP4 file format. Apple released it in 2006 with the iTunes Store video catalogue. The byte structure inside is identical to MP4 — same boxes, same codecs (H.264 video and AAC audio). The only difference is four bytes at offset 8: a label `M4V ` instead of `mp42`.
Is M4V the same as MP4?
Structurally yes, with one four-byte difference. M4V and MP4 use the same underlying file structure, the same H.264 video, and the same AAC audio. The only structural difference is a four-byte brand label at offset 8. Apple's iTunes and Apple TV apps read that label to apply Apple-specific rules and lock iTunes Store purchases. Every other player ignores it.
How do I play an M4V file on Windows?
Most Windows players ignore `.m4v` files because the extension is unfamiliar. The byte structure inside is identical to MP4. Right-click the file, rename to `.mp4`, and Windows Media Player opens it. VLC Media Player plays `.m4v` directly without renaming because VLC reads the file structure, not the extension.
Is my M4V file DRM-protected?
Open the file in VLC and check the codec name. Unprotected M4Vs show H.264 video; FairPlay-protected files show an encrypted-codec marker the player cannot decode. iTunes Store purchases are FairPlay-protected; HandBrake exports, Final Cut Pro renders, and screen recordings are not. The four-byte brand label outside the file does not tell them apart.
What makes .M4V special
Four Bytes Apart: The Structural Difference Between M4V and MP4
Open an M4V file and an MP4 file in a hex viewer side by side. The first eight bytes of each are identical: 00 00 00 20 66 74 79 70. The first four bytes are the file size; the next four spell ftyp — the file's first labeled section, the part that announces what kind of file this is. Skip past byte 11 and read the rest of each file. Also identical. The encoded video frames, the AAC audio compression, the index telling the player where every frame lives — every byte that does the actual work of being a video file matches between the two. The difference between the two formats lives in four bytes at offset 8 of each file: the major_brand, the 4-byte label inside the file that says which kind of MP4 family member this is. The M4V file says M4V — with a trailing space, the four-character string Apple uses for iTunes Store video. The MP4 file says mp42 — the generic MP4 brand label, what FFmpeg and HandBrake write by default. Same compressed frames. Same audio. Same container structure underneath. One label different. That difference is the entire structural distinction between the formats. Apple has been writing those four bytes since 2006 — and writing variants of them that Apple never bothered to register.
Continue reading — full technical deep dive
Apple Is the Registration Authority — and Apple Ignores It
The MP4 Registration Authority — the registry where every legal MP4 brand label is filed, administered by Apple itself — has exactly one M4V entry. Search the public list for M4V: one row, registered with the description MPEG-4 protected audio+video. Now search the file(1) magic database — the rule list every macOS and Linux system uses to identify file types, shipped with every Unix-like operating system since the 1980s. Three rows: M4V for Apple iTunes Video, M4VH for Apple TV's M4V variant, and M4VP for Apple iPhone's M4V variant. Two of three brand labels Apple has shipped on M4V files since 2006 do not exist in Apple's own registry. Apple wrote the registry. Apple administers the registry. Apple has shipped two brand labels — one on every Apple TV, one on every iPhone — without ever filing them. The file(1) project caught the brands by reverse-engineering actual files from Apple devices; the canonical registry never received a submission. Identifying an M4V file in 2026 still requires consulting both lists. The brand is supposed to mean protected. That's what Apple's own registry says. Open an actual M4V file and check whether it's protected: the brand will lie to you.
The Brand Says Protected. Most Files Aren't.
Open a music video bought from iTunes Store in 2008. Open a HandBrake export from 2024 with the Apple TV preset. Both files are .m4v. Both have M4V at offset 8 — the four-byte string registered with the description MPEG-4 protected audio+video. The brand says encrypted on both files. Now open the codec table inside each file — the part that names the video and audio compression. The 2008 iTunes file says encv, the codec label MP4 uses to mark a video or audio track as encrypted. Real FairPlay protection — Apple's video DRM, the encryption Apple uses to control playback of iTunes Store purchases. The 2024 HandBrake file says avc1, the codec label for unencrypted H.264 video. No DRM. No encryption. The same brand label outside the file. The brand was meant to mean encrypted. The byte format the world ships says encrypted on both files. The actual files are protected on one and unprotected on the other — the brand cannot tell them apart. FairPlay protection lives in the codec entry inside the file, not in the four-byte label outside it. The HandBrake file, the Final Cut Pro render, the QuickTime screen recording — they all carry the M4V brand without ever touching FairPlay. Which is why the workaround everyone has used since 2006 actually works — and why Apple's own software is the only thing that notices.
Why the Rename Trick Works (And Why Only Apple Notices)
A user on a 2009 Windows XP machine has just bought a music video from iTunes Store. The download finishes. Double-click the .m4v file. Windows Media Player opens, looks at the file extension, decides it doesn't know what .m4v is, and refuses to play. The user right-clicks the file, picks Rename, types .mp4. Double-clicks again. Windows Media Player opens, looks at the new extension, decides it knows MP4, reads the file, finds the H.264 video and AAC audio inside, and plays. The bytes never changed. The codec never changed. Not a single byte of the file moved. Windows Media Player dispatches on the file extension; the moment the extension changes, it recognizes the file. The file was always playable; it was just labeled wrong for the player asking. iTunes on the same machine works in the opposite direction: iTunes opens the file, reads the four bytes at offset 8, sees M4V , and treats the file as iTunes Store property. The extension does not matter to iTunes. It reads the brand. Apple is the only software in the world that does. Every other player on every other operating system reads the box hierarchy and ignores the four-byte label entirely. Rename to .mp4, the file plays. The brand is still M4V . Apple's apps would still notice. Nothing else does.
.M4V compared to alternatives
| Formats | Criteria | Winner |
|---|---|---|
| .M4V vs .MP4 | Structural identity vs Apple-specific brand handling M4V and MP4 are the same format underneath — same wrapping, same video compression (H.264), same audio compression (AAC). The structural difference is four bytes inside the file that act as a label. M4V uses one of Apple's labels (`M4V `, `M4VH`, or `M4VP` for iTunes Store, Apple TV, or iPhone). MP4 uses a generic label (`mp42` or `isom`). Apple's apps pay attention to those four bytes to apply Apple-specific rules and lock iTunes Store purchases. Other apps — VLC, HandBrake, most Android players — ignore the label and treat the file as MP4. Neither format wins. They are the same file with two different labels. | Draw |
| .M4V vs .MOV | Two Apple-rooted ISOBMFF variants MOV (QuickTime, 1991) predates the ISO Base Media File Format spec by 13 years — Apple's QuickTime atom-tree was the prototype the ISO standard later formalized. M4V (2006) is the iTunes Store video brand of that ISO standard. MOV is the format Final Cut Pro writes for editing pipelines, with rich support for ProRes, multiple audio tracks, and edit-friendly codecs. M4V is the iTunes Store delivery container, restricted to H.264 video and AAC / Dolby Digital audio for Apple device playback. MOV wins on flexibility and editing-pipeline use; M4V wins on iTunes / Apple TV native dispatch but only because Apple's software notices the brand. | MOV wins |
| .M4V vs .MKV | Apple ecosystem vs open multimedia container MKV (Matroska, 2002) is open-spec, IETF-standardized in RFC 9559 (2024), and codec-agnostic — any video codec, any audio codec, unlimited subtitle and font tracks, chapter markers. M4V is Apple-owned, ISO Base Media File Format-based, and codec-restricted to H.264 / AAC / Dolby Digital. MKV does not natively support any DRM scheme; M4V supports Apple FairPlay for iTunes Store-purchased content. MKV wins on openness, codec freedom, and multi-track flexibility. M4V wins inside Apple's playback chain because Apple's software honors the four-byte brand label and dispatches accordingly. | MKV wins |
Convert .M4V to...
Technical reference
- MIME Type
video/x-m4v- Magic Bytes
00 00 00 xx 66 74 79 70ftyp box, same structure as MP4.- Developer
- Apple Inc.
- Year Introduced
- 2006
- Open Standard
- No — View specification
ftyp box, same structure as MP4.
Binary Structure
M4V files use the ISO Base Media File Format defined by ISO/IEC 14496-12 — the same byte layout as MP4, MOV, and HEIF. Every M4V file is a sequence of `boxes`. Each box begins with a 4-byte size field followed by a 4-byte type tag. The first box is always `ftyp` — the file's first labeled section — at offset 4 (bytes `66 74 79 70` ASCII `ftyp`). The ftyp box payload starts at offset 8 with the major_brand: a 4-byte ASCII string that identifies which kind of MP4 family member this file is. M4V uses one of three brand labels at offset 8: `M4V ` (4D 34 56 20, with trailing ASCII space) for iTunes Store video, `M4VH` (4D 34 56 48) for Apple TV-encoded video, or `M4VP` (4D 34 56 50) for iPhone-encoded video. The first is registered with the MP4 Registration Authority; the other two are not. After the major_brand, a 4-byte minor_version, then a list of compatible_brands — additional 4-byte labels the file claims to also conform to (typically `mp42`, `isom`, `avc1`). After the ftyp box, the standard top-level sequence continues with a `moov` box (the index inside an MP4 — the table that tells the player where every frame lives, with per-track sample tables) and an `mdat` box (the encoded video and audio themselves). Inside the moov box, a `trak` box per stream, and inside each trak a `mdia.minf.stbl.stsd` box that names the codec — `avc1` for H.264 video and `mp4a` for AAC audio in unprotected M4V files. FairPlay-protected M4V files rewrite those codec entries to `encv` (encrypted video) and `enca` (encrypted audio), and add a `sinf` (Protection Scheme Information) box with the FairPlay scheme parameters — the real DRM signaling, hidden inside the box hierarchy rather than visible in the brand label outside it.
| Offset | Length | Field | Example | Description |
|---|---|---|---|---|
0x00 | | size | | Big-endian 4-byte length of the ftyp box, including this size field. Determines where the next box begins. |
0x04 | | type | | ASCII tag identifying this as the file type box — the file's first labeled section, mandatory and always at offset 4 per ISO/IEC 14496-12. |
0x08 | | major_brand | | The 4-byte brand label that distinguishes M4V from MP4. `M4V ` (with trailing space) is iTunes Store video, registered with MP4RA. `M4VH` is Apple TV's variant; `M4VP` is the iPhone variant. Neither is registered. |
0x0C | | minor_version | | Informational version of the major_brand. Apple writes 1 in this field for iTunes Store video; FFmpeg and HandBrake write 512 (`00 00 02 00`) when producing M4V output. |
0x10+ | | compatible_brands | | List of additional 4-byte brand labels the file also conforms to. Parsers walk this list and dispatch on whichever brand they recognize first — which is how non-Apple players treat M4V as MP4. |
Attack Vectors
- Demuxer parsing bugs in older FFmpeg `libavformat/mov.c` (which handles MP4, MOV, and M4V): CVE-2020-21041 heap overflow, CVE-2017-9608 out-of-bounds read, CVE-2014-9603 heap overflow. Patched in current FFmpeg; legacy bundles remain exposed.
- iTunes / QuickTime parsing bugs in Apple's stack: legacy QuickTime for Windows (discontinued April 2016) had unpatched ftyp / moov exploits — CVE-2016-1769, 1768, 1767. macOS QuickTime stays maintained.
- FairPlay-encrypted-codec parse edge cases: when `encv`/`enca` codec entries are read with invalid or absent FairPlay keys, parsers historically crashed or leaked memory. Apple-internal vector, documented in iTunes patch notes (2010-2015).
Mitigation: FileDex processes M4V files entirely in-browser via FFmpeg WebAssembly. The WASM sandbox confines any demuxer or codec exploit to the browser's isolated memory — no host execution, no DLL loading, no iTunes stack contact. FairPlay-protected M4Vs fail to read because FFmpeg cannot decrypt them; FileDex never accepts unauthorized content.
- Specification Information technology — Coding of audio-visual objects — Part 14: MP4 file format
- Specification Information technology — Coding of audio-visual objects — Part 12: ISO Base Media File Format
- Registry MP4 Registration Authority — Brand registry
- Registry file(1) magic database — animation rules
- History M4V — Wikipedia
- History FairPlay — Wikipedia