Remux vs re-encode
Two operations that both turn an MKV into an MP4, with completely different consequences for the picture. One copies the frames. The other rebuilds them.
One copies, one rebuilds
Every video file is a compressed stream plus an index that records where each frame starts and how long it lasts. The container is the envelope around both.
A remux reads that index, copies the compressed stream untouched, and writes a new index in the target format. Not one frame is decoded. This is what ffmpeg -i in.mkv -c copy out.mp4 does, and it is what the tool on this site does.
A re-encode decodes every frame back to pixels, then compresses it again with a new encoder and new settings. That is how resolution, bitrate or codec get changed — and it is also how quality is lost, a little, every single time.
| Remux | Re-encode | |
|---|---|---|
| Compressed frames | copied bit for bit | discarded and rebuilt |
| Picture after conversion | identical | close, never identical |
| Do it ten times | no change at all | ten generations of loss |
| Time for a 1 GB file | seconds, disk-bound | minutes, CPU-bound |
| CPU and battery | close to idle | every core busy |
| Can change resolution or codec | no | yes |
| Needs a video decoder | no | yes |
Why most online converters re-encode anyway
Because it always works. A transcoder accepts any input and produces a playable MP4, including files a remux would have to refuse. The price is time plus a small permanent loss on every file.
Many browser converters go further: they download a complete ffmpeg build compiled to WebAssembly, around 30 MB, then run it with default settings. Those defaults do not copy — they transcode. The result is a progress bar for several minutes and a file slightly worse than the one you started with.
For the common case, H.264 or HEVC video inside an MKV that only needs to open on a phone, a remux is not the cheaper compromise. It is the better operation, and the only reason it is not the default everywhere is that it cannot handle every input.
When you actually need to re-encode
- VP9 or AV1 video. They can be stored in MP4, but playback outside a browser is unreliable. This tool refuses rather than hand you a file that stalls on a television.
- Audio MP4 will not play. AC-3, DTS, Opus, Vorbis and FLAC. The video can still be copied; only the audio needs converting.
- You want a smaller file. A remux keeps the original bitrate by definition. Shrinking means encoding, and encoding means making a quality decision.
- You are cutting or joining clips. Anything that moves frame boundaries needs a re-encode, at least of the affected section.
- You are changing resolution. Same reason: new frame size, new encode.
A quick way to tell what a converter did
Read the output's metadata. A remux preserves the original encoder tag and bitrate almost exactly; a re-encode writes a new encoder string and a different bitrate. Output size that barely moved is another signal — copying a stream cannot change its size by more than the index overhead.
The exact test is frame hashes:
ffmpeg -i input.mkv -map 0:v -f framemd5 -
ffmpeg -i output.mp4 -map 0:v -f framemd5 -
Identical lists mean identical frames. How to check the picture yourself walks through the comparison in detail.
Try it on your own file
The tool on the home page lists the streams inside your MKV, and what it will refuse or drop, before it converts anything. If the video is H.264 or HEVC, the output is identical by construction rather than by promise.