MPG to OGV — Should You Convert to Theora, or to WebM?
If you need a patent-free, open video format, MPG (an MPEG-1 or MPEG-2 file) converts cleanly to OGV — the Ogg container, classically carrying Theora video with Vorbis audio (this tool preselects the more efficient VP8, with Theora as the legacy option). But be honest about timing: Theora is effectively obsolete. Chrome disabled it by default in version 120 and Chromium removed it in 123 (March 2024), and Firefox disabled it by default in 126, so OGV only makes sense for a few specific workflows today. For everything else, MPG to WebM is the open format you actually want.
OGV (Theora) vs WebM — Side by Side
| Property | OGV (Ogg Theora) | WebM (VP9 / AV1) |
|---|---|---|
| Container origin | Xiph.Org Foundation (Ogg, ~2002) | Google / WebM Project (2010) |
| Video codec | Theora — bitstream frozen since June 2004 | VP8, VP9, AV1 — actively developed |
| Audio codec | Vorbis, Opus, FLAC | Vorbis, Opus |
| Royalty status | Fully royalty-free | Fully royalty-free |
| Compression efficiency | Weak — larger files at equal quality | Strong — much smaller at equal quality |
| Chrome support | Removed in v123 (March 2024) | Yes (all current versions) |
| Firefox support | Disabled following Chromium | Yes |
| Safari support | Never supported | WebM since Safari 14.1 (2021) |
| Linux (libre distros) | Ships out of the box | VP8/VP9 ship; AV1 widely available |
| Best for | Wikimedia uploads, strictly-libre setups | Modern web, HTML5 <video>, smaller files |
When to Pick OGV
- Wikipedia and Wikimedia Commons — Wikimedia accepts only patent-free formats. Ogg Theora is explicitly on the accepted list (so is WebM), while MPEG-1/MPEG-2 is not. If a contribution workflow specifically asks for Ogg Theora, OGV is the right output.
- Strictly-libre Linux distributions — Fedora, Trisquel, and Debian main avoid non-free codecs by default. Theora playback works without adding extra repositories.
- Legacy toolchains that already expect Ogg Theora — older CMS plugins, jPlayer setups, and archival pipelines that were built around
.ogvfiles.
When to Pick WebM Instead
- Web embedding in 2026 — Theora playback is gone from Chrome and Firefox, so an OGV embedded in a
<video>tag will not play for most visitors. WebM plays in Chrome, Firefox, Edge, and Safari 14.1+. - Smaller files — VP9 and AV1 produce dramatically smaller files than Theora at the same visual quality, which matters for bandwidth and storage.
- Anything you intend to keep or share broadly — WebM is royalty-free like OGV but is still actively maintained, so it is the safer long-term open format. See MPG to WebM.
How to Convert MPG to OGV
- Upload Your MPG File: Drag and drop or click "Add Files" to select your MPG or MPEG file. MPEG-1 and MPEG-2 sources both decode cleanly, and you can queue several files to convert in one batch.
- Pick a Quality Preset: The OGV output uses VP8 video by default, with Vorbis audio; Theora is selectable under Video Codec for legacy Ogg tooling. Under Advanced Options, choose a Quality Preset — the default is "Very High (Recommended)" — or switch to Constant Quality, target a specific file size, or set a constant/variable bitrate. You can also swap Vorbis audio for Opus.
- Resize or Trim (Optional): Keep the original resolution, choose a Preset Resolution (1080p / 720p / 480p / 360p / 240p), set a custom Width x Height, scale by percentage, or trim to a Time Range with start and duration.
- Convert and Download: Click Convert. Files are uploaded over an encrypted connection, processed on our servers, and deleted automatically after a few hours — no sign-up, no watermark, never shared.
What Is Actually Inside Your MPG File?
.mpg is not one format. It is a family: an MPG can carry MPEG-1 video (Video CD era) or MPEG-2 video (DVD and broadcast era), and the two decode very differently. Knowing which you have tells you what quality ceiling the OGV can possibly reach — the encoder can only re-package what the source already contains.
| Property | MPEG-1 | MPEG-2 |
|---|---|---|
| Standard | ISO/IEC 11172 (1993) | ISO/IEC 13818 (1995-96) |
| Video codec | MPEG-1 Part 2 | MPEG-2 Part 2, also published as ITU-T H.262 |
| Usual audio | MPEG-1 Audio Layer II (sometimes Layer III) | Layer II, AC-3, or AAC |
| Typical frame size | 352 x 240 (NTSC) / 352 x 288 (PAL) | 720 x 480 (NTSC) / 720 x 576 (PAL), up to HD |
| Typical bitrate | Around 1.15 Mbps on Video CD | 4-9 Mbps on DVD-Video |
| Interlacing | Progressive only | Progressive and interlaced |
| Where you met it | Video CD, early web clips | DVD-Video, DVB and ATSC broadcast, camcorder captures |
A low-resolution MPEG-1 source will not gain sharpness in OGV, so leave the resolution on "Keep original" rather than upscaling. An interlaced MPEG-2 source is the trickier case: no deinterlacing is applied, so the two woven fields are carried into the OGV frames as stored and moving subjects can show comb lines — deinterlace in a desktop editor first if that matters.
Frequently Asked Questions
Is OGV worth using instead of WebM in 2026?
For most purposes, no. Theora's bitstream has been frozen since June 2004, Chrome disabled it by default in version 120 and Chromium removed it in 123 (March 2024), and Firefox disabled it by default in 126. OGV is still worth it only for Wikimedia uploads that ask for Ogg Theora and for strictly-libre Linux setups. For general web video or anything you want to keep, MPG to WebM is smaller, sharper, and still royalty-free.
Will converting MPG to OGV improve quality?
No. Both MPG (MPEG-1/MPEG-2) and OGV (VP8 or Theora) are lossy formats, so this is a lossy-to-lossy re-encode. You cannot recover detail the original MPG already discarded. To keep quality loss minimal, use the "Very High" or a Constant Quality preset, but the output will never look better than the source.
Why is my OGV file sometimes larger than the original MPG?
The Ogg codecs — the legacy Theora option especially — are not dramatically more efficient than the MPEG-2 used in many MPG files, so at matching quality the OGV can end up larger. In our testing, a 60-second 720p MPG re-encoded to OGV at the Very High preset was roughly comparable to or slightly larger than the source, while the same clip converted to WebM (VP9) came out noticeably smaller. If size is your priority, choose MPG to WebM.
Can OGV play in browsers now that Chrome dropped Theora?
Largely no. Chrome disabled Theora by default in version 120 and Chromium removed the decoder in 123, Firefox disabled it by default in 126, and Safari never supported it. An OGV embedded in an HTML5 <video> tag will fail to play for most visitors today. If you need in-browser playback, convert to WebM or MP4 and use OGV only where a specific tool requires Ogg Theora.
Should I keep Vorbis audio or switch to Opus?
Vorbis is the historical Ogg audio codec and the safest default for OGV — it has the broadest support in Theora-era players and on Linux media stacks. Opus is newer and more efficient at low bitrates and works in modern Ogg players, but a few older Theora-only tools may not read it. Pick Vorbis for maximum compatibility, Opus for the best quality-per-byte.
Is OGV accepted on Wikipedia and Wikimedia Commons?
Yes. Wikimedia accepts only patent-free media, and Ogg Theora is on the accepted list alongside WebM. MPEG-1/MPEG-2 files are not accepted, which is the most common reason people convert MPG to OGV. Wikimedia transcodes uploaded OGV to WebM server-side for browsers that no longer decode Theora.
What is the difference between .ogv, .ogg, and .oga?
They are all the same Ogg container with different extensions that describe the payload. Xiph.Org, which created Ogg, published a naming convention to end the confusion caused by .ogg being used for everything: .ogv for video (with or without audio), .oga for audio-only, .ogx for anything multiplexed or unusual, and .ogg reserved for its historical meaning of a Vorbis audio file. This page produces .ogv because the output carries a video stream. If a tool insists on .ogg, renaming the file usually works — the container bytes do not change — but the correct label for a Theora video is .ogv.
My MPG is from a DVD or camcorder capture and looks combed after converting. Why?
That is interlacing. DVD-era and broadcast MPEG-2 often stores each frame as two interleaved fields captured a fraction of a second apart, which a TV displayed correctly but a computer shows as horizontal comb lines on anything moving. The encode does not deinterlace — the woven fields are carried into the OGV frames as they are, so the combing stays. To remove it, run a deinterlace filter in a desktop editor first, then convert the progressive export; and for a file you actually intend to watch, MPG to MP4 or MPG to WebM gives you a modern codec that holds quality far better than Theora-era OGV.