Convert MPG to WTV — Free Online Tool
Convert MPG files (MPEG-1/2 video with MP2 audio) to WTV format, the Windows Media Center broadcast recording container that uses H.264 video and AAC audio. This conversion modernizes legacy VCD- or DVD-era MPEG streams into a DVR-compatible format recognized by Windows Media Center and compatible playback software.
to
FFmpeg Command
Copy this command to run the same conversion locally with FFmpeg on your desktop. Download FFmpeg
Drop your MPG file here
or click to browse
Free — no uploads, no signups. Your files never leave your browser.
Settings
Note: Browser-based encoding uses approximate quality targets. For precise CRF compression, copy the FFmpeg command above and run it on your desktop.
Estimated output:
Conversion Complete!
DownloadHow It Works
MPG files carry video encoded with MPEG-1 or MPEG-2 and audio typically encoded as MP2 — the codec trio that powered VCD, DVD, and analog broadcast pipelines. WTV requires a full transcode because neither codec is native to the WTV container: the MPEG-2 video stream is re-encoded into H.264 using libx264 (a far more efficient modern codec), and the MP2 audio stream is re-encoded into AAC. The result is a WTV file with broadcast metadata support, multiple audio track capability, and subtitle embedding support — features MPG lacks entirely. Because both stages involve lossy-to-lossy re-encoding, some generation loss is inherent, though at CRF 23 and 128k AAC the output quality is typically indistinguishable from the MPG source for most content.
What Each Flag Does
| Flag | What it does |
|---|---|
ffmpeg
|
Invokes the FFmpeg binary — the open-source multimedia processing engine that handles the demuxing of the MPG program stream, transcoding of both video and audio, and muxing into the WTV container. |
-i input.mpg
|
Specifies the input MPG file containing the MPEG-2 (or MPEG-1) video stream and MP2 audio stream that will be transcoded. FFmpeg detects the MPEG program stream format automatically. |
-c:v libx264
|
Selects the libx264 encoder to transcode the incoming MPEG-2 video into H.264, replacing the decades-old MPEG-2 codec with a modern, far more compression-efficient standard that the WTV container expects. |
-c:a aac
|
Selects FFmpeg's built-in AAC encoder to transcode the MP2 audio from the MPG source into AAC, the default and most compatible audio codec for the WTV container. |
-crf 23
|
Sets the Constant Rate Factor for the H.264 encode to 23 — the libx264 default, which delivers a good balance of visual quality and file size for standard-definition MPG broadcast content. Lower values (e.g., 18) improve quality; higher values (e.g., 28) reduce file size. |
-b:a 128k
|
Sets the AAC audio bitrate to 128 kilobits per second, which is appropriate for the MP2 audio streams typical in MPG broadcast recordings and produces clean stereo audio in the WTV output. |
output.wtv
|
Specifies the output filename with the .wtv extension, which instructs FFmpeg to mux the transcoded H.264 video and AAC audio into the Windows Television container format. |
Common Use Cases
- Importing digitized VHS or broadcast recordings stored as MPG files into a Windows Media Center library, where WTV is the native DVR format for organized playback and metadata tagging.
- Archiving old MPEG-2 broadcast captures from a TV tuner card in a more storage-efficient format, since H.264 in WTV achieves similar visual quality at roughly half the bitrate of MPEG-2.
- Preparing legacy MPG content for playback on a Windows Home Theater PC (HTPC) setup that indexes and manages WTV recordings from Windows Vista or Windows 7 Media Center.
- Converting DVD-ripped MPG files to WTV so they can be browsed alongside recorded television in a unified Media Center interface with episode metadata.
- Packaging MPEG broadcast segments from older capture devices into WTV for use with DVR management tools and third-party Media Center extenders that expect WTV-wrapped H.264.
- Reducing the file size of large MPEG-2 MPG recordings before long-term storage by transcoding to H.264 inside WTV, taking advantage of modern compression efficiency.
Frequently Asked Questions
Yes, some quality loss is unavoidable because this is a lossy-to-lossy transcode — the MPEG-2 video and MP2 audio from the MPG are fully re-encoded into H.264 and AAC respectively. At the default settings (CRF 23 for video, 128k for audio), the output is generally visually comparable to the MPG source for standard-definition broadcast content. For higher-quality MPG sources, lowering the CRF value (e.g., to 18) in the FFmpeg command will preserve more detail at the cost of a larger file.
MPEG-2, the video codec used in most MPG files, was designed in the early 1990s and is far less efficient than H.264 (libx264) used in the WTV output. H.264 uses more advanced compression techniques — including better inter-frame prediction and entropy coding — that can deliver similar visual quality at roughly 40–60% of the MPEG-2 bitrate. This is why WTV files produced from MPG sources are frequently significantly smaller despite containing comparable image quality.
MPG files have very limited metadata support and do not carry subtitle streams, so there is effectively no metadata or subtitle content to lose during conversion. WTV natively supports subtitle embedding and broadcast metadata fields (such as title, episode, channel, and air time), but these fields will be empty in the output unless you add them manually using a tool like Windows Media Center itself or a metadata editor that understands WTV. The format upgrade gives you the capability to add rich metadata post-conversion.
WTV is a Windows-centric format originally designed for Windows Vista and Windows 7 Media Center. On Windows, VLC and Media Player Classic can open WTV files natively. On macOS and Linux, support is sparse — VLC may handle it but compatibility varies. If broad cross-platform playback is your goal, MP4 would be a more practical output container for the same H.264/AAC codec pair. WTV is best chosen specifically when Windows Media Center integration or DVR workflow compatibility is the requirement.
The video quality is controlled by the -crf flag, which accepts values from 0 (lossless) to 51 (worst quality). The default used here is 23, which suits most standard-definition MPG broadcast content. To improve quality, lower the number — for example, '-crf 18' produces noticeably sharper output with a larger file size. To reduce file size at the cost of some quality, raise the number to 28 or 35. For audio, replace '128k' after '-b:a' with '192k' or '256k' if the source MPG has high-quality MP2 audio worth preserving more faithfully.
Yes. On Windows, you can use a simple batch script: 'for %f in (*.mpg) do ffmpeg -i "%f" -c:v libx264 -c:a aac -crf 23 -b:a 128k "%~nf.wtv"'. On Linux or macOS, use: 'for f in *.mpg; do ffmpeg -i "$f" -c:v libx264 -c:a aac -crf 23 -b:a 128k "${f%.mpg}.wtv"; done'. The in-browser tool processes one file at a time and is best suited for individual conversions; the FFmpeg command is the recommended approach for batch jobs, particularly for collections of large MPEG-2 recordings.
Technical Notes
MPG is a program stream container wrapping MPEG-1 or MPEG-2 video alongside MP2 (MPEG-1 Audio Layer II) audio — a codec pairing that predates modern containers by decades and carries no support for subtitles, chapters, or multiple audio tracks. WTV (Windows Television) is a RIFF-based container introduced with Windows Vista Media Center, designed to wrap digital broadcast recordings with full metadata, multiple audio tracks, and subtitle streams. This conversion performs a complete codec transcode on both streams: libx264 replaces the MPEG-2 video encoder, producing an H.264 Annex B stream that is dramatically more compressible, and AAC replaces MP2, offering better audio fidelity at equivalent bitrates. One known limitation is that the WTV muxer in FFmpeg has historically had incomplete metadata write support compared to what Windows Media Center itself generates, so some DVR management applications may not read all expected WTV metadata fields from FFmpeg-produced files. The MPG input's lack of transparency support, subtitles, and chapters means none of these need to be mapped — the conversion is straightforward with no stream selection complexity beyond video and audio.