MPG to WEBA Converter

MPG to WEBA Converter

MPG is an MPEG program stream — the VCD, DVD and digital-TV container that interleaves MPEG-1 or MPEG-2 video with an audio track. WEBA is the audio-only counterpart of WebM: the .weba extension exists purely to signal "this WebM file has no video in it". This conversion throws away the picture, decodes whatever audio the program stream was carrying, and re-encodes it as Opus inside a WebM container. That combination is what the modern web serves audio with, and it is dramatically smaller than the MPEG-1 Layer II or Dolby Digital track a DVD-era file usually holds.

WEBA Format at a Glance

MPG Audio at a Glance

Because DVD-Video standardises on 48 kHz, most .mpg files feed Opus its preferred rate with no resampling at all. Leave Audio Sample Rate on Original and that is what happens.

How to Convert MPG to WEBA

1. Upload Your MPG File: Drag and drop the .mpg or .mpeg file onto the page, or click "+ Add Files" to browse. Files upload over an encrypted connection, are processed on our servers, and are deleted automatically a few hours later — no sign-up, no watermark, never shared or made public.
2. Choose a Rate-Control Mode Under File Compression: Quality Preset is the mode this page starts in. Switch to Constant Bitrate and pick a value from the 8–384 kbps list if you want a predictable, repeatable result, or Custom Bitrate to type an exact figure, or Specific file size to name a size and have the bitrate solved for you.
3. Set Audio Channel, Sample Rate and Trim (Optional): Audio Channel offers Original, Mono or Stereo; Audio Sample Rate offers Original plus 8000, 12000, 16000, 24000, 44100 and 48000 Hz; Trim takes a Start time and Duration in either plain seconds or HH:MM:SS.sss.
4. Convert and Download: Click Convert and download the .weba. If a player refuses the extension, rename it to .webm — the bytes are already a WebM file.

What Renders on This Page — and What Does Not

There is no Audio Codec control here. Every entry in that group, Opus and Vorbis included, is hidden on the WEBA path, and the output codec is decided by the extension itself: .weba maps to Opus, which is handed to libopus. So there is nothing to choose and nothing to get wrong — but equally, you cannot ask this page for a Vorbis-in-WebM file. If you need Vorbis, target MPG to OGG instead.

What does render: File Compression (Quality Preset, Specific file size, Custom Bitrate, Constant Bitrate), Audio Channel, Audio Sample Rate, Trim, and the File extension selector. There is no video control of any kind, because the video stream is switched off before encoding — this is a strict audio extraction.

Picking a Bitrate

Xiph's own recommendations are the best starting point, since they wrote the codec: 64–96 kb/s for stereo music streaming, 96–128 kb/s for stereo music storage, and 24 kb/s for mono audiobooks and podcasts, with the blunt note that "Opus at 128 KB/s (VBR) is pretty much transparent". A DVD soundtrack you want to keep sounding like the disc sits comfortably at 96–128 kbps stereo; a lecture, commentary track or home-video soundtrack is fine at 32–64 kbps, and mono halves that again.

Do not read the Quality Preset scale as if it were an MP3 quality dial. Opus's usable rate span in our pipeline runs all the way to 512 kbps, and the presets map across that whole span, so the top settings will ask libopus for far more bitrate than Opus needs to be transparent. If you care about the exact output size, Constant Bitrate or Specific file size are the honest controls.

Frequently Asked Questions

Why can't I choose Vorbis instead of Opus?

WebM permits both, but this page does not expose the choice — every codec entry in the Audio Codec group is hidden on the WEBA path and the output codec is pinned to Opus by the extension mapping. That is a deliberate simplification rather than a limitation of the container: Opus beats Vorbis at essentially every bitrate for the same content, and it is the codec browsers ship for WebM audio. If you specifically need Vorbis, use MPG to OGG, which writes Vorbis in an Ogg container.

I picked 44100 Hz and got a 48 kHz file. Is that a bug?

No, and it will not fail either. Opus has no 44.1 kHz mode at all — it operates at 8, 12, 16, 24 or 48 kHz — so our validation layer rewrites a 44100 Hz request to 48000 Hz before the encoder ever sees it. Calling ffmpeg yourself with -ar 44100 on libopus errors out; here it quietly does the sensible thing. Since DVD-sourced MPG audio is already 48 kHz, the usual result is no resampling at all.

Is the audio re-encoded, or copied straight out of the MPG?

Re-encoded, always. The MPEG-1 Layer II, AC-3, DTS or LPCM track is decoded and then compressed again as Opus. For the lossy sources that means a second generation of loss, which is why it is worth not skimping on bitrate: 96–128 kbps stereo keeps a DVD soundtrack indistinguishable from the disc in normal listening, while 32 kbps will audibly hollow out music.

What is the difference between .weba, .webm and .opus?

.weba and .webm are the same container — WebM, a constrained Matroska profile — and the shorter extension is only a hint that there is no video track inside. Renaming between them changes nothing about the bytes. .opus is different: that is a raw Opus stream in an Ogg container, which is what MPG to OPUS produces. Ogg-Opus is the better pick for desktop audio players; WebM-Opus is the better pick for browsers and <audio> elements.

Why is the WEBA so much smaller than the audio inside the MPG?

Because you are replacing a 1990s codec with a 2012 one. A DVD's Dolby Digital track can run to 448 kbit/s and its MPEG-1 Layer II track to 912 kbit/s, while Opus reaches transparency for stereo music around 128 kbit/s. Dropping the video obviously accounts for most of the reduction, but even audio-to-audio you should expect a large saving at matched perceptual quality.

Can I pull out just one section of the soundtrack?

Yes — use the Trim control on this page rather than converting the whole file first. Set Start time and Duration, in seconds or as HH:MM:SS.sss, and only that span is encoded. Trimming the source before conversion is also the faster route for a long DVD rip, and our Video Cutter will do that on the MPG itself if you prefer to work visually.

Will a WEBA file play on my phone, TV or car stereo?

Treat it as a web format, not a device format. Browsers handle it well — caniuse lists full Opus support in Chrome 33+, Firefox 15+, Edge 14+ and Opera 20+, with Safari 11+ marked partial — but many hardware players, car head units and older set-top boxes will not even recognise the extension, let alone the codec. For those, MPG to MP3 remains the compatibility answer, and MPG to M4A the middle ground on Apple devices.

How are my files handled while this runs?

The MPG is uploaded over an encrypted connection and processed on our servers; both the upload and the finished .weba are deleted automatically a few hours later. There is no sign-up, no watermark, and files are never shared or made public. The realistic constraint on a two-hour DVD rip is upload time rather than the conversion, so trimming to the section you need before uploading is worth it when the source is large.