Convert MOD to HEVC — Free Online Tool
Convert MOD camcorder footage to HEVC (H.265), re-encoding the MPEG-2 video stream with libx265 to dramatically reduce file size while preserving visual quality. HEVC delivers roughly half the bitrate of H.264 at equivalent quality, making it ideal for archiving bulky JVC or Panasonic MOD recordings.
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-PS container — a format common on older JVC and Panasonic SD-card and HDD camcorders. Because HEVC and MPEG-2 are completely different codecs, this conversion requires a full video re-encode: FFmpeg decodes the MPEG-2 stream frame by frame and re-encodes it using libx265, the open-source H.265 encoder. The output is a raw HEVC bitstream (.hevc) containing only the video — audio from the MOD file is not carried over into this container format. The CRF (Constant Rate Factor) quality model is used, meaning the encoder adjusts bitrate dynamically to maintain consistent visual quality across the entire clip rather than targeting a fixed file size.
What Each Flag Does
| Flag | What it does |
|---|---|
ffmpeg
|
Invokes the FFmpeg multimedia processing tool. All conversion work — demuxing the MOD container, decoding MPEG-2 video, encoding to HEVC — is handled by this single binary running locally in your browser via WebAssembly. |
-i input.mod
|
Specifies the input MOD file from your JVC or Panasonic camcorder. FFmpeg automatically detects the MPEG-PS container and the MPEG-2 video stream (along with any audio) inside it. |
-c:v libx265
|
Instructs FFmpeg to re-encode the video using libx265, the open-source H.265/HEVC encoder. This replaces the original MPEG-2 codec entirely, requiring a full decode-and-reencode of every frame rather than a simple stream copy. |
-crf 28
|
Sets the Constant Rate Factor to 28, which is the libx265 default and a good starting point for camcorder footage. The encoder varies bitrate scene by scene to maintain this perceptual quality level — lower numbers (e.g., 18) mean higher quality and larger files, higher numbers (e.g., 35) mean smaller files with more visible compression. |
-x265-params log-level=error
|
Passes a configuration string directly to the x265 library, telling it to suppress its normally verbose per-frame encoding statistics and only report actual errors. This has no effect on output quality or the encoded bitstream. |
output.hevc
|
The output filename with a .hevc extension, which tells FFmpeg to write a raw H.265 Annex B bitstream. This format contains only the HEVC video stream with no container wrapper, so audio from the original MOD file is not included in the output. |
Common Use Cases
- Archiving years of family camcorder footage shot on a JVC Everio or Panasonic SDR, cutting storage requirements roughly in half compared to keeping the original MPEG-2 MOD files.
- Preparing old camcorder clips for long-term cold storage where maximum compression efficiency matters more than broad playback compatibility.
- Reducing the footprint of a large collection of MOD recordings before transferring them to a NAS or external drive with limited capacity.
- Creating a high-quality HEVC master from MOD footage that will later be transcoded into delivery formats, preserving as much detail as possible from the original MPEG-2 source.
- Extracting and re-encoding the video-only stream from MOD files when the original MPEG-2 audio (AC-3 or MPEG audio) needs to be handled separately or replaced entirely in post-production.
- Testing HEVC encode quality at different CRF values against the original MOD source to find the optimal compression setting before batch-processing a full tape transfer.
Frequently Asked Questions
Yes, this is a lossy transcode. The original MOD file already contains lossy MPEG-2 video, and re-encoding it to HEVC with libx265 introduces a second generation of compression. At the default CRF 28, the output will look very close to the source for typical camcorder footage, but fine detail and subtle gradients may soften slightly. If you need the highest fidelity, lower the CRF value (e.g., CRF 18–20) at the cost of a larger output file.
The .hevc container is a raw video bitstream format — it holds only H.265-encoded video and has no standardized structure for audio tracks. The audio present in the original MOD file (typically AC-3 or MPEG-1 Layer II) is dropped during this conversion. If you need to retain audio, consider converting to a container like MKV or MP4 instead, which can wrap both an HEVC video stream and an audio track together.
MOD files use MPEG-2 video, which is significantly less efficient than HEVC. In practice, you can expect the HEVC output at CRF 28 to be 50–70% smaller than the original MOD file for typical camcorder footage like family events or travel recordings. Scenes with a lot of motion or fine texture (e.g., foliage, crowds) will see less size reduction, while static or low-motion clips may compress even further.
This flag suppresses the verbose per-frame encoding statistics that libx265 normally prints to the console, limiting output to actual errors only. It does not affect the encoded video in any way — the output quality and file are identical with or without it. It is purely a cosmetic flag to keep the terminal output clean. You can safely remove it from the command if you want to see detailed encoding progress information.
Change the number after -crf to control quality. The CRF scale for libx265 runs from 0 (lossless) to 51 (lowest quality), with 28 as the default. Lower values produce better quality and larger files — CRF 18 is often considered visually near-lossless for most content, while values above 35 will produce noticeable blockiness in MPEG-2-sourced material. For archival of old camcorder footage, CRF 20–24 is a good balance between quality and storage savings.
Yes. On Linux or macOS, you can run: for f in *.MOD; do ffmpeg -i "$f" -c:v libx265 -crf 28 -x265-params log-level=error "${f%.MOD}.hevc"; done. On Windows Command Prompt, use: for %f in (*.MOD) do ffmpeg -i "%f" -c:v libx265 -crf 28 -x265-params log-level=error "%~nf.hevc". This processes each MOD file sequentially and saves a corresponding .hevc file with the same base name. Note that this browser-based tool processes one file at a time; the FFmpeg command is the recommended approach for bulk conversions.
Technical Notes
MOD is essentially a renamed MPEG-PS (Program Stream) file containing MPEG-2 video, typically at standard-definition resolutions (720×480 NTSC or 720×576 PAL) at around 6–8 Mbps. Some higher-end Panasonic models recorded at up to 1080i in MOD/TOD variants. When decoding MPEG-2 for this transcode, FFmpeg's native MPEG-2 decoder handles the source cleanly without any special flags required. The libx265 encoder used here produces a raw Annex B HEVC bitstream in the .hevc output file, which lacks a container wrapper entirely — meaning metadata such as frame rate, pixel aspect ratio, and color space signaling may not be preserved in a readily readable form for all players. Camcorder-specific metadata embedded in the MOD container (recording date, GPS data on some models, scene mode tags) is not carried into the output. For downstream use in video editors or media servers, wrapping the same libx265 stream in an MKV or MP4 container is strongly recommended. The -x265-params log-level=error flag is passed directly to the x265 library to suppress informational encoder output without affecting any encoding parameters.