Convert RM to M2TS — Free Online Tool
Convert legacy RealMedia (.rm) files to M2TS (BDAV MPEG-2 Transport Stream), re-encoding the MJPEG or AAC streams into a modern H.264/AAC package suited for Blu-ray-compatible players and HD workflows. This tool runs entirely in your browser using FFmpeg.wasm — no upload required.
to
FFmpeg Command
Copy this command to run the same conversion locally with FFmpeg on your desktop. Download FFmpeg
Drop your RM 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
RealMedia files typically carry video encoded with MJPEG (a series of individual JPEG frames) and audio in AAC or MP3. Neither of these streams is natively compatible with the M2TS container, which expects MPEG-2 Transport Stream-wrapped content — most commonly H.264 video and AAC audio for BDAV use. This conversion is therefore a full transcode: the MJPEG video is decoded frame-by-frame and re-encoded into H.264 using libx264 with a CRF of 23, which produces a visually high-quality result at a much smaller file size than the original frame-based encoding. The AAC audio is decoded and re-encoded at 128k into a fresh AAC stream. The output is wrapped in an MPEG-2 Transport Stream (.m2ts), making it compatible with Blu-ray players, AVCHD camcorders, and professional broadcast workflows.
What Each Flag Does
| Flag | What it does |
|---|---|
ffmpeg
|
Invokes the FFmpeg binary — the open-source multimedia processing engine that handles all decoding, transcoding, and remuxing. In this browser tool, it runs as a WebAssembly (FFmpeg.wasm) instance with no server involvement. |
-i input.rm
|
Specifies the input RealMedia file. FFmpeg will probe this file to detect the container format (RealMedia) and the contained streams — typically MJPEG video and AAC or MP3 audio — before beginning the transcode. |
-c:v libx264
|
Selects the libx264 encoder to transcode the MJPEG video stream into H.264. This is necessary because MJPEG frames cannot be directly placed into an M2TS container, and H.264 is the standard video codec for BDAV M2TS files. |
-c:a aac
|
Encodes the audio stream to AAC using FFmpeg's native AAC encoder. The original RealMedia audio (whether AAC or MP3) is fully decoded and re-encoded to produce a clean AAC stream properly framed for the MPEG-2 Transport Stream multiplexer. |
-crf 23
|
Sets the Constant Rate Factor for the H.264 encoder to 23, which is libx264's default and a well-balanced quality setting. For content originally encoded as MJPEG at streaming-era quality, CRF 23 will typically match or exceed the perceived quality of the source at a fraction of the bitrate. |
-b:a 128k
|
Sets the output AAC audio bitrate to 128 kilobits per second. This is sufficient for most mono or stereo audio that originated in a RealMedia streaming file, where the source audio bitrate was often 32k–128k to begin with. |
output.m2ts
|
Defines the output filename with the .m2ts extension, which signals FFmpeg to wrap the encoded H.264 video and AAC audio into an MPEG-2 Transport Stream container — the format used by Blu-ray discs and AVCHD camcorders. |
Common Use Cases
- Archiving old RealMedia streaming recordings from the late 1990s or early 2000s into a modern, Blu-ray-compatible format for long-term preservation on disc.
- Preparing digitized VHS or legacy MJPEG-encoded .rm footage for import into professional NLE software that expects M2TS or BDAV transport streams.
- Converting RealMedia content captured from early web streams into M2TS for playback on Blu-ray players or Sony and Panasonic AVCHD-compatible devices.
- Migrating a library of RealMedia conference recordings or lectures into H.264-based M2TS for use in a broadcast or digital signage system.
- Re-encoding low-efficiency MJPEG video from .rm files into H.264 inside M2TS to dramatically reduce file size while retaining acceptable visual quality for archival display.
- Supplying historical RealMedia video content to a post-production house whose ingest workflow only accepts MPEG-2 Transport Stream containers.
Frequently Asked Questions
The conversion involves a full transcode from MJPEG (the typical video codec in RealMedia) to H.264, so some generation loss is mathematically unavoidable. However, MJPEG is a relatively low-compression format — each frame is essentially a JPEG — so H.264 at CRF 23 will almost always look comparable or even cleaner due to better inter-frame compression. The bigger quality factor is the quality of the original .rm file itself, which may have been streamed at low bitrates.
RealMedia files using MJPEG encode every frame independently as a JPEG image, which is inherently inefficient compared to modern inter-frame codecs. H.264 inside M2TS only stores differences between frames for most of the video, achieving far better compression per unit of quality. So even though M2TS is associated with HD and Blu-ray, the actual bitrate of the output depends on the CRF value you set — at CRF 23, H.264 will typically produce a much smaller file than an equivalent-quality MJPEG stream.
The audio is fully transcoded — not copied — because the M2TS container requires properly framed MPEG-TS audio packets rather than a raw RealMedia audio stream. If the source .rm file contains AAC audio, it is decoded and re-encoded into a fresh AAC stream at 128k. If it contains MP3 audio (libmp3lame), the same transcode applies. No audio metadata such as chapter markers or multiple tracks is preserved, as RealMedia does not support those features.
The output is a valid MPEG-2 Transport Stream with H.264 video and AAC audio, which matches the BDAV specification used by Blu-ray and AVCHD. However, burning it to a playable Blu-ray disc requires additional authoring steps — you need software like MakeMKV, tsMuxeR, or a BD authoring tool to wrap the M2TS into the proper BDMV directory structure. For AVCHD camcorder cards, similar folder structure requirements apply.
To change video quality, adjust the -crf value: lower numbers (e.g., -crf 18) produce higher quality at a larger file size, while higher numbers (e.g., -crf 28) compress more aggressively. To change audio bitrate, replace -b:a 128k with a value like -b:a 192k or -b:a 256k for better audio fidelity. For example: ffmpeg -i input.rm -c:v libx264 -c:a aac -crf 18 -b:a 192k output.m2ts.
Yes. On Linux or macOS, you can use a shell loop: for f in *.rm; do ffmpeg -i "$f" -c:v libx264 -c:a aac -crf 23 -b:a 128k "${f%.rm}.m2ts"; 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.m2ts". The browser tool processes one file at a time, so the FFmpeg command is especially useful for large collections or files over 1GB.
Technical Notes
RealMedia (.rm) is a proprietary container from RealNetworks designed for low-bandwidth streaming in the dial-up era. Its video codec in this context is MJPEG — Motion JPEG — which compresses each frame as a standalone JPEG and has no inter-frame prediction, making it easy to seek but very large relative to modern codecs. M2TS uses the MPEG-2 Transport Stream multiplex, originally designed for broadcast and digital satellite TV, and repurposed by Sony and Panasonic for AVCHD and by the Blu-ray Disc Association for BDAV. The H.264 (libx264) encoder used here applies both intra- and inter-frame compression, producing files that are dramatically more storage-efficient than MJPEG at equivalent perceptual quality. One known limitation: RealMedia files sometimes contain proprietary RealVideo (RV10/RV20/RV30/RV40) streams rather than MJPEG — this tool is configured for MJPEG-based .rm files, and RealVideo streams may fail to decode without additional codec support. Subtitles and chapters are not supported in RealMedia, so nothing is lost there. M2TS does support multiple audio tracks and subtitles, but these will not be present in the output unless added manually. No container-level metadata from the source .rm file (such as title or author fields) is automatically transferred to the M2TS output.