Initializing... drag & drop files here
Supports: APNG, PNG
Almost everyone who lands here is converting an animated PNG into a RealMedia file because something specific asks for one: an old media library organised around .rmvb, a player or set-top box from the RealNetworks era, or a workflow nobody has updated in fifteen years. That is a perfectly good reason, and this page does the job properly. But it is worth saying plainly first: if you are free to choose the format, APNG to MP4 will give you a smaller, sharper file that plays on every phone and browser, and RMVB will not. Below is the comparison that decides it, the difference between the two RealVideo codecs on offer, and the conversion itself.
| RMVB | MP4 | |
|---|---|---|
| Container | RealMedia, introduced by RealNetworks; the variable-bitrate flavour dates to about 2003 | ISO base media file format, still the industry default |
| Video codecs here | RealVideo 1.0 and 2.0, both H.263-derived | H.264, H.265, AV1, VP9, MPEG-4, Xvid |
| Coding efficiency | Late-1990s generation | H.264 and newer — far more quality per bit |
| Browser playback | None | Native in every current browser |
| Phone / smart TV playback | Needs a third-party app | Built in |
| Social and messaging uploads | Rejected almost everywhere | Accepted almost everywhere |
| Editor ingest | Rare outside legacy suites | Universal |
| Hardware decoding | Effectively none on modern devices | Standard for H.264 and H.265 |
| Still actively developed | No | Yes |
The Video Codec dropdown offers exactly two entries on this page, because those are the RealVideo variants available for encoding. The naming trips people up: RV10 is RealVideo 1.0, the first release, not a tenth version.
| RealVideo 1.0 (RV10) | RealVideo 2.0 (RV20) | |
|---|---|---|
| Introduced | With the first RealVideo release in 1997 | The following generation |
| Based on | ITU-T H.263 | H.263 with RealNetworks extensions |
| Decoder reach | The widest — anything that ever played RealMedia | Slightly narrower, but covered by VLC, MPlayer and FFmpeg-based players |
| Quality at the same bitrate | Lower | Modestly better |
| Pick it when | Maximum compatibility with very old RealPlayer builds | You want the better-looking of the two and control the player |
RealNetworks' later proprietary codecs, RV30 and RV40, are decode-only in most open tooling and are not offered here for encoding. Whichever of the two you choose, the file is written as a RealMedia container — running our encode locally, ffprobe reports the result as format rm / RealMedia with a stream identified as rv10 (RealVideo 1.0) or rv20 (RealVideo 2.0) respectively.
.rm or .rmvb in its manual..apng onto the page or use the upload button. Plain .png files are accepted too, and several can be queued at once..rmvb. No sign-up, no watermark. Files are uploaded over an encrypted connection, processed on our servers, and deleted automatically after a few hours.Use RMVB only when something in your chain specifically requires RealMedia. RV10 and RV20 are H.263-derived codecs from the late 1990s, so at a given quality they need substantially more bitrate than H.264, and no browser, phone, or social platform will play the result without extra software. If nothing is demanding a .rmvb, convert to MP4 — you can always produce an RMVB later if something turns out to need it.
VLC handles it on every desktop platform, as do MPlayer, mpv, and Media Player Classic — essentially anything built on FFmpeg's RealMedia demuxer. RealPlayer itself still opens them. What will not play them is any browser, the stock video app on iOS or Android, or most smart TVs, without installing a third-party player first.
Both are the RealMedia container. The .rmvb extension signals variable bitrate — the encoder is allowed to spend more bits on complex scenes and fewer on simple ones, rather than holding a constant rate — which RealNetworks added around 2003 for better quality per megabyte on file-based playback rather than live streaming. Players treat the two extensions the same way; the demuxer does not care which one is on the filename.
RealVideo has no alpha channel, so transparency cannot survive. Every frame is composited onto a single solid colour before encoding — whatever Background Color is set to, white unless you change it — so semi-transparent edges blend smoothly into that colour instead of leaving a hard fringe. Pick the colour that matches wherever the clip will be shown. If transparency has to be preserved, stay on APNG or use a WebP output instead.
Yes. An animated APNG is read as a video-like source rather than a single still image, so the per-frame delays stored in the file drive the output's frame rate and duration. That is also why this page shows no "hold each image for N seconds" or merge control — those exist for still-image sources, which have no timing of their own, and are hidden when the input is already animated.
No. APNG cannot carry sound, so there is nothing to encode and the output is silent. RealMedia would normally pair RealVideo with RealAudio or AAC, but with no source audio those settings have nothing to act on. Add a soundtrack afterwards in an editor if the clip needs one.
No. APNG stores a play count inside the file; RealMedia has no equivalent flag, so playback stops at the end unless the player is set to repeat. If continuous looping is the whole point of the animation, RMVB is a poor fit — an MP4 in a <video loop> tag, or simply keeping the APNG, does the job with no extra configuration.
Because it is the first RealVideo codec, released in 1997 and based on ITU-T H.263. The four-character codes RV10, RV20, RV30 and RV40 identify generations one through four, so RV40 — the last of them — is RealVideo 4, not RealVideo 40. It is a common source of confusion when reading ffprobe output or a player's codec panel.
Yes. Queue them and each one is converted with the same settings, producing its own .rmvb. There is no "combine these into one clip" mode for animated inputs, because each APNG already defines its own sequence and timing — that control only appears for still-image sources. To join finished clips, convert them first and merge afterwards.