MPG to OGA Converter

MPG to OGA — Which Codec Should Go Inside the Ogg Wrapper?

Converting an MPG to .oga discards the video and keeps the soundtrack in Xiph.Org's audio-only Ogg container. The real decision is not the extension — it is which of the four codecs on this page you put inside it, because they behave very differently once you start touching the bitrate and sample-rate controls. Short answer: leave it on Vorbis unless you have a specific reason not to. Vorbis is the default, it is what "Ogg audio" means to almost every player, and it is the only one of the four whose quality controls all behave the way the labels suggest.

The Four Codecs This Page Offers

When to Stay on Vorbis

• You want an open, royalty-free file that plays without a plug-in in Chrome, Firefox, Edge and Safari 18.4 or later — about 95% of browsers by usage share.
• The target is a game engine: Unity, Godot and Unreal all import Ogg Vorbis directly.
• You are uploading to Wikimedia or another project with a free-format requirement.
• You want the bitrate controls to mean what they say. On Vorbis, Quality Preset maps to the encoder's own quality scale (roughly -q:a 10 at the top preset down to -q:a -1 at the bottom), and the bitrate modes set real bitrates.

When Another Codec Earns the Switch

• Opus if the file is going somewhere modern and size matters — it holds up far better than Vorbis below 96 kbps, which is exactly where long speech recordings live. It is also the right voice codec, not Speex.
• FLAC only if lossless matters more than control. Understand the trade: the Quality Preset, Constant Bitrate, Custom Bitrate and Specific file size controls all still render, and none of them can change a lossless encode. You get whatever the encoder's default compression does.
• Speex effectively never. It is kept for compatibility with old voice archives, and choosing it forces the audio down to 8 or 16 kHz because "Original" is removed from the sample-rate list.

How to Convert MPG to OGA

1. Upload Your MPG File: Drag and drop your .mpg or .mpeg file, or click "Add Files" to browse. Both extensions name the same MPEG program stream, and several recordings can be queued and converted with one set of settings.
2. Confirm the Audio Codec: Vorbis is selected. FLAC, Opus and Speex are the alternatives — read the table above before switching, because each one changes which of the controls below still do anything.
3. Set File Compression, Audio Channel or Trim: File Compression opens on Quality Preset with no particular preset preselected; Constant Bitrate offers 8–384 kbps and sits on 128 kbps, Custom Bitrate takes a typed value, and Specific file size targets an output size. Audio Channel folds a stereo recording to Mono, and Trim takes a Start time and Duration in seconds or HH:MM:SS.sss.
4. Convert and Download: Click Convert and save the .oga. Files upload over an encrypted connection, are processed on our servers, and are deleted automatically after a few hours — no sign-up, no watermark.

MPG and OGA Side by Side

Frequently Asked Questions

Why did picking "384K" under Variable Bitrate give me a constant-bitrate file?

Because that entry has no Vorbis equivalent, and the fallback is not what the label implies. Vorbis's variable-bitrate rungs in our pipeline stop at 320K. Selecting 384K finds no match, falls back to treating the label as a plain bitrate figure, and then hits the validation layer that keeps Vorbis inside a 32–320 kbps window — so what you actually get is a fixed 320 kbps encode with the variable-bitrate quality mode silently abandoned. If you want a genuine VBR encode, pick 320K or lower; if you want a specific fixed rate, use Constant Bitrate, which is the control designed for that.

I chose FLAC and none of the bitrate settings changed anything. Is that a bug?

It is a rendering gap on our side, and the output is still correct. FLAC is lossless, so "bitrate" is not a thing you can set — the encoder emits however many bits the audio needs. The Quality Preset, Constant Bitrate, Custom Bitrate and Specific file size controls all render on this page anyway because they are shared across every audio target, and for FLAC they are ignored. The one control that would genuinely matter, compression level, is hidden on .oga, so a FLAC-in-Ogg file here comes out at the encoder's default effort. If you want a lossless file with real control, MPG to FLAC exposes the compression-level setting properly.

Does Opus in an Ogg file really support 44,100 Hz?

The dropdown offers it, but Opus itself has no 44.1 kHz mode — the codec is defined for 8, 12, 16, 24 and 48 kHz only. Choosing 44100 does not fail: our validation layer detects the mismatch and snaps the encode to 48000 Hz before the encoder ever sees it. Worth knowing because running the equivalent command against raw ffmpeg does error out, so testing codec limits on the command line will not predict what happens here. The practical advice is to leave Audio Sample Rate on Original for Opus and let the pipeline resolve it.

Why does choosing Speex force a lower sample rate?

Because Speex is a narrowband and wideband speech codec and the option list reflects that: selecting it removes "Original" from Audio Sample Rate and leaves only 8000 and 16000 Hz. Any music or full-bandwidth audio in your MPG is therefore downsampled, permanently and audibly. That is correct behaviour for the codec and a good reason not to use it — Opus does everything Speex was designed for, sounds better at the same bitrate, and does not force a downsample. Speex remains on the page for compatibility with older voice archives.

Is OGA the same as OGG?

The bytes are the same kind of thing; the extension is a hint about the contents. RFC 5334 registered audio/ogg in September 2008 with .oga as the recommended extension for audio-only Ogg bitstreams, keeping .ogg registered too for backward compatibility with the Vorbis-only files that had already spread everywhere. Practically: .oga says "this is audio, whatever codec is inside", .ogg carries an old implicit assumption of Vorbis. If a specific tool insists on the older spelling, MPG to OGG produces it.

Which browsers and players open an OGA file?

Ogg Vorbis audio plays natively in Chrome from version 4, Firefox from 3.5, Edge from 17 and Opera from 10.5, and Safari reached full support in version 18.4 after several releases of partial support — around 95% of browsers by global usage share. Apple devices older than that will refuse the file, which is the single biggest reason people end up back on MP3. VLC and Audacity open OGA on every desktop platform, and Unity, Godot and Unreal import Ogg Vorbis natively.

My MPG has more than one audio track — which one gets extracted, and how much quality is lost?

One track survives, and there is no picker: the stream with the most channels is chosen, with ties going to the lowest index. On a DVD rip carrying a 5.1 main mix and a stereo commentary, the 5.1 mix wins. As for quality — program-stream audio is normally MP2, which is already lossy, so re-encoding to Vorbis stacks a second lossy generation and cannot recover anything the first pass discarded. Keeping the rate at or above the source's, or leaving Quality Preset near the top of its range, keeps that second generation inaudible for most material.

Should I convert to OGA or MP3, and what happens to my file afterwards?

Choose OGA when you want a royalty-free file for the web, a game engine, a Linux desktop or a free-format archive. Choose MP3 when maximum device compatibility matters — car stereos, older phones and any Apple device predating Safari 18.4 will take an MP3 without argument. As for the file: your upload travels over an encrypted connection, the audio is extracted and encoded on our servers, and both the upload and the result are deleted automatically after a few hours. Nothing is shared or made public, there is no sign-up and no watermark. To shorten a long recording, either set a Trim range here, cut the source first with Video Cutter, or split the finished audio with Audio Cutter, which accepts .oga.