Convert RMVB to MP4
RealMedia Variable Bitrate (RMVB) was the dominant fansub and download format across Asia in the 2000s. Modern browsers refuse it, mobile devices refuse it, RealPlayer's support has stalled. Wave decodes RealVideo and Cook audio locally in your browser and re-encodes to a modern H.264 MP4.
What actually changes
RMVB is a container extension of RealMedia (.rm), the format Real Networks shipped alongside RealPlayer starting in 1997. The .rm files were constant-bitrate; .rmvb variable-bitrate versions started shipping around 2002 and became the default packaging for high-quality Asian video downloads through the mid-2010s. A typical RMVB file contains RealVideo 9 or 10 (RV40) video and Cook audio - both proprietary Real codecs, both licensed strictly for a decade until the patents expired and open-source implementations became feasible.
MP4 rejects RealVideo and Cook entirely - the codec sets don't overlap (see Codecs vs containers for the wrapper-vs-codec framing). Wave decodes both streams through the FFmpeg-wasm engine (which contains the reverse-engineered RealVideo and Cook decoders that landed in FFmpeg between 2004 and 2010, now well-audited), then re-encodes video to H.264 via WebCodecs and audio to AAC. The re-encode preserves the visual quality of the source; RealVideo 10 at reasonable bitrates and H.264 at similar bitrates are perceptually indistinguishable on typical content.
The reason RMVB fell out of use by 2015 was not codec quality - RV40 was competitive with H.264 - but the licensing model. Real Networks required per-decode royalties from software vendors, which killed cross-platform playback support. Chrome refused to bundle a decoder; iOS never had one; Android varied by manufacturer. Meanwhile H.264 in MP4 was the codec every hardware decoder targeted. A large body of Asian TV and film in RMVB now needs conversion to be played on any current device.
File-size expectations: a typical 45-minute anime episode as RMVB at "high quality" was 175-250 MB in the format's heyday. Wave's H.264 re-encode at equivalent visual quality lands around 300-450 MB - larger because H.264 at 2005-era comparable-quality bitrates is less efficient than the aggressive Real encoders were (though modern H.264 encoders can match). If storage matters, use HandBrake locally after Wave with the H.265 preset to bring the file back down to RMVB-scale size.
Three steps.
-
01
Step 1
Drop your .rmvb (or .rm) file onto Wave. Wave inspects and confirms Re-encode from RealVideo + Cook to H.264 + AAC.
-
02
Step 2
Convert. The re-encode runs through the browser's WebCodecs H.264 encoder for hardware acceleration; a 45-minute episode typically finishes in 3-5 minutes.
-
03
Step 3
Save the output MP4. Plays on every modern browser, mobile device, and smart TV.
Answers, specifically.
Will the H.264 MP4 look as good as the RealVideo source?
At the H.264 bitrate Wave targets, effectively yes on any consumer display. RealVideo 10 was competitive with early H.264 encoders; re-encoding through a modern H.264 encoder recovers most of that efficiency. Studio-monitor comparison might show minor edge-detail changes; casual viewing is indistinguishable.
What is Cook audio?
Real Networks' proprietary audio codec, used inside RM and RMVB containers from the late 1990s onward. Fixed sample rate (typically 44.1 kHz) with a range of bitrates from 8 kbps voice to 128 kbps stereo music. Wave decodes it through FFmpeg-wasm and re-encodes to AAC at 192 kbps.
RMVB with hard-coded subtitles - do they survive?
Yes. Hard-coded subtitles are burned into the video frames, so the re-encode preserves them as image content. Soft subtitles (embedded as a separate track) are rare in RMVB and would be dropped during the conversion.
Multiple audio tracks (Japanese + Chinese dubs)?
Wave takes the default-flagged audio track. If the RMVB has two languages and you need the alternate, ffmpeg locally works: `ffmpeg -i input.rmvb -map 0:v -map 0:a:1 -c:v libx264 -c:a aac output.mp4`.
.rm (constant bitrate RealMedia) - same converter?
Yes. The container format is the same; only the bitrate model differs. Wave handles both identically. If your file has both audio and video, it converts; if it's RealAudio only (no video track), use the /rm-to-mp3/ page for MP3 extract.
What size RMVB files can I convert?
Wave handles up to 8 GB per file. Typical RMVB files are 175 MB - 1 GB, so this is rarely a constraint. For larger files, ffmpeg locally handles them without size limit.
The output plays but the aspect ratio is wrong.
RMVB sometimes encodes non-square pixel aspect ratios that RealPlayer respected but H.264 does not encode natively. Wave detects the sample aspect ratio and applies it during re-encode; if the output looks stretched, the source may have declared an unusual aspect ratio. Right-click the output MP4 in VLC and use Video → Aspect Ratio → 16:9 or 4:3 to override.