Convert M2TS to MOD — Free Online Tool
Convert M2TS Blu-ray and AVCHD footage to MOD format used by JVC and Panasonic camcorders, re-encoding the video with H.264 and audio with AAC into a modified MPEG-PS container. This is useful for repurposing high-definition Blu-ray source material into a format compatible with legacy camcorder-based editing workflows.
to
FFmpeg Command
Copy this command to run the same conversion locally with FFmpeg on your desktop. Download FFmpeg
Drop your M2TS 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
M2TS files store video (typically H.264 or MPEG-2) and audio inside an MPEG-2 Transport Stream container, which is designed for streaming and broadcast reliability. MOD is a proprietary variant of MPEG Program Stream used by JVC and Panasonic camcorders, and it has a fundamentally different container structure — so this conversion cannot be a simple remux. The video is fully re-encoded using the H.264 (libx264) codec at CRF 23, and the audio is transcoded to AAC at 128k bitrate. Because MOD does not support multiple audio tracks, subtitles, or chapters, only the primary video and first audio track from the M2TS source will be carried through to the output. The result is a lossy output file optimized for compatibility with camcorder-oriented software rather than preserving all the rich metadata features of Blu-ray.
What Each Flag Does
| Flag | What it does |
|---|---|
ffmpeg
|
Invokes the FFmpeg tool, which handles the full transcode pipeline — demuxing the M2TS Transport Stream, decoding video and audio, re-encoding both, and muxing into the MOD Program Stream container. |
-i input.m2ts
|
Specifies the M2TS source file as input. FFmpeg will parse its MPEG-2 Transport Stream structure to locate the video and primary audio elementary streams for processing. |
-c:v libx264
|
Re-encodes the video stream using the H.264 codec (libx264). This is necessary because MOD uses a Program Stream container structure that is incompatible with a direct stream copy from MPEG-2 Transport Stream, regardless of whether the source video codec matches. |
-c:a aac
|
Transcodes the primary audio track — which in a Blu-ray M2TS may be TrueHD, DTS-HD, or AC-3 — into AAC, the only audio format MOD will carry in this conversion. All secondary audio tracks from the M2TS are discarded because MOD supports only a single audio stream. |
-crf 23
|
Sets the Constant Rate Factor for the H.264 video encode to 23, which is the libx264 default and produces a good balance between visual quality and file size. For high-motion Blu-ray content, lowering this to 18 will better preserve fine detail at the cost of a larger output file. |
-b:a 128k
|
Sets the AAC audio bitrate to 128 kilobits per second. This is a reasonable default for stereo audio but represents a substantial reduction from lossless Blu-ray audio sources like TrueHD. Increase to 192k or 256k if audio fidelity from the source is a priority. |
output.mod
|
Specifies the output filename with the .mod extension, which tells FFmpeg to mux the encoded video and audio into the modified MPEG Program Stream container that JVC and Panasonic camcorder software expects. |
Common Use Cases
- Repurposing ripped Blu-ray scenes into MOD files so they can be imported into legacy JVC or Panasonic camcorder editing software that only recognizes MOD format.
- Archiving AVCHD footage from an M2TS-recording camcorder into a MOD-compatible format for editing on an older dual-format camcorder workstation.
- Creating a lower-complexity video file from Blu-ray M2TS source content for playback on hardware media players that support MOD but not M2TS or Transport Stream formats.
- Converting M2TS broadcast captures to MOD for use in camcorder-native file management tools that organize footage by the MOD naming convention.
- Preparing Blu-ray-sourced video clips in MOD format for direct transfer to JVC Everio camcorder memory cards for on-device playback.
- Stripping the multi-track audio, subtitle, and chapter complexity from an M2TS file down to a simple single-track MOD file when only the primary video and audio stream are needed.
Frequently Asked Questions
Yes — this is a lossy conversion in both directions. The M2TS source may contain lossless or high-bitrate audio tracks and high-quality Blu-ray video, all of which are re-encoded rather than copied. The H.264 re-encode at CRF 23 is visually near-transparent for most content, but the process is generational — each re-encode introduces some quality loss compared to the source. If your M2TS source was already H.264, you are decoding and re-encoding the same codec, which compounds any existing compression artifacts.
M2TS uses an MPEG-2 Transport Stream container while MOD uses a modified MPEG Program Stream container — these are fundamentally different multiplexing structures and are not byte-compatible. Even if both files contain H.264 video, the stream framing, timing references, and container metadata are organized entirely differently. A direct stream copy would produce an unplayable or malformed MOD file, so a full transcode is required.
They are dropped. MOD does not support multiple audio tracks, subtitle streams, or chapter markers, so FFmpeg will map only the first (default) audio track to the output and discard all remaining audio tracks and subtitle streams. If you need a specific non-default audio track — for example, a DTS-HD or secondary language track — you would need to modify the FFmpeg command to explicitly select it using the -map flag before running the conversion.
TrueHD and DTS-HD are lossless or high-bitrate audio formats that MOD cannot carry. FFmpeg will decode whichever audio track it selects from the M2TS and re-encode it as AAC at 128k bitrate for the MOD output. This is a significant reduction in audio fidelity from lossless Blu-ray audio, though for most dialogue-heavy content the result is acceptable. If you need higher audio quality, increase the -b:a value to 192k or 256k in the FFmpeg command.
To change video quality, adjust the -crf value — lower numbers (e.g., 18) produce better quality at larger file sizes, while higher numbers (e.g., 28) produce smaller files with more compression. To select a specific audio track from the M2TS, add -map 0:v:0 -map 0:a:1 before the output filename, replacing '1' with the zero-indexed track number you want. For example, to pick the second audio track and increase audio bitrate: ffmpeg -i input.m2ts -map 0:v:0 -map 0:a:1 -c:v libx264 -c:a aac -crf 18 -b:a 192k output.mod
Yes, with a shell loop. On Linux or macOS, run: for f in *.m2ts; do ffmpeg -i "$f" -c:v libx264 -c:a aac -crf 23 -b:a 128k "${f%.m2ts}.mod"; done. On Windows Command Prompt, use: for %f in (*.m2ts) do ffmpeg -i "%f" -c:v libx264 -c:a aac -crf 23 -b:a 128k "%~nf.mod". The browser-based tool processes one file at a time, so the FFmpeg command is especially useful for batch jobs involving many M2TS files.
Technical Notes
MOD is a camcorder-specific container format created by JVC and Panasonic that predates widespread H.264 adoption — original camcorder MOD files typically contained MPEG-2 video, but modern FFmpeg maps libx264 to the MOD output, which is broadly compatible with software that reads MOD. One important limitation is that MOD does not carry stream metadata such as language tags, subtitle tracks, chapter markers, or secondary audio streams, all of which are valid features of M2TS. Any such data from the source will be silently discarded. M2TS files from AVCHD camcorders are typically 1080i or 1080p H.264 streams; re-encoding these at CRF 23 will produce a visually similar result but at a different bitrate profile than the original AVCHD specification. Blu-ray M2TS sources often have very high video bitrates (20–40 Mbps), and the CRF 23 output will typically be a fraction of that size. The MOD format also does not support transparency (alpha channels), though M2TS does not either, so this is not a practical concern for this conversion path.