Convert MOD to RM — Free Online Tool
Convert MOD camcorder footage from JVC or Panasonic devices into RealMedia (.rm) format using MJPEG video encoding and AAC audio — all processed locally in your browser via FFmpeg.wasm. This tool is particularly useful for archivists and retro-media enthusiasts who need to store or stream camcorder footage in the legacy RealMedia container.
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 use MPEG-2 video stored inside a modified MPEG Program Stream container, which is the raw recording format output by JVC and Panasonic SD-card camcorders. During this conversion, the MPEG-2 video stream is fully re-encoded into MJPEG (Motion JPEG), a codec that stores each video frame as an individual JPEG image — a very different compression philosophy from MPEG-2's interframe prediction. The AAC audio track is passed through or re-encoded into AAC at 128k bitrate inside the RealMedia container. The result is an .rm file, the proprietary container format developed by RealNetworks that was widely used for internet streaming in the late 1990s and early 2000s.
What Each Flag Does
| Flag | What it does |
|---|---|
ffmpeg
|
Invokes the FFmpeg tool, which handles all media demuxing, decoding, re-encoding, and muxing for this MOD-to-RM conversion pipeline. |
-i input.mod
|
Specifies the input MOD file — the modified MPEG Program Stream container output by JVC or Panasonic camcorders — which FFmpeg will demux to extract the MPEG-2 video and audio streams for re-encoding. |
-c:v mjpeg
|
Sets the output video codec to MJPEG (Motion JPEG), which re-encodes each frame of the MPEG-2 camcorder video as an independent JPEG image. This is the only video codec FFmpeg supports for writing into the RealMedia container. |
-c:a aac
|
Sets the output audio codec to AAC, re-encoding the original camcorder audio (typically AC-3 or PCM from the MOD file) into AAC for storage in the RealMedia container, which does not support AC-3. |
-q:v 5
|
Sets the MJPEG video quality scale to 5, the midpoint of the 1–10 range where 1 is highest quality and 10 is most compressed. This balances file size and visual fidelity for typical SD camcorder footage. |
-b:a 128k
|
Sets the AAC audio bitrate to 128 kilobits per second, which is the default and provides clean, transparent audio quality for typical camcorder-recorded speech, ambient sound, and music. |
output.rm
|
Specifies the output filename and triggers FFmpeg to mux the re-encoded MJPEG video and AAC audio into the RealMedia (.rm) container format developed by RealNetworks. |
Common Use Cases
- Archiving old JVC or Panasonic camcorder footage into a period-appropriate RealMedia format for historical media collections or digital nostalgia projects
- Preparing camcorder recordings for playback on legacy systems or media players such as RealPlayer that natively support the .rm container
- Converting MOD footage into MJPEG-encoded video for use in older non-linear editing workflows that accept MJPEG but not MPEG-2
- Creating frame-accurate video clips from camcorder footage, since MJPEG's intra-frame encoding makes every frame independently decodable — useful for scrubbing-heavy review workflows
- Reducing the complexity of MOD files for distribution over retro-style streaming setups or self-hosted media servers with RealMedia support
- Demonstrating or teaching media format history by producing authentic .rm files from modern camcorder source footage
Frequently Asked Questions
Yes — this conversion involves two stages of lossy compression and a fundamental change in video codec architecture. The original MOD file uses MPEG-2, which compresses video using temporal (interframe) prediction across groups of pictures. Re-encoding into MJPEG discards that structure entirely and compresses each frame independently as a JPEG image. At the default quality setting (-q:v 5), the output is generally acceptable for archival viewing but will not match the sharpness or compression efficiency of the source MPEG-2 stream. If quality is critical, lower the -q:v value toward 1 for higher MJPEG quality.
The RealMedia (.rm) container format has extremely limited codec support in FFmpeg, and MJPEG is the primary video codec that FFmpeg can mux into an .rm file. Modern codecs like H.264 or H.265 are not compatible with the RealMedia container as implemented in FFmpeg. This is a fundamental constraint of the legacy .rm format, which was designed around RealNetworks' own proprietary codecs that are not freely encodable today.
The audio from the MOD file — typically AC-3 or PCM — is re-encoded into AAC at 128k bitrate for inclusion in the RealMedia container. AAC is a modern and efficient lossy audio codec that provides good quality at 128k, and it is one of the two audio codecs FFmpeg supports for .rm output. The original audio format from the camcorder is not preserved, but 128k AAC is generally transparent for speech and ambient camcorder audio.
Playback of .rm files in modern players is inconsistent. VLC Media Player has broad RealMedia support and is the most reliable modern option for playing .rm files. Windows Media Player, macOS QuickTime, and most browser-based players do not natively support RealMedia. The format was purpose-built for RealPlayer, which is still available but largely obsolete. If broad compatibility is your goal, consider converting to a more universal format like MP4 instead.
The video quality is controlled by the -q:v flag, which sets the MJPEG quantization scale. Values range from 1 (highest quality, largest file) to 10 (lowest quality, smallest file), with the default set to 5. To improve output sharpness and reduce JPEG compression artifacts, run the command with -q:v 2, for example: ffmpeg -i input.mod -c:v mjpeg -c:a aac -q:v 2 -b:a 128k output.rm. You can also adjust audio bitrate using -b:a, with options up to 256k for better audio fidelity.
Yes. On Linux or macOS, you can batch convert all MOD files in a directory with a shell loop: for f in *.mod; do ffmpeg -i "$f" -c:v mjpeg -c:a aac -q:v 5 -b:a 128k "${f%.mod}.rm"; done. On Windows Command Prompt, use: for %f in (*.mod) do ffmpeg -i "%f" -c:v mjpeg -c:a aac -q:v 5 -b:a 128k "%~nf.rm". This is especially practical for large MOD archives from camcorder memory cards where you have dozens of clip files to process at once.
Technical Notes
MOD is a container format specific to consumer JVC and Panasonic camcorders and is structurally a modified MPEG Program Stream (.mpg) with a renamed extension. It typically encodes video in MPEG-2 at standard definition resolutions (720x480 NTSC or 720x576 PAL) with AC-3 or linear PCM audio. When converting to RealMedia, all of this structure is discarded and replaced with the .rm container, which has no support for MPEG-2 video, AC-3 audio, chapters, subtitles, or multiple audio tracks. The MJPEG codec used for output is intra-frame only, meaning file sizes for MJPEG at equivalent visual quality will be significantly larger than MPEG-2 — expect .rm files to be noticeably bigger than the source .mod files depending on the -q:v setting. Metadata embedded in MOD files (such as recording date from the camcorder) is not preserved in the RealMedia container. The .rm format also has no support for transparency or subtitle streams, though MOD files do not carry these either, so no data of that kind is lost in this particular conversion.