Video · WebM to MP4
WebM to MP4, on your device.
WebM and MP4 do not share codecs, so a WebM with VP8 video has to be re-encoded. This does it locally, tells you what is copied and what is not, and never uploads your recording.
How to convert WebM to MP4
- Choose the WebM file (a browser screen recording, a download, a clip from a web editor).
- Read the track table. VP8 video shows Re-encoded to H.264; Opus or Vorbis audio shows Re-encoded to AAC. VP9 or AV1 video shows Copied.
- For a re-encode pick Balanced or Faster, and optionally cap the height at 1080p, 720p or 480p. Press Convert and download the MP4.
Why this one re-encodes
WebM is limited to VP8, VP9 or AV1 video and Vorbis or Opus audio. The standard MP4 for phones, editors and social uploads uses H.264 with AAC. The muxer for MP4 will not even accept VP8 (the engine reports it has no tag for that codec), so there is no remux shortcut for VP8. The video is decoded and encoded again as H.264, and the Opus audio becomes AAC. A re-encode is a second round of lossy compression, so the MP4 is slightly less faithful than the WebM; at the default quality setting the difference is rarely visible on screen recordings.
VP9 and AV1 inside a WebM can be copied into MP4, and Auto does so, converting only the Opus audio. Those files then play in recent browsers, but some phones and older editors still do not decode VP9 or AV1. If your target device is picky, choose Always re-encode.
Honest speed numbers
This tool uses a single-threaded WebAssembly build of FFmpeg. In our own test runs, H.264 at the Balanced setting encoded 640x360 at roughly 40 frames per second but 1920x1080 at roughly 2 frames per second. A ten-minute 1080p screen recording at 30 fps is 18,000 frames and could take over two hours on that basis. Shrinking to 720p or choosing Faster cuts that substantially; screen recordings with little motion also encode faster. If you have a long HD recording, desktop software with multi-threading will beat this by a wide margin. If it is a short clip, a meeting snippet or a bug-report capture, a browser is fine and the file stays private.
Screen recordings and missing durations
Browser screen recorders often write WebM without a duration or seek index, so players show no length and cannot jump around. Converting to MP4 writes a proper index and moves it to the start of the file, so the result seeks normally and starts playing quickly on the web.
Worked example
A 90-second 1280x720 browser screen recording in VP8 and Opus: Method Auto, Balanced. The table shows video Re-encoded to H.264 and audio Re-encoded to AAC. At 720p the job takes on the order of ten minutes on a laptop; the MP4 uploads to a video editor that rejected the WebM.
Common mistakes
- Choosing Remux only. It refuses VP8 files and says why.
- Leaving a 4K recording at full size. Cap the height; it is the single biggest speed lever.
- Expecting the MP4 to be smaller. VP9 is often more efficient than H.264 at the same quality, so the MP4 can be larger.
Your file never leaves your browser
Nothing in this page sends your WebM anywhere. The converter sits in a sandboxed frame that is only allowed to use local blob and data URLs, with no ads or analytics inside. FFmpeg, compiled to WebAssembly, reads the file from your disk, and the MP4 is generated in your browser's memory and saved with a normal download. The one network request is the converter engine itself, loaded after you pick a file.
Limits and what this does not do
- One file at a time, up to 2 GB; the result is built in memory, so low-memory devices may fail on large files.
- No batch queue, no trimming, no watermark removal, no editing.
- A WebM with a transparent (alpha) background is flattened; MP4 has no standard alpha channel.
- WebVTT subtitles are carried over as MP4 text subtitles.
Common mix-ups
-
Often assumedEvery WebM video stream can be copied into MP4.
What the source saysMDN's video codec guide lists the containers per codec: VP8 appears with 3GP, Ogg and WebM, while VP9 appears with MP4, Ogg and WebM. VP8 therefore needs re-encoding for MP4 and VP9 can be copied. [1]
-
Often assumedWebM audio can always be copied into MP4 untouched.
What the source saysMDN lists Opus as a codec MP4 supports but Vorbis only for WebM and Ogg in its container tables. A WebM with Vorbis audio needs its audio converted, for example to AAC. [2]
Checked against these sources on .
Frequently asked questions
Why can WebM not just be renamed or copied into MP4?
MP4 does not accept VP8 video or Opus audio in a way phones and editors can use, and the engine refuses VP8 outright. The streams must be decoded and re-encoded as H.264 and AAC.
Does converting WebM to MP4 reduce quality?
Slightly, for tracks that are re-encoded, because lossy compression is applied twice. If the video is VP9 or AV1 it is copied and only the audio is re-encoded.
Why is it so slow?
Re-encoding video in a single-threaded WebAssembly engine is slow, especially at 1080p and above. Capping the height to 720p or 480p, or choosing the Faster setting, helps a lot. Copying (VP9 or AV1) is fast.
Can I convert a WebM screen recording that has no duration?
Yes. The MP4 is written with a full index, so the length shows and seeking works.
Will my transparent WebM keep its transparency?
No. MP4 has no standard alpha channel, so transparent areas become opaque.
Will the MP4 work in Premiere, iMovie or on social sites?
H.264 with AAC is the broadly accepted format. A copied VP9 or AV1 track may not be accepted by older editors; use Always re-encode for those.
Is there a file size limit?
Up to 2 GB, with a warning above 500 MB. The practical limit is your tab memory.
Is my recording uploaded?
No. It is processed on your device in a frame without network access.
Sources
Last checked
- WebM container guidelines — WebM allows only VP8, VP9 or AV1 video with Vorbis or Opus audio
- MDN: video codecs used on the web — H.264, HEVC, VP8, VP9, AV1 and MPEG-4 Part 2 support and licensing notes
- FFmpeg wiki: H.264 encoding guide — CRF quality scale and presets (ultrafast to veryslow)
- FFmpeg formats documentation — the MP4, Matroska, WebM and Ogg muxers and their options (movflags faststart)
- ffmpeg.wasm project — FFmpeg compiled to WebAssembly, the engine this page runs in your browser
- Emscripten file system API — WORKERFS, which lets the converter read your file without copying it into memory first
Runs entirely in your browser. Your file is read on your device and is never uploaded.