Convert AVI to MOD — Free Online Tool
Convert AVI files to MOD format — the MPEG-2 based container used by JVC and Panasonic camcorders — by re-encoding video with H.264 (libx264) and audio with AAC. This is useful when you need to produce MOD-compatible output from legacy AVI source footage for camcorder-adjacent workflows or archival pipelines.
to
FFmpeg Command
Copy this command to run the same conversion locally with FFmpeg on your desktop. Download FFmpeg
Drop your AVI 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
AVI is a Microsoft container that can hold a variety of video codecs (commonly DivX, Xvid, or H.264) alongside MP3 or PCM audio. MOD is a modified MPEG-PS container used by JVC and Panasonic camcorders, historically based on MPEG-2, but this tool targets it with H.264 video and AAC audio for broader compatibility. Because AVI and MOD use fundamentally different container structures and the audio codec changes from MP3 (the AVI default) to AAC, a full re-encode of both video and audio streams is required — this is not a simple remux. The video is decoded from its AVI-wrapped codec and re-encoded using libx264 at CRF 23, while the audio is transcoded to AAC at 128k bitrate. The result is a .mod file that matches the container expectations of MOD-aware software and devices.
What Each Flag Does
| Flag | What it does |
|---|---|
ffmpeg
|
Invokes the FFmpeg multimedia processing tool, which handles all decoding, re-encoding, and container muxing for this AVI-to-MOD conversion. |
-i input.avi
|
Specifies the input AVI file. FFmpeg will detect the AVI container and identify the video and audio streams inside it — which could be any number of codecs historically packaged in AVI, such as Xvid, DivX, MJPEG, or H.264. |
-c:v libx264
|
Re-encodes the video stream using the H.264 encoder (libx264), replacing whatever codec was used in the source AVI. H.264 is chosen here because it offers efficient compression suitable for the MOD container, even though original camcorder MOD files use MPEG-2. |
-c:a aac
|
Transcodes the audio stream to AAC, which is the default audio codec for MOD output. AVI files commonly carry MP3 audio, so this step is a mandatory transcode — not a copy — to meet the MOD format's audio expectations. |
-crf 23
|
Sets the Constant Rate Factor for libx264 video encoding to 23, which is the default balanced quality level. Lower values (e.g., 18) produce higher quality and larger MOD files; higher values (e.g., 28) reduce file size with more visible compression. |
-b:a 128k
|
Sets the AAC audio bitrate to 128 kilobits per second, which is a standard quality level for stereo speech and general-purpose video audio. Increase to 192k or 256k if the AVI source contains high-fidelity music or critical audio. |
output.mod
|
Specifies the output filename with the .mod extension, which signals FFmpeg to mux the encoded H.264 video and AAC audio into the MOD container format used by JVC and Panasonic camcorders. |
Common Use Cases
- Preparing legacy AVI footage from older DV or DVD-based camcorders for ingestion into JVC or Panasonic camcorder management software that expects MOD-format files.
- Archivists converting AVI recordings into MOD to maintain consistency within a collection of camcorder footage that already uses the .mod extension.
- Videographers who need to place externally sourced AVI clips onto a JVC Everio or Panasonic SD camcorder's memory card for in-camera playback.
- Editors standardizing a mixed-format project by converting all legacy AVI clips to MOD before importing into software that handles camcorder formats natively.
- Testing or debugging media players and NLEs that claim MOD support by generating MOD files from known-good AVI sources.
- Converting AVI training or instructional videos for playback on camcorder-connected TV setups that read directly from SD cards in MOD format.
Frequently Asked Questions
Yes, some generation loss is inevitable. The AVI source video — regardless of whether it was encoded with DivX, Xvid, or H.264 — is fully decoded and re-encoded into H.264 using libx264 at CRF 23. Re-encoding any already-compressed video introduces additional lossy compression. At CRF 23 the quality loss is generally minimal for most content, but if your AVI source is already heavily compressed, artifacts may compound. Lowering the CRF value (e.g., to 18) in the FFmpeg command will reduce quality loss at the cost of a larger output file.
Authentic camcorder-recorded MOD files use MPEG-2 video inside a modified MPEG-PS container, but MOD is not a strictly enforced standard — it is essentially a renamed container. This tool targets MOD with H.264 (libx264) and AAC audio because libx264 produces superior compression and quality compared to MPEG-2 at equivalent bitrates, and FFmpeg does not include a native MPEG-2 encoder by default in all builds. If your target device or software strictly requires MPEG-2 video inside the MOD container, you would need to substitute '-c:v mpeg2video' in the FFmpeg command and adjust bitrate settings accordingly.
No. AVI supports multiple audio tracks, but the MOD format as targeted by this tool does not support multiple audio tracks. Only the first (default) audio track from the AVI source will be transcoded to AAC and included in the MOD output. If your AVI contains secondary audio tracks such as a commentary or alternate language, those will be dropped during conversion. You should verify which audio track is the primary one before converting.
The 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 23, which is a balanced midpoint. For near-transparent quality on clean AVI source material, try '-crf 18'. For a smaller file where some visual degradation is acceptable, try '-crf 28'. The valid range for libx264 is 0 (lossless) to 51 (worst quality). You can also adjust audio quality by changing the '-b:a' value — for example, '-b:a 192k' for higher-fidelity AAC audio.
The command shown processes a single file, but you can adapt it for batch processing in a shell. On Linux or macOS, use: 'for f in *.avi; do ffmpeg -i "$f" -c:v libx264 -c:a aac -crf 23 -b:a 128k "${f%.avi}.mod"; done'. On Windows Command Prompt, use: 'for %f in (*.avi) 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 the recommended approach for batch jobs or files over 1GB.
AVI metadata support is limited to begin with — it uses RIFF INFO chunks for basic tags like title or artist, and these are not guaranteed to map cleanly to the MOD container format. During this conversion, most AVI metadata will be lost because the MOD container structure does not have equivalent metadata fields, and FFmpeg does not attempt to translate them by default. If preserving metadata is important, you can explicitly copy tags using '-map_metadata 0' added to the FFmpeg command, though support depends on what the output container accepts.
Technical Notes
AVI files arriving at this converter may contain a wide variety of video codecs — Xvid, DivX, MJPEG, uncompressed, or H.264 — all of which must be decoded before re-encoding to H.264 for the MOD output. This means conversion time scales with the complexity of both decode and encode operations, unlike a simple remux. MOD is a proprietary-adjacent format tied to JVC Everio and Panasonic SD camcorder lines; it uses a modified MPEG-PS wrapper (.mod extension) and pairs with companion .modd and .moi index files that actual camcorders generate alongside footage — this tool produces only the .mod video file, not those sidecar files. The absence of subtitle and chapter support in both formats means no metadata of those types can be transferred. AVI's lack of modern container features (no HDR metadata, no B-frame timestamp handling in some encoders) can occasionally cause PTS/DTS timestamp issues during decode; FFmpeg generally handles this gracefully but you may see warnings in the console. Because MOD is lossy-only, there is no path to lossless output in this conversion regardless of CRF settings — CRF 0 in libx264 produces mathematically lossless H.264, but the MOD format context means this is unconventional and may not be recognized correctly by camcorder hardware.