Cut RMVB files by setting start and end times. Free, no quality loss.
Process files in seconds with our optimized servers
Frame-accurate cuts with intuitive timeline controls
Maintain original quality with smart re-encoding
.rmvb files from your computer — old Chinese drama episodes, anime fansubs, locally archived RealMedia downloads, or anything else carrying the RMVB container. Batch is supported: drop in multiple .rmvb files and apply the same cut range to each.12.5) or HH:MM:SS.sss format (00:14:30.500). Add multiple trim segments to extract several clips from one source — each pair produces its own output file. RMVB itself uses a wide GOP (often 5-10 seconds between keyframes), but that doesn't limit precision here — the cut is re-encoded and lands exactly on your timestamp; see the table below..rmvb as the container, with the cut re-encoded at the visually-lossless default preset. If you plan to play the cut on a modern phone, browser, or smart TV, switch the output to H.264 / H.265 in an MP4 or MKV container and pick a quality preset (Lowest / Low / Medium / High / Highest), a CRF (18-28 typical for H.264), or a target bitrate. Resize via the resolution preset (1080p / 720p / 480p / 360p / 240p) or scale by percentage.RMVB (RealMedia Variable Bitrate) is the variable-bitrate extension of RealNetworks' RealMedia container, introduced in 2003 to deliver smaller-than-CBR files at the same perceived quality. It dominated Asian peer-to-peer scenes through the 2000s — entire libraries of Chinese television, K-drama, Japanese anime, and Hong Kong cinema were ripped to 350-700 MB RMVB episodes for download over BitTorrent, eDonkey, and FTP. Most of those collections still exist on personal NAS boxes, external drives, and family servers; cutting RMVB is what you do when you need a clip out of one of those archives.
For a different output container after cutting, see RMVB to MP4, RMVB to MKV, or RMVB to AVI. To shrink the file without trimming, see Compress RMVB.
| Property | Default (.rmvb output) |
H.264 / H.265 / MPEG-4 output |
|---|---|---|
| Speed | Proportional to clip length | Proportional to clip length and codec |
| Quality | Re-encoded at the visually-lossless default preset | Whatever CRF / bitrate you pick |
| Cut precision | Frame-accurate to your timestamp | Frame-accurate to your timestamp |
| Container | .rmvb retained |
.mp4, .mkv, .avi, .webm |
| Player support | Needs RealPlayer, VLC, MPC, or FFmpeg-based player | Plays everywhere modern (browsers, phones, smart TVs) |
| Best for | Consistency with an existing RealMedia archive | Sharing the cut online, social media, modern playback |
RMVB encoders typically place keyframes 5-10 seconds apart to maximize VBR compression — a much wider GOP than modern H.264 (1-2 s) or H.265 (1-4 s) recorders. That layout doesn't limit the cut here: the kept segment is decoded and re-encoded, so the cut starts exactly at the timestamp you typed. Pick an H.264/H.265 output when you want the clip to play on devices that don't support RealVideo.
| Property | RMVB | MP4 (H.264) | MKV (H.265) |
|---|---|---|---|
| Year introduced | 2003 | 2003 (MPEG-4 Part 14) | 2002 |
| Video codec | RealVideo 9 / 10 (RV30 / RV40) | H.264 / AVC | H.264 / H.265 / AV1 |
| Audio codec | Cook (proprietary) | AAC | AAC, AC-3, FLAC, Opus |
| Typical bitrate (480p) | 350-450 kbps VBR | 700-1500 kbps | 400-900 kbps |
| Native browser playback | None | Chrome / Firefox / Safari / Edge | Chrome / Firefox / Edge (not Safari) |
| iOS / Android native playback | No | Yes | Yes (H.264), partial (H.265) |
| VLC / MPC playback | Yes | Yes | Yes |
| Active development | Legacy (mainstream development wound down ~2012) | Active (HEVC successor, AV1 emerging) | Active (open spec, Matroska Org) |
| Best use today | Reading old archives | Universal delivery | Quality archives, fan rips |
RMVB compresses tighter than H.264 at very low bitrates (its original advantage), but H.265 / AV1 match or beat it at every bitrate and play natively where RMVB cannot. If you're cutting an RMVB for a one-time share, output the cut as MP4. Keeping .rmvb output only makes sense for consistency with an existing RealMedia archive.
No — the cut always decodes and re-encodes the kept segment; there is no stream-copy path. The upside is frame accuracy: even though RMVB encoders place keyframes 5-10 seconds apart, the cut starts exactly at your timestamp instead of snapping back to a keyframe. Left on defaults, the re-encode uses the visually-lossless default quality preset, so the clip looks the same as the source.
With XConvert it shouldn't — the cut re-encodes the kept segment, so the output starts exactly at the time you typed. The snap-back you're describing is how stream-copy cutters behave: they can only begin output on a keyframe (I-frame), and RMVB encoders place keyframes 5-10 seconds apart, so those tools would start a requested 00:01:23 cut at 00:01:17. Here the cut is frame-accurate.
Yes. The cut output stays in the RealMedia container, which plays in the same FFmpeg-based players that handled the source: RealPlayer SP and successors, VLC (uses FFmpeg's reverse-engineered RealMedia decoder), MPlayer, Media Player Classic with the right filters, and mpv. It will NOT play in browsers, on iOS or Android natively, on smart TVs, or in any modern messaging app — those need a re-encode to MP4 or MKV (use RMVB to MP4 for the simplest universal output).
There's no fixed server cap. Cutting runs on our servers, so the practical ceiling depends on upload size and connection speed and how long you're willing to wait for the file to load. Processing time scales with the length of the segment you keep, not the full source duration — a 90-second scene from a 4-hour 1.5 GB RMVB archive processes quickly. On phones and Chromebooks, smaller files (under 500 MB or so) upload more comfortably.
Yes. Add multiple trim segments — each pair of start time + duration produces a separate output file. Useful for pulling several scenes from a single 45-minute drama episode, splitting a long sermon or lecture RMVB into chapters, or extracting all the relevant clips from one long fansub release in one batch.
If you only need to keep it in a personal archive that plays through VLC or RealPlayer, RMVB output keeps the archive consistent. For anything you'll share, post to social, watch on a phone, or stream from a browser, output MP4 (H.264) or MKV (H.265) — neither iOS, Android, Chrome, Firefox, Safari, Edge, nor any smart-TV platform plays RMVB natively. The recommended workflow for sharing: cut first, then run RMVB to MP4 on the cut clip — far faster than transcoding the full source then trimming.
.rmvb but the content looks different from RealMedia?Some downloaders and renamers slap a .rmvb extension on files that are actually MP4, MKV, or AVI containers — this was common on early-2010s file-share sites that wanted to standardize their naming. If our cutter rejects the file or the cut produces a corrupted output, the file is almost certainly mislabeled. Open it in VLC; the codec info will show the real container. Then use the matching xconvert tool: Cut MP4, Cut MKV, or Cut AVI.
Yes. Cut the RMVB first to the segment you want, then run RMVB to MP3 or RMVB to WAV on the result. Cutting first is faster because the audio extraction only has to process the clip, not the full source. Cook audio decodes cleanly to MP3 or WAV via FFmpeg's reverse-engineered Cook decoder; quality is preserved subject to the destination format's compression.
RMVB's container has no native chapter support and limited subtitle support — most RMVB releases relied on hardcoded (burned-in) subtitles instead of soft subtitles. If the source has burned-in subs they're carried through automatically because they're part of the video pixels. If you have an external .srt or .ass file paired with the RMVB, cut both to the same time range and re-attach the subtitle to the cut output (or convert RMVB to MKV, which supports soft subtitles, and mux the trimmed subtitle in).