RM to BMP Converter

Convert RM to BMP: One Frame, Written as a Windows Bitmap

RealMedia .rm is a video container — RealNetworks' RealVideo, usually with a RealAudio track alongside it. BMP is a single still picture in Microsoft's Windows bitmap format. So this page is a frame grab: the server decodes the RealVideo stream, takes the moment you ask for, and writes it as a .bmp.

What makes this page different from every other still-image target on the site is the Quality Preset control. On a JPEG or WebP page that dropdown is a compression dial with seven rungs. On BMP it has three entries, and each one routes the frame through a completely different encoder producing a structurally different bitmap. Understanding which is which is the whole job, so that is what this guide covers.

How to Convert RM to BMP

1. Upload Your RM File: Drop the .rm on the page or click "Add Files". A queue of RealMedia clips all share the same frame and quality settings, which is handy when you want the same timestamp from a series of captures.
2. Pick the Frame: Under Frame Selection, "Specific Frame" is the mode on load with Time (seconds) at 0 — literally the first frame, which on a real recording is often black or mid-fade. Type the second you want; decimals such as 12.5 are accepted. "Multiple Screenshots" with a Capture Rate is the alternative when you want a series across the clip.
3. Choose a Quality Preset and Image resolution: Quality Preset offers High, Medium and Low and nothing else; the table below says what each one writes. Image resolution opens on Keep original, with Resolution Percentage, Preset Resolutions, Width, Height and Width x Height as alternatives.
4. Convert and Download: Click Convert and save the bitmap. Files are uploaded over an encrypted connection, processed on our servers and deleted automatically after a few hours — no sign-up, no watermark, never shared or made public.

The Three Presets Are Three Different Bitmaps

The important consequence: none of these is a 24-bit truecolour BMP. "High" is the highest-fidelity option the page offers, and it is a 16-bit RGB555 bitmap — every channel is quantised to 32 levels instead of 256. Decoding one frame of a 352 x 288 RealVideo clip gave a picture with 9,572 distinct colours; the same frame written through the High preset came back with 3,275. On photographic material with smooth gradients, that shows as faint banding in skies and skin tones.

If you need pixels that match the decoded frame exactly, BMP is the wrong target on this page — take the still as RM to PNG, which is genuinely lossless at its top preset and usually smaller as well.

BMP File Size Is Arithmetic, Not Content

Because the High preset stores two bytes per pixel with no compression, its size is fixed by the frame dimensions alone: width x height x 2 plus a 54-byte header (14 bytes of file header and a 40-byte BITMAPINFOHEADER). Content makes no difference — a black frame and a busy one weigh the same.

The Medium and Low numbers are the only ones that move with picture content, since run-length encoding compresses runs of identical palette entries. Those two figures come from a single decoded RealVideo frame and are indicative rather than a formula — a flatter frame compresses much further, a noisy one barely at all.

Common Errors and How to Fix Them

• "The bitmap is black or half-faded" — Time (seconds) is still at 0. Most recordings open on black, a fade-in or a channel logo. Type a real timestamp.
• "The colours look banded or posterised" — you are seeing 5-bit-per-channel quantisation on the High preset, or the 256/86-colour palettes on Medium and Low. There is no preset above High on a BMP output; use RM to PNG if the banding matters.
• "There are comb-like lines across anything moving" — the source is interlaced and nothing in this pipeline de-interlaces, so both fields land in the still. Choose a frame from a static shot, or de-interlace afterwards in an image editor.
• "I got dozens of files" — Frame Selection is on "Multiple Screenshots". Its Capture Rate is an interval measured in seconds between stills, so a fast rate on a long recording produces a very large series. Switch back to "Specific Frame".
• "The picture is horizontally squashed" — many RealVideo captures were encoded from non-square-pixel sources. The extracted still keeps the stored pixel dimensions rather than the display shape, so correct it with Width x Height if the proportions matter.
• "My file will not decode at all" — a .ram playlist renamed to .rm contains no video, and RealMedia files carrying RealNetworks rights management cannot be decoded by a general-purpose converter.

Frequently Asked Questions

Why does the Quality Preset dropdown only show three entries here?

Because the seven-rung ladder used on JPEG-family pages does not map onto a bitmap. BMP has no quality parameter in the JPEG sense, so the three entries stand for three distinct write paths — a 16-bit uncompressed bitmap, a 256-colour run-length-encoded BMP3, and an 86-colour run-length-encoded bitmap. High is the first entry offered and the one the control resolves to.

Is a BMP from this page lossless?

Not in the sense people usually mean. The High preset applies no compression at all, but it stores only 5 bits per colour channel, so the frame is quantised on the way in. Medium and Low reduce the image to a palette before writing. If "lossless" means pixel-for-pixel identical to what the decoder produced, none of the three qualifies — RM to PNG at its highest preset is the option that does.

Why is there no "Specific file size" option on this page?

It is suppressed for BMP targets, and reasonably so: the High preset's size is fixed by pixel count, and the two palettised presets compress by run length in a way that cannot be aimed at a byte figure. The way to control BMP size is Image resolution — halving both dimensions quarters the High preset's output exactly.

Which preset should I pick for a screenshot I plan to edit?

High. It is the only entry that does not reduce the frame to a palette, so gradients survive better and an editor has real colour data to work with. Medium and Low are appropriate when you are feeding something that expects an indexed bitmap, or when you want a small file and the frame is mostly flat colour and graphics rather than photographic detail.

Why would anyone want BMP rather than PNG or JPG?

Compatibility with software that reads nothing else. Old Windows GDI-era applications, some print drivers, embedded and industrial displays, and a few machine-vision toolchains accept .bmp and refuse everything modern. Decoding is also trivial — the pixel array sits in the file ready to be read directly. For anything you are going to share, view online or email, RM to JPG is a far better fit.

Does the BMP keep the audio from the RealMedia file?

No. A .rm carries RealVideo plus RealAudio; a bitmap holds pixels and has no audio support of any kind, so the sound is discarded. Convert the same file with RM to MP3 if the audio is what you are after, and run it separately from the frame grab.

Can I get several stills from one clip in a single run?

Yes — set Frame Selection to "Multiple Screenshots" and pick a Capture Rate. The dropdown entries are intervals, not frame rates: "1 second per frame" writes one bitmap for every second of runtime, and "10 seconds per frame" writes one every ten seconds. Given the High preset's fixed size, a long clip at a fast rate produces an alarming amount of data very quickly — start slow.

What resolution will the bitmap be?

The source frame size, because Image resolution opens on Keep original. RealVideo material is usually small by modern standards — 320 x 240 and 352 x 288 are the common shapes — so the still tends to be small too. Note that the Preset Resolutions list sets height only, with width following the source aspect, so use Width x Height when you need exact pixel dimensions.

The still looks softer than I expected. Is that the converter?

Almost certainly not. RealVideo was designed for dial-up and early broadband bitrates, and its compression is aggressive by modern standards; a frame grab inherits every artefact that was baked in when the file was created. Raising the Quality Preset cannot recover detail that the original encode discarded, and neither can upscaling the still afterwards.

What happens to my file after the conversion?

It is uploaded over an encrypted connection, decoded on our servers and deleted automatically after a few hours, along with the bitmap it produced. There is no sign-up, no watermark, and files are never shared or made public. If you only want one still out of a long recording, cutting the clip down first with Video Cutter — which accepts .rm directly — saves the upload.