Initializing... drag & drop files here
Supports: RMVB
This walk-through is for anyone sitting on old .rmvb files — typically 2000s Asian film and TV rips from the fansub era — that current browsers, phones and media servers refuse to open. It shows how to re-encode a RealMedia Variable Bitrate clip into WebM, the open royalty-free web container, so the footage plays inline in an HTML <video> element or streams from a self-hosted media server without RealPlayer or a codec pack. It also flags the one codec-and-mode combination on this page that quietly does not do what it looks like it does.
.rmvb onto the page or click "+ Add Files". Batch uploads work and one set of options is applied across the whole queue.HH:MM:SS.sss. Click Convert. Files upload over an encrypted connection, are processed on our servers and are deleted automatically after a few hours — no sign-up, no watermark.| Video Codec | Encode speed | Playback reach | Pick it when |
|---|---|---|---|
| VP9 (this page's starting choice) | Moderate | Very broad — the mainstream WebM codec | You want a small, modern file that plays essentially everywhere WebM plays |
| VP8 | Fastest | Broadest legacy reach, including very old Android | You are targeting genuinely old hardware and accept a larger file |
| AV1 | Slowest by a wide margin | Newer browsers and devices only | You are archiving and encoding time does not matter |
The audio side is simpler: Opus is the modern pairing and better per kilobit, particularly on speech; Vorbis is the original WebM audio codec and the safer bet if something in your chain is old enough to predate Opus. The WebM Project's own definition of the format is "video streams compressed with the VP8 or VP9 video codecs and audio streams compressed with the Vorbis or Opus audio codecs" — AV1 is a later addition that this page also allows, and it is decoded by the browsers that support AV1 at all.
| Mode | What you control | Notes |
|---|---|---|
| Quality Preset | A named level from Highest to Lowest | Where this page starts, on "Very High (Recommended)" |
| Specific file size | A byte target, with an Auto Scale toggle | The box opens at 24 MB; use it when the file must fit a hard limit |
| Constant Bitrate | One fixed bitrate, with Auto Scale | Opens at 4 Mbps; predictable size per minute |
| Variable Bitrate | Target, minimum and maximum bitrate, with Auto Scale | Opens at 4 Mbps target, 2 Mbps floor, 8 Mbps ceiling |
| Constant Quality | A CRF slider from 16 to 63 | Works on VP9 and AV1. On VP8 it is inert — see below. |
| Constraint Quality | A CRF value plus Qmin, Qmax and a Max bitrate ceiling | Quality-targeted encoding that will not exceed a bitrate cap |
The trap is worth stating plainly, because the interface gives no hint: if you switch Video Codec to VP8 and then choose Constant Quality, a 16-63 slider appears and looks exactly like the VP9 one, but the VP8 encoder path does not pass that value through. The encoder falls back to its own internal default instead of honouring the number you set, so dragging the slider changes nothing about the output. On VP8, use Quality Preset, Constant Bitrate or Variable Bitrate — all of which do work — or simply stay on VP9, where Constant Quality behaves as expected.
The RealVideo picture and the RealAudio soundtrack are both fully re-encoded — there is no pass-through path, because WebM only admits its own codec set and RealMedia's codecs are not in it. That means one generation of loss on top of a source that was already lossy, which at the default preset is not something you are likely to notice on SD material, but it does mean the answer to "will this improve my video" is always no.
A format change cannot repair a broken file. DRM-protected RealMedia will not decode anywhere, and a truncated .rmvb from an interrupted download often converts partially and then stops — VLC's repair prompt or a clean re-download is the better first move. If your goal is broad device playback rather than web embedding, WebM is simply the wrong target: use RMVB to MP4. If you want a Matroska container that can hold subtitle tracks and multiple audio streams, RMVB to MKV is closer to what you want. And if your source is a plain .rm from the constant-bitrate streaming era rather than the VBR variant, start at RM to WebM.
Some, unavoidably. This is a re-encode, not a container swap — WebM cannot carry RealVideo or RealAudio, so both streams are decoded and encoded again. The RealVideo source was already lossy, so you are adding a second generation on top of the first. VP9 is efficient enough that at the starting preset the difference on SD material is hard to spot, but nothing recovers detail the original encode discarded.
Per caniuse, full WebM support starts at Chrome 25, Firefox 28, Edge 79, desktop Safari 16 and iOS Safari 17.4, covering roughly 96% of tracked traffic. The Apple versions are the ones that catch people out: a Mac or iPhone that has not been updated in a few years may refuse the file even though every other device you own plays it.
They are transcoded, not carried over. The picture becomes VP9 by default (VP8 or AV1 if you choose), and the soundtrack becomes Opus by default, with Vorbis as the alternative. WebM only admits VP8, VP9 and AV1 video with Vorbis or Opus audio, so there is no configuration in which the original RealMedia codecs survive into the output.
Because the VP8 encoding path does not forward that value to the encoder. The slider renders — it is the same control VP9 and AV1 use — but on VP8 the encoder ends up applying its own internal default rather than your number, so the output is identical whatever you set. This is a real inconsistency in the option surface rather than something you are doing wrong. Use Quality Preset or a bitrate mode on VP8, or switch to VP9.
The rate-control model, not the container. RealMedia (.rm) was designed around constant-bitrate streaming for dial-up and early broadband; RMVB varies the bitrate, spending more data on complex frames, which yields a smaller file at comparable quality and made it the preferred format for video you kept on disk. They share one container format — probing a .rmvb file reports it as RealMedia — which is why a single decoder handles both.
Only for archiving. AV1 compresses better than VP9 at the same visual quality, but it encodes far more slowly and its playback support is narrower — caniuse puts AV1 at around 94% of tracked traffic with Safari and iOS Safari still listed as partial. For an SD source the absolute size saving is small in megabytes, so VP9 is usually the better trade.
Usually. The decode runs on our servers rather than depending on codecs installed on your machine, so files that Windows Media Player or a browser rejects for lack of a RealMedia decoder still convert here. DRM-protected RealMedia is the exception and will not convert anywhere.
Because sharpness is a property of the original encode, not the container. Fansub-era RMVB rips were typically standard-definition and heavily compressed to keep an episode small, and a faithful re-encode reproduces exactly that. A modern codec preserves the existing detail more efficiently; it does not synthesise detail that was never recorded.