Convert M2TS to RM — Free Online Tool
Convert M2TS Blu-ray and AVCHD video files to RealMedia (.rm) format using MJPEG video encoding and AAC audio — entirely in your browser with no file uploads. This tool bridges the gap between modern high-definition disc formats and the legacy RealMedia streaming container from the early internet era.
to
FFmpeg Command
Copy this command to run the same conversion locally with FFmpeg on your desktop. Download FFmpeg
Drop your M2TS 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
M2TS files typically contain H.264 or H.265 video with Dolby Digital or DTS audio streams inside an MPEG-2 Transport Stream wrapper — a container built for Blu-ray disc and AVCHD camcorder use. Converting to RM requires a full re-encode of both streams: the video is transcoded to MJPEG (Motion JPEG), which stores each frame as an independent JPEG image rather than using inter-frame compression like H.264, and the audio is transcoded to AAC at 128k bitrate. Because MJPEG encodes every frame independently, it loses all the temporal compression efficiency that makes H.264 and H.265 so compact — expect significantly larger output files for equivalent visual quality, or noticeably lower quality at similar file sizes. The RM container itself is a proprietary RealNetworks format with no support for subtitles, chapters, or multiple audio tracks, so any secondary audio tracks or subtitle streams in the M2TS source will be dropped.
What Each Flag Does
| Flag | What it does |
|---|---|
ffmpeg
|
Invokes the FFmpeg command-line tool, the open-source multimedia framework that powers this conversion both locally and inside the browser via FFmpeg.wasm (WebAssembly compilation). |
-i input.m2ts
|
Specifies the input file — an M2TS Blu-ray or AVCHD container that may contain H.264/H.265 video, Dolby Digital or DTS audio, subtitle streams, and multiple audio tracks. FFmpeg will parse the MPEG-2 Transport Stream structure to identify all available streams. |
-c:v mjpeg
|
Transcodes the video stream to MJPEG (Motion JPEG), the only video codec supported by FFmpeg's RM muxer. Unlike the H.264 or H.265 in the source M2TS, MJPEG compresses each frame independently as a JPEG image, with no inter-frame prediction or temporal compression. |
-c:a aac
|
Re-encodes the audio to AAC, replacing whatever codec is in the M2TS source — typically Dolby Digital, DTS, or lossless TrueHD — since none of those are compatible with the RealMedia container. AAC is the higher-quality of the two audio options available in this RM output. |
-q:v 5
|
Sets the MJPEG video quality using a scale of 1 (highest quality, largest file) to 10 (lowest quality, smallest file). A value of 5 is the midpoint default, balancing file size against visual fidelity; lower values like 2 or 3 will produce sharper frames from the original HD M2TS content at the cost of larger output files. |
-b:a 128k
|
Sets the AAC audio bitrate to 128 kilobits per second, the default for this conversion. This is adequate for stereo audio but represents a significant downgrade from the lossless or high-bitrate audio tracks often found in Blu-ray M2TS sources; increase to 192k or 256k for better fidelity. |
output.rm
|
Defines the output file with the .rm extension, telling FFmpeg to use the RealMedia muxer. The resulting file is a proprietary RealNetworks container holding MJPEG video and AAC audio, with no subtitle tracks, chapters, or secondary audio streams from the original M2TS. |
Common Use Cases
- Archiving Blu-ray or AVCHD footage into a legacy format for playback in older RealPlayer-based kiosk systems or institutional media libraries that have not been updated since the early 2000s
- Creating low-resolution preview clips from HD camcorder M2TS footage for distribution over very slow or constrained network connections that historically relied on RealMedia streaming infrastructure
- Preparing video content for retro-web or digital history projects that intentionally recreate the look and feel of early 2000s internet video portals
- Converting short AVCHD clips from a camcorder into RM files for compatibility with legacy video editing or cataloging software that only accepts RealMedia input
- Extracting a single audio-video stream from a multi-track M2TS broadcast recording and packaging it in RM for use in a legacy e-learning platform built on RealMedia delivery
- Testing or demonstrating MJPEG encoding characteristics on real-world Blu-ray source material for educational or forensic video analysis purposes
Frequently Asked Questions
M2TS files use highly efficient inter-frame codecs like H.264 or H.265 that compress video by storing only the differences between frames. MJPEG, the only video codec supported by the RM container here, compresses each frame independently as a JPEG image with no inter-frame prediction. This means MJPEG requires dramatically higher bitrates to match the visual quality of H.264, and at the default quality setting (-q:v 5) the output will be noticeably softer than your Blu-ray or AVCHD source. If quality is critical, try lowering the -q:v value toward 1 or 2 for sharper MJPEG output.
No — the RealMedia container does not support subtitles, chapters, or multiple audio tracks in this context. Only the primary video and first audio stream from your M2TS file will be included in the output. If your M2TS source contains Blu-ray PGS subtitles, Dolby TrueHD tracks, or multiple language audio streams, all of those will be silently discarded during conversion. If preserving these elements matters to you, consider an intermediate format like MP4 or MKV instead.
Dolby Digital (AC-3) and DTS audio — common in M2TS files from Blu-ray discs — are fully re-encoded to AAC at 128k bitrate during this conversion. Neither codec is supported in the RM container, so transcoding is unavoidable. AAC at 128k is a reasonable quality level for stereo content, but if your source has lossless audio like Dolby TrueHD or DTS-HD Master Audio, you will experience a significant quality reduction. You can increase the -b:a value to 192k or 256k in the FFmpeg command to partially mitigate this.
For video quality, adjust the -q:v value: lower numbers mean higher quality MJPEG (1 is best, 10 is worst), with 5 as the default. For example, use -q:v 2 for significantly sharper output at the cost of a larger file size. For audio quality, change -b:a 128k to a higher value like -b:a 192k or -b:a 256k — the RM format supports up to 256k for AAC audio. Note that because MJPEG is inherently less efficient than H.264, even high-quality settings will produce larger files than the original M2TS.
Yes — on Linux or macOS you can batch process with a shell loop: for f in *.m2ts; do ffmpeg -i "$f" -c:v mjpeg -c:a aac -q:v 5 -b:a 128k "${f%.m2ts}.rm"; done. On Windows Command Prompt, use: for %f in (*.m2ts) do ffmpeg -i "%f" -c:v mjpeg -c:a aac -q:v 5 -b:a 128k "%~nf.rm". The browser-based tool processes one file at a time, so the FFmpeg command is especially useful for batch jobs or files larger than 1GB.
RealMedia support in modern players is limited but not absent. VLC Media Player and MPC-HC can generally open RM files, including those with MJPEG video and AAC audio. However, the format is effectively obsolete and was never adopted by mobile platforms or modern streaming services. If your goal is broad compatibility, converting to MP4 (H.264 + AAC) would serve you far better — RM is only the right choice when a specific legacy system explicitly requires it.
Technical Notes
The RM container is a proprietary binary format designed by RealNetworks in the mid-1990s for dial-up and broadband streaming, and it carries significant modern limitations. FFmpeg's RM muxer supports only MJPEG for video and AAC or MP3 for audio, meaning the rich codec ecosystem of the M2TS source — H.264, H.265, VC-1, Dolby TrueHD, DTS-HD, lossless PCM — is entirely unavailable in the output. MJPEG is an intra-frame-only codec: each frame is a self-contained JPEG, which makes it excellent for frame-accurate editing but very inefficient for storage compared to modern predictive codecs. A 1080p M2TS file at 25 Mbps (typical Blu-ray) converted to MJPEG at -q:v 5 may produce an RM file that is larger despite appearing lower quality, due to MJPEG's inherent inefficiency. Metadata from the M2TS container — including disc title information, stream language tags, and timestamp data — will not be transferred to the RM output, as the format has no standardized metadata fields equivalent to those in modern containers. The 1GB browser processing limit is particularly relevant here: large Blu-ray M2TS files often exceed 1GB, making the displayed FFmpeg command especially practical for local desktop use with full-length recordings.