Initializing... drag & drop files here
Supports: MPEG2
This walks through turning a .mpeg2 program stream — DVD or broadcast-era MPEG-2 video, standardised as ITU-T H.262 since July 1995 — into a RealNetworks .rm file. It is a deliberately narrow job: RealMedia is a 1990s streaming format, and the encoders available here write the first two generations of RealVideo, not the later ones. If you are only after a file you can watch, stop now and use MPEG-2 to MP4 instead. Keep reading if you are feeding a RealServer archive, matching an existing .rm library, or preserving a format for its own sake — because this page has three sharp edges that the generic converter pages do not.
.mpeg2 file onto the page or click "+ Add Files" to browse. Several clips can be queued and they all convert with the same settings..rm. Files upload over an encrypted connection, are processed on our servers, and are deleted automatically after a few hours — no sign-up, no watermark.On nearly every target format one audio codec is pre-selected and you can ignore the control. RM is the exception. Two separate configuration rules apply to this page at once — one that governs RealVideo output and one that governs the RealAudio codec — and they nominate different defaults. The result is that whichever codec the dropdown happens to land on is not something you should rely on. Pick one explicitly:
| Audio Codec | What you get | When to choose it |
|---|---|---|
| RealAudio 1.0 | Mono only, 8 kHz, roughly 8–16 kbps — a speech codec from 1995 | Maximum authenticity for a period-correct .rm, or a RealPlayer-era system that accepts nothing else |
| AC3 | Dolby Digital, multichannel-capable | A player or archive tool that you have confirmed reads AC-3 from a RealMedia container |
| AAC | Modern lossy audio, multichannel-capable | Same caveat as AC-3 — confirm the consumer first |
Two consequences follow. First, RealAudio 1.0 is genuinely tiny and genuinely mono: a 5.1 DVD soundtrack collapses to a single 8 kHz channel, and there is no Audio Channel or Audio Sample Rate control on this page to intervene. It will sound like a 1995 RealAudio stream, because that is exactly what it is. Second, AAC and AC-3 in a RealMedia container are not pre-flighted by us at all — nothing in the pipeline checks audio codec against container for .rm. If the RealMedia muxer refuses the pairing, the job fails outright rather than quietly substituting something that works. If a conversion errors with no obvious cause, changing Audio Codec to RealAudio 1.0 is the first thing to try.
RealVideo 1.0 and 2.0 do not use a constant-rate-factor scale the way H.264 or VP9 do. They are driven by a quantizer, -q:v, on a 1–31 scale where lower means better quality — the inverse of the CRF scales most guides describe.
| File Compression mode | Behaviour with RealVideo 1.0 / 2.0 |
|---|---|
| Quality Preset (default) | Works normally — scales the source bitrate into a variable-bitrate target with headroom |
| Constant Quality | Emits a quantizer, but the slider arrives pre-set at 23 on the 1–31 scale, which is near the worst end. Drag it down to roughly 4–8 before converting |
| Constraint Quality | The safer manual route — same 1–31 quantizer plus a Max bitrate ceiling |
| Constant Bitrate / Variable Bitrate | Straightforward target rates, with Auto Scale available |
| Specific file size | Works backwards from a byte target, with Auto Scale available |
If you are not sure, leave it on Quality Preset. If you want manual control, use Constraint Quality rather than Constant Quality, because its default position does not fight you.
There is no path here to RealVideo 3 or 4. The encoders available are RealVideo 1.0 and 2.0 — RV10 is derived from H.263 — so do not expect the compression efficiency of the later RealVideo generations that RealPlayer shipped with in the 2000s. A retail CSS-protected DVD also cannot be read here at all; decrypt and rip it to a plain file with desktop software first. And if what you actually needed was the variable-bitrate RealMedia profile rather than the fixed one, MPEG-2 to RMVB is the sibling page. Going the other way later is straightforward — RM to MP4 — but a round trip is lossy in both directions, so keep the original MPEG-2.
There isn't a dependable one, and that is unusual enough to be worth stating plainly. Two configuration rules cover this page simultaneously — one tied to RealVideo output and one tied to the RealAudio codec — and they specify different audio defaults, so the value the dropdown settles on should not be treated as an intentional recommendation. Open Audio Codec and pick from AAC, AC3 or RealAudio 1.0 explicitly before converting.
Because the audio codec and the RealMedia container are not validated against each other before the job runs. There is no compatibility entry for .rm audio in our codec registry, so nothing pre-flights AAC or AC-3 into a RealMedia file — the muxer itself is the first thing that gets an opinion, and when it declines you get a failed conversion rather than an automatic fallback. RealAudio 1.0 is the pairing the container was built around, so try that first when a job fails.
No. The Video Codec list contains RealVideo 1.0 and RealVideo 2.0 only. RealVideo 1.0 is derived from H.263, which puts it in the same efficiency class as late-1990s video coding — a long way behind H.264, let alone VP9 or AV1. The later RealVideo generations are not available here, so a .rm produced on this page will be substantially larger than an MP4 of the same visual quality.
Because RealVideo is a quantizer codec rather than a CRF codec, and its scale runs from 1 to 31 with lower numbers meaning better quality — the reverse of the H.264 CRF convention. The slider inherits a starting value of 23 from the shared rate-control configuration, which on this scale sits near the bottom of the quality range. It is not broken, but it is pointing the wrong way for most people. Drag it down towards 4–8, or use Constraint Quality instead, which pairs the same quantizer with a Max bitrate ceiling.
No. Re-encoding cannot add detail that was never captured, and here you are moving from MPEG-2 to an older and less efficient codec, so the realistic outcomes are "about the same" at a high bitrate and "visibly softer" at a low one. MPEG-2 DVD sources are also standard definition to begin with — 720×480 or 720×576 — so there is little headroom to work with. Convert to RM because something requires the format, never because you expect it to look better.
Very little without effort. RealPlayer is the original and still opens it; some desktop players handle RealMedia through FFmpeg-based decoding, which is why VLC and mpv usually manage it. Browsers, phones, smart TVs and mainstream video editors do not. That is the core reason this page opens by pointing at MP4: if the goal is watching or sharing the video, MPEG-2 to MP4 removes the problem entirely.
No. There is no deinterlacing step anywhere in the pipeline, so an interlaced 480i or 576i source keeps its field structure and will show comb artefacts on motion during progressive playback. If you need clean progressive frames, deinterlace with a desktop tool before uploading. Similarly, non-square anamorphic pixel aspect is not corrected — any resize normalises pixels to square, so widescreen DVD geometry has to be restated manually through Width x Height.
Yes — RM to MP4 converts in the other direction. Understand that it is a second lossy generation on top of the first, though: whatever detail the RealVideo encode discarded does not return, and the RV10/RV20 encode discards a fair amount. If you still have the original .mpeg2, converting that directly to MP4 will always beat a round trip through RealMedia.
Files are uploaded over an encrypted connection, processed on our servers, and deleted automatically after a few hours — no sign-up, no watermark, never shared or made public. There is no fixed per-file quota; on a long DVD capture the real limit is upload size and time over your own connection.