Initializing... drag & drop files here
Supports: RMVB
RMVB is RealMedia Variable Bitrate — RealNetworks' 2003 variant of the RealMedia container, aimed at stored files rather than the constant-bitrate streams the original RM format was built around. For most of a decade it was how film and drama releases circulated across Asia, which is why so many of them are still sitting in archives nothing modern will open.
OGV is video in an Ogg container, the free-format stack Xiph.org built around Theora and Vorbis. It was the open-web answer to patent-encumbered video for a few years, and it has since been overtaken almost entirely by WebM.
So this is a conversion between two formats the mainstream has moved past. It is still worth doing when a tool, a wiki upload requirement, or a free-software workflow specifically asks for Ogg — and this page is mainly about the two decisions inside it that actually change your result: which video codec, and which quality control.
The Video Codec list on this page offers exactly two entries, and the page selects VP8. They behave completely differently.
| VP8 (selected) | Theora | |
|---|---|---|
| Origin | On2, released by Google in 2010 | Xiph.org, derived from On2 VP3; bitstream frozen June 2004 |
| Compression efficiency | Meaningfully better | Roughly a generation behind |
| Quality control that works here | Quality Preset only | Quality Preset and Constant Quality |
| Constant Quality slider | Renders at 16-63, opens at 30 — and is discarded | Renders at 0-10, opens at 7, and is honoured |
| Rate control the encoder sees | Bitrate, scaled from your source | A direct quality value |
| Native home container | WebM | Ogg |
| Current browser decoding | Widely supported, but in WebM rather than Ogg | Removed from Chromium in 123, disabled by default in Firefox 126, never shipped in Safari |
The quality-control row is the one that costs people time, so it is worth stating flatly: on VP8 the Constant Quality slider does nothing. Measured on a 10-second RMVB, encoding with the slider at 16 and again at 63 produced files of 376,861 bytes both times — byte-for-byte identical. The value never reaches the encoder, so libvpx falls back to its own internal defaults regardless of what you set.
Quality Preset does work on VP8, because for a video source it scales the real bitrate of the incoming file:
| Setting | Output |
|---|---|
| VP8, Quality Preset at Very High | 417,675 bytes |
| VP8, Quality Preset at Medium | 311,683 bytes |
| VP8, Quality Preset at Lowest | 208,279 bytes |
| VP8, Constant Quality — any slider value | 376,861 bytes |
| Theora, Constant Quality at 9 | 634,796 bytes |
| Theora, Constant Quality at 8 | 544,062 bytes |
| Theora, Constant Quality at 7 (opening value) | 458,490 bytes |
| Theora, Constant Quality at 2 | 193,882 bytes |
So: stay on VP8 and drive it with Quality Preset, or switch to Theora if you want a quality number you can dial directly and do not mind a larger file for the same picture.
.rmvb on the page or click "+ Add Files". Several files can be queued and run with the same settings.The Audio Codec list offers Vorbis (selected), Opus, FLAC and Speex. RMVB files usually carry RealAudio Cook at a low bitrate, sometimes AAC in later releases, so whatever you pick is a second lossy generation on top of a fairly aggressive first one.
Vorbis is the right default: it is Ogg's native audio codec, it is what every Ogg-capable player expects, and it is efficient enough that matching the source bitrate is generous. Opus is technically better at low bitrates but pairs more naturally with WebM. FLAC is lossless and will inflate the file enormously without recovering anything RealAudio discarded. Speex is a speech-only codec from the same era, worth choosing only for voice recordings where size is critical.
Because VP8 is selected and this pipeline does not pass a quality value to libvpx. VP8 was never a quality-target codec in the way H.264 or VP9 are — it works from quantizer bounds and a bitrate — so the slider renders, accepts a number between 16 and 63, and the number is dropped before the encoder runs. Two encodes at opposite ends of the slider produced identical files in testing. Use Quality Preset instead on VP8, or switch the codec to Theora, where the slider is real.
Assume not. Chromium removed Theora decoding in version 123 after disabling it by default in 120; Firefox disabled it by default in 126; Safari never shipped it at all. VP8 is still widely decoded, but browsers expect it inside WebM rather than Ogg, so a VP8-in-Ogg file is an unusual pairing that many players will not recognise. If browser playback is the goal, RMVB to WebM is the correct target and RMVB to MP4 is the universally safe one. Choose OGV when a specific tool or upload policy names it.
The bitstream has not changed since it was frozen in June 2004, so every Theora file ever written still decodes. The reference library is a different question, and the common claim that it was abandoned in 2011 is wrong: libtheora 1.0 shipped in November 2008, 1.1.1 in January 2010, and 1.2.0 on 29 March 2025. So the codec is maintained; what has gone is browser support, which is the part that determines whether your file plays.
Because the blur is in the source and nothing downstream can undo it. RMVB existed to fit a feature-length release into a few hundred megabytes, and RealVideo achieves that by spending its bit budget on motion prediction rather than per-frame detail. Re-encoding faithfully reproduces what it is handed, so raising the quality only prevents additional damage. Give the second encode a bit more room than the first had and stop there — anything beyond that is spending bits to store compression artefacts precisely.
No. There is no deinterlacing step anywhere in this pipeline, so if your RMVB was encoded from an interlaced broadcast master the combing stays baked into every output frame. This is worth checking on television rips, which are the commonest source of interlaced RMVB. A desktop tool with a yadif or bwdif filter is the only fix, and it has to happen before or instead of this conversion.
Yes, and it is the default. Video resolution opens on Keep original, so a 640 x 352 release comes out 640 x 352. Preset Resolutions set the height and let the width follow the source aspect ratio; Width x Height forces both exactly. Be aware that any resize flattens the pixel aspect ratio to square — if your source is anamorphic, set an explicit Width x Height that matches the display shape rather than relying on a preset.
The rate control, and what they were designed for. Original RealMedia targeted constant-bitrate streaming over a fixed connection; RMVB, introduced in 2003, allows the bitrate to vary with scene complexity, which is what you want for a file sitting on a disk. The container structure is the same family and the two extensions are frequently interchangeable in practice — the video codec inside is more likely to be RV30 or RV40 in an RMVB and RV10 or RV20 in an older RM. Both convert through the same path here.
Only if you have a reason. Opus is the better codec by a clear margin at low bitrates, and it is legal inside Ogg — Ogg Opus is a defined mapping. But Vorbis is what Ogg-capable software has expected for twenty years, and the audio in an RMVB is usually so compressed already that the difference between the two at a sensible bitrate is inaudible. Pick Opus if the receiving system asks for it; otherwise Vorbis is the safer pairing.
Yes. Trim opens on Unchanged; switching it to Time Range gives you a Start time and a Duration, each accepting plain seconds or HH:MM:SS.sss. That is one continuous range per job. For several cuts out of a feature-length file, do the surgery first with Video Cutter, which accepts .rmvb directly, and convert each piece afterwards.
Your .rmvb is uploaded over an encrypted connection, decoded and re-encoded on our servers, and both the upload and the .ogv it produced are deleted automatically after a few hours. Files are never shared or made public, no account is required, and no watermark is applied.