RM to MTS Converter

Convert RM to MTS: What This Tutorial Covers

This walks you through turning an old RM (RealMedia) video into an MTS (AVCHD) file — re-encoding RealVideo to H.264 so the clip drops into an AVCHD-style camcorder workflow. It is aimed at people rescuing 1990s–2000s RealMedia archives, and it is honest about what you can and can't get back: RealVideo's compression losses are permanent, so the goal here is a clean, editable re-encode, not a quality upgrade.

How to Convert RM to MTS

1. Upload Your RM File: Drag and drop your .rm (or .rmvb) file, or click "+ Add Files." Batch upload works — queue several clips and they convert with the same settings. Files are uploaded over an encrypted connection.
2. Confirm the Video and Audio Codec: MTS output defaults to H.264 video with AAC audio under Advanced Options. Leave these as-is for the widest AVCHD-editor compatibility; H.264 is the codec real AVCHD camcorders record.
3. Set Resolution and Quality (Optional): Use Video resolution to keep the source size (recommended for SD Real streams — there is no detail to upscale into), set Quality Preset to "Very High," or cap output with Specific file size. Use Trim to clip a time range before encoding.
4. Convert and Download: Click "Convert" and download your .mts file. No sign-up, no watermark.

Walk-through: Choosing Codec, Resolution, and Audio

The defaults are right for most RealMedia rescues, but here is what each control actually does so you can match your source:

• Keep the resolution at the original. Real streams from the dial-up and early-broadband era were encoded small and soft — often 320×240 or smaller. Upscaling to 1080 only interpolates pixels; it adds file size, not detail. Set Video resolution to "Keep original" unless an editor specifically demands a fixed frame size.
• Leave the video codec on H.264. AVCHD is an H.264/MPEG-4 AVC format by design, so H.264 is what editors expect inside a .mts wrapper. The page also exposes H.265, MPEG-2, MPEG-4, DivX, and Xvid — but choosing anything other than H.264 produces a file that is .mts in name only and may confuse AVCHD-aware tools.
• Audio defaults to AAC; switch to AC3 if your editor wants true AVCHD audio. Genuine AVCHD uses Dolby AC-3 or LPCM. AAC plays back fine and keeps files small, but if you are feeding a strict AVCHD pipeline, pick AC3 under Audio Codec to mirror the spec.
• Don't expect to recover lost quality. RealVideo is lossy. Re-encoding to H.264 preserves what survived the original encode; it cannot reconstruct detail RealNetworks' codec already discarded. Use a high quality preset so the re-encode itself doesn't add a second generation of loss.

Common Errors and How to Fix Them

• "Why is my MTS the same softness as the RM?" — That softness is baked into the RealVideo source from its original low-bitrate streaming encode. Converting can't remove it. Keep the original resolution so you don't amplify it by upscaling.
• "My editor imports the file but the audio is missing or wrong." — Some AVCHD-strict editors expect AC-3 or LPCM, not AAC. Re-run the conversion with Audio Codec set to AC3.
• "The .mts won't open in a basic media player." — Plain MTS isn't as universally playable as MP4. If you just want a file that plays everywhere, use RM to MP4 instead — MP4 with H.264 + AAC opens on virtually every device and browser.
• "My RM file won't upload or convert at all." — Check that it isn't a DRM-protected RealMedia stream (many paid 2000s downloads were). Encrypted RM cannot be decoded.
• "The output file is bigger than the original." — Old Real streams were heavily compressed for dial-up; a modern H.264 re-encode at high quality can legitimately be larger. Lower the Quality Preset or set a Specific file size target.

When This Doesn't Work — and Whether You Even Need MTS

Be honest with yourself about the target format first. MTS / AVCHD is a camcorder and editing-workflow container — its main advantage is that some editors auto-detect .mts as AVCHD footage. That is a narrow reason. If you are not feeding a specific AVCHD pipeline, MP4 is almost always the better choice: use RM to MP4 for a file that plays on any phone, browser, or TV. If you only want the soundtrack from a RealMedia clip, RM to MP3 extracts the audio directly. Conversion also fails on DRM-locked or corrupted RM files — no server-side tool can decode an encrypted stream. And because RealVideo decoders survive today mainly through open-source projects like FFmpeg rather than RealNetworks itself (which sold the bulk of its video-codec patents and next-generation codec software to Intel, a deal completed April 5, 2012), the practical advice is to migrate aging Real archives now, while decoders are still maintained.

Frequently Asked Questions

Why would I convert RM to MTS instead of MP4?

Almost the only good reason is an AVCHD editing workflow — some editors (and camcorder-import tools) auto-detect .mts as AVCHD footage and treat it accordingly. That is niche. For general playback, sharing, or archiving, MP4 with H.264 is more compatible and smaller for the same quality, so most people should use RM to MP4 instead. Pick MTS only when a specific AVCHD pipeline asks for it.

Will converting from RM to MTS improve the video quality?

No. RealVideo is a lossy codec, and the losses from the original encode are permanent — re-encoding to H.264 can't reconstruct detail that was already thrown away. A clip that streamed at a low dial-up-era bitrate will look exactly as soft in MTS. The conversion gives you an editable, modern H.264 file; it does not give you a sharper picture.

Should I upscale my old RM video to 1080p when converting?

No. Most 1990s–2000s Real streams were encoded at small resolutions like 320×240 for slow connections. Upscaling to 1080 only interpolates pixels and bloats the file without adding real detail. Set Video resolution to "Keep original" so the MTS keeps the source dimensions. Real upscaling needs AI tooling, not a format conversion.

Why is my RM file so small and low-resolution to begin with?

RealMedia was built by RealNetworks (starting around 1997) for streaming over dial-up and early broadband, so files were aggressively compressed and often kept at sub-VHS resolutions to survive slow connections. In our testing, typical archived .rm clips decode to roughly 320×240 with visible compression softness — that is the source ceiling, and no conversion target, MTS included, can exceed it.

Can I convert a DRM-protected or RMVB RealMedia file?

RMVB (the variable-bitrate RealMedia variant) converts the same way — just upload it. DRM-protected RM files, common among paid 2000s downloads, cannot be decoded by any server-side converter because the stream is encrypted; you would need the original DRM-licensed player. If your file fails to upload or errors out, encryption is the most likely cause.

Is my file kept private after the conversion?

Yes. Your RM file is uploaded over an encrypted connection, processed on our servers, and deleted automatically a few hours after conversion. No account is required, there are no watermarks, and files are never shared or made public. If you need the reverse direction, MTS to RM re-encodes AVCHD footage back into the RealMedia container.