How remuxing differs from transcoding

A video file has two layers: the container (such as MP4, MOV, MKV, or WebM) and the encoded streams inside it (such as H.264, HEVC, or AV1 video plus AAC audio). Remuxing copies those already-encoded streams bit-for-bit into a new container. Because the codec data is untouched, there is no quality loss and the operation finishes in seconds rather than minutes.

Transcoding, by contrast, decodes the streams back to raw frames and re-encodes them. That is what changes the codec or bitrate, and it is slow and lossy. Remuxing is the right tool when you only need a different wrapper, for example to make a file playable on a device that supports the codec but not the original container.

When remuxing is used

Common cases include converting an MKV download to MP4 for broad device support, fixing a file that plays but has a broken or non-streamable container, or moving a clip into a container that better supports fast-start playback for streaming. Tools like FFmpeg perform a remux with stream copy (`ffmpeg -i in.mkv -c copy out.mp4`), and many editors and players expose it as a 'passthrough' or 'copy' export.

Remuxing cannot change resolution, bitrate, or codec, and it only succeeds when the target container actually supports the streams inside, since not every codec is legal in every container. If a device rejects the underlying codec, you need true transcoding instead.

Storage relevance

Remuxing keeps file size essentially unchanged because the heavy media data is copied, not re-compressed; only container overhead shifts slightly. To actually shrink a clip you need to re-encode to a more efficient codec or a lower bitrate. Cleanor focuses on finding and removing the large and duplicate videos that eat storage, and points you to real compression when a smaller file is the goal.