Convert MOD to MKV — Free Online Tool
Convert MOD camcorder footage from JVC or Panasonic devices into MKV, re-encoding the MPEG-2 video stream to H.264 using libx264 for dramatically smaller file sizes with comparable visual quality. MKV's open container adds support for chapters, multiple audio tracks, and subtitles — features the original MOD format cannot carry.
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 as MPEG-2 inside a modified MPEG-PS container, the same underlying format used by DVDs. During this conversion, the MPEG-2 video stream is fully re-encoded to H.264 (libx264) — this is a transcode, not a remux, because MKV can technically hold MPEG-2 but the goal is modern compression efficiency. The AAC audio replaces the AC-3 or MPEG audio typically found in MOD files. The result is an MKV file that is often 50–70% smaller than the original MOD while retaining broadcast-quality visual fidelity at the default CRF 23 setting.
What Each Flag Does
| Flag | What it does |
|---|---|
ffmpeg
|
Invokes the FFmpeg binary. This conversion runs entirely in your browser via FFmpeg.wasm (WebAssembly), so no installation is required and no files leave your device — the same binary can be run locally on your desktop for files over 1GB. |
-i input.mod
|
Specifies the input MOD file — a renamed MPEG-2 Program Stream as recorded by JVC Everio or Panasonic SD camcorders. FFmpeg detects the MPEG-2 video and AC-3/MPEG audio streams inside the modified PS container automatically. |
-c:v libx264
|
Re-encodes the video stream from MPEG-2 to H.264 using the libx264 encoder. This is a full transcode (not a copy) because the goal is modern compression efficiency — H.264 achieves comparable visual quality to MPEG-2 at roughly half the bitrate. |
-c:a aac
|
Re-encodes the audio stream to AAC, replacing the AC-3 or MPEG Layer II audio typically found in MOD camcorder files. AAC is natively supported by virtually all modern playback devices and is the standard audio codec for streaming and media servers. |
-crf 23
|
Sets the Constant Rate Factor for the H.264 encode to 23, the libx264 default. This is a perceptual quality target — lower values (e.g., 18) produce higher quality and larger files, while higher values (e.g., 28) reduce file size at the cost of visible softness in the camcorder footage. |
-b:a 128k
|
Sets the AAC audio bitrate to 128 kilobits per second. For typical camcorder audio — ambient sound, speech, family events — 128k AAC is transparent and indistinguishable from the original. Increase to 192k or 256k if the original MOD contains high-quality stereo music or surround audio. |
output.mkv
|
Specifies the output file in Matroska (MKV) format. MKV is an open-standard container that supports the H.264 video and AAC audio streams produced by this conversion, and additionally provides support for subtitles, chapters, and multiple audio tracks that can be added to the file after conversion without re-encoding. |
Common Use Cases
- Archiving old JVC Everio or Panasonic SD camcorder recordings into a modern, widely-supported format before the original MOD files become unplayable on newer systems
- Preparing home video footage shot on a MOD-based camcorder for editing in video software like DaVinci Resolve or Premiere Pro, which handles H.264-in-MKV more efficiently than raw MPEG-2-in-MOD
- Reducing the storage footprint of large camcorder libraries — MOD files using MPEG-2 are much larger than equivalent H.264 encodes at the same perceived quality
- Converting MOD footage to MKV so it can be played back on a Plex or Jellyfin media server, which streams H.264/MKV natively without requiring server-side transcoding
- Preserving family event recordings (weddings, graduations, school plays) from older JVC camcorders in a future-proof open-standard container with the option to add chapter markers and subtitles post-conversion
- Batch-converting a memory card full of MOD clips before transferring to a NAS or cloud backup, where storage costs make the MPEG-2 file size impractical
Frequently Asked Questions
Yes, but at the default CRF 23 setting the quality loss is minimal and imperceptible for most home video content. The original MOD file already uses lossy MPEG-2 compression, so this conversion involves transcoding from one lossy format (MPEG-2) to another (H.264). If preserving maximum quality is critical, lower the CRF value toward 18 or 15 — lower numbers mean higher quality and larger files. Setting CRF to 0 enables lossless H.264, though the resulting file will be significantly larger.
Yes. MOD files from JVC and Panasonic camcorders typically store audio as Dolby Digital (AC-3) or MPEG Layer II, neither of which is preserved in this conversion. The FFmpeg command re-encodes the audio to AAC at 128k, which is a different codec. AAC at 128k is transparent for most spoken-word and ambient camcorder audio, but if you need higher fidelity, increase the bitrate to 192k or 256k by modifying the -b:a flag. If you want to preserve multi-channel surround audio from the original MOD, note that this tool's default output is stereo AAC.
MOD files embed recording metadata such as date, time, and device information in the MPEG-PS container. FFmpeg will attempt to copy compatible metadata tags into the MKV output, but some camcorder-specific fields may not map cleanly to MKV's metadata schema and could be lost. Critical timestamps (creation date) are typically preserved in standard format. If metadata preservation is essential, inspect the output file with a tool like MediaInfo before discarding the original MOD.
No. The MOI file is a sidecar used by the camcorder's management software and contains playlist and clip information — it is not required for video playback or conversion. FFmpeg reads only the MOD file directly, so you can ignore the MOI files when converting. However, the MOI files may contain additional metadata like recording mode that won't be transferred to the MKV output.
The -crf 23 flag controls video quality on a scale from 0 (lossless) to 51 (lowest quality). Decreasing the number improves quality and increases file size — CRF 18 is often described as visually lossless for H.264. Increasing the number reduces quality and file size — CRF 28 produces noticeably softer footage but much smaller files. For camcorder footage where storage savings are the priority, CRF 28 is a reasonable compromise. You can also change -b:a 128k to 192k or 256k for better audio quality.
Yes. On Linux or macOS, you can run a shell loop: for f in *.MOD; do ffmpeg -i "$f" -c:v libx264 -c:a aac -crf 23 -b:a 128k "${f%.MOD}.mkv"; 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.mkv". This is particularly useful for processing a full memory card dump from a JVC or Panasonic camcorder where dozens of MOD clips need to be converted at once. Note that each file requires a full MPEG-2-to-H.264 transcode, so batch processing can be CPU-intensive.
Technical Notes
MOD is essentially MPEG-2 Program Stream with a renamed extension — the same underlying format used on DVD-Video — recorded at standard interlaced resolutions such as 720x480 (NTSC) or 720x576 (PAL). When transcoding to H.264/MKV, FFmpeg will automatically handle deinterlacing if needed, though for best results you may want to add an explicit deinterlace filter (-vf yadif) to the command, particularly for footage shot in interlaced mode on older JVC Everio models. The H.264 output is progressive by default, which is the correct choice for modern playback. MKV is a superset container relative to MOD: it can hold subtitles (ASS, SRT, PGS), multiple audio tracks, chapter markers, and rich metadata — none of which MOD supports — so the converted file can be enriched post-conversion with tools like MKVToolNix without re-encoding. One known limitation is that MOD files recorded with camcorder-specific GOP structures or non-standard MPEG-2 profiles may produce minor artifacts during the initial frames of the transcode; adding -ss 0 -accurate_seek to the input flags can help in edge cases. File sizes typically drop by 50–70% compared to the original MOD at CRF 23, making this conversion particularly valuable for archiving large camcorder libraries.