About RM Files
RealMedia
RealMedia is a proprietary multimedia container format created by RealNetworks for streaming audio and video over the internet. It was widely used in the early web era for low-bandwidth streaming but has been largely superseded by modern formats.
Family
Video Files
Extension
.rm
MIME Type
application/vnd.rn-realmedia
Can Use As
HOW RM
CAME TO BE.
RealMedia — .rm — was the container for RealAudio and RealVideo streams, both pioneered by Progressive Networks (later RealNetworks) starting in 1995. RealAudio 1.0 was the first streaming audio codec usable over 28.8 kbit/s dial-up; RealVideo arrived in 1997 as the first credible streaming video codec. For a stretch of the late 1990s, if you watched news clips, listened to a talk radio show’s archive, or heard a sports broadcast online, you used the RealPlayer.
Then RealNetworks made a series of strategic missteps: the player bundled adware, nag screens multiplied, users migrated to Windows Media and later to Flash. By 2005 RealMedia was the format nobody wanted and nobody removed — a vestige of the early streaming web. The company still exists; the format does not meaningfully exist outside legacy archive sites.
CURIOSITIES &
TRIVIA.
RealAudio 1.0 (1995) was the first codec that could stream voice over a 28.8 kbit/s dial-up modem in real time.
For most of the late 1990s, RealPlayer was the most-downloaded software on the planet — peaking at over 90 million installs.
The RealPlayer installer's bundled spyware and nag screens became internet-famous as the worst-behaved widely-installed software of the era.
RealVideo was the default format for BBC Radio archives and ESPN sports clips from 1997 to about 2005.
Apple's QuickTime Player rejected RealMedia playback in the late 2000s by policy — users had to install the standalone RealPlayer.
STRENGTHS &
LIMITATIONS.
Strengths
- First viable streaming format for dial-up audiences.
- Historic archive value for late-1990s web content.
- Variants covered voice, music, and video.
Limitations
- Commercially abandoned — RealNetworks pivoted away from player software.
- Bundled adware and UX hostility damaged the brand permanently.
- Modern browsers do not support RealMedia.
- Replaced by Flash Video, then HTML5.
- Archival format only.
Typical Sizes & Weights
Voice-grade audio (5 min at 20 kbps)
~750 KB
Video clip (5 min at 56 kbps dial-up)
~2 MB
Technical Specifications
- MIME type
- application/vnd.rn-realmedia
- Extensions
- .rm, .rmvb (VBR), .ra (audio only)
- Codecs
- RealAudio (cook, sipr), RealVideo (rv10-40)
- Native player
- RealPlayer (legacy)
- Status
- Deprecated
CONVERT FROM
RM
Common Use Cases
Legacy streaming video, early web multimedia, RealPlayer content
Related Formats
Popular comparisons
RM vs JPG
Differences, file size, and when to choose each format.
RM vs PNG
Differences, file size, and when to choose each format.
RM vs WEBP
Differences, file size, and when to choose each format.
RM vs GIF
Differences, file size, and when to choose each format.
RM vs BMP
Differences, file size, and when to choose each format.
RM vs MP4
Differences, file size, and when to choose each format.
Popular RM conversions
The most-requested destinations when starting from RM.
Frequently Asked Questions about RM
Frequently Asked Questions
RM (RealMedia) is a video container format that bundles one or more video streams, audio tracks, and optional subtitles into a single file. The container format determines how metadata is organised and which codecs can live inside; the visual quality itself depends on the codec (H.264, H.265, VP9, AV1) rather than the RM wrapper. It is part of the video files family.
VLC, MPV and PotPlayer play nearly every RM file on desktop. Browser support varies: modern Chromium, Firefox and Safari play common containers via the HTML5 <video> tag, but niche RM variants may fail. If a device refuses your RM, convert to MP4 with our RM to MP4 converter for universal playback.
Upload your RM to KaijuConverter and pick MP4, MOV, MKV, WebM, or any other target. Our pipeline uses FFmpeg under the hood and stream-copies when codecs are compatible (no quality loss) or transcodes at high-quality defaults otherwise. Conversion runs server-side; both files delete within two hours.
Only when the target requires re-encoding. If the codecs inside RM match what the target container supports, FFmpeg stream-copies the streams and the output is bit-identical to the source. Transcoding uses transparent quality defaults (CRF 20–23 H.264) and produces output indistinguishable from the original at normal viewing distance.