JPEG to RM Converter

How to Convert JPEG to RM Online

1. Upload Your JPEG Files: Drag and drop or click "Add Files" to load .jpg, .jpeg, or .jfif images. Batch is supported — drop an entire folder of stills to build one slideshow or a per-image set. Files stay on our servers; no upload to third-party storage.
2. Pick Merge Strategy and Image Duration: Set Merge Strategy to Merge images (single RM slideshow) or Video per image (one RM file per still). Then choose Image Duration — anything from 1/60 second per frame (effectively a flipbook) up to 10 seconds. Total runtime = image count × duration.
3. Choose Codec, Quality, Resolution, and Background: Pick Video Codec (default RV10 — the native RealVideo for .rm; switch to RV20/RV40 if your target player supports it) and Audio Codec (default REAL_144 for silent slideshows; Cook or AAC if you add a music track). Set File Compression to Quality Preset (Highest through Lowest, default Very High), Target file size as %, Specific file size, Constant Bitrate, Variable Bitrate, or Constant Quality (CRF). Use Video Resolution to pick 360p/480p/720p or enter a custom size with Keep aspect ratio; choose a Background Color (Black is standard for letterboxing — White, Gray, and 20+ named colors are available).
4. Convert and Download: Click "Convert". Output is a standards-compliant .rm container playable in RealPlayer, VLC, MPC-HC, and PotPlayer. No sign-up, no watermark.

Why Convert JPEG to RM?

.rm (RealMedia) is RealNetworks' streaming container, first released in 1997. It is now a niche legacy format — MP4/H.264 has replaced it almost everywhere — but a handful of workflows still require RM input, and turning a stack of JPEGs into a slideshow video is one of the few practical reasons to build an RM file from scratch today.

• Feeding legacy RealPlayer-based kiosks and digital signage — Pre-2010 retail and corporate signage controllers in Asia and parts of Eastern Europe shipped with Helix DNA Server or RealPlayer SDK and accept .rm natively. Re-encoding to MP4 means swapping the controller; converting JPEGs to RM is the cheaper compatibility fix.
• Archive-format parity — Universities, broadcasters, and libraries that hold long-running .rm collections (lecture archives, news clips from the late 1990s and early 2000s) often standardise new material to the same container so a single RealPlayer-driven catalog can index everything.
• Authoring slides for old training kits — Compliance, language-learning, and corporate-training CDs/DVDs from the RealPlayer era used RM slideshows with narration. Refreshing the slide imagery without rebuilding the kit means producing a drop-in .rm.
• Low-bandwidth streaming demos — RV10 was designed for dial-up (28.8/56 kbps modems). A 480p slideshow at constrained bitrate can showcase how a format meant for narrow pipes still looks, which is occasionally useful for codec coursework or retro-computing demos.
• Format-conformance testing — QA suites for media players (VLC, MPlayer, FFmpeg, GStreamer's realmedia demuxer) need synthetic .rm samples that exercise specific codec/duration combinations. A JPEG-to-RM pass produces controlled inputs.
• Personal nostalgia projects — Rebuilding a "RealPlayer screensaver" or an early-2000s-style slideshow as a stylistic choice, the same way some hobbyists author DivX AVIs or MJPEG QuickTimes today.

If you instead need a modern, universally playable slideshow, build it with JPEG to MP4 or JPEG to WebM. Going the other way? See RM to MP4 to extract a stack of stills from an existing RealMedia file's keyframes.

RM vs MP4 — Container Comparison

RealVideo Codec Quick Guide

Frequently Asked Questions

Why is Trim greyed out for JPEG to RM?

Trim operates on an existing video timeline, and a stack of JPEGs has none until the conversion runs. Control the runtime by changing the Image Duration (1/60 second up to 10 seconds per frame) and the number of input files. For example, 30 stills at 4 seconds each yields a 2-minute slideshow.

Which Video Codec should I pick — RV10, RV20, RV30, or RV40?

Stay on RV10 for maximum compatibility with older RealPlayer builds and embedded RealPlayer SDK targets — it shipped with RealPlayer 5 and is the only codec that every RealMedia decoder accepts. Choose RV40 if you know the target is RealPlayer 9 or newer (released 2002) and you want better quality at the same bitrate; it is believed to be based on an early H.264 draft. RV20 and RV30 are rarely the right answer in 2026 — pick RV10 for compatibility or RV40 for quality.

Is RealMedia still playable in 2026?

Yes, but not in browsers. RealPlayer for Windows is still maintained (RealPlayer 24 reached version 25.0.0.316 in November 2025), VLC plays .rm on every desktop OS, and FFmpeg's realmedia demuxer covers most other tooling. Chrome, Firefox, Safari, and Edge have no native .rm playback — embedding RealMedia on a public website is not viable, which is why MP4 is the right output for anything web-facing.

What is RMVB and should I output it instead?

.rmvb is RealMedia with variable bitrate audio/video — RealNetworks introduced it to give better picture quality at the same average bitrate than constant-bitrate .rm. This converter outputs .rm; if you specifically need .rmvb to fit an archive convention, build a .rm here with Variable Bitrate mode under File Compression, then rename the extension. The container is the same; the .rmvb extension just signals the variable-rate encoding to the player.

Can I add background music to the slideshow?

Yes. Add an audio file alongside your JPEGs and the encoder muxes it into the RM container — pick Cook or AAC under Audio Codec for music (REAL_144 is voice-only at 14.4 kbps). If you only have JPEGs without audio, the output is a silent .rm with a quiet REAL_144 track, which is what RealPlayer expects.

What resolution should I pick for a RealMedia slideshow?

480p (854x480) or 360p (640x360) are the historically idiomatic choices — RealMedia was designed for sub-megabit streaming on dial-up and early DSL, and most legacy RealPlayer kiosks expect SD-class input. 720p works, but file size grows fast and you lose the compatibility benefit. Use the live page's Preset Resolutions dropdown for one-click presets, or Fixed Resolutions + custom width/height with Keep aspect ratio for non-standard targets.

Will the output play in a modern web browser?

No. None of Chrome, Firefox, Safari, or Edge support .rm playback natively, and there is no actively maintained <video> codec extension that adds it. If the slideshow needs to play in a browser, convert your JPEGs to MP4 with JPEG to MP4 instead. RM is for desktop players (RealPlayer, VLC, MPC-HC, PotPlayer, KMPlayer, MPlayer) and legacy embedded systems.

How many JPEGs can I drop in at once?

The browser is the bottleneck — a 16 GB-RAM laptop in Chrome handles a few hundred JPEGs in one batch comfortably; an older machine should keep batches under ~100. If you have thousands of stills, split them into chunks, run each chunk separately, and either deliver the resulting .rm files as a per-image set or concatenate them afterwards with FFmpeg's concat demuxer.

Which input formats does this page accept?

.jpg, .jpeg, and .jfif. For other source formats, use the matching converter: PNG to RM, BMP to RM, or JPG to RM (an alias of this page using the .jpg extension in the URL).