RM to TIFF Converter

Grab a TIF Still from an RM Video: What This Covers

This tool freezes one moment of a RealMedia (.rm) video and writes it out as a TIF image. Under the hood the frame is extracted as a lossless PNG first and then encoded to TIFF, so nothing is lost between the decoder and the image writer — the only quality decision that matters is which Compression Type you pick at the end, and that choice changes the file by a factor of fourteen.

The walk-through below covers picking the timestamp, choosing a compression type on real measured numbers, and the two compression settings that will silently produce a broken file if you select them.

How to Convert RM to TIF

1. Upload Your RM File: Drag and drop the .rm file onto the page or click "Add Files". Files travel over an encrypted connection and are converted on our servers.
2. Pick the Frame under Frame Selection: Leave Specific Frame selected and type the moment into Time (seconds) — the field takes decimals, so 2.100 lands on the frame at 2.1 seconds. It opens at 0, which grabs the first frame. Switch to Multiple Screenshots to sample stills across the whole clip instead, at a Capture Rate from ten frames per second down to one frame every ten seconds.
3. Choose Compression Type and Quality: Compression Type opens on JPEG and offers LZW, LOSSY, DEFLATE, PACKBITS, CCITT Fax 4, NONE, WebP, ZSTD and JP2K alongside it. Quality Preset opens on Very High (Recommended). Confirm File extension is set to TIF, and scale the still with Resolution Percentage, Preset Resolutions or Width x Height if you need it smaller.
4. Convert and Download: Click Convert and save the .tif. No sign-up, no watermark; uploads and outputs are deleted automatically after a few hours.

Walk-through: Choosing a Compression Type That Fits the Job

TIFF is a wrapper, not a single compression scheme, and this is the one control that genuinely changes what you get. We measured all of them on the same frame — a 320×240 still pulled from a RealVideo (RV20) clip encoded at 200 kbit/s, which is a realistic stand-in for the archived RealMedia most people are converting.

Three things worth knowing before you pick:

• The uncompressed number is not arbitrary. A 320×240 RGB frame at eight bits per channel is 320 × 240 × 3 = 230,400 bytes of pixel data, and the NONE file came out at 230,638 — the pixels plus a small header. That is the ceiling every other row is measured against.
• PackBits came out larger than uncompressed, by 1,858 bytes. That is not a bug: PackBits is a byte-oriented run-length scheme, and the TIFF 6.0 specification documents a worst case of one extra byte per 128 bytes of non-repeating data. 230,400 ÷ 128 = 1,800, which is almost exactly the overhead we measured. Photographic frames have very few byte runs, so PackBits has nothing to compress and pays the overhead anyway.
• JPEG being the default is fine here specifically. JPEG-compressed TIFF is lossy and cannot carry an alpha channel, which makes it a poor default for images with transparency — but a video frame is a solid opaque rectangle, so there is no alpha to lose. If you want a true archival master, switch to LZW or DEFLATE and accept roughly double the file size.

TIF vs JPG vs PNG as a Frame-Grab Target

Common Errors and How to Fix Them

• "The TIF is empty or 238 bytes" — you selected CCITT Fax 4 or JP2K. Fax 4 is a bilevel scheme that requires one bit per sample and refuses colour outright; JP2K is not implemented in this pipeline's TIFF writer. Both stop mid-write and leave a stub. Pick LZW or DEFLATE for lossless, JPEG for small.
• "The grab is blurry or motion-smeared" — you landed on a frame during fast motion or across a scene cut. Nudge Time (seconds) by a few hundredths and re-run; RealVideo clips are usually 15–30 fps, so consecutive frames are only 0.03–0.07 s apart.
• "There are thin horizontal comb lines through moving objects" — the source was interlaced, which was common for RealMedia ripped from broadcast or DVD. Nothing in this pipeline deinterlaces, so the combing is baked into the extracted frame. Choose a moment where the subject is still.
• "I asked for several frames and got several files" — that is expected. Multiple Screenshots writes one image per sampled frame and delivers them together; it does not build a multi-page TIFF.
• "The still looks softer than the video did" — RealVideo compression artifacts are much harder to ignore at 100% zoom on a static image than they are at 15 fps. The frame is an exact copy of what the decoder produced; the format is not adding softness.
• "The upload will not finish" — the limiting factor on a long RealMedia file is upload size and time. Trim the source first with the Video Cutter, which accepts .rm and .rmvb, then grab your frame from the shorter clip.

Frequently Asked Questions

Will saving the frame as TIF make my old RealMedia clip look sharper?

No. RealVideo was compressed hard for dial-up and early-broadband streaming, so the source frames are small and carry visible quantization artifacts. TIF stores those pixels faithfully — with LZW, DEFLATE, ZSTD or NONE it stores them exactly — but it cannot reconstruct detail the original encode discarded. The honest reason to do this is preservation: pulling a usable still out of a webcast, lecture or news archive in a format that print and editing tools accept.

Which Compression Type should I actually choose?

If the still is an archival or print master, choose DEFLATE or LZW — both are lossless, both are read by Photoshop, Affinity Photo, GIMP, ImageMagick and Preview, and DEFLATE came out about 11% smaller than LZW on our test frame. If you just want a small file and the still is going into a document, leave it on the JPEG default. Choose NONE only when a piece of legacy imaging software refuses anything else. Avoid PACKBITS on photographic content, and never choose CCITT Fax 4 or JP2K.

Can I get one multi-page TIF containing every frame?

No. The TIFF format itself supports multiple images in one file, but this tool writes one image per file: Multiple Screenshots returns each sampled frame as its own .tif rather than assembling a multi-page document. If you want a contact-sheet-style set of stills, that mode is the right one — set the Capture Rate to something like one frame every two seconds. If you want a single moment, stay on Specific Frame.

How big is a TIF frame from a RealMedia file?

It depends almost entirely on the compression type, not the source. We measured a 320×240 frame extracted from an RV20 clip at 230,638 bytes uncompressed, 111,740 with LZW, 99,106 with DEFLATE and 56,765 with the default JPEG setting. The uncompressed figure tracks the raw pixel math exactly — 320 × 240 × 3 bytes — so you can predict it for any frame size. A 640×480 frame would be four times that before compression.

Does the TIF come out at 300 DPI for printing?

There is no DPI control on this page and no resolution tag to rely on. What actually determines print quality is pixel count, and a RealMedia frame has very few of them: a 320×240 still is about one inch square at 300 DPI. If you need a printable still, start from the highest-resolution source you have; no conversion setting can add pixels that were never in the stream.

Will the TIF open in a web browser or an email preview?

Mostly not. Per MDN, Safari is the only browser that natively renders TIFF in web content — Chrome, Firefox and Edge need an add-on or a helper library. TIFF is meant for downloadable artwork, print and precision editing rather than display on a page. If the still is going into an email, a document or a web page, grab it as RM to JPG or as a lossless RM to PNG instead.

What is the difference between the TIF and TIFF outputs?

Nothing, at the format level — .tif and .tiff are two spellings of the same file type, a hangover from eight-character DOS filenames. The File extension control on this page lets you pick either, and the RM to TIFF converter is the same conversion pre-set to the four-letter spelling. Choose whichever your downstream tool expects; some older Windows software still assumes three.

Can I extract a frame from an RMVB file, or only .rm?

This page accepts .rm. RMVB, the variable-bitrate sibling of the same container, has its own page at RMVB to TIF with identical options. Either way the frame is decoded by the same RealVideo decoder, so the picture you get out is the same.

How are my files handled and how long do you keep them?

The .rm file is uploaded over an encrypted connection, the frame is extracted and encoded on our servers, and both the upload and the .tif output are deleted automatically after a few hours. There is no account to create, no watermark on the image, and files are never shared or made public. If you want the whole moving clip rather than one still, convert it with RM to MP4.