MTS to RM Converter

Convert MTS to RM: Read This First

MTS is the AVCHD stream your Sony or Panasonic camcorder writes to its memory card — H.264 video up to 1920x1080 with AC-3 (Dolby Digital) or LPCM audio, introduced by Sony and Panasonic in 2006. RM is RealNetworks' RealMedia container from the late-1990s and 2000s streaming era, and its ecosystem wound down after RealNetworks sold its video patents and next-generation codec software to Intel for $120 million, a deal completed on April 5, 2012. So converting modern HD camcorder footage into RealMedia produces a file that almost nothing plays in 2026 — RealPlayer is rarely installed, and outside of FFmpeg-based players like VLC there is little that opens a fresh .rm. Most people who land here actually want a file that plays everywhere, which is MTS to MP4, not this. Only continue with RM if a specific legacy system genuinely requires a .rm.

MTS vs RM at a Glance

How to Convert MTS to RM

1. Upload Your MTS File: Drag and drop your .MTS clip onto the page, or click "Add Files" to browse. You can queue several clips and they share the same output settings.
2. Set the Video Codec to RealVideo: Open "Show All Options" and leave Video Codec on RealVideo 1.0 (RV10), the default — it is the H.263-class codec the most RealMedia players recognize. RealVideo 2.0 (RV20) is the only other choice; it is the slightly later RealVideo G2 codec. Both are far less efficient than the H.264 in your MTS.
3. Pick Quality, Resolution, and Trim (Optional): Choose a Quality Preset (the default is "Very High (Recommended)") or switch to Constant Bitrate or Specific file size for an exact MB target. Use Preset Resolutions or Resolution Percentage to scale the 1080p source down to a streaming-era frame size, and switch Trim from "Unchanged" to a Time Range to export just one section.
4. Convert and Download: Click "Convert" and download your .rm. No sign-up, no watermark.

Walk-through: codec, audio, and resolution for a usable RealMedia file

The honest part of this conversion: H.264 inside your MTS is a far more efficient, modern codec than anything RealMedia can hold. Re-encoding to RealVideo means going backward into an abandoned, less efficient codec — to match the same visual quality you need a higher bitrate, or quality drops if you keep the bitrate low. You are doing this to satisfy a legacy .rm requirement, not to gain anything technically. Set the options around that target:

• Keep the codec on RealVideo 1.0 (RV10) unless a system specifically wants RV20. RV10 is RealVideo 1.0, the H.263-based codec that shipped with RealPlayer 5; RV20 is the later RealVideo G2, introduced with RealPlayer 6. Both encode through FFmpeg's open-source RealVideo encoders. RV10 is the most broadly recognized, so it is the safe default.
• Pick the audio codec to match the target player. The Audio Codec list offers RealAudio 1.0 (the REAL_144 codec — the period-correct pairing for .rm), AAC, and AC3. The original AVCHD AC-3 or LPCM track is transcoded either way; a 5.1 surround mix is downmixed during conversion.
• Match the legacy target's resolution, and expect it to be small. RealMedia was built for dial-up and early-broadband streaming, so source material was usually 320x240 or similar. Use Preset Resolutions or Resolution Percentage to scale the 1080p source down; keeping it at full HD bloats the file and helps nothing, since any device that plays 1080p comfortably can play MP4.
• Export one section instead of the whole clip. A long 1080p AVCHD recording re-encoded to RealVideo will be large. Switch Trim to a Time Range and set the start and duration to keep the .rm manageable.

The codec choices in one view:

Common Errors and How to Fix Them

• "The RM file won't open on my computer" — that is expected in 2026, not a conversion fault. RealVideo development stopped after the 2012 patent sale to Intel, and RealPlayer is rarely installed today. Play the file in VLC or another FFmpeg-based player, which still decode RealVideo.
• "File is much larger than the MTS, or looks soft" — RealVideo (RV10/RV20) is an H.263-era codec, roughly half as efficient as the H.264 in your MTS, so matching quality takes more bits and a low bitrate looks blocky. Drop the resolution to a streaming-era size, raise the Quality Preset, or set a higher Constant Bitrate.
• "No audio in the converted file" — confirm the player supports the audio codec you picked. Very old RealPlayer builds expect specific RealAudio versions; an FFmpeg-based player like VLC is the most reliable way to hear it.
• "The MTS itself won't convert" — a genuinely corrupted or partially-copied camera clip cannot be fixed by any converter. Re-copy the original .MTS off the camcorder card and try again.

When This Doesn't Work

For almost every real-world goal in 2026, RM is the wrong target — you would be re-encoding modern HD into an abandoned format with no playback benefit. If you just want camcorder footage that plays on a phone, laptop, browser, or smart TV, convert to MTS to MP4 instead; H.264-in-MP4 keeps your quality and plays everywhere. The only honest reason to make a .rm is feeding an un-migrated legacy system that still expects RealMedia — an old intranet streaming server, a media archive indexed by .rm filenames, or courseware wired to RealPlayer that nobody has migrated yet. If you are going the other direction and need to get footage out of an old .rm and onto a camcorder-style format, use the reverse converter, RM to MTS. And if a legacy Flash system is your actual target rather than RealMedia, MTS to FLV is the closer match.

Frequently Asked Questions

Why would I convert HD MTS footage into RM at all?

Honestly, for almost no modern reason. The one legitimate case is feeding an un-migrated legacy system that still expects RealMedia — an old intranet or campus streaming server, a media archive that indexes files by .rm, or RealPlayer-based courseware nobody has migrated. If none of those apply, MTS to MP4 keeps your quality and plays in every browser, phone, and editor without hunting for a RealMedia decoder.

Will the converted RM file play on modern devices and browsers?

No, not natively. RealVideo development stopped after RealNetworks sold its video patents and codec software to Intel in 2012, and no current browser, phone, or smart TV decodes RealMedia out of the box. To play the .rm you generally need VLC or another FFmpeg-based player; the official RealPlayer is rarely installed today. This is the core reason the page steers most people to MP4 instead.

Which video codec does the RM use, and can I get H.264?

The default is RealVideo 1.0 (RV10), the H.263-based codec that shipped with RealPlayer 5, and the only other option is RealVideo 2.0 (RV20), the later RealVideo G2. Both are encoded through FFmpeg's open-source RealVideo encoders and are far less efficient than H.264. H.264 is not a valid codec inside a RealMedia container — if you need H.264, you are really looking for MTS to MP4.

What happens to the AC-3 or LPCM audio from my MTS?

It is transcoded to whichever codec you pick under Audio Codec — RealAudio 1.0 (REAL_144, the period-correct pairing for a RealMedia file), AAC, or AC3. A 5.1 surround track from the camcorder is downmixed to stereo during conversion. RealAudio 1.0 is the choice legacy RealPlayer-era tooling expects; AAC sounds far better on modern FFmpeg-based players.

Why is the RM file blocky or larger than I expected?

Because RealVideo (RV10/RV20) is an H.263-era codec from the late 1990s, roughly half as efficient as the H.264 in your MTS. Matching the source quality therefore needs a higher bitrate, and a low bitrate produces visible blocking. In our testing, a 60-second 1080p AVCHD clip re-encoded to RV10 at a streaming-era resolution looked noticeably softer than the H.264 source at the same bitrate — that is the codec, not the converter. Scale the resolution down and raise the bitrate to keep it watchable.

What is the difference between RM and RMVB, and which should I make?

Both are RealMedia containers. A plain .rm was tuned for constant-bitrate streaming — the format old RealServer and RealPlayer pipelines expect — while .rmvb is the later variable-bitrate variant popular for locally stored files. If the legacy system you are feeding names .rm, stay here; if it specifically wants the VBR variant, use MTS to RMVB instead so the container matches what it expects.

Can I convert several MTS clips in one batch?

Yes. Queue multiple .MTS files in one upload and they all convert with the same settings — the same codec, quality preset, resolution, and trim range apply to every clip in the batch. That is convenient for a card full of camcorder segments destined for the same legacy system, but set the options before you start the batch.

What happens to my file after I convert it?

Your MTS is uploaded over an encrypted connection, processed on our servers, and deleted automatically a few hours after conversion. Files are never shared or made public, and there is no sign-up or watermark.