Convert MOD to M2TS — Free Online Tool
Convert MOD camcorder footage to M2TS, the BDAV MPEG-2 Transport Stream format used by Blu-ray discs and AVCHD devices. This tool re-encodes your JVC or Panasonic camcorder files using H.264 video and AAC audio, producing an M2TS file compatible with Blu-ray authoring software and high-definition playback systems.
to
FFmpeg Command
Copy this command to run the same conversion locally with FFmpeg on your desktop. Download FFmpeg
Drop your MOD 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
MOD files store MPEG-2 video inside a modified MPEG Program Stream container — a format proprietary to JVC and Panasonic SD-card and HDD camcorders. M2TS uses a MPEG-2 Transport Stream container, which is a fundamentally different packetization scheme designed for Blu-ray and broadcast environments. Because MOD's native MPEG-2 video codec is not retained in this conversion (the tool uses H.264/libx264 for the output), the video stream must be fully re-encoded rather than remuxed. The audio is similarly transcoded from the MOD file's AC-3 or PCM audio to AAC. The result is a standards-compliant M2TS file with a CRF 23 H.264 video stream and 128k AAC audio, suitable for Blu-ray authoring tools, AVCHD-compatible players, and NLE import.
What Each Flag Does
| Flag | What it does |
|---|---|
ffmpeg
|
Invokes the FFmpeg program, the open-source multimedia processing engine that handles all decoding, transcoding, and muxing operations in this conversion. |
-i input.mod
|
Specifies the input MOD file — the MPEG-2 Program Stream video produced by JVC or Panasonic camcorders. FFmpeg automatically detects the MOD container and demuxes its MPEG-2 video and audio streams for processing. |
-c:v libx264
|
Re-encodes the video stream using the libx264 H.264 encoder, replacing the MPEG-2 video from the MOD file with a more compression-efficient H.264 stream appropriate for M2TS containers used in Blu-ray and AVCHD workflows. |
-c:a aac
|
Transcodes the audio — typically AC-3 or PCM from the original MOD file — to AAC using FFmpeg's built-in AAC encoder, which is widely supported in M2TS playback environments including smart TVs and Blu-ray players. |
-crf 23
|
Sets the Constant Rate Factor for the H.264 encoder to 23, the default quality level. This produces a good balance between file size and visual fidelity when re-encoding the camcorder's MPEG-2 source material. Lower values (e.g., 18) yield better quality at larger file sizes. |
-b:a 128k
|
Sets the AAC audio output bitrate to 128 kilobits per second, a standard quality level appropriate for camcorder dialogue and ambient sound. For music-heavy content or high-fidelity audio, increase this to 192k or 256k. |
output.m2ts
|
Defines the output filename with the .m2ts extension, instructing FFmpeg to wrap the H.264 video and AAC audio streams inside an MPEG-2 Transport Stream container formatted for Blu-ray BDAV and AVCHD compatibility. |
Common Use Cases
- Importing old JVC Everio or Panasonic SDR camcorder footage into Blu-ray authoring software like Vegas DVD Architect or Nero Blu-ray Disc that expects M2TS-wrapped video
- Preparing MOD camcorder recordings for playback on a PlayStation 3 or 4, which natively supports M2TS files from its Blu-ray drive but may not recognize MOD files
- Archiving home video from SD-era camcorders in M2TS format alongside AVCHD recordings from a newer camera, creating a unified library with consistent container formatting
- Editing MOD footage in DaVinci Resolve or Adobe Premiere Pro by converting to M2TS, which these applications handle more reliably than the non-standard MOD container
- Creating a Blu-ray disc from older MOD camcorder footage by converting it to the M2TS format required for BDMV folder structures
- Combining MOD recordings with other M2TS clips for a multi-source video project, enabling consistent timeline handling in an NLE without format mismatches
Frequently Asked Questions
The MOD format stores MPEG-2 video, and this conversion re-encodes it to H.264 using a CRF value of 23. H.264 at CRF 23 is generally more efficient than the MPEG-2 in MOD files, so the output file can actually be smaller with comparable or better perceptual quality. That said, any transcoding step introduces some generation loss since you are decoding and re-encoding. For archival purposes, lowering the CRF value (e.g., to 18) in the FFmpeg command will preserve more detail at the cost of a larger file.
While M2TS technically supports MPEG-2 video as a stream type, the MOD container's MPEG-2 variant uses a Program Stream (PS) structure, and the audio encoding (often AC-3 or PCM) may not match what this tool's output pipeline targets. This tool standardizes on H.264 and AAC for broad compatibility, which means a full transcode is necessary. If you need to preserve the original MPEG-2 stream for strict Blu-ray spec compliance, a dedicated Blu-ray authoring tool would be more appropriate.
MOD files embed limited metadata inside the MPEG-PS container, including recording timestamps written by the camcorder. During this transcode to M2TS, that embedded camcorder metadata is generally not preserved in the output container, as FFmpeg does not map MOD-specific metadata fields to M2TS. If preserving the original recording date is important, note it separately before converting, or check the source MOD file's metadata using ffprobe before conversion.
The browser-based tool supports files up to 1GB processed entirely in your browser via WebAssembly. For MOD files exceeding that limit — which is common for longer camcorder recordings — you can copy the exact FFmpeg command shown on this page and run it locally on your desktop. FFmpeg is free, cross-platform, and handles files of any size. The command is identical to what the browser tool runs, so results will be the same.
The video quality is controlled by the -crf flag in the command. CRF (Constant Rate Factor) ranges from 0 (lossless) to 51 (lowest quality) for H.264, with 23 as the default used here. To improve quality, lower the number — for example, replace '-crf 23' with '-crf 18' for a noticeably sharper result. To reduce file size at the cost of quality, increase it to 28 or 35. You can similarly adjust audio bitrate by changing '-b:a 128k' to '-b:a 192k' or '-b:a 256k' for higher-fidelity AAC audio.
The single-file command shown here can be wrapped in a shell loop for batch processing. On Linux or macOS, use: 'for f in *.mod; do ffmpeg -i "$f" -c:v libx264 -c:a aac -crf 23 -b:a 128k "${f%.mod}.m2ts"; done'. On Windows Command Prompt, use: 'for %f in (*.mod) do ffmpeg -i "%f" -c:v libx264 -c:a aac -crf 23 -b:a 128k "%~nf.m2ts"'. The browser-based tool processes one file at a time, so the local FFmpeg approach is strongly recommended for large batches of camcorder footage.
Technical Notes
MOD is a format produced exclusively by certain JVC (Everio series) and Panasonic camcorders, storing MPEG-2 video at standard definition resolutions (typically 720x480 NTSC or 720x576 PAL) inside an MPEG Program Stream container with a .MOD file extension. The audio in MOD files is most commonly Dolby Digital (AC-3) at 256 kbps. M2TS, by contrast, uses an MPEG-2 Transport Stream container and is the standard for Blu-ray BDAV content and AVCHD footage. This conversion uses libx264 for H.264 re-encoding — a significant codec upgrade from MPEG-2 that yields better compression efficiency, though the source SD resolution is preserved unless you add scaling flags. M2TS supports multiple audio tracks and subtitles, but since MOD files typically contain a single audio track and no subtitle streams, those M2TS features are not utilized in this conversion. The output M2TS file will not contain a BDMV folder structure on its own; Blu-ray authoring software is still required to create a compliant Blu-ray disc image. One known limitation: MOD files sometimes span multiple segments (e.g., MOD001.MOD, MOD002.MOD) for long recordings — these should be concatenated using FFmpeg's concat demuxer before conversion to produce a single continuous M2TS output.