Transmuxing — also called "repackaging" or "remuxing" — is changing a video's container format without re-encoding. Take an MP4 file containing H.264 video, transmux it, and you get an MPEG-TS file with the exact same H.264 video inside — just wrapped differently. The actual encoded video bytes are copied unchanged; only the outer container layer is rewritten. The operation takes seconds (limited mostly by disk I/O speed) and produces no quality loss because nothing got re-encoded.
The contrast with transcoding matters operationally and economically. Transcoding (decode → re-encode) costs CPU/GPU time proportional to the video's length and complexity — often the most expensive step in a video pipeline. Transmuxing costs almost nothing. So whenever a workflow needs to ship the same video in different container formats — MP4 for download, HLS-fMP4 for Apple devices, DASH-fMP4 for everything else, MPEG-TS for some broadcast pipeline — transmuxing from a single source encode saves a fortune compared to re-encoding for each output.
For a product team, transmuxing is the cheap operation that lets one encode serve many delivery formats. Standard pipeline: encode the video once into your chosen codec (H.264, HEVC, AV1), then transmux into whichever containers each delivery endpoint needs. Modern packagers (Shaka Packager, AWS MediaPackage, Bitmovin, Unified Streaming) make transmuxing a core feature — feed them a single MP4 input, get HLS and DASH outputs sharing the same underlying bytes. The economics: if you ever see a pipeline doing parallel transcodes to produce HLS-TS and DASH-MP4 versions of the same content, replace it with a transmux step and watch your encoding bill drop dramatically.
