Convert RM to MOD — Free Online Tool

Convert legacy RealMedia (.rm) files to MOD format, re-encoding the MJPEG or AAC streams from the proprietary RealNetworks container into an H.264/AAC-based MOD file compatible with JVC and Panasonic camcorder workflows. This is especially useful for archiving or editing old streaming-era video clips in a modern, widely-supported codec.

FFmpeg Command

Copy this command to run the same conversion locally with FFmpeg on your desktop. Download FFmpeg

Free — no uploads, no signups. Your files never leave your browser.

Estimated output:

Conversion Complete!

Download

How It Works

RealMedia files store video using codecs like MJPEG and audio using AAC or MP3, wrapped in RealNetworks' proprietary container format. During this conversion, FFmpeg decodes the MJPEG video stream from the .rm container and re-encodes it using the H.264 codec (libx264), producing significantly better compression while maintaining comparable visual quality. The AAC audio track is passed through or re-encoded at 128k bitrate into the MOD container, which is structurally an MPEG-PS derivative used by JVC and Panasonic camcorders. Because both the video and audio are being fully re-encoded (not remuxed), this is a transcoding operation — not a lossless copy — and some generation loss is inherent. The CRF 23 setting for H.264 is a widely accepted default that balances file size and visual fidelity well for archival or editing purposes.

What Each Flag Does

Flag What it does
ffmpeg Invokes the FFmpeg executable, the open-source multimedia processing engine that powers this conversion both in the browser (via FFmpeg.wasm) and on the desktop command line.
-i input.rm Specifies the input file — in this case a RealMedia .rm file, which FFmpeg opens using its built-in RealMedia demuxer to extract the contained video and audio streams.
-c:v libx264 Sets the video encoder to libx264, re-encoding the MJPEG video stream from the RealMedia source into H.264, which provides far superior compression efficiency and near-universal playback compatibility compared to MJPEG.
-c:a aac Sets the audio encoder to AAC, re-encoding or passing through the audio from the RealMedia file into AAC format, which is compatible with the MOD container and widely supported by modern playback software and hardware.
-crf 23 Sets the Constant Rate Factor for H.264 encoding to 23, the libx264 default, which produces a good balance between visual quality and file size. Lower values (e.g., 18) produce higher quality at larger file sizes, while higher values (e.g., 28) compress more aggressively.
-b:a 128k Sets the AAC audio bitrate to 128 kilobits per second, a standard quality level that is appropriate for most speech and music content found in legacy RealMedia streaming files.
output.mod Specifies the output filename with the .mod extension, signaling FFmpeg to write the re-encoded H.264 video and AAC audio into a MOD container — the MPEG-PS-derived format used by JVC and Panasonic camcorders.

Common Use Cases

  • Recovering old streaming video clips saved from late-1990s or early-2000s RealPlayer sessions and converting them into MOD files for import into JVC or Panasonic camcorder editing software
  • Digitizing and archiving RealMedia news broadcasts or educational content from legacy media libraries into a format that can be more easily ingested into modern NLE timelines via MOD import workflows
  • Preparing historical RealMedia footage for integration into a project that uses footage shot on JVC Everio or Panasonic camcorders, normalizing the container format across all source clips
  • Converting .rm files recovered from old CD-ROMs or DVD-ROMs that contain multimedia content originally distributed in RealNetworks format, to preserve them in a more durable codec like H.264
  • Re-encoding MJPEG-based RealMedia clips into H.264 within a MOD wrapper to dramatically reduce file sizes while retaining acceptable quality for archival screening copies
  • Batch converting a folder of .rm video files from a legacy corporate intranet or e-learning platform into MOD format for compatibility with older video playback hardware that supports MPEG-PS-based formats

Frequently Asked Questions

MOD is a format specifically used by JVC and Panasonic camcorders and is based on the MPEG-PS container with MPEG-2 video, though modern tools like FFmpeg can write H.264 into a MOD-like wrapper. You would choose MOD specifically if you need compatibility with camcorder editing suites or hardware that expects this format. If your goal is general playback or editing, MP4 would be a more universally compatible output choice.
Yes, some quality loss is expected because this conversion fully re-encodes both the video and audio streams — it is a transcode, not a remux. The source RealMedia file itself was already lossy (compressed with MJPEG video and AAC audio), so re-encoding introduces an additional generation of compression. Using CRF 23 with libx264 produces good quality for most content, but if the source .rm file was low-resolution or low-bitrate to begin with (as many streaming-era RealMedia files were), the output quality ceiling is limited by the source.
FFmpeg has built-in support for the RealMedia container and can decode common codecs found in .rm files, including MJPEG video and AAC or MP3 audio. However, some older .rm files may use RealVideo or RealAudio codecs (rv10, rv20, cook, atrac, etc.) which have partial or no support in FFmpeg. If your file uses those legacy Real-proprietary codecs rather than MJPEG or standard AAC, the conversion may fail or produce incorrect output.
The video quality is controlled by the -crf flag, where lower values produce higher quality and larger files, and higher values produce smaller files with more compression artifacts. The default is -crf 23, which is a good general-purpose setting. For better quality, try -crf 18; for smaller file sizes at the cost of quality, try -crf 28. For audio quality, change the -b:a value — for example, use -b:a 192k for higher-fidelity audio.
RealMedia files can contain metadata such as title and author fields in their container headers, but the MOD format (based on MPEG-PS) has very limited metadata support. FFmpeg will attempt to map compatible metadata tags during conversion, but most RealMedia-specific metadata will not survive into the MOD container. If metadata preservation is critical, consider converting to a format with richer metadata support, such as MKV or MP4.
Yes. On Linux or macOS, you can use a shell loop such as: for f in *.rm; do ffmpeg -i "$f" -c:v libx264 -c:a aac -crf 23 -b:a 128k "${f%.rm}.mod"; done. On Windows Command Prompt, use: for %f in (*.rm) do ffmpeg -i "%f" -c:v libx264 -c:a aac -crf 23 -b:a 128k "%~nf.mod". The browser-based tool on this page processes one file at a time, so the FFmpeg command is the recommended approach for batch jobs.

Technical Notes

RealMedia (.rm) was designed for low-bandwidth streaming and often contains video encoded at low resolutions (240p–480p) and low bitrates, which limits the quality ceiling of any transcoded output regardless of the output codec settings. The MJPEG codec used in some .rm files is an intra-frame-only format with no temporal compression, meaning each frame is stored independently as a JPEG image — this makes it relatively easy to decode but results in larger source files compared to interframe codecs. When re-encoding to H.264 (libx264) with CRF 23, the output will typically be much smaller than an equivalent MJPEG source, as H.264 uses sophisticated temporal prediction. The MOD container is a modified MPEG-PS format and does not support subtitles, chapters, or multiple audio tracks, so any such streams in a source file will be dropped. Transparency is not supported in either format. Note that some .rm files distributed in the late 1990s use RealVideo (rv10/rv20/rv30/rv40) or RealAudio (cook, raac) codecs rather than standard MJPEG/AAC, and those files may not convert cleanly with this command — FFmpeg's support for those proprietary codecs is incomplete.

Related Tools