What is Remuxing?
Remuxing transfers already encoded audio, video, and related streams from one container or packaging structure to another. It changes their organization without decoding and recompressing the media content.
How Remuxing works
A remuxer reads packetized elementary streams and their timing metadata from one container, then writes compatible packets into a new container layout. Codec bitstreams generally remain intact, but timestamps, indexes, track identifiers, and metadata may be rewritten to satisfy the target format. This is distinct from transcoding, which reconstructs samples and encodes them again. It is commonly used before playback, editing, archival, or streaming packaging when compression is already suitable.
Key facts
- Because compressed samples are copied rather than re-encoded, remuxing normally preserves audiovisual quality and is limited mainly by parsing, storage, and I/O speed.
- A target container must permit the existing codecs and required track features; subtitles, chapters, attachments, or color metadata may not map cleanly between formats.
- Broken or nonmonotonic timestamps can cause drift, seeking errors, or muxer rejection even when the encoded audio and video payloads themselves are valid.
When Remuxing matters
Remux when existing codecs meet quality requirements but a player or delivery protocol needs different packaging. The operation is fast and avoids generation loss, but incompatible codecs may still require transcoding.