Convert WEBM to MP4
WEBM is Google's video file format - what you get when you download from YouTube with yt-dlp, save a screen recording out of OBS in its default settings, or capture video from a browser page. It plays perfectly in Chrome, Firefox, and Edge, and refuses to play almost everywhere else. Because WEBM uses different video and audio compression than MP4, converting between them takes real work - not a fast wrapper swap. Wave does the whole thing locally in your browser using your device's hardware, so nothing gets uploaded and a five-minute video finishes in about a minute.
What actually changes
To understand why WEBM to MP4 takes minutes rather than seconds, it helps to know that WEBM and MP4 use completely different compression formats inside. WEBM holds video compressed with VP8, VP9, or AV1 (open codecs developed by Google) plus audio compressed with Opus (an open codec used by browsers). MP4 holds video compressed with H.264 or HEVC plus audio compressed with AAC (older codecs with universal player support). Neither format's compression is compatible with the other, so Wave has to actually decompress every frame back to raw pixels, then re-compress with H.264 that MP4 accepts. That decode-then-encode work is what takes the time. If the "codec vs. container" distinction is unfamiliar, Codecs vs containers explains it in plain English.
For the encoding step, Wave prefers your browser's built-in WebCodecs H.264 encoder when available - this is a modern browser feature that lets web pages use the same hardware video encoder your device already uses for FaceTime, Zoom, and screen recording. Several times faster than a software-only encoder. On browsers without a WebCodecs H.264 encoder (mostly Firefox as of 2026), Wave falls back to a software encoder written in WebAssembly that's slower but produces the same MP4-compatible output. Audio always re-encodes to AAC at 192 kbps (a bitrate high enough that most listeners can't tell it from the source on consumer headphones). Every codec Wave ships is LGPL-licensed - meaning it's license-clean and doesn't drag other software into open-source obligations - never the more common GPL-licensed x264, which would infect anything that uses it.
A short history for context: WEBM launched in 2010, driven by Google after YouTube acquired On2 (the company that made VP8). Google wanted a video format it could ship in Chrome and stream from YouTube without paying MPEG-LA (the industry patent pool) fees on every H.264 decode. WEBM's container is actually a stripped-down version of the same Matroska format that MKV uses - which is why some MKV players will happily open WEBM files too. The video codecs inside evolved over time: VP8 (2010) gave way to VP9 (2013) with roughly 30% better compression, and then AV1 (2018) which is another 30% better than VP9. Screen recordings from OBS Studio, YouTube downloads via yt-dlp, and any video captured in a browser via the MediaRecorder API all typically land in WEBM by default.
For a WEBM file containing VP9 video and Opus audio (by far the most common combination in 2026), the mechanical cost of the conversion is real but manageable. Every video frame gets decoded from VP9 into a raw uncompressed pixel buffer, then re-encoded to H.264 by your browser's hardware encoder. On a modern laptop or phone with WebCodecs available, a five-minute 1080p WEBM finishes in about 30-90 seconds. On older hardware or in Firefox without WebCodecs H.264 acceleration, the software encoder does the same job in 3-8 minutes and produces a slightly less efficient file at similar visual quality. Either way, your file never leaves your device, and you get an MP4 that plays on iPhone, iPad, Windows, Android, Chromecast, smart TVs, and every video app that refused your original WEBM.
Three steps.
-
01
Step 1
Drop your WEBM file onto the card.
-
02
Step 2
Wave will show "Re-encode needed" - the streams need to be rewritten to fit MP4.
-
03
Step 3
Convert. Slower than a remux, but everything happens on your device.
Answers, specifically.
Why is WEBM to MP4 slower than MKV to MP4?
Because it can't be a remux. Every video frame has to be decoded from VP8/VP9 and re-encoded, and every audio sample has to be decoded from Opus and re-encoded to AAC.
Will the MP4 look identical to the WEBM?
Very close. Wave targets high quality, but small transcoding losses are unavoidable whenever you go through decode-then-encode.
Do I get H.264 or MPEG-4 Part 2?
H.264 whenever your browser exposes a WebCodecs H.264 encoder - which is Chrome, Edge, Safari 16.4+, and most Chromium-based mobile browsers. On browsers without WebCodecs H.264, Wave falls back to MPEG-4 Part 2 because the GPL-licensed libx264 can't be bundled without pulling the whole site under GPL. The player-compatibility difference is small; the file-size difference is a few percent in H.264's favour.
Does the audio come out as AAC or Opus?
AAC. Opus in an MP4 file is legal but plays inconsistently in non-web players, so we default to AAC.
Do YouTube downloads work here?
Wave doesn't download from YouTube - that's a separate legal and technical animal. If you already have the .webm file, this converts it.
What about WEBM screen recordings from OBS?
They convert fine. OBS Studio's WebM output uses VP9 or VP8 video with Opus audio, exactly the case Wave's transcode path handles. If OBS is configurable on your machine, recording directly to MP4 (with H.264) skips the conversion entirely - it's faster to record right the first time when you can.
How do I know if my WEBM is VP8, VP9, or AV1?
Wave shows the codec on the inspect screen after you drop the file. All three go through the same re-encode path to H.264 in MP4. AV1-in-WebM files are increasingly common on YouTube's 4K tier; they convert like the others but decoding is slower without hardware AV1 support.
Can I record video from a browser page and convert it?
Sort of. A browser recording via MediaRecorder produces a WebM blob you can save to disk, then feed to Wave to convert to MP4. The MP4 side works normally; the recording quality depends on what the browser captured (frame rate, bitrate) which you cannot influence much.
Why does my downloaded WebM play video but no sound in some apps?
The audio is Opus, and the app you tried does not decode it. WebM audio is Opus (modern) or Vorbis (older) - both play in every browser and in VLC, but Windows Media Player, older iOS players, and many hardware players skip them. Converting to MP4 with AAC audio (which this page does) is the fix: after the conversion, the same audio plays everywhere.
Will converting WEBM to MP4 lose quality?
A small, usually-invisible amount. WEBM cannot be remuxed into MP4 because MP4 rejects VP8, VP9, and Opus - the streams must decode to raw pixels and PCM audio and re-encode to H.264 and AAC. Wave targets a high-quality H.264 bitrate for the video encode, and for typical 1080p live-action or screen-recording content the difference from the source is well below the perceptual threshold. A 4K or high-motion source with a marginal source bitrate will show more loss because the second encode compounds the first.