Short answer: to turn a QuickTime .mov into an .mp4, start with -c copy. If the file is already H.264 video plus AAC audio, stream copy remuxes the packets, the first-frame RGB24 md5 stays the same, and the duration does not change. If the video is ProRes, DNxHR, or another codec that MP4 players will not handle, you have to re-encode. The five pytest checks below were run on a real 12.064-second 720×1280 fixture (grey-hoodie-v2.mp4, md5 a50e13313b71a76dbd179dcdc2c2b6bf).

This is a reproducible FFmpeg/Python check, not a product walkthrough. An optional later CTA points at Voor's Tiny Desk AI page if you want to see a current image-to-video form after you have a portable MP4.

Why changing the extension is not a conversion

A .mov file and an .mp4 file are both containers. The container can hold several codecs. Changing the suffix, or remuxing with -c copy, does not transcode the video. That is useful when the bitstream is already H.264 or H.265 and you only need a more widely accepted wrapper. It is the wrong tool when the bitstream is ProRes.

The fixture used here is an H.264 MP4. The tests first remux it to MOV without touching the packets, then convert that MOV back to MP4 in two ways.

Stream copy when the codecs already match

Remux the source to MOV, then back to MP4, copying both streams:

ffmpeg -i fixture.mp4 -c copy fixture.mov ffmpeg -i fixture.mov -c copy remuxed.mp4 

-c copy does not decode the video. The first-frame RGB24 md5 of remuxed.mp4 equals the source, the duration stays 12.064 seconds, and the audio stream md5 is unchanged. The output video codec is still h264, the audio codec is still aac, and the size is 720×1280. If ffmpeg reports that stream copy cannot be used, stop and switch to a re-encode; do not assume the file became more compatible.

You can also add -movflags +faststart so the moov atom is written at the front of the MP4, which helps web playback. That flag still works with -c copy because it only relocates metadata.

Re-encode when the codec cannot live in a playable MP4

To show the other path, the tests write a short ProRes MOV from the same fixture and then transcode it:

ffmpeg -i fixture.mp4 -t 2 -c:v prores_ks -c:a pcm_s16le prores.mov ffmpeg -i prores.mov -c:v libx264 -pix_fmt yuv420p -crf 20 -c:a aac encoded.mp4 

The ProRes MOV's video codec is prores. After the second command, encoded.mp4 is h264 plus aac, 720×1280, and its duration is about two seconds. Stream-copying that ProRes MOV into an MP4 container fails: FFmpeg reports that ProRes is not currently supported in the MP4 container and refuses to write the header. A copy-only command does not produce a playable H.264 MP4. Re-encoding is the step that changes the codec.

-c copy and a filter graph also cannot be mixed on the same video stream. If you need to scale, pad, or change the frame rate, you are already on the re-encode path.

What the tests check

The pytest file in this post runs five checks against the fixture and the two commands above:

  1. Remuxing the H.264 MP4 to MOV with -c copy keeps the first-frame RGB24 md5, the 12.064-second duration, and codecs h264 / aac.
  2. Remuxing that MOV back to MP4 with -c copy again matches the first-frame md5 and duration, still h264 / aac at 720×1280.
  3. The AAC stream md5 is identical across the source MP4, the remuxed MOV, and the remuxed MP4.
  4. A two-second ProRes MOV transcoded with libx264 plus AAC becomes an H.264 MP4 at 720×1280, with a duration close to two seconds.
  5. Stream-copying the same ProRes MOV into an .mp4 container is rejected (codec not currently supported in container), so a copy-only command is not a substitute for the transcode.

Run them from the directory that contains test_mov_to_mp4.py and inputs/grey-hoodie-v2.mp4:

python3 -m pytest -q test_mov_to_mp4.py 

After you have a portable MP4

Once the file plays as H.264 in a normal MP4 player, you can upload it, edit it, or send it to another tool without guessing the container. If you then want to turn a still into a short clip, Voor's Tiny Desk AI page is a current image-to-video form you can inspect without using the commands above.