ffmpeg -i in.mov -c copy out.mp4 moves H.264 and AAC into an MP4 in under 1 second without touching a frame; on ReelSDK that costs under a fifth of a cent at $0.02 per compute minute. ProRes can't be copied and needs a re-encode.

Convert MOV to MP4 with ffmpeg: copy or transcode

When the MOV holds H.264 or HEVC with AAC, MP4 takes the same streams as they are, and ReelSDK's API had the remux back in about 3 seconds. ProRes 422 has no place in MP4, so it is encoded again, to 8-bit 4:2:0 H.264.

GuidesUpdated

remux
ffmpeg -i phone.mov -c copy -movflags +faststart phone.mp4

-c copy moves the video and audio packets into an MP4 container as they are, so nothing is decoded, the frames stay identical, and it takes a fraction of a second. +faststart puts the index at the front for playback on the web.

Variations

The other commands you will need

  1. Check what the MOV holds

    Print the codec of every stream before you choose. Our phone.mov printed h264,High,avc1 and aac,LC,mp4a; prores.mov printed prores,Proxy,apco,yuv422p10le and a pcm_s16le audio track.

    inspect
    ffprobe -v error -show_entries \
      stream=codec_name,codec_tag_string,profile,pix_fmt,bit_rate \
      -of csv=p=0 prores.mov
  2. Transcode a ProRes MOV to H.264

    -c copy stops here: Could not find tag for codec prores in stream #0, codec not currently supported in container. Encode the video with libx264 in 8-bit yuv420p and the audio to AAC. Our 59 MB ProRes file came out at about 10 MB, after about 27 seconds.

    transcode
    ffmpeg -i prores.mov -c:v libx264 -crf 20 -pix_fmt yuv420p \
      -c:a aac -b:a 192k -movflags +faststart prores.mp4

The flags

The flags in these commands

The flags in these commands
FlagWhat it doesUsed here
-c copyCopies every selected stream without decoding itRemux
-movflags +faststartMoves the index (moov atom) to the start of the fileBoth
-c:v libx264 -crf 20Encodes H.264 at constant quality; 23 is the default, lower is betterTranscode
-pix_fmt yuv420p8-bit 4:2:0, the format players expect; without it libx264 kept ProRes' 10-bit 4:2:2Transcode
-c:a aac -b:a 192kEncodes the audio to AAC at 192 kb/sTranscode
ffprobe -show_entries stream=...Prints the chosen fields of every streamInspect

Sources: ffmpeg documentation, FFmpeg H.264 encoding guide, checked November 2026.

Why most MOV files copy straight across

MP4 grew out of Apple's QuickTime format, and both store streams in the same kind of boxes. A MOV with H.264 or HEVC video and AAC audio holds nothing MP4 can't hold, so -c copy only rewrites the container around the same packets. That is why the remux took a fraction of a second, and why the result looks exactly like the source.

If the MOV has HEVC video, keep it as it is and add -tag:v hvc1 so Apple players open the MP4; the H.265 guide explains the tag.

ProRes needs a re-encode

ProRes is an editing codec: even the light 422 Proxy flavour ran at about 43 Mbit/s on our clip. ffmpeg 8.1's MP4 muxer has no tag for it, so a copy stops before writing anything. The only way into MP4 is to encode the video again, usually to H.264 or HEVC.

The audio is less strict. ffmpeg 8.1 copied the 16-bit PCM track into MP4 as an ipcm track, but players are built for AAC in MP4, and AAC at 192k is an eighth of the PCM bitrate. We converted both.

Keep the bit depth or go 8-bit

libx264 encodes whatever pixel format it is given if it can. Fed ProRes without -pix_fmt, it kept the 10-bit 4:2:2 picture and wrote the High 4:2:2 profile, which browsers and phones don't play. -pix_fmt yuv420p converts to 8-bit 4:2:0 and the High profile that plays everywhere.

Keep 10-bit only when the file goes back into an editor. For delivery, CRF 20 holds up well; 17 or 18 is visually lossless according to the CRF guide, at a larger size.

Without installing ffmpeg

The same command as one API call

Send the same args to POST /v1/ffmpeg with the MOV's URL in inputs. Each job runs ffmpeg 8.1 on a fresh machine at $0.02 per compute minute, billed per second; this remux finished in about 3 seconds, download and upload included, and cost under a fifth of a cent.

terminalTry it
curl "https://api.reelsdk.com/v1/ffmpeg?wait=60" \
  -H "Authorization: Bearer $REELSDK_KEY" \
  --json '{
    "inputs": {
      "phone.mov": "https://api.reelsdk.com/f/lib/out/job_2aw5h5hby6h7ofi1bqi8/phone.mov"
    },
    "args": [
      "-i", "phone.mov", "-c", "copy", "-movflags", "+faststart",
      "phone.mp4"
    ],
    "outputs": ["phone.mp4"]
  }'
phone.mp4 from the API: the same H.264 and AAC streams as the MOV, frame for frame.Input: phone.movprores.mov

FAQ

Questions, answered

How do I convert MOV to MP4 without losing quality?

If the MOV holds H.264 or HEVC with AAC, remux it: ffmpeg -i in.mov -c copy out.mp4. The packets are copied, not re-encoded, so the frames are identical. On our 11-second clip it took a fraction of a second.

Why does ffmpeg say codec not currently supported in container?

The MP4 muxer has no tag for one of the streams you asked it to copy. With a ProRes MOV it stops on the video stream; encode that stream instead, for example with -c:v libx264 -pix_fmt yuv420p.

Do I need -pix_fmt yuv420p when converting MOV to MP4?

For ProRes and other 10-bit or 4:2:2 sources, yes. Without it libx264 kept our ProRes file's yuv422p10le and wrote the High 4:2:2 profile, which most players can't decode.

Is MP4 smaller than MOV?

Not by itself: the remuxed file was practically the same size as the MOV. The codec decides the size. Our ProRes MOV shrank from 59 MB to about 10 MB because the video was encoded to H.264.

Can I convert MOV to MP4 without installing ffmpeg?

Yes. Send the same args to POST https://api.reelsdk.com/v1/ffmpeg with the MOV's URL in inputs. It runs ffmpeg 8.1 on a fresh machine per job for $0.02 per compute minute, billed per second, and failed jobs are free.

Ready to build?

Ship video from your app today

Your first $0.50 is free, and one key covers every endpoint.

Moonlit lake with a lit cabin under the mountains