Convert MOD to Y4M — Free Online Tool
Convert MOD camcorder footage (JVC/Panasonic MPEG-2 based video) to Y4M (YUV4MPEG2), a fully uncompressed intermediate format ideal for lossless video processing pipelines. This conversion decodes the MPEG-2 video stream from the MOD container into raw YUV frames, giving downstream tools like FFmpeg filters, Avisynth, or VapourSynth direct access to uncompressed pixel data.
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 in a modified MPEG Program Stream container — a lossy, inter-frame compressed format used by JVC and Panasonic camcorders. During this conversion, FFmpeg fully decodes every MPEG-2 frame (including resolving inter-frame dependencies from P- and B-frames) and writes each frame as raw YUV planar data into a Y4M file. Y4M adds a minimal header per frame and per file to declare resolution, frame rate, and color space, but applies absolutely no compression. The result is a very large file where every frame is independently accessible and pixel-perfect — no further decoding is needed by downstream tools. Audio is not carried by the Y4M format, so it is dropped during this conversion.
What Each Flag Does
| Flag | What it does |
|---|---|
ffmpeg
|
Invokes the FFmpeg binary. In the browser-based version of this tool, this runs via FFmpeg.wasm (WebAssembly) entirely in your browser — no server is involved. When running locally on your desktop, this calls your system-installed FFmpeg executable. |
-i input.mod
|
Specifies the input MOD file — the JVC/Panasonic camcorder recording in MPEG-2/MPEG-PS format. FFmpeg automatically detects the MPEG-PS container and MPEG-2 video stream without requiring any additional demuxer flags, even though the file extension is .mod rather than .mpg. |
-c:v rawvideo
|
Instructs FFmpeg to write the decoded video frames as raw, uncompressed pixel data — the codec used by the Y4M format. This fully decodes every MPEG-2 frame from the MOD source, including resolving all inter-frame P- and B-frame dependencies, and writes each frame without any re-compression. |
output.y4m
|
The output filename with the .y4m extension, which causes FFmpeg to use the yuv4mpegpipe muxer and write a valid YUV4MPEG2 file. The file will contain a stream header declaring the resolution, frame rate, chroma subsampling, and interlacing of the decoded MPEG-2 source, followed by uncompressed YUV frame data. |
Common Use Cases
- Feeding old JVC or Panasonic camcorder footage into a lossless video processing pipeline (e.g., VapourSynth or Avisynth) without introducing any additional compression artifacts on top of the original MPEG-2 decode.
- Preparing MOD camcorder clips for frame-accurate analysis or forensic video examination, where uncompressed YUV frames are required to inspect individual pixel values without codec interference.
- Piping decoded camcorder video into a second FFmpeg process or another command-line tool via stdin, using Y4M as the interchange format to avoid writing a lossy intermediate file.
- Using Y4M as a lossless intermediate step before re-encoding old MOD footage into a modern codec like AV1 or HEVC, ensuring the re-encoder works from the best possible source rather than a re-compressed intermediate.
- Deinterlacing MOD footage using an external tool (such as yadif or QTGMC) that accepts Y4M input, allowing the interlaced MPEG-2 content typical of standard-definition camcorders to be processed frame by frame.
- Archiving a fully decoded, format-agnostic copy of camcorder recordings so the content is no longer dependent on MPEG-2 decoder availability in future software environments.
Frequently Asked Questions
MOD files use MPEG-2 compression, which achieves significant size reductions by encoding only the differences between frames and applying DCT-based spatial compression within each frame. Y4M stores every single frame as raw, uncompressed YUV pixel data — there is no inter-frame prediction or spatial compression at all. A typical 1GB MOD file can expand to 20–50GB or more as Y4M, depending on resolution and frame rate. This is expected and is exactly the point: Y4M is an intermediate format, not a storage format.
The Y4M output is losslessly accurate to the decoded MPEG-2 source — no additional compression is applied during the conversion. However, the MPEG-2 video in the MOD file was already lossy when it was recorded by the camcorder, so any compression artifacts present in the original footage will be preserved in the Y4M output. Converting to Y4M does not recover quality lost during recording, but it guarantees no further quality degradation is introduced.
The Y4M format has no provision for audio — it is a video-only container designed purely for raw frame data. FFmpeg will silently drop the audio track during this conversion. If you need to preserve the audio, you should extract it separately before or after the conversion using a command like 'ffmpeg -i input.mod -vn -c:a copy audio.ac3' (MOD files typically carry AC-3 or MPEG audio). You can then recombine the audio with your processed video in a later step.
The Y4M output will use the color space decoded from the MPEG-2 stream in the MOD file, which is typically YUV 4:2:0 — the standard chroma subsampling used by MPEG-2 in consumer camcorders. The Y4M header will declare this color space explicitly, so downstream tools can correctly interpret the raw frame data. If your MOD footage uses a different chroma format, FFmpeg will reflect that in the Y4M header automatically.
Yes. On Linux or macOS, you can use a shell loop: 'for f in *.mod; do ffmpeg -i "$f" -c:v rawvideo "${f%.mod}.y4m"; done'. On Windows Command Prompt, use: 'for %f in (*.mod) do ffmpeg -i "%f" -c:v rawvideo "%~nf.y4m"'. Because Y4M files are very large, make sure you have sufficient disk space before batch processing — each MOD file will expand dramatically in size.
Yes, and this is one of Y4M's primary design purposes. You can write to stdout by replacing the output filename with 'pipe:1' or '-' and then pipe into another application: 'ffmpeg -i input.mod -c:v rawvideo -f yuv4mpegpipe - | your_tool'. Many video processing tools such as x264, x265, VapourSynth scripts, and custom frame processors accept Y4M via stdin, avoiding the need to write a multi-gigabyte intermediate file to disk entirely.
Technical Notes
MOD is a container format specific to JVC (and some Panasonic) standard-definition camcorders, essentially a renamed MPEG Program Stream (.mpg) file. The video is encoded as MPEG-2 at resolutions such as 720x480 (NTSC) or 720x576 (PAL), commonly interlaced, with a typical bitrate of 6–8 Mbps. FFmpeg handles MOD files natively since they are structurally valid MPEG-PS — no special demuxing flags are needed. The Y4M (YUV4MPEG2) output format is supported by FFmpeg via the 'yuv4mpegpipe' muxer. The '-c:v rawvideo' flag instructs FFmpeg to write decoded frames as raw pixel data rather than re-encoding them. One important limitation: Y4M does not support audio, chapters, or metadata of any kind — only raw video frames with per-file and per-frame headers containing resolution, frame rate, interlacing flags, and color space. If the MOD source contains interlaced content (which is common for camcorder footage), the interlacing information is preserved in the Y4M headers, allowing downstream deinterlacers to operate correctly. File sizes should be planned for carefully: a 60-second clip at 720x480 with 4:2:0 YUV at 29.97fps produces approximately 1.86GB of Y4M data.