MP4 vs WebM vs MOV: containers, codecs and what plays where
The file extension names the container, not the compression inside it, and playback depends on both. H.264 video with AAC audio in an MP4 is the combination least likely to fail; the others are worth choosing for specific reasons.
ConvertBoxPublished
A file extension names the container, not the compression
MP4, MOV, WebM, MKV and AVI are containers: file layouts that hold one or more compressed streams plus the timing information that keeps them in sync. The streams themselves are produced by codecs. H.264, H.265 (HEVC), VP9 and AV1 compress the picture; AAC, Opus, Vorbis and MP3 compress the sound. The extension tells you which wrapper was used and almost nothing about what is inside it.
That is why two .mp4 files can behave differently. One holds H.264 video with AAC audio and plays on a ten-year-old television; another holds AV1 with Opus and fails on a phone from a few years ago. Playback is decided stream by stream: the player must understand the container, then have a decoder for the video codec, then one for the audio codec. To see what a file really contains, open it in VLC and look at the codec information, or inspect it with MediaInfo.
The codecs you will actually meet
| Codec | Kind | Where it plays | Worth knowing |
|---|---|---|---|
| H.264 (AVC) | Video | Practically every browser, phone, TV and editor | The safe default; larger files than newer codecs at the same quality |
| H.265 (HEVC) | Video | Recent phones, TVs and Apple devices; on Windows and in browsers it depends on hardware and installed components | Similar quality at roughly half the bitrate of H.264; what recent iPhones record by default |
| VP8 | Video | All current browsers | Older royalty-free codec; less efficient than VP9 |
| VP9 | Video | Chrome, Firefox, Edge and Android; recent versions of Safari | Royalty-free, in the same efficiency class as HEVC; widely used for web streaming |
| AV1 | Video | Chrome, Firefox and Edge; Apple devices only where the chip has an AV1 decoder | The most efficient of the group, but slow to encode in software |
| AAC | Audio | Practically everywhere | The usual partner of H.264 in MP4 and MOV |
| Opus | Audio | All current browsers and Android; often missing on older hardware players | The usual audio in WebM; efficient at low bitrates |
Why a file will not play: the four usual causes
- The video codec has no decoder on that device. The classic case is an HEVC clip from an iPhone opened on a Windows PC without HEVC support: the player shows a black frame or an error.
- The audio codec is the unsupported one. You get picture and silence, typically with AC-3 or DTS tracks in MKV files or camera footage played in a browser.
- The container and codec do not belong together. WebM permits only VP8, VP9 or AV1 video with Vorbis or Opus audio, so H.264 data in a file named .webm is rejected even by players that handle both formats.
- The file is incomplete. An MP4 keeps its index in one block, often written at the very end; if a recording or download is cut short, the index is missing and the player cannot find the frames. That calls for a repair tool, not a converter.
What each container is for
| Container | Usually holds | Strength | Weak point |
|---|---|---|---|
| MP4 | H.264 or HEVC with AAC | Plays almost anywhere; the standard for sharing and uploading | An interrupted recording can be unreadable |
| MOV | H.264, HEVC or ProRes with AAC or PCM | Native to Apple cameras and editing software | Some non-Apple apps and older Windows players refuse it |
| WebM | VP8, VP9 or AV1 with Vorbis or Opus | Royalty-free and built for browsers; what browser screen recorders write | Many editors and older Apple software will not import it |
| MKV | Almost anything, with several audio and subtitle tracks | Flexible, and an interrupted recording usually stays readable | Patchy support in browsers, built-in phone players and some editors |
| AVI | Older codecs such as DivX, Xvid or MJPEG with MP3 | Understood by legacy Windows software and devices | A 1990s design that handles modern codecs and subtitles poorly |
Remux or re-encode: changing the wrapper or the contents
There are two ways to change a format. A remux copies the compressed streams unchanged into a different container. Nothing is decoded, so it takes seconds, loses no quality and leaves the size almost the same. A re-encode decodes every frame and compresses it again with a new codec or new settings. It is slow, and each pass discards a little more detail.
Remuxing works only when the target container accepts the codecs already in the file. H.264 with AAC moves freely between MP4, MOV and MKV, which is why an iPhone MOV holding H.264 can become an MP4 with no loss in software that offers stream copy. The same file cannot be remuxed into WebM, because WebM does not allow H.264; that conversion has to re-encode. And if the real problem is the codec, as with HEVC on an old PC, changing only the container fixes nothing.
What a browser-based converter writes for each target
A converter that offers one button per format is making these codec choices for you, so it helps to know them. ConvertBox's Convert Video tool has no codec, bitrate or quality controls; each target has one fixed recipe, and resolution and frame rate pass through unchanged.
- MP4, MOV and AVI: re-encoded to H.264 at CRF 28 with AAC audio (128 kbps for MP4), using the ultrafast encoder preset. Compatible nearly everywhere, but fine texture comes out softer than the source.
- WebM: re-encoded to VP8 at a fixed 1 Mbps with Vorbis audio at 128 kbps, whatever the resolution. Adequate for 720p screen captures, thin for 1080p footage with a lot of motion. It does not produce VP9 or AV1.
- MKV: a remux. Video and audio are copied bit for bit, so there is no quality loss and the job finishes almost at once.
- Not available: HEVC or AV1 output, hardware-accelerated encoding, and files over 50 MB. Desktop software such as HandBrake or a native FFmpeg install covers those.
- Related tools: Compress Video always returns H.264 in MP4, and Trim Video writes H.264 while keeping the source extension, so convert a WebM recording to MP4 before trimming it.
Which format to pick for sharing, the web and editing
When in doubt, H.264 video with AAC audio in an MP4 file is the combination least likely to fail.
- Sending to other people or uploading to a platform: MP4 with H.264 and AAC. Platforms re-encode uploads anyway, so compatibility matters more than efficiency.
- Embedding on your own website: MP4 with H.264 as the baseline every browser plays, plus a WebM with VP9 or AV1 offered first where the smaller files justify the extra encoding work.
- Editing: keep the camera original, often a MOV, and convert before editing only if the editor refuses the file. Every re-encode is another lossy generation.
- Archiving a file with several audio or subtitle tracks: MKV, which holds them all and can be filled by remux without loss.
- Saving storage on files you keep for yourself: HEVC or AV1 from a desktop encoder, once you have checked that your devices play them.
- A WebM screen recording that an editor rejects: convert it to MP4. The re-encode also rebuilds the seeking index that browser recorders often leave incomplete.