Initializing... drag & drop files here
Supports: RMVB
RMVB is RealMedia Variable Bitrate, RealNetworks' 2003 container for locally stored video, and by now it is a format with almost no tooling left. No browser ever decoded RealVideo, most current editors dropped RealMedia demuxing years ago, and the operating system will not give you a thumbnail. So when you need one frame out of an .rmvb — a screenshot for documentation, an evidence still, a thumbnail for a catalogue entry — you are usually working blind.
BMP is the other end of that problem: the Windows device-independent bitmap, a format so old and so literal that machine-vision rigs, embedded display drivers, printer utilities and forensic tools still name it as the one image format they trust. This page decodes a frame from the RealVideo stream and writes it as .bmp.
Two things decide whether the result is useful. The frame you get by default is the very first one, which on a video file is frequently black or a title card. And the Quality Preset is not a compression slider — on a BMP target it selects between three genuinely different bitmap encodings, only one of which is uncompressed and none of which is 24-bit truecolour.
BMP has nothing to trade off in the JPEG sense, because it stores pixels literally. What the preset chooses is the bitmap format itself. These are the three options and what we measured writing them from one 640 x 480 RealVideo frame:
| Preset | Bitmap written | Colours in our output | Size |
|---|---|---|---|
| High | Uncompressed, 16 bits per pixel in the RGB 555 layout | 6,009 distinct, from 22,201 in the decoded frame | 614,454 bytes |
| Medium | 8-bit palette bitmap, RLE-compressed, written in the classic BMP3 header form, with Floyd-Steinberg dithering and a light selective blur before quantising | 256 | 121,178 bytes |
| Low | 8-bit palette bitmap, RLE-compressed, Floyd-Steinberg dithering, tagged at 150 pixels per centimetre | 86 | 94,596 bytes |
The High figure is not an estimate — it is arithmetic you can check. 640 x 480 is 307,200 pixels, at two bytes each that is 614,400, plus a 54-byte header gives exactly 614,454. Microsoft's BITMAPINFOHEADER reference documents both halves of why: at 16 bits per pixel with BI_RGB the layout is always RGB 555, and the minimum row stride is the width in bytes rounded up to the nearest four-byte boundary. Uncompressed bitmap sizes are predictable in a way compressed formats never are.
One practical warning that catches people: the preset which is pre-selected on every other image target is one of the entries a BMP target hides, so do not assume the box already holds a sensible value. Open the list and choose High, Medium or Low deliberately.
.rmvb onto the page or click "+ Add Files" to browse. Several files can be queued and they all use the same frame and quality settings.0. Type the moment you actually want — the field takes decimals, so 754.5 is twelve and a half minutes in. Multiple Screenshots instead walks the whole file at a Capture Rate, from one frame every 10 seconds up to ten frames per second, opening at one per second.The frame grab happens in two stages: the picture is decoded out of the RealVideo stream as a lossless PNG, and that PNG is then encoded into the bitmap you asked for. The decode itself is exact — so every question about how the still looks is a question about the preset you chose or about the source, never about the file being read badly.
That split matters because RMVB sources have a characteristic weakness. The format existed to fit a feature-length release into a few hundred megabytes, and RealVideo hit that budget by spending its bits on motion prediction rather than on detail within any single frame. Our test frame carried 22,201 distinct colours where an equivalent frame from a modern source would carry many times that. A high preset stops the bitmap stage from adding further damage; it cannot recover what RealVideo discarded.
Two things genuinely help, in this order:
And one thing that does not: the conversion does not deinterlace. Some RMVB releases were encoded from interlaced broadcast masters, and nothing in this pipeline removes the field structure, so combing on a fast-moving frame is written straight into the bitmap. Choosing a still moment is the only remedy available here.
| Property of the source | Result in the BMP |
|---|---|
| RealAudio soundtrack | Discarded — a bitmap has no sound |
| Motion | Discarded. One frame, or one file per sampled frame |
| Selectable subtitle tracks | Discarded. Subtitles burned into the picture survive, because they are pixels |
| Transparency | Not applicable. Video frames are opaque and these presets write no alpha channel |
| Colour depth beyond the preset | Reduced to 32,768, 256 or 86 colours depending on the preset you picked |
| Non-square pixel aspect | Written as the stored raster, not stretched to display shape, so anamorphic footage looks narrow |
| Container metadata | The BMP header stores dimensions, bit depth and pixel density and nothing else |
No, and this is the single thing people most often get wrong here. High writes an uncompressed bitmap at 16 bits per pixel in the RGB 555 layout — five bits each for red, green and blue, giving 32,768 possible colours. It is genuinely uncompressed and it is the highest-fidelity option this page offers, but it is not the 24-bit bitmap you may be picturing. If a downstream tool specifically requires 24-bit BMP, or if you need every colour value the frame held, take the still as RMVB to PNG — which is true-colour and lossless — and set the bit depth in a tool that lets you.
Because Frame Selection opens on "Specific Frame" with Time (seconds) at 0, and the first frame of a video file is very often not content. Fades from black, distributor cards and release-group idents are all standard at the head of an RMVB release. Type a timestamp from inside the programme instead — the field accepts plain seconds with an optional decimal, so 65.5 and 2.100 are both valid.
Both write an RLE-compressed 8-bit palette bitmap with Floyd-Steinberg dithering, which spreads quantisation error into neighbouring pixels so banding reads as fine noise rather than hard steps. Medium keeps 256 colours, writes the classic BMP3 header form and applies a light selective blur before quantising, which helps flat areas quantise cleanly. Low drops to 86 colours and tags the file at 150 pixels per centimetre. On our test frame the difference in size was modest — 121,178 against 94,596 bytes — while the difference in colour count was threefold, so Medium is usually the better trade.
Not every frame, and on a feature-length source you would not want to. Multiple Screenshots samples the file at the Capture Rate you choose, writing one bitmap per sample, and the fastest available rate is one frame every 0.1 seconds — which is still not every frame of a 25 fps release. Do the arithmetic before you start: at the default of one frame per second, a 45-minute episode produces 2,700 uncompressed bitmaps. Start at one frame every 10 seconds, narrow the window, then re-run.
Because a bitmap stores every pixel literally while the video stored an approximation of the whole timeline. On the High preset the arithmetic is fixed at two bytes per pixel plus header and row padding, so a 1920 x 1080 frame is about 4 MB and a 3840 x 2160 frame about 16.6 MB whatever the picture contains. Medium and Low cut that by dropping to an 8-bit palette and run-length encoding the result, which is dramatic on flat graphics and much less so on grainy footage.
Because the source is anamorphic and the converter writes the stored raster rather than the display shape. Some RMVB releases store a widescreen picture in a narrower pixel grid and rely on the player to stretch it at display time, and a bitmap has no pixel-aspect field that receiving software will honour. Fix it explicitly: set Image resolution to Width x Height and type the display dimensions you want.
.rmvb so I can find the right timestamp?VLC and mpv both still carry RealVideo decoders and open .rmvb files on Windows, macOS and Linux, as does anything built on ffmpeg — which is how this converter reads the file in the first place. That is worth knowing in both directions: if the file plays in VLC but nowhere else, converting it is exactly the right instinct, and RMVB to MP4 gives you something the rest of your tools will handle.
By default, yes. Image resolution opens on Keep original, so a 640 x 352 source yields a 640 x 352 bitmap. Preset Resolutions set the height and let width follow the source aspect, so they will not produce an exact raster — use Width x Height when the receiving device needs specific dimensions. Upscaling past the source is not worth doing: the frame carries only the detail RealVideo recorded, and enlarging interpolates rather than reveals.
PNG, unless something specifically demands a bitmap. It is lossless and true-colour, so it keeps every one of the frame's colours rather than 32,768 of them, and it is a fraction of the size — RMVB to PNG is the better general answer. BMP earns its place where the consumer is old or embedded software that reads nothing else: machine-vision rigs, display drivers, printer utilities and Windows tools written before PNG existed. If size matters more than fidelity, RMVB to JPG beats both.
It is uploaded over an encrypted connection, decoded on our servers, and both the upload and every still it produced are deleted automatically after a few hours. Nothing is shared or made public, there is no watermark and no account is required. RMVB files are usually full-length films or episodes, so upload time is the part you will wait on — if you only need one frame from late in a long file, cutting the section out first with the video cutter is much quicker than sending the whole thing.