Convert WebM to MP4
WebM was designed for browsers and it does that job well. Everywhere else it is awkward: video editors often refuse it, older phones cannot decode VP9, and plenty of upload forms do not list it. Converting to MP4 re-encodes the picture as H.264, which is the one video codec you can assume anything will play.
Use this without the search next time. Prathom Workbench puts Prathom's tools in your toolbar.
Add to Chrome — freeDrop your WEBM file here, or click to browse
Up to 50 MB. Deleted automatically after 30 minutes.
What it does
- VP8 or VP9 video re-encoded as H.264, Opus or Vorbis audio as AAC
- Resolution, frame rate and duration preserved
- Output plays on phones, in editors and in every browser
How to use WebM to MP4
- 1
Upload the WebM
A recording from a browser, a download, or an export from a web tool.
- 2
The picture is re-encoded
VP9 or VP8 becomes H.264 and the audio becomes AAC. This is a real re-encode, not a repackage, because the codecs are genuinely different.
- 3
Expect it to take a few seconds
Decoding VP9 and encoding H.264 is the slowest part. A short clip is quick; a long one is proportionally longer.
How it works
The WebM is opened, the video decoded from VP8 or VP9 and the audio from Opus or Vorbis, and both re-encoded — H.264 for the picture, AAC for the sound — into an MP4. Resolution, frame rate and duration are unchanged.
This is a full re-encode. There is no shortcut available, because none of the codecs on the way in is one an MP4 player expects on the way out.
What WebM is good at, and where that stops
Inside a browser, WebM is excellent: it is royalty-free, VP9 compresses better than H.264 at the same quality, and every modern browser plays it natively. That is exactly what it was designed for.
Outside a browser the picture changes. Video editors frequently refuse it or import it badly. Hardware VP9 decoding is recent enough that many phones fall back to software and stutter. And a great many upload forms simply do not list the format.
The size surprise
The MP4 may be larger than the WebM it came from. That is not a fault: VP9 is a more efficient codec, so representing the same picture in H.264 takes more bits. You are trading size for compatibility, which is usually the right trade when the alternative is a file nothing will open.
Renaming does not work
It is worth saying plainly because people try it. Changing .webm to .mp4
relabels the container and leaves VP9 inside, so the player opens it, fails to
decode, and reports a corrupt file. The problem then looks like a damaged
download rather than a codec mismatch.
What to keep
If the WebM is the original recording, keep it. The MP4 is the copy for the editor, the phone or the upload form.
Why so much of what you download is WebM
Browsers negotiate a format with the site rather than being handed one, and where WebM is offered they will generally take it, because it is what they support natively and royalty-free. The consequence is that a great deal of saved web video is WebM without anybody having chosen it.
That is the same pattern as Windows producing years of WMV files and XPS documents: the format was the default in the dialog rather than a decision. Those are always the formats that accumulate quietly and need converting in bulk later, because nobody was keeping track of what they were collecting.
What the conversion costs
VP9 and H.264 are both lossy, so this is a second generation of encoding rather than a repackage. At normal viewing sizes the difference is not something you will pick out, and the trade buys a file that plays on hardware decoders everywhere, which is the entire point.
Examples
A browser screen recording for a video editor
The editor imports it without complaint. Most editors either refuse WebM outright or import it and then behave oddly on the timeline, which is worse than a refusal.
A clip for an older phone
VP9 decoding in hardware is recent; H.264 is in essentially every device made in the last fifteen years. The MP4 plays smoothly where the WebM stuttered or refused.
Frequently asked questions
Why can I not just rename the file?
Because the codecs inside are different, not just the wrapper. A WebM holds VP8 or VP9 video with Opus or Vorbis audio; an MP4 player expects H.264 with AAC. Renaming changes the extension and nothing else, so the player opens a file it cannot decode — usually reported as a corrupt file, which sends people looking for the wrong problem.
Does the quality drop?
There is one lossy re-encode, so yes, slightly. In practice it is not visible in ordinary viewing at the settings used. It is worth knowing that VP9 is a more efficient codec than H.264, so the MP4 may be somewhat larger than the WebM at comparable quality — the trade for compatibility is size, not just a generation of loss.
Why is this slower than converting between other video formats?
Because it is a genuine re-encode in both directions: VP9 has to be decoded and H.264 encoded, frame by frame. Some video conversions are only a container change, where the streams are copied across untouched in a fraction of a second. This is not one of those, because no MP4 player would understand the streams if they were copied.