
MOV to MP4
Repackage a QuickTime MOV into MP4. Both are the same ISOBMFF box family carrying the same H.264/H.265 and AAC, so every packet is copied across with no decode and no re-encode.
MOV to MP4 moves a QuickTime file straight into an MP4 wrapper. Since both containers use the ISOBMFF box layout, the video, audio and codec data travel across untouched, nothing decoded or rebuilt. A codec MP4 cannot legally hold is named and turned away rather than silently transcoded. Node, the CLI and MCP handle this exactly like the browser does.
Questions
Does this re-encode my video?
No. Every packet is copied straight from the MOV into a new MP4 with no decode and no re-encode, since MOV and MP4 are both the same ISOBMFF box family carrying the same H.264, H.265 and AAC data. The picture and sound come out bit for bit identical to the source.
What do I stand to lose?
Nothing from the video or audio itself. A track using a codec MP4 cannot legally hold is refused by name rather than dropped or re-encoded, so the only way to lose something here is a codec MP4 was never built to store.
Which engine handles this, and where can it run?
A packet-copy remux tool copies data through the mediabunny demuxer and muxer, with no WebCodecs decode step anywhere. Since nothing is decoded, this runs in Node, on the command line and through MCP as well as the browser.
What size should I expect?
The same size, or extremely close to it. Since packets are copied rather than re-encoded, the output MP4 holds the same compressed data as the source MOV, with only a small difference from the container header bytes.
What is the reverse page?
There is none. Nothing on this site writes MOV, since MOV is not one of the output formats Convert video offers.