Step 1: Share your MPEG files using the button above or by drag and drop.
Step 2: Click the 'Transform' button to start the transformation.
Step 3: Grab your converted WebM files.
MPEG to WebM Transformation FAQ
How do I re-encode MPEG to WebM without losing video quality?
+
Upload your MPEG file and the converter runs a CRF-based re-encode targeting visually-lossless WebM output (CRF 18 by default, lower values = larger file / higher quality). The codec is chosen to match the WebM container — H.264 for broad-compat MP4, H.265 for size-efficient MKV, VP9 for WebM, AV1 for newer pipelines. The video is MPEG-1 or MPEG-2 with MP2 or AC-3 audio, multiplexed into a stream designed to be decoded by fixed-function hardware. WebM is deliberately narrow: VP8 or VP9 video (AV1 more recently) with Vorbis or Opus audio, and nothing else.
My MPEG footage shows comb lines on movement — will that carry into the WebM?
+
It will unless you deinterlace, and MPEG content very often is interlaced because the format comes from the broadcast and DVD era. Interlaced frames store two half-height fields captured a fiftieth of a second apart; on a progressive-scan phone or monitor that reads as horizontal combing on anything that moves. Turn on the deinterlace option and the encoder weaves the fields into whole progressive frames before writing the WebM. MPEG here means an MPEG-1 or MPEG-2 program stream, the format standardised for Video CD and then for DVD and broadcast television.
Can I add selectable subtitles once the file is WebM?
+
Yes. MPEG has no usable soft-subtitle track, so subtitles for MPEG content had to be burned into the picture or shipped as a separate sidecar file. WebM carries subtitles as their own selectable stream, so after conversion you can attach an SRT track the viewer can switch on, switch off or restyle.
My MPEG has several audio tracks — do they all survive into the WebM?
+
Not dependably. MPEG stores multiple audio streams as first-class tracks, but WebM playback support past the first track is inconsistent, so most players will only ever expose one. Choose the track you actually want before converting; the others are better extracted to their own files than left in a container that hides them. MPEG program streams are decoded by literally every DVD player, set-top box and broadcast chain ever built, and they tolerate bit errors gracefully. WebM is a poor fit anywhere outside a browser — video editors, phones’ native galleries and Smart TVs largely ignore it.
Will the WebM play in a browser when the MPEG would not?
+
Yes, and that is usually the whole reason for the conversion. An MPEG embedded in a web page either shows a broken player or forces a download, because browsers ship no decoder for it. WebM plays inline through the native HTML5 video element with no plugin and no external application. WebM plays natively in every modern browser with no plugin, no licence fee and no patent exposure, which makes it the default for web-embedded video.
Is it worth converting old MPEG recordings to WebM at all?
+
For anything you intend to keep, yes. MPEG belongs to an earlier generation of video tooling and the software that reads it is steadily disappearing from phones, browsers and operating systems. Moving the footage to WebM now, while a clean decoder still exists, is the difference between an archive you can open in ten years and one you cannot. MPEG-2 needs roughly four to six times the bitrate of H.264 for the same picture, and its content is frequently interlaced, which looks combed on modern displays.
Which video codec does the WebM output use?
+
It depends on the WebM container. MP4 defaults to H.264 for the broadest playback support across phones, browsers, and Smart TVs. MKV defaults to H.265 / HEVC for roughly half the file size at equivalent quality. WebM defaults to VP9. The advanced options expose explicit codec choice if you need to override. WebM is a strict subset of Matroska that Google published in 2010 specifically to give HTML5 video a royalty-free container.
Will my audio track survive MPEG to WebM conversion?
+
Yes. When MPEG and WebM share an audio codec (e.g. both carry AAC), audio is re-muxed with no re-encode — bit-identical. When the codecs differ, audio is transcoded to AAC / Opus / Vorbis depending on what the WebM container supports. Multi-track audio (commentary, alternate languages) is preserved.
Can I keep the original framerate when converting MPEG to WebM?
+
By default yes — a 24fps MPEG stays 24fps in WebM; a 60fps MPEG stays 60fps. If you need to change rate (e.g. interlaced 29.97 → progressive 30, or 60 → 30 for upload limits), the framerate option handles 3:2 pulldown, deinterlacing, and frame-blending in the same encode pass.
How much will the file size change going from MPEG to WebM?
+
Same-codec re-mux (MPEG H.264 → WebM H.264 just changing container): nearly identical size. Codec change can swing dramatically: H.264 → H.265 typically halves the file at the same visual quality; VP9 is roughly comparable; AV1 cuts another 20-30% but is slower to encode.
Will the WebM file play on iPhone, Android, and Smart TVs?
+
MP4 / H.264 plays natively on every modern device. MOV / H.264 plays on Apple devices and most TVs but not always on older Android. MKV needs VLC on iOS. WebM is browser-first. The advanced options include a "device compatibility" preset that picks the safest WebM codec / container for your target.
How long does converting a 1-hour MPEG video to WebM take?
+
Same-codec re-mux is near-instant — 30 to 60 seconds for a 1-hour file. A full codec re-encode runs at roughly 0.3-0.7x source duration on our GPU pipeline, so a 1-hour MPEG → WebM finishes in 18-40 minutes depending on resolution and target codec.
