Convert WebM to MP4

Almost nobody sets out to make a WebM. It arrives. A browser-based screen recorder wrote one, a Discord or WhatsApp Web voice message downloaded as one, a page used the browser’s own MediaRecorder to capture a camera, or a download tool saved the stream a site was already serving. Google published the format in 2010 precisely so that video could be delivered on the web without licence fees, and browsers do all read it.

Everything else largely does not. QuickTime has no VP9 decoder, Premiere and After Effects will not import one without help, PowerPoint refuses the file, and a phone’s camera roll will not take it. That gap — every browser yes, almost every desktop application no — is the whole reason this conversion is one of the most searched-for on the internet, and it is why MP4 is the answer rather than a codec pack.

Some container conversions are a matter of rewriting a header and copying the compressed data across untouched. This is not one of them. WebM holds VP8, VP9 or AV1; the MP4 written here holds H.264, because H.264 is the codec every device made in the last twenty years can decode in hardware. Two different codecs means every frame is decoded back to pixels and compressed again from scratch.

Budget accordingly. A one-minute clip at 1080p is usually done before you have switched tabs. A forty-minute screen recording of a meeting is minutes of sustained work on your own CPU and GPU, and the tab has to stay open while it happens. Anyone promising an instant WebM to MP4 conversion is either copying a stream a device will not play or has not started yet.

The video track is written as H.264 at High profile, level 3.1 — in codec-string form, `avc1.64001f`. The audio, which in a browser-made WebM is nearly always Opus, is written as AAC. That pairing is deliberate: an MP4 containing AV1 is a perfectly valid MP4 that a television will refuse to play, and a conversion that produces a file the destination rejects has not solved anything.

The practical consequence is that the MP4 is playable by default everywhere an MP4 is expected — iOS and Android, Windows Media Player, QuickTime, every editor, every social platform’s uploader. High profile rather than Baseline is worth knowing about only in one place: extremely old hardware players that predate it. Everything from the last decade and a half handles it.

Because every frame is being rebuilt anyway, changing the resolution costs nothing extra. The control offers 2160p, 1440p, 1080p, 720p, 480p and 360p alongside keeping the original size, and the width follows the height automatically so nothing is ever stretched.

Asking for more than the source has is quietly ignored. A 720p screen recording set to 4K would be four times the file with not one pixel of new detail in it, so the request is treated as "leave it alone". The useful direction is downward: a 4K capture dropped to 1080p has a quarter of the pixels, and the MP4 shrinks roughly in proportion.

Most WebM files that need converting are screen recordings, and screen content is unusually kind to a re-encode. Flat interface panels, solid blocks of colour and unmoving text compress extremely well and survive a second pass with almost nothing visible lost. A recorded software demo converted to MP4 generally looks identical to the WebM beside it.

Camera footage is the harder case. Grain, hair, foliage and fast motion are exactly what a codec spends its bits on, and asking a second codec to describe the first one’s approximations shows. If the WebM came out of a webcam and the result is going into an edit rather than straight to a viewer, raise the quality band before converting rather than after.

Picture and sound cross over in full: every video track and every audio track the browser can decode, in the order the WebM held them, because MP4 has no practical ceiling on how many it can store. What does not survive is everything that is neither — no subtitle tracks, no chapter marks. For a browser-made capture this is almost always academic, because those files contain one video track and one audio track and nothing else.

Transparency is the one that occasionally surprises people. VP9 in WebM can carry an alpha channel — it is how animated overlays are delivered on the web — and H.264 has no alpha channel at all. A transparent WebM converted to MP4 comes back opaque, and no setting changes that. If the transparency is the point, keep the WebM and use it in a `<video>` element.

The H.264 encoder used here belongs to the browser and the machine, not to this page. Chrome, Edge and Safari have one on essentially every current computer and phone. Some Firefox installations, particularly on Linux, do not, and in that case the conversion stops before it starts with a sentence saying so rather than failing halfway through.

There is no software fallback, and that is a decision rather than an omission. An H.264 encoder compiled to WebAssembly is tens of megabytes to download and roughly an order of magnitude slower than the hardware encoder sitting idle next to it. Telling you to open the same page in a different browser is a better answer than a fifty-megabyte download that then takes an hour.

Drop up to a hundred files together. Each one converts on its own with its own progress, and once more than one has finished they can be downloaded as a single ZIP. This is the ordinary case for anyone whose screen recorder has been quietly producing WebM for months.

Because nothing is uploaded, a batch costs no bandwidth and hits no daily limit — the only constraint is how much work your machine wants to do at once. It is also the point at which the local approach stops being about privacy and starts being about not spending an afternoon watching an upload bar.

Screen recordings are the single most sensitive category of file most people convert. They contain inboxes, dashboards, customer names, internal tooling and whatever else happened to be on screen, and the usual route for this conversion is to hand all of that to a website you found ten seconds ago.

Here the video is decoded, re-encoded and muxed inside the tab, using codecs the browser already has. Nothing carrying the file is sent anywhere, there is no account, and there is no queue behind other people’s uploads. The check takes ten seconds if you want to make it: open developer tools, watch the network tab, convert something and see what moves.