Convert M4V to MOD — Free Online Tool
Convert M4V files from iTunes or iOS devices into MOD format used by JVC and Panasonic camcorders, re-encoding the H.264 video and AAC audio into an MPEG-PS compatible stream. This is useful for archiving Apple-purchased video content into a camcorder-native format or integrating iTunes video into MPEG-2-based editing workflows.
to
FFmpeg Command
Copy this command to run the same conversion locally with FFmpeg on your desktop. Download FFmpeg
Drop your M4V 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
M4V files store H.264 or H.265 video and AAC audio inside an MPEG-4 container, often with Apple-specific DRM or chapter metadata. MOD is a camcorder format based on MPEG-2 video inside a modified MPEG Program Stream container, used natively by JVC and Panasonic devices. Because the containers and typical codec expectations differ significantly, this conversion fully re-encodes the video stream using libx264 and packages it into the MOD container — there is no stream copy shortcut here. The AAC audio is also re-encoded at 128k bitrate. Note that MOD does not support subtitles, chapters, or multiple audio tracks, so any of those features present in your M4V source file will be dropped during conversion. The output is a standard-definition compatible MPEG-PS-style file playable by camcorder software and legacy MPEG-2 editing tools.
What Each Flag Does
| Flag | What it does |
|---|---|
ffmpeg
|
Invokes the FFmpeg binary, the open-source multimedia processing engine running here via WebAssembly in your browser. This is the same command-line tool you would run on your desktop to reproduce this conversion locally. |
-i input.m4v
|
Specifies the input file as an M4V — Apple's MPEG-4-based video container. FFmpeg will parse the container to extract the video and audio streams, handling M4V-specific metadata like chapter markers and track labeling during the demux stage. |
-c:v libx264
|
Re-encodes the video stream using libx264, the industry-standard H.264 encoder. This is required because the M4V and MOD containers are incompatible at the stream level — no stream copy is possible — and libx264 produces the most broadly compatible output for MPEG-PS-style containers like MOD. |
-c:a aac
|
Encodes the audio stream using the AAC codec, which is also the native audio codec in M4V. This re-encodes the audio rather than copying it, since the container change requires remuxing, but keeps the codec consistent between input and output to minimize audio quality degradation. |
-crf 23
|
Sets the Constant Rate Factor for the libx264 video encoder to 23, which is the default balanced quality level. Lower values produce higher quality MOD output at larger file sizes; higher values compress more aggressively. This controls the visual quality of the re-encoded video in the final MOD file. |
-b:a 128k
|
Sets the AAC audio bitrate to 128 kilobits per second in the MOD output. This is a standard quality level for stereo audio that balances file size and fidelity, appropriate for the speech and music content typical in M4V video sources from iTunes or iOS recordings. |
output.mod
|
Specifies the output filename with the .mod extension, which tells FFmpeg to write the encoded video and audio into an MPEG Program Stream container compatible with JVC and Panasonic camcorder software and MPEG-2-based editing tools. |
Common Use Cases
- Importing an iTunes movie or TV episode download into a JVC or Panasonic camcorder editing suite that only accepts MOD files from its own devices
- Archiving Apple-purchased video content into a flat MPEG-PS stream format for long-term storage in legacy video management systems
- Preparing M4V content for playback on older Panasonic televisions or DVD recorders that accept MOD files from camcorders via USB
- Converting iOS screen recordings saved as M4V into MOD format for integration with camcorder footage in a mixed-source video project
- Stripping Apple-container-specific metadata and chapters from M4V files to produce a clean, single-stream video file compatible with MPEG-2 based workflows
- Batch converting a library of M4V home videos recorded on older Apple devices into MOD for compatibility with camcorder archiving software
Frequently Asked Questions
No. MOD is a format based on MPEG Program Stream and does not support chapters, subtitle tracks, or multiple audio tracks at the container level. Any chapter markers or subtitle streams embedded in your M4V file will be silently dropped during conversion. If preserving chapters or subtitles is important, you should choose a different output format such as MKV or MP4.
M4V stores video inside an MPEG-4 container, while MOD uses a modified MPEG Program Stream structure. These two containers are fundamentally incompatible at the stream packaging level, so a direct stream copy is not possible. FFmpeg must decode the video and re-encode it using libx264 to produce a stream that can be wrapped correctly in the MOD container. This re-encoding means some quality loss compared to the original is expected.
No. M4V files purchased from iTunes that are protected by Apple's FairPlay DRM cannot be processed by FFmpeg or any browser-based converter. FFmpeg will either fail to open the file or produce a broken output. Only DRM-free M4V files — such as those you have personally recorded, ripped, or purchased from DRM-free sources — can be converted with this tool.
The -crf flag controls video quality. The default value of 23 is a balanced midpoint — lower values (e.g., 18) produce higher quality and larger files, while higher values (e.g., 28 or 35) produce smaller files with more compression artifacts. To reduce file size for large M4V sources, try increasing the CRF to 28. To improve quality at the cost of a larger MOD file, lower it to 18. You can also adjust audio bitrate by changing the -b:a value, for example replacing 128k with 96k to reduce file size further.
Because both the input and output use lossy compression and the default CRF of 23 is the same quality level used in many M4V encodes, file sizes will often be similar. However, MOD does not benefit from the MPEG-4 container's optimizations like faststart or fragmented MP4 streaming, and the re-encoding step introduces a generational quality loss. If your M4V was encoded at a high bitrate, the MOD output may actually be smaller due to libx264's efficient compression at CRF 23.
The browser-based tool processes one file at a time, but the displayed FFmpeg command can be adapted for batch processing on your desktop. On Linux or macOS, you can run: for f in *.m4v; do ffmpeg -i "$f" -c:v libx264 -c:a aac -crf 23 -b:a 128k "${f%.m4v}.mod"; done. On Windows Command Prompt, use a for loop: for %f in (*.m4v) do ffmpeg -i "%f" -c:v libx264 -c:a aac -crf 23 -b:a 128k "%~nf.mod". This is especially useful for large collections of camcorder-imported M4V files exceeding the 1GB browser limit.
Technical Notes
MOD files are natively produced by JVC Everio and Panasonic SD camcorders and are essentially MPEG-2 video streams wrapped in a modified MPEG Program Stream container, though this tool re-encodes using H.264 via libx264 rather than true MPEG-2, which produces a more compact and higher-quality output at the same bitrate. The MOD container imposes significant limitations compared to M4V: it has no support for multiple audio tracks, embedded subtitles, chapter markers, or streaming optimization flags like -movflags +faststart. Any of these features present in the M4V source will be lost. M4V files are closely related to MP4 and may contain H.264 or H.265 video; both are re-encoded to H.264 in the output since libx264 is the most compatible choice for downstream MPEG-PS-based tools. Apple's M4V container also allows for protected content via FairPlay DRM — such files cannot be converted. The AAC audio codec is preserved across both formats, so audio quality loss is minimized to the re-encoding step rather than a codec change. Users editing MOD output in camcorder software should be aware that some tools validate MOD files by checking for true MPEG-2 video streams and may reject H.264-encoded MOD files produced by this conversion.