Step 1: Provide your MPEG files using the button above or by toss and let go.
Step 2: Click the 'Convert' button to start the conversion.
Step 3: Fetch your converted WebM files.
MPEG to WebM Conversion FAQ
How do I convert MPEG to WebM without re-encoding the video stream?
+
When the MPEG and WebM containers can both carry the same codec (H.264, H.265, VP9, AV1), the converter falls back to a remux: the elementary streams are copied byte-for-byte into the WebM container and only the wrapper changes. A remux of a 1 GB MPEG into WebM typically finishes in 5-15 seconds with zero quality loss. 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.
Will multi-track audio survive MPEG to WebM conversion?
+
Yes — every audio track in the MPEG (director commentary, alternate languages, descriptive audio) is preserved in the WebM when the target container supports multi-stream audio. MKV and MOV handle unlimited audio tracks; MP4 supports many but some hardware players only see track 1; WebM is capped at one Opus / Vorbis track. WebM is a strict subset of Matroska that Google published in 2010 specifically to give HTML5 video a royalty-free container.
Are subtitle tracks preserved when converting MPEG to WebM?
+
Soft subtitles (selectable tracks) survive when WebM can carry them: MKV holds SRT, ASS, SSA, PGS, VobSub natively; MP4 only holds mov_text (a stripped-down format). Converting an MKV with ASS styled subs to MP4 will typically downgrade them to mov_text or burn them in. Hardsubs (burned into the video) carry over regardless.
Does MPEG to WebM keep chapter markers / DVD-style navigation?
+
Chapter metadata transfers between MPEG and WebM whenever both containers support a chapter atom (MKV, MP4, MOV). WebM stores chapters in a Matroska-compatible block, so MKV <-> WebM chapters round-trip cleanly. AVI has no chapter spec at all, so an AVI source arrives with no chapters to carry across and an AVI target cannot store the ones it was handed; add markers manually afterwards if you need them.
What about MKV attachments (fonts, cover art) when going MPEG to WebM?
+
MKV is the only mainstream container that stores arbitrary attached files (TTF fonts for ASS subs, JPG cover art, fan-translated PDF inserts). Going from MPEG to WebM drops these attachments when WebM is not MKV — the elementary streams convert, but the attached payload stays in the source. Keep MPEG as a backup if you depend on attached fonts.
Which codec does the WebM output use by default?
+
The default codec is chosen to match the WebM container conservatively: MKV defaults to H.265 (HEVC) for better compression; MP4 defaults to H.264 for the widest device support; WebM defaults to VP9; AVI uses MPEG-4 ASP (DivX/Xvid lineage). Override via the advanced codec dropdown — AV1 is available for MKV / WebM where you want maximum compression and can wait through the encode.
How does HDR (HDR10, Dolby Vision) survive MPEG to WebM?
+
HDR static metadata (HDR10 mastering display values, max content light level) carries through to WebM when both containers and the chosen codec support it (HEVC, AV1 in MKV / MP4). Dolby Vision is more fragile — DV profile 5 / 7 / 8.1 in MPEG commonly survives only into MKV with HEVC; converting to a WebM container that does not carry the DV layer flattens to HDR10.
