Video · MP4 to WebM
MP4 to WebM, VP8 and Opus.
Turn an MP4 into a WebM with VP8 video and Opus audio, encoded on your device. VP9 is not offered, and the page explains why. Your video is not uploaded.
How to convert MP4 to WebM
- Choose your MP4. The track table shows H.264 video as Re-encoded to VP8 and AAC audio as Re-encoded to Opus.
- Pick Balanced or Faster, and cap the height if the source is large. Smaller frames encode much faster.
- Press Convert to WebM and download the result, with a preview to check it plays.
Why VP8 and not VP9
WebM allows VP8, VP9 or AV1 video. VP9 compresses better, but we tested the VP9 encoder in the WebAssembly engine this site ships and it crashed with an out-of-bounds memory error on 640x360 and 1080p inputs in every setting we tried. A converter that sometimes crashes is worse than one that does one thing reliably, so this page only offers VP8, which encoded without problems in our tests. Expect a VP8 WebM to be somewhat larger than the VP9 equivalent and often similar to or larger than the H.264 MP4 you started with.
If the MP4 already holds VP8, VP9 or AV1 video (uncommon) and AAC audio, Auto copies the video and re-encodes only the audio to Opus, so those cases are fast. The WebM format cannot hold AAC, so audio is always converted unless it is already Opus or Vorbis.
When WebM is the right choice
- A short looping clip for a web page with a modern-browser-only audience, where you want an open format rather than H.264.
- A site or tool that explicitly asks for a WebM upload.
- You want the picture and sound in an open, royalty-free container and codec set (VP8 and Opus).
If you only want a smaller MP4, the video compressor is the better tool: H.264 is usually smaller and plays everywhere.
Speed, size and settings
VP8 is the quicker of the two encoders in this build. In our own test runs, VP8 at 1920x1080 encoded at roughly 16 frames per second and at 640x360 at roughly 40 frames per second on one test machine. A 60-second 1080p clip at 30 fps (1,800 frames) would take on the order of two minutes at the Faster setting; a ten-minute clip about twenty. Results vary a lot by device. Balanced uses a higher bitrate cap and slower search for better quality; Faster uses the quickest settings and larger files for the same visual quality.
Audio becomes Opus at 128 kbps (256 kbps for surround). Subtitles in the MP4 are converted to WebVTT, the only text format WebM supports; picture subtitles are left out. Videos are output in 8-bit 4:2:0, so 10-bit and HDR sources are flattened and the tool warns you.
Worked example
A 20-second 1920x1080 H.264/AAC clip of 24 MB. Choose Balanced and cap the height at 720p. The table shows video Re-encoded to VP8 and audio Re-encoded to Opus, and the job runs for under a minute at that size. The resulting WebM is in the same range of file size as the MP4, which is normal for VP8.
Common mistakes
- Expecting WebM to be smaller than H.264. With VP8 it usually is not.
- Selecting Remux only for an H.264 file. WebM cannot hold H.264, so the tool refuses and explains.
- Converting at 4K. Cap the height first.
- Using WebM for iPhone or older Safari. Support has improved, but MP4 is still the safest for Apple devices.
Your file never leaves your browser
The video is read from your disk by FFmpeg running as WebAssembly in a sandboxed frame. The frame's content security policy blocks every network connection except local blob and data URLs and contains no ads or analytics. The WebM is built in your browser's memory and saved through a normal download. The engine itself is the only thing that downloads, and it only starts after you pick a file.
Limits and what this does not do
- VP8 and Opus only. No VP9, AV1 or Vorbis encoding.
- One file at a time up to 2 GB; warning above 500 MB.
- No alpha-channel (transparent) output, no editing, no batch.
- Encoding is single-threaded and slower than desktop software.
Common mix-ups
-
Often assumedWebM is MP4 with a different extension.
What the source saysMDN says WebM is based on Matroska and that compliant implementations must support the VP8 and VP9 video codecs and the Vorbis and Opus audio codecs. MP4 usually holds H.264 and AAC, so the streams must be re-encoded. [1]
-
Often assumedRe-encoding to WebM keeps the picture exactly as it was.
What the source saysMDN's video codec guide says most video codecs are lossy, so decoded video does not precisely match the source and more compression means more lost detail. Encoding H.264 into VP8 is a fresh lossy pass. [2]
Checked against these sources on .
Frequently asked questions
Can this make a VP9 WebM?
No. The VP9 encoder in the WebAssembly build crashed in our tests, so this page offers VP8 with Opus audio only. VP8 files play in all current browsers.
Is a VP8 WebM smaller than my MP4?
Usually not. VP8 is less efficient than H.264, so at similar quality the file is the same size or larger.
Why is audio always converted?
WebM cannot hold AAC. AAC audio is re-encoded to Opus; audio that is already Opus or Vorbis is copied.
How long does the conversion take?
VP8 encoded 1080p at roughly 16 frames per second and 360p at roughly 40 in our tests. A short clip takes about a minute or two. Cap the height and choose Faster for long videos.
Can I convert a MOV or MKV to WebM here too?
Yes. Any of MP4, M4V, MOV or MKV is accepted; the track table shows what is copied and what is encoded.
Do subtitles survive?
Text subtitles are converted to WebVTT. Picture-based subtitles cannot be stored in WebM and are left out with a warning.
Will the WebM play on iPhone or Safari?
Recent Safari versions play WebM with VP8 and Opus, but older ones do not. If your audience includes older Apple devices, keep the MP4.
Is my video uploaded?
No. It is encoded on your device inside a frame that has no network access.
Sources
Last checked
- WebM container guidelines — WebM allows only VP8, VP9 or AV1 video with Vorbis or Opus audio
- FFmpeg wiki: VP8 encoding guide — constrained-quality mode with -crf and a maximum -b:v
- FFmpeg codecs documentation — the encoders used here (libx264, libvpx, aac, libopus) and their options
- MDN: media container formats — which codecs each container can hold and where browsers can play them
- MDN: video codecs used on the web — H.264, HEVC, VP8, VP9, AV1 and MPEG-4 Part 2 support and licensing notes
- ffmpeg.wasm project — FFmpeg compiled to WebAssembly, the engine this page runs in your browser
Runs entirely in your browser. Your file is read on your device and is never uploaded.