X3F to RM Converter

How to Convert X3F to RM Online

1. Upload Your X3F Files: Drag and drop or click "Add Files" to select the Sigma Foveon RAW files you want to stitch into a RealMedia slideshow. Batch upload is supported — every X3F you add becomes a frame in the output reel.
2. Pick Merge Strategy and Image Duration: Default is "Merge images" (all X3Fs combined into one.rm) — switch to "Video per image" to emit one RM per photo. Set Image Duration to control how long each still holds on screen (presets from 1/60 second up to 10 seconds per frame). Pick a Background Color (default Black) to fill letterbox bars when photo aspect ratios differ from the video frame.
3. Set Quality Preset and Resolution (Optional): Choose Quality Preset — "Constant Quality" locks visual fidelity per frame, "Constraint Quality" caps the bitrate. The Preset dropdown ranges from Lowest to Highest (Very High is recommended for Foveon detail). Under Video resolution, keep original Foveon dimensions or pick a Preset Resolution (144p through 4320p) — RealMedia is most often played at 360p–720p, which matches the era's player ecosystem.
4. Convert and Download: Click Convert. 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.

Why Convert X3F to RM?

X3F is Sigma's proprietary Foveon RAW container, introduced with the SD9 in 2002 and still produced today by the dp Quattro and SD Quattro lines after Sigma acquired Foveon outright in November 2008. RM (RealMedia) is RealNetworks' multimedia container — debuted in 1997 alongside the RV10 video codec, the same H.263-derived format that powered late-90s streaming for CNN, the BBC, and the first generation of internet radio. Wrapping a Foveon stills sequence into RM is a niche but specific need: archival pipelines, retro media installations, and any toolchain that still expects RealPlayer-compatible input.

• Feed legacy RealPlayer kiosks or digital signage — museums, hotel info loops, and corporate AV racks built between 1998 and 2005 often still autoplay.rm content via RealPlayer or an embedded RealNetworks SDK. A Foveon photo reel encoded as RM drops straight in without re-authoring the playlist.
• Bandwidth-constrained streaming archives — RV10 was designed for 28.8 kbps dial-up, so even high-pixel-count Foveon stills downscale into RM clips that play smoothly under 100 kbps, useful for low-bandwidth intranets or historical reconstructions.
• RealServer / Helix Server pipelines — any remaining Helix DNA Server deployment expects.rm with RV10/RV20 video plus RealAudio Cook or PCM audio; this converter outputs that pairing directly.
• Archival format diversity — institutions following LOCKSS principles ("Lots Of Copies Keep Stuff Safe") sometimes retain a RealMedia derivative of a slideshow as a deliberate format hedge alongside the modern MP4 master.
• Retro media art and demoscene work — artists deliberately targeting the early-2000s web aesthetic ship in.rm because the codec artifacts and 4:3 letterboxing are part of the piece.
• Tooling that refuses modern containers — older video-cataloging databases (Cumulus, Extensis Portfolio, some library-science systems) still scan.rm metadata reliably even when MP4 indexing breaks.

X3F vs RM — Format Comparison

Quality Preset and Resolution Quick Guide

Frequently Asked Questions

Why would I ever convert Foveon RAW directly to RealMedia instead of going through MP4?

Almost no general-purpose workflow needs this — MP4 with H.264 is the right answer for 99% of slideshow exports. You'd pick RM specifically when the downstream player, signage controller, or archival mandate requires a RealNetworks-compatible container. If you only need a modern slideshow, convert X3F to MP4 instead; if MOV suits your edit environment, X3F to MOV works similarly.

Will my Foveon detail survive being wrapped in RM?

Partially. The Foveon X3 sensor's 3-layer stack captures full RGB per photosite, which is what makes Sigma stills look distinctive at base ISO. RM uses RV10 or RV20 — both H.263-based, both lossy DCT codecs — so fine chroma detail compresses heavily. Picking "Very High" or "Highest" Quality Preset preserves more of that texture, but the codec ceiling is the limiting factor, not the source RAW. For maximum fidelity, export your X3Fs to TIFF in SIGMA Photo Pro first, then run that into the slideshow.

What software can play the resulting RM file in 2026?

RealPlayer (free download from real.com, last updated July 2024) is still the most reliable. VLC plays RM containers — audio almost always works; video playback depends on whether VLC's bundled FFmpeg supports the specific RV variant in your file. MPlayer / mpv handle most RV10/RV20 streams. Modern browsers, QuickTime, Windows Media Player, and most mobile players do not handle.rm natively — that's the cost of choosing the format.

How is RM different from RMVB?

RM (RealMedia) uses constant bitrate; RMVB (RealMedia Variable Bitrate) added variable-bitrate encoding for better quality-per-byte and was widely adopted in East Asia for fan-distributed anime and TV through the mid-2000s. If your destination tolerates RMVB, convert X3F to RMVB instead — it ships smaller files at the same visual quality. Stick with RM only when the consumer specifically rejects RMVB.

What's the maximum Image Duration I can set per X3F frame?

The Image Duration dropdown ranges from 1/60 second per frame (effectively a 60 fps animation if you have enough X3Fs) up to 10 seconds per frame for slow, contemplative photo holds. Most slideshows look natural at 3–5 seconds per frame. Going below 1 second per frame creates a stop-motion or time-lapse feel; going above 8 seconds drags unless you're scoring it to narration.

Can I add audio to the RM slideshow?

This converter outputs video-only RM clips from X3F stills — there's no audio upload step in the image-to-video flow. RealMedia natively supports RealAudio Cook, AC3, AAC, and PCM audio tracks, but adding them requires a separate mux pass. The typical workflow is: convert X3F to RM here for the video pass, then mux audio with FFmpeg (ffmpeg -i video.rm -i audio.wav -c copy output.rm) or RealProducer if you still have a license.

How long does the conversion take for a batch of Foveon files?

X3F decoding is the bottleneck, not RM encoding. A single Sigma Quattro X3F at full resolution (~5,424 × 3,616) takes a few seconds to demosaic; a 30-photo batch typically finishes in under a minute at Medium quality. The RV10/RV20 encoder is decades old and runs faster than any modern codec — once the RAWs are decoded, the actual RM packaging is near-instant.

Why does my output look soft compared to the X3F preview?

Two reasons. First, RealMedia codecs predate modern psychovisual tuning — they were optimized for sub-1990s bitrates, not 4K photo detail. Second, slideshow encoders downsample stills to the video resolution you picked, so a 39-megapixel Foveon Quattro frame rendered at 720p drops more than 95% of its pixel count. Use the highest Preset Resolution your player supports (1080p or 4K if the playback target accepts it) and set Quality Preset to "Very High" or "Highest" to retain as much of the Foveon look as possible.