RM to M2V Converter
Initializing... drag & drop files here
Supports: RM
Advanced Options - Our defaults are optimized for the best results. We recommend you keeping the defaults unless you have a specific need.
Reset to defaults
Need help?Convert RM to M2V
An .m2v file is an MPEG-2 video elementary stream: coded pictures and nothing else. No container, no audio track, no subtitle track, no metadata. It is the raw output of an MPEG-2 encoder, the form DVD and broadcast authoring tools expect when they want to multiplex the video and the audio themselves rather than accept a pre-muxed file.
RM is the other end of the spectrum — RealNetworks' RealMedia container, holding RealVideo and RealAudio streams that were sized for dial-up and early broadband. Converting one to the other decodes the RealVideo, re-encodes it as MPEG-2, and writes it bare. The RealAudio does not come along, and that is not an oversight.
How to Convert RM to M2V
- Upload Your RM File: Drag the
.rmfile onto the page or click "Add Files". Several clips can be queued and share the same settings. Uploads travel over an encrypted connection and are processed on our servers. - Leave Video Codec on MPEG-2: The codec list is long here — DivX, H.261, H.263, H.263+, H.264, H.265, MJPEG, MPEG-1, MPEG-2, MPEG-4 and Xvid — but MPEG-2 is what opens, and it is the only one that makes the
.m2vextension mean what it says. Anything else produces a file whose name misdescribes its contents. - Set Video Resolution: Video resolution opens on Keep original, with Resolution Percentage, Preset Resolutions, Width, Height and Width x Height available. On this route resolution is not a minor setting — it is the control with the most influence on the output, for reasons the bitrate section explains.
- Set File Compression and Convert: Compression opens on Quality Preset at Very High (Recommended), alongside Specific file size, Constant Bitrate, Variable Bitrate, Constant Quality and Constraint Quality. Click Convert and save the
.m2v. No sign-up, no watermark; files are deleted automatically after a few hours.
There Is No Audio in an M2V, and the Page Reflects That
You may notice an Audio Codec heading with nothing under it. That is correct rather than broken: an MPEG-2 video elementary stream has no provision for an audio track, so no codec is offered and none is applied. We converted a RealMedia file carrying a full stereo audio track through this path and probed the output — one mpeg2video stream at the source frame size, inside a mpegvideo elementary stream, and no audio stream at all.
If your destination is DVD authoring, this is exactly the workflow the tools want. The standard pattern is two files: the video as .m2v and the audio as a separate elementary stream, usually AC-3 or MP2, which the authoring package multiplexes together as it builds the disc. To produce that pair here, convert the same .rm twice — once on this page for the video, and once through an audio target such as RM to MP3 for the sound, re-encoding it to the format your authoring tool asks for.
If you would rather have one file with picture and sound already together, you want a container instead: RM to MPEG writes the same MPEG-2 video into a program stream with the audio alongside it, and RM to MP4 is the general-purpose answer.
The MPEG-2 Bitrate Floor, and Why the File Grew
MPEG-2 cannot be starved. Below a certain bitrate for a given frame size the encoder fails outright, so the pipeline enforces a minimum and raises any lower request up to it. That minimum scales with the pixel count:
| Output frame size | Enforced minimum video bitrate |
|---|---|
| 352×288, 640×480, 720×480, 720×576 — anything standard definition | 2.0 Mbit/s (the floor) |
| 1280×720 | About 2.8 Mbit/s |
| 1920×1080 | About 7.5 Mbit/s |
| 2560×1440 | About 16.6 Mbit/s |
| 3840×2160 | About 44.8 Mbit/s |
This is where most of the surprise on this route comes from. We converted a 640×480 RealMedia clip encoded at 700 kbit/s and the resulting .m2v measured about 2.2 Mbit/s — roughly three times the source rate — because 2 Mbit/s is the floor at that frame size and the encoder will not go below it. The output is bigger than the input, and no compression setting can change that without also changing the resolution.
The lever that does work is the frame size. Fewer pixels means a lower floor and a genuinely smaller file, so if size matters, set Width x Height or a preset height rather than fighting the bitrate controls.
Which Controls Actually Move the Output
MPEG-2 has no constant-quality mode, and that changes what several of the compression settings do:
| Control | Effect on an MPEG-2 elementary stream |
|---|---|
| Video resolution | The most effective control. Fewer pixels lowers the enforced bitrate floor and shrinks the file |
| Specific file size | Works — the encoder targets your byte budget, subject to the floor above |
| Constant Bitrate | Works — a fixed rate, again subject to the floor |
| Variable Bitrate | Works — a target with headroom for complex scenes |
| Quality Preset | Works indirectly. With no quality mode available it scales the source bitrate instead: 1.5× at Highest, 1.32× at the Very High default, 1.14× at High, 0.9× at Medium, 0.72× at Low, 0.54× at Very Low and 0.3× at Lowest |
| Constant Quality | Ineffective. The value is accepted and then converted to a plain bitrate at the minimum for the frame size — the number you type does not reach the encoder as a quality setting |
| Constraint Quality | Ineffective for the same reason — it collapses into the same bitrate substitution |
The short version: use resolution plus one of Specific file size, Constant Bitrate or Variable Bitrate. The two quality-shaped controls look like they should work and do not, which is worth knowing before you spend time tuning a slider that is being discarded.
Frequently Asked Questions
Why does my M2V file have no sound?
Because the format cannot hold any. An MPEG-2 video elementary stream is a bare sequence of coded pictures — there is no multiplexing layer to carry a second stream, which is why the Audio Codec list on this page is empty. This is normal and expected for .m2v. If you need audio in the same file, convert to a container instead; if you are authoring a disc, convert the audio separately and let the authoring tool combine them.
Can I select H.264 and still call the file .m2v?
The codec list will let you, and the file will be written, but you should not. The .m2v extension specifically denotes MPEG-2 video, and any tool that reads it expects an MPEG-2 sequence header. Handing such a tool an H.264 stream under that name usually results in a refusal rather than a graceful fallback. If you want H.264 as an elementary stream, use an extension that says so.
Why is my M2V larger than the RM file it came from?
Two reasons compound. MPEG-2 is roughly a generation behind the codecs RealVideo competed with in efficiency, so matching the same picture needs considerably more bits. On top of that, the encoder enforces a minimum bitrate for the frame size — 2 Mbit/s at standard definition — so a 700 kbit/s source is re-encoded at nearly three times its original rate. Reduce the frame size if the output size matters; that is the only change that lowers the floor.
How do I turn this back into something with picture and sound together?
Feed it to an authoring or muxing tool along with a separate audio file. That is the workflow .m2v exists to serve, and DVD authoring packages handle it as a matter of routine. If you have no such workflow and simply wanted a playable file, converting the original .rm to a container was the right route in the first place — an elementary stream is a building block, not a deliverable.
Will an M2V file play in VLC or a media player?
VLC and other FFmpeg-based players will show the picture, since decoding a bare MPEG-2 sequence is straightforward. What you will notice is missing scaffolding: seeking is imprecise or unavailable because there is no index, the reported duration may be wrong or absent, and there is of course no audio. It plays, but it does not behave like a proper media file — which is a fair description of every elementary stream.
Should I upscale my old RealMedia clip before converting?
No, and on this route it is actively expensive. Upscaling adds no detail — it interpolates the pixels that are already there — and it raises the enforced bitrate floor sharply, so a 320×240 clip pushed to 1080p goes from a 2 Mbit/s minimum to roughly 7.5 Mbit/s while looking no better. Leave Video resolution on Keep original, or reduce it.
Does the conversion deinterlace or clean up the old footage?
No. There is no deinterlacing anywhere in this pipeline, so an interlaced source keeps its comb artifacts and they are re-encoded into the MPEG-2 stream. MPEG-2 does carry interlaced video natively, so this is not a problem for a disc-authoring workflow, but do not expect the conversion to tidy up the picture. Pixel aspect is worth watching too: leaving resolution on Keep original preserves the source's sample aspect, while any resize flattens it to square pixels.
How are my files handled while they are on your servers?
The .rm file is uploaded over an encrypted connection, converted on our servers, and both the upload and the finished .m2v are deleted automatically after a few hours. There is no account to create, no watermark, and files are never shared or made public. Since the enforced bitrate floor makes MPEG-2 output large, download size can matter as much as upload size here — trimming the source first with the Video Cutter, which accepts .rm directly, keeps both manageable.