Initializing... drag & drop files here
Supports: MPG, MPEG
If you are holding a .mpeg or .mpg file, you are holding an MPEG program stream: the DVD, VCD, and TV-capture-card format from the 1990s. It is a fine archive container and a terrible web container — no browser will decode it in a <video> tag. WebM is the opposite: it is useless as a disc format and it is the format the open web was built around. So the short answer is that you convert to WebM when the file's destination is a web page, and you leave it as MPEG when the destination is a disc, an editing timeline, or a hardware player from the DVD era.
| Property | MPEG (.mpeg / .mpg) | WebM (.webm) |
|---|---|---|
| What it is | Program stream — MPEG-1 (ISO/IEC 11172, 1993) or MPEG-2 (ITU-T H.262 / ISO/IEC 13818-2, 1995-1996) | Container derived from Matroska, published by Google in May 2010 |
| Video codec | MPEG-1 Part 2 or MPEG-2 Part 2 | VP9 (the default here), VP8, or AV1 |
| Audio codec | Typically MP2, MP3 or AC-3 | Opus (the default here) or Vorbis |
| Licensing | MPEG-2 shipped under a patent pool | Royalty-free, open BSD-style licence |
| Native web playback | None — browsers do not decode program streams | 96.25% of global browsers per caniuse: Chrome 25+, Firefox 28+, Edge 79+, Safari 16+, iOS Safari 17.4+ |
| Typical frame handling | Very often interlaced (field-based), often anamorphic 720x480 or 720x576 | Progressive; carries a pixel aspect ratio, but any resize here normalises it to square |
| Alpha channel | No | Yes (VP8/VP9 carry alpha) |
| Sweet spot | DVD authoring, capture-card archives, legacy set-top playback | HTML5 <video>, background loops, page-weight budgets |
If the file instead needs to play on phones, smart TVs, and social platforms, H.264 is the safer landing zone — use MPEG to MP4 for that.
.mpeg / .mpg files. Batch uploads are supported and every file in the batch uses the same settings.| Codec | Quality controls that actually work | Use it when |
|---|---|---|
| VP9 (default) | Quality Preset, Constant Quality (CRF 16-63), Constraint Quality, and every bitrate mode | Almost always — best size-to-quality balance and the widest WebM decode base |
| VP8 | Quality Preset and the bitrate modes only. The Constant Quality slider renders but does nothing | You need the fastest encode or you are targeting very old Android hardware |
| AV1 | Same CRF-based controls as VP9 | You want the smallest possible file and encode time does not matter |
The VP8 caveat is worth repeating because the control does not look broken: our VP8 encoder path deliberately does not emit a CRF value, since VP8 has no CRF mode. If you select VP8, set the size with Constant Bitrate, Variable Bitrate, or Specific file size instead.
VP9. It is the default video codec for every WebM output here, and it is the right pick for almost everyone: markedly more efficient than VP8 at the same visual quality, with hardware decode common on devices from roughly 2017 onward. AV1 compresses harder still but encodes far more slowly. VP8 exists mainly for legacy decode targets.
The sound survives; the codec does not. WebM only permits Opus and Vorbis audio, and MPEG program streams carry MP2, MP3, or AC-3 — so the track is decoded and re-encoded into Opus (the default) or Vorbis. It stays in sync and keeps its channel layout, but it is a fresh lossy encode, not a copy of the original stream.
Because DVD-era MPEG-2 stores non-square pixels. A 16:9 NTSC DVD is a 720x480 raster with a pixel aspect ratio that stretches it to roughly 854 wide at playback. Leaving Video resolution on "Keep original" carries that ratio into the WebM intact, but any resize option flattens the pixel aspect to square — so a 480p preset on a 720x480 anamorphic source produces a 3:2 picture instead of 16:9. If you need to resize anamorphic material, use Width x Height and type the display dimensions yourself: 854 x 480 for 16:9 NTSC, 640 x 480 for 4:3 NTSC, 1024 x 576 for 16:9 PAL, or 768 x 576 for 4:3 PAL.
No. There is no deinterlacing filter anywhere in this conversion, so if your MPEG-2 source is field-based, the comb pattern is re-encoded into the WebM exactly as it appears. A WebM cannot signal interlacing the way MPEG-2 can, so the combing simply becomes part of the picture. Deinterlace in a video editor first if that matters, then convert.
Because VP8 has no constant-quality mode. The slider renders for VP8 in the current UI, but the encoder path skips it — in our testing, the same 6-second clip encoded through the VP8 constant-quality path came out byte-for-byte identical (423,402 bytes) at slider position 10 and at position 50. Use Constant Bitrate, Variable Bitrate, or Specific file size on VP8; the CRF sliders only bite on VP9 and AV1.
It depends entirely on the source bitrate, but the direction is reliable: MPEG-2 was designed around DVD bitrates of roughly 4-9 Mbps for standard definition, and VP9 reaches similar perceptual quality at a small fraction of that. If you need a specific number rather than a ratio, switch File Compression to Specific file size and type the megabyte target you want.
No — the preset list sets height only, and the width follows from the source raster. That is fine for progressive square-pixel footage and wrong for anamorphic DVD material, where the stored raster is not the display shape. If you need exact dimensions, use the Width x Height option instead, which is also the correct place to fix anamorphic DVD material.
<video> tag?Yes, for the overwhelming majority of visitors. caniuse currently puts WebM at 96.25% global support, with Chrome from 25, Firefox from 28, Edge from 79, desktop Safari from 16.0, and iOS Safari from 17.4. The gap is older Apple hardware, so if you support long-tail iOS devices, ship an H.264 MP4 as a second <source> — you can produce one from the same file with MPEG to MP4.
Yes. Trim takes a start time and a duration in either seconds or HH:MM:SS.sss, so you can encode a single scene out of a long capture without touching the rest. For a longer session of cutting where you want to preview the in and out points first, Video Cutter accepts .mpeg and .mpg directly.