Convert MOD to MTS — Free Online Tool
Convert MOD camcorder footage (JVC/Panasonic MPEG-2 based format) to MTS (AVCHD), re-encoding the video with H.264 and audio with AAC inside an MPEG-2 Transport Stream container. This is ideal for modernizing older camcorder recordings into a format compatible with Sony and Panasonic AVCHD workflows.
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 video using MPEG-2 in a modified MPEG Program Stream container — a format used by older JVC and Panasonic SD camcorders. MTS (AVCHD) uses an MPEG-2 Transport Stream container with H.264 video and AAC or AC-3 audio. Since the video codecs differ (MPEG-2 vs H.264), the video stream must be fully re-encoded — it cannot be simply remuxed. FFmpeg decodes the MPEG-2 video from the MOD file and re-encodes it to H.264 using libx264, while the audio is similarly transcoded to AAC. The result is a smaller file with comparable or better visual quality, packaged in the transport stream container that AVCHD-compatible editors and devices expect.
What Each Flag Does
| Flag | What it does |
|---|---|
ffmpeg
|
Invokes the FFmpeg tool. In the browser-based version, this runs via FFmpeg.wasm (WebAssembly) entirely within your browser — no data is sent to a server. On the desktop, this calls your locally installed FFmpeg binary. |
-i input.mod
|
Specifies the input file — your MOD camcorder recording stored in the MPEG Program Stream container with MPEG-2 video. FFmpeg automatically detects the container and codec from the file content, not just the extension. |
-c:v libx264
|
Sets the video encoder to libx264, which re-encodes the MPEG-2 video from the MOD file into H.264. This is the required step since MOD and MTS use fundamentally different video codecs — no stream copy is possible here. |
-c:a aac
|
Encodes the audio track to AAC using FFmpeg's built-in AAC encoder. MOD files often carry MPEG-1 Layer 2 or AC-3 audio, so the audio is transcoded to AAC, which is the standard audio codec for AVCHD-compatible MTS files. |
-crf 23
|
Sets the Constant Rate Factor for the H.264 encode to 23, which is libx264's default and provides a good balance of visual quality and file size. Lower values (e.g., 18) produce larger, higher-quality files; higher values (e.g., 28) produce smaller files with more visible compression artifacts in the re-encoded footage. |
-b:a 128k
|
Sets the AAC audio bitrate to 128 kilobits per second, which is sufficient for the mono or stereo audio tracks typical of MOD camcorder recordings. Increase to 192k or 256k if the original audio was high-fidelity stereo and you want to preserve more audio detail. |
output.mts
|
Specifies the output filename with the .mts extension. FFmpeg uses this extension to determine that the output container should be MPEG-2 Transport Stream (MPEGTS), which is the correct container format for AVCHD MTS files used by Sony and Panasonic camcorder ecosystems. |
Common Use Cases
- Importing older JVC or Panasonic SD camcorder footage into Sony Vegas, Premiere Pro, or other NLEs that have native AVCHD/MTS project templates
- Archiving MOD recordings in a more compressed and widely supported format — H.264 in MTS achieves better compression than MPEG-2, reducing long-term storage requirements
- Preparing family camcorder footage from a JVC Everio or Panasonic SD series camera for editing alongside MTS clips shot on a Sony Handycam
- Converting MOD files so they can be played on Blu-ray players or media streamers that support AVCHD disc structures but do not recognize the MOD container
- Standardizing a mixed collection of MOD and MTS footage from different camcorders into a single MTS format for a unified editing workflow
- Reducing file size for long-duration event recordings (weddings, concerts) originally captured in MPEG-2 MOD before uploading or sharing with clients
Frequently Asked Questions
Yes, some quality loss is unavoidable because this conversion requires transcoding from MPEG-2 to H.264 — two different codecs. However, H.264 is significantly more efficient than MPEG-2, so at the default CRF 23 setting, the output MTS file will often look visually similar to the original while being considerably smaller. If you need to prioritize quality, lower the CRF value (e.g., CRF 18) to produce a higher-quality encode at the cost of a larger file.
MOD files use MPEG-2 video encoding, which is an older codec that requires significantly more bitrate to achieve the same visual quality as H.264. When re-encoding to MTS with libx264, the H.264 codec typically produces files 40–60% smaller than MPEG-2 at comparable quality. This is a normal and expected benefit of the conversion, not a sign of quality degradation.
MOD files can embed recording timestamps and some camera metadata in the MPEG-PS container. However, MTS (AVCHD) uses a different container structure and metadata schema, and FFmpeg does not automatically map all MOD metadata fields to their MTS equivalents during transcoding. Recording date metadata may be partially preserved, but specialized AVCHD fields will likely be lost. If metadata preservation is critical, consider using dedicated camcorder software to transfer footage before converting.
In most cases, yes. The output MTS file uses H.264 video and AAC audio inside an MPEG-2 Transport Stream, which matches the core codec profile of AVCHD. Software like Adobe Premiere Pro, Sony Vegas, and DaVinci Resolve can import MTS files directly. However, true AVCHD compliance requires a specific folder structure (AVCHD/BDMV/STREAM/) which this conversion does not create — the file itself will import correctly as a standalone MTS, but it won't be recognized as part of an AVCHD disc structure.
The video quality is controlled by the -crf flag, which accepts values from 0 (lossless) to 51 (worst quality). The default is 23, which is a good balance for most MOD footage. To get a higher quality output closer to the original MPEG-2 source, try -crf 18. To prioritize a smaller file size, use -crf 28 or higher. Audio bitrate is set separately with -b:a; replacing 128k with 192k or 256k will improve audio fidelity at the cost of a slightly larger file.
Yes, you can adapt the command into a shell loop for batch processing on your desktop. 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}.mts"; 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.mts". The in-browser tool processes one file at a time, so the FFmpeg command is especially useful for bulk conversions of large MOD archives.
Technical Notes
MOD is a container format unique to older JVC Everio and Panasonic SD-series camcorders, essentially an MPEG-PS (Program Stream) container with a .mod extension and MPEG-2 video encoded at standard definition resolutions (typically 720x480 NTSC or 720x576 PAL). MTS, on the other hand, is the file extension for AVCHD streams stored in an MPEG-2 Transport Stream container, almost universally carrying H.264 video. Because these share no common video codec, this conversion always requires a full video transcode — there is no lossless remux path between them. The libx264 encoder handles the MPEG-2 to H.264 conversion with good compatibility across players and editing software. One notable limitation is that MOD files do not contain subtitles or chapter markers, so MTS's support for those features is irrelevant here — nothing will be lost. MTS does support multiple audio tracks, but since MOD files typically carry a single stereo or mono audio track, the output will likewise be single-track AAC. If the source MOD footage was filmed in 4:3 aspect ratio, that ratio is preserved in the H.264 encode via the SAR (Sample Aspect Ratio) metadata — no cropping or pillarboxing is applied automatically.