Convert MPG to MOD — Free Online Tool
Convert MPG files (MPEG-1/2 video, common in VCD, DVD, and broadcast archives) to MOD format used by JVC and Panasonic camcorders, re-encoding the video stream from MPEG-2 to H.264 (libx264) and the audio from MP2 to AAC inside a modified MPEG-PS container. This is useful for importing legacy broadcast or disc-ripped footage into camcorder-based editing workflows that expect the MOD file structure.
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 store video as MPEG-1 or MPEG-2 streams with MP2 audio inside an MPEG program stream container. MOD files — used by JVC Everio and Panasonic SD camcorders — are also MPEG-PS-derived containers but conventionally store H.264 video with AAC audio. Because the video codecs differ (MPEG-2 in MPG vs. H.264 expected in MOD), the video stream must be fully re-encoded by libx264, not simply remuxed. Similarly, the MP2 audio track is transcoded to AAC. The re-encoding process means the conversion is computationally intensive and the output quality depends on the CRF value chosen — the default CRF 23 with 128k AAC audio produces a reasonable balance of file size and quality for standard-definition or interlaced MPEG-2 source material typical in MPG files.
What Each Flag Does
| Flag | What it does |
|---|---|
ffmpeg
|
Invokes the FFmpeg tool, which handles the full pipeline of demuxing the MPG container, decoding the MPEG-2 video and MP2 audio streams, re-encoding both, and muxing them into the MOD output container. |
-i input.mpg
|
Specifies the input MPG file containing an MPEG-1 or MPEG-2 video stream and typically an MP2 audio stream, wrapped in an MPEG program stream container. |
-c:v libx264
|
Re-encodes the MPEG-2 (or MPEG-1) video stream from the MPG source into H.264 using the libx264 encoder, which is required because the MOD container workflow expects H.264 rather than the legacy MPEG-2 codec used in the original MPG file. |
-c:a aac
|
Transcodes the MP2 audio track from the MPG source into AAC using FFmpeg's native AAC encoder, replacing the broadcast-era MP2 codec with the more modern and widely compatible AAC format expected in the MOD output. |
-crf 23
|
Sets the Constant Rate Factor for the H.264 encode at 23, which is libx264's default quality level and produces a good balance between file size and visual quality for standard-definition MPEG-2 source material typical in MPG files. Lower values (e.g., 18) increase quality and file size; higher values (e.g., 28) reduce both. |
-b:a 128k
|
Sets the AAC audio output bitrate to 128 kilobits per second, which is appropriate for stereo audio transcoded from MP2 sources typical in MPG files. If the source MPG has high-quality MP2 audio at 192k or above, increasing this to 192k or 256k will better preserve the original audio fidelity. |
output.mod
|
Specifies the output filename with the .mod extension, which signals FFmpeg to wrap the H.264 video and AAC audio into the modified MPEG-PS container structure associated with JVC and Panasonic camcorder recordings. |
Common Use Cases
- Importing archived broadcast or VCD/DVD-ripped MPG footage into a JVC Everio or Panasonic SD camcorder editing suite that organizes clips by MOD file structure
- Converting MPEG-2 news or documentary footage from a broadcast archive into the MOD format expected by legacy NLE software configured for camcorder workflows
- Preparing standard-definition MPG video captured from a DVD recorder or set-top box for playback on a camcorder with an SD card slot that reads MOD files
- Migrating a collection of MPG home video transfers (e.g., from VHS-to-DVD conversions) into the MOD format to consolidate them with existing camcorder recordings on the same storage card
- Re-encoding interlaced MPEG-2 MPG content into H.264 MOD files to reduce storage size while maintaining compatibility with camcorder-based file organization tools
Frequently Asked Questions
Yes, some quality loss is unavoidable because this conversion involves a full re-encode from MPEG-2 video to H.264 and from MP2 audio to AAC — neither stream is copied losslessly. However, H.264 at CRF 23 is generally more efficient than MPEG-2 at typical MPG bitrates, meaning the output can look comparable to or even cleaner than the source at a smaller file size. For highest fidelity, lower the CRF value (e.g., CRF 18) at the cost of a larger output file.
While MOD files originating from camcorders do use MPEG-2 video internally, many editing and playback tools that consume MOD files also accept H.264 video within the same modified MPEG-PS container structure. This tool re-encodes to H.264 (libx264) because it offers significantly better compression efficiency than MPEG-2 for the same visual quality. If you specifically need native MPEG-2 video inside the MOD container for strict camcorder compatibility, you would need to modify the FFmpeg command to use the mpeg2video codec instead of libx264.
The audio content is preserved but transcoded — the MP2 audio track from the MPG source is re-encoded to AAC at 128k bitrate in the MOD output. MP2 is a broadcast-era codec not natively supported in the MOD container ecosystem, so transcoding to AAC is necessary. If your MPG source has high-quality MP2 audio at 192k or 256k, increase the -b:a value in the FFmpeg command to 192k or 256k to retain more of that audio fidelity.
By default, FFmpeg passes interlacing flags through during re-encoding, but H.264 handles interlaced content differently than MPEG-2. For best results with interlaced MPG source material, you may want to add a deinterlace filter (e.g., -vf yadif) to the FFmpeg command before encoding to MOD, which converts the interlaced frames to progressive scan. This improves playback quality on modern displays and editing software that does not handle interlaced H.264 well.
Video quality is controlled by the -crf flag, where lower values mean higher quality and larger files, and higher values mean lower quality and smaller files. The default is CRF 23 — for archival or high-quality output, use -crf 18; for smaller files where quality is less critical, use -crf 28. You can also adjust the audio bitrate with -b:a (e.g., -b:a 192k or -b:a 256k) if your MPG source has high-quality MP2 audio you want to preserve more faithfully in the AAC output.
The displayed command processes a single file, but you can batch-convert in a shell loop. 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}.mod"; done. On Windows Command Prompt, use: for %f in (*.mpg) do ffmpeg -i "%f" -c:v libx264 -c:a aac -crf 23 -b:a 128k "%~nf.mod". Batch processing is especially relevant here because MPG archives (e.g., DVD rips or broadcast recordings) often consist of many individual episode or segment files.
Technical Notes
MPG files typically carry MPEG-2 video at fixed bitrates common in broadcast and DVD authoring (e.g., 4–8 Mbps) with MP2 stereo audio. When converting to MOD, both streams require full re-encoding: libx264 replaces mpeg2video and AAC replaces MP2. The output file uses the .mod extension, which signals camcorder-style MPEG-PS wrapping, but the internal codec profile is standard H.264/AAC rather than the native MPEG-2 used in original camcorder MOD files. Metadata such as chapter markers and subtitle streams are not supported in either format in this pipeline, so no metadata loss beyond what both formats already lack occurs. File sizes will typically decrease compared to the MPG source because H.264 is significantly more efficient than MPEG-2 at equivalent quality levels — a 1 GB MPG file may compress to 300–500 MB as MOD at CRF 23. One known limitation is that very old MPG files encoded with MPEG-1 video (e.g., from VCD sources) are also supported as input since FFmpeg handles both mpeg1video and mpeg2video decoders transparently. However, MPEG-1 source material is typically lower resolution (352×240 or 352×288) and upscaling is not applied automatically, so the MOD output will retain the original low resolution unless a scale filter is added to the command.