RM to WEBA Converter

RM to WEBA: Pulling Opus Audio Out of a RealMedia File

RM is RealNetworks' container from the dial-up era. The audio inside is normally RealAudio — usually the Cook codec at somewhere between 32 and 64 kbps, occasionally AAC in later files — and it is the reason those files existed at all: RealAudio was the first codec that made streaming speech over a modem tolerable.

.weba is the audio-only convention for WebM. Open one in a hex editor and the first four bytes are 1A 45 DF A3, the EBML signature — a .weba is a Matroska/WebM file that happens to contain only an audio track, and the extension is a naming habit rather than a separate format. What goes inside it here is Opus, the codec standardised in RFC 6716 that WebM pairs with audio-only content.

This page throws away the RealVideo picture, decodes the RealAudio track, and re-encodes it as Opus in a WebM container.

How to Convert RM to WEBA

1. Upload Your RM File: Drop the .rm on the page or click "+ Add Files". Several files can be queued and run with the same settings.
2. Set File Compression: The panel opens on Quality Preset. Read the next section before you trust it — on this route the presets ask for far more than the material can use. Custom Bitrate (a free value, preset to 128 kbps) and Constant Bitrate (a fixed list from 8 to 384 kbps, with 128 kbps preselected in that list) are the controls that behave sensibly here, and Specific file size is there when you have a hard byte budget.
3. Set Audio Channel and Audio Sample Rate: Both lists start at ORIGINAL. MONO roughly halves the result on a spoken-word recording. The sample-rate list offers 8000, 12000, 16000, 24000, 44100 and 48000 Hz — note the caveat about 44100 in the FAQ below.
4. Trim and Convert: Trim opens on Unchanged; switch it to Time Range for a start time and duration if you only want part of the recording. Click Convert — files are uploaded over an encrypted connection, decoded and re-encoded on our servers, and deleted automatically after a few hours.

The Quality Presets Are Calibrated Far Too High for Opus

The preset ladder maps linearly across Opus's full permitted bitrate range — 8 kbps at the bottom, 512 kbps at the top — rather than across the range Opus is actually useful in. Opus reaches transparency on stereo music somewhere around 128 to 160 kbps and on speech far below that. So every preset from High upward is asking for several times what the codec can spend.

Measured on a 10-second RealMedia file whose audio track was around 96 kbps:

The ladder is not broken — every value is honoured, and the file sizes move exactly as requested. It is simply scaled to the codec's ceiling rather than to its useful range, which puts "Very High" somewhere no one needs to go. Constant Bitrate or Custom Bitrate with a number you choose is the better control on this route.

What to pick: 64 kbps mono for a lecture, interview, sermon or talk radio recording, which is what most surviving RM files are. 96 to 128 kbps stereo for music or anything with a mix. Going higher cannot recover what RealAudio already discarded — you would be spending bits to store the compression artefacts more faithfully.

Frequently Asked Questions

Why is there nothing to choose in the Audio Codec list?

Because a .weba gets Opus and there is no alternative to offer. The Audio Codec group heading renders on this page, but every codec entry inside it is suppressed, so there is nothing selectable — the codec is determined by the output extension rather than by you. That is correct behaviour for this target even though the empty group looks odd. If you want a choice of codec, pick a container that supports several: RM to MP3 for maximum compatibility, or RM to WAV for uncompressed PCM.

What happened to the video?

Discarded before encoding. .weba is the audio-only convention for WebM, so the RealVideo stream is dropped and the output carries a single audio track. If you want the picture too, RM to WebM writes both streams into the same container family — VP8 or VP9 video alongside the audio — and remains a WebM file.

Why does my output say 48 kHz when the source was 44.1 kHz?

Because Opus does not have a 44.1 kHz mode. RFC 6716 defines the codec at 8, 12, 16, 24 and 48 kHz only, and 48 kHz is its native internal rate. The 44100 entry still appears in the shared sample-rate list, and choosing it does not fail the job — the audio is resampled to 48 kHz on the way in. A 44.1 kHz RealMedia source came out of this route as a 48 kHz .weba in testing. There is nothing to correct; it is how Opus works.

Is a .weba different from a .webm?

Only by convention. Both are Matroska-derived WebM files with the same 1A 45 DF A3 EBML header at the front; .weba signals that there is no video track inside. Some software filters its file picker on .webm and will not show a .weba — renaming it to .webm is a complete fix and changes nothing about the bytes. Web servers should send audio/webm for it, and browsers play it either way.

Will re-encoding RealAudio to Opus lose quality?

Yes, a little — both are lossy, and moving between them means decoding to PCM and encoding again. In practice the loss is small and the audible effect is dominated by whatever RealAudio already did to the recording, which was usually a lot. The way to keep the second stage inaudible is to give it a bit more room than the first had: if the RealAudio track was around 64 kbps, encode Opus at 64 to 96 kbps rather than trying to save space. Opus is efficient enough that matching the source bitrate is generous.

Which browsers and devices play a .weba?

Opus support is broad but not quite universal — caniuse currently puts it at about 96% of tracked traffic.

On the desktop, VLC, mpv and foobar2000 handle the file without extras. The real gaps are older hardware — car head units, older smart TVs and cheap media players often have no Opus decoder at all. When a file has to play absolutely everywhere, RM to MP3 is the safe answer.

Can I trim the recording during conversion?

Yes. The Trim group opens on Unchanged; switching it to Time Range exposes a Start time and a Duration, each taking plain seconds or HH:MM:SS.sss. That gives you one continuous range per job, which is usually enough to drop an intro or a trailing Q&A. If you need several separate cuts, do the surgery on the source first with Video Cutter, which accepts .rm directly, then convert each piece.

Does the RealMedia title and author metadata come across?

No. RealMedia stores title, author and copyright in its own header fields, and this conversion does not carry them into the WebM container's tags. The output is audio and container structure and nothing else. If the metadata matters, note it from the source before you discard the .rm, and add it back with a tagging tool afterwards.

Why can nothing on my computer open the .rm in the first place?

Because RealMedia support was withdrawn almost everywhere. RealPlayer's own decline aside, browsers never supported it, and mainstream editors and media libraries dropped RealAudio and RealVideo demuxing years ago. What still reads them is anything built on ffmpeg — VLC and mpv on the desktop, and this converter on the server side. That is exactly why moving the audio into a current container is worth doing while the file still opens somewhere.

What happens to my file after the conversion?

Your .rm is uploaded over an encrypted connection, decoded and re-encoded on our servers, and both the upload and the .weba it produced are deleted automatically after a few hours. Files are never shared or made public, no account is needed, and nothing is watermarked.