RMVB to TS Converter

Convert RMVB to TS: What You Are Actually Doing

An .rmvb file is RealMedia Variable Bitrate — RealNetworks' container from 2003, a variable-bitrate sibling of the constant-bitrate .rm streaming format. It carries RealVideo (RV20/RV30/RV40) picture and RealAudio sound, and it spread widely as a distribution format for Asian television and film because it packed a long episode into a small file. A .ts file is an MPEG-2 Transport Stream: the ISO/IEC 13818-1 packet format that digital broadcast, IPTV and HLS all run on.

This is a full re-encode, not a rewrap. RealVideo cannot ride inside a transport stream, so the picture is decoded and encoded again — H.264 by default — and the RealAudio soundtrack is decoded and re-encoded as AAC. Nothing here is a copy operation, so pick your settings once and convert once rather than round-tripping.

How to Convert RMVB to TS

1. Upload Your RMVB File: Drag the .rmvb onto the page or click "+ Add Files" to browse. Several files can queue at once and they all convert with the same settings.
2. Confirm Video Codec and Audio Codec: Video Codec opens on H.264, which is what HLS segmenters and modern transport-stream players expect. Audio Codec opens on AAC. The other TS-legal choices are listed in the table below.
3. Choose a File Compression Mode: The panel opens on Quality Preset at "Very High (Recommended)". Constant Bitrate, Variable Bitrate, Specific file size, Constant Quality and Constraint Quality are all available and all functional on an H.264 target.
4. Set Resolution or Trim, Then Convert: Video resolution opens on Keep original; Trim opens on "Unchanged" and takes a Time Range. Click Convert to download the .ts. Files are uploaded over an encrypted connection, processed on our servers, and deleted automatically after a few hours — no sign-up, no watermark.

Walk-through: Picking the Codec Pair

Almost every RMVB conversion should leave both dropdowns alone. These are the cases where changing them is justified.

• Feeding an HLS packager or a modern player — keep H.264 + AAC. This is the pairing every transport-stream tool has supported since the format's streaming era began, and it is the only combination you can assume will work without a remux.
• Feeding older DVB or ATSC broadcast equipment — switch Video Codec to MPEG-2 and Audio Codec to MP2. That is the original broadcast payload the transport stream was designed around. Expect a much larger file: MPEG-2 needs several times the bitrate of H.264 for comparable detail.
• Squeezing a long episode down hard — switch Video Codec to H.265. It compresses better than H.264 at the same visual quality, but transport-stream support for HEVC is narrower, so confirm the receiving device handles it first.
• You saw DTS (DCA) in the list — pick something else. Our pipeline treats the DTS encoder as experimental and substitutes AC-3 before the job runs, so selecting DTS gets you an AC-3 track under a different label. If you want Dolby, choose AC3 directly and know what you are getting.

Because the target codec is H.264 rather than RealVideo, Constraint Quality works normally on this page. That is worth saying because it is not true in the opposite direction: on pages that write RealVideo, the max-bitrate constraint is stripped before encoding. Here the constraint is honoured.

RMVB Source vs TS Output

Codec Choices Available on This Page

Common Errors and How to Fix Them

• "The output is soft compared with the RMVB" — RMVB was tuned to look acceptable at low bitrates, and re-encoding it to H.264 is a lossy-to-lossy pass. Raise the Quality Preset to "Highest" or switch to Constant Quality and lower the CRF value, and leave Video resolution on Keep original so you are not paying for a rescale as well.
• "My player opens the .ts but there is no sound" — some transport-stream players only decode MP2 or AC-3 audio. Re-run with Audio Codec set to AC3 or MP2 instead of AAC.
• "The file is bigger than the original" — that is normal. RMVB's variable-bitrate encoding plus the transport stream's per-packet overhead means the .ts is usually the larger of the two even when the picture is identical. In our testing a 10-second 640×480 RealVideo clip of 1.19 MB produced a 1.29 MB transport stream at the default H.264 CRF 23 with AAC audio.
• "The RMVB will not upload or fails to decode" — some RMVB files carry RealNetworks DRM or use a RealVideo variant with no open decoder. There is no online workaround for a protected stream; play it back in the original authorised player instead.
• "I wanted a normal video file, not a transport stream" — you almost certainly want RMVB to MP4 or RMVB to MKV. TS is a delivery and broadcast format, not a general playback one.

Frequently Asked Questions

Why does RMVB have to be re-encoded instead of just rewrapped into TS?

Because a transport stream cannot carry RealVideo. The MPEG-2 Systems specification defines which elementary streams a TS may multiplex, and RealNetworks' codecs were never registered among them — there is no stream type a RealVideo payload could claim. So the picture must be decoded and re-compressed into a codec the transport stream recognises, which on this page defaults to H.264. The same applies to the RealAudio track, which becomes AAC. Every conversion on this route is therefore a fresh lossy encode, not a container swap.

What is the difference between .rm and .rmvb?

They are the same container family with different rate control. .rm holds RealMedia encoded at a constant bitrate, which suited RealNetworks' original streaming use case where the delivery channel had a fixed budget. .rmvb is the variable-bitrate variant, meant for files stored locally: complex scenes get more data and static ones less, so an episode fits into a smaller file at the same perceived quality. Both share the .RMF header signature, and this converter handles the RMVB spelling.

Will the transport stream play in VLC?

Yes. VLC reads MPEG-2 transport streams on Windows, macOS and Linux without extra components, and it decodes the default H.264 plus AAC pairing this page produces. That is worth knowing in both directions: VLC is also one of the few current players that still decodes RealVideo, so if a .rmvb opens in VLC but nowhere else, converting it is exactly the right move.

Can I join several converted TS files into one stream?

Yes, and it is one of the format's genuine strengths. A transport stream is a run of self-contained 188-byte packets rather than a single indexed file, so clips encoded with matching codec, resolution and frame rate can be appended end to end and still play as one. Convert every RMVB episode with identical settings first so the streams line up; mismatched resolutions or frame rates will make players stumble at the joins.

Does the conversion keep the subtitles that were in my RMVB?

No. Subtitle handling is not part of this conversion, and RealMedia's own subtitle mechanisms do not map onto a transport stream's elementary-stream model. If the subtitles were burned into the picture they survive, because they are part of the video frames; if they were a separate selectable track, they are dropped. Extract them with a desktop tool before converting if you need to keep them.

Why is the audio only as good as it was, even at a high setting?

Because you cannot recover what the source never stored. RealAudio tracks in .rmvb files were usually encoded at low bitrates to keep episode sizes down, and re-encoding a lossy track into AAC is a second lossy generation on top of the first. A high quality setting stops the conversion from adding more damage, but the ceiling is whatever RealAudio captured. If the soundtrack matters more than the picture, extract it once with RMVB to MP3 and keep that copy.

What resolution will the TS be?

Whatever the RMVB was, unless you change it. Video resolution opens on "Keep original" and no rescale is applied by default. If you do pick a preset, note that the preset list sets height only and lets the width follow the source's aspect ratio, so it will not produce an exact frame size — use Width x Height when a specific raster is required. Avoid upscaling a low-bitrate RMVB; enlarging the frame spreads the same detail thinner and makes the compression artefacts more obvious rather than less.

Should I convert RMVB to TS or to MP4?

MP4 in nearly every case. It plays on phones, browsers, TVs and editors, and it carries the same H.264 video with far less packet overhead — RMVB to MP4 is the sensible default. Reach for TS only when the destination demands it: an HLS segmenting pipeline, an IPTV or broadcast chain, or a workflow where you intend to concatenate several clips into one continuous stream. If you want a container that also handles multiple audio tracks and chapters, RMVB to MKV is the better middle ground.

How are my files handled during conversion?

Your .rmvb is uploaded over an encrypted connection, converted on our servers and deleted automatically a few hours afterwards, along with the transport stream we produced. There is no sign-up, no watermark, and files are never shared or made public. RMVB files are often full-length episodes, so the part of the job you will actually wait on is the upload over your own connection rather than the encode.