MP4 vs MOV vs WebM: which video file should you use?

Containers hold, codecs compress

A container is the box rather than its contents. It stores one or more streams of compressed video and audio, keeps them in sync, and carries information such as duration, subtitles or chapter points. MDN's media reference traces the family tree: MP4 is derived from the ISO base media file format, which was itself derived from Apple's QuickTime file format, the one behind files ending in .mov. WebM comes from a different line, based on the Matroska format and designed specifically for modern web environments. So MP4 and MOV are close relatives with a similar internal structure, while WebM is a separate design that deliberately limits itself to a small, openly licensed set of codecs.

How each one is used

MP4 is the general purpose delivery format. MDN's advice is that if you can provide only one format, choose the one available on the broadest selection of devices and browsers, which for video means MP4. YouTube's recommended upload settings also specify MP4, with the index, known as the moov atom, placed at the front of the file so playback can begin before the whole file arrives. MOV remains common as a capture and editing format on Apple systems and professional cameras, but MDN notes it is no longer widely used on the internet because its support is mainly on Apple devices. WebM requires support for VP8 and VP9 video with Vorbis and Opus audio, and the WebM Project publishes the format and its codecs under open licences.

When the choice matters

It matters at every handover. A MOV straight from an editing workstation can be much larger than an MP4 exported from the same timeline, and a recipient on Windows or Android may struggle to preview it. It matters on web pages, where offering WebM alongside MP4 lets a browser pick the open format while devices that prefer MP4 still play. It matters for recordings made in a browser, which are often saved as WebM, and which may need converting before an editing tool or upload form will accept them. And it matters for any platform or form with a fixed list of accepted containers, where the wrong extension simply fails at the upload step before quality is ever considered. A simple rule covers most teams: keep MOV or the original camera file as the master, deliver MP4 to people and platforms, and add WebM only where you control the web page that plays it.

Common mistakes

Renaming a file from .mov to .mp4 is the classic one. It changes the label, not the contents, and it only works when the codecs inside happen to suit the new extension; converting with a real export is the reliable route. The second is assuming a WebM will be accepted everywhere because it plays in a browser, when many upload forms and editing tools still expect MP4. The third is sending an editing MOV as the final file, which wastes storage and fails to preview for many recipients. The fourth is forgetting the audio track: a container can hold audio in a codec the destination cannot play, which produces a silent video that looks like a missing soundtrack.

Where it shows up in the product

The video builder here takes all three as input and produces one as output. An uploaded clip can be an MP4, WebM or MOV file up to 200 MB, trimmed by start and end time and set either to cover its box or to fit inside it. Every export is an MP4 with H.264 video at 30 frames per second, which is the file to upload, attach or embed. The share link is not a file at all but a live player page that draws the video in the viewer's browser, so anything that needs a download needs the exported MP4. The one WebM output in the wider product comes from the slides module, where the presentation recorder saves WebM files with VP9 or VP8 video and Opus audio.

Questions people ask