How to convert MOV to MP4 on Mac (the fast, lossless way)

QuickTime, the iPhone camera, and the macOS Screen Recording shortcut all save video in MOV. Most upload forms, web players, and Windows machines prefer MP4. The conversion is almost always trivial — the two formats are much more similar than they look — but the right way to do it depends on what’s inside the file.

This post is the fast version: how to convert MOV to MP4 on a Mac, how to do it without quality loss, when re-encoding is unavoidable, and how to get a 3-second remux instead of a 10-minute encode.

TL;DR

If your MOV contains H.264 or H.265 video (almost all MOVs do), you can convert it to MP4 in seconds by remuxing — changing the container without touching the video stream. The video is bit-identical to the source.

Three ways, fastest first:

1. ffmpeg one-liner: ffmpeg -i input.mov -c copy output.mp4 — takes seconds, lossless, free.
2. Video Forge → “Web Optimized” destination with the “Already fits — will remux” chip: 3 seconds, lossless, no command line.
3. QuickTime → File → Export As → 1080p (or higher) → MP4: 30 seconds to several minutes, slight quality loss, no command line.

The first two are functionally identical. The third re-encodes and shouldn’t be your first choice.

What’s actually in a MOV file

MOV and MP4 are both containers. A container is the outer wrapper that holds video, audio, and metadata streams. Both MOV and MP4 use the same underlying structure (the ISO base media file format, ISO/IEC 14496-12), which is why they’re nearly interchangeable.

The actual video and audio bits inside are encoded with codecs:

• iPhone video: H.264 or H.265 (HEVC) video, AAC audio. Container: MOV.
• Mac screen recording (built-in): H.264 video, AAC audio. Container: MOV.
• iMovie export: H.264, AAC. Container: MOV.
• Final Cut export to ProRes: ProRes video, PCM audio. Container: MOV.
• DSLR or mirrorless camera: H.264 or H.265, PCM audio. Container: MOV.

The codecs themselves are platform-agnostic. H.264 video doesn’t care whether it’s wrapped in MOV or MP4 — it plays the same. Re-wrapping (remuxing) is fast and lossless because the encoded video stream doesn’t change. (If you’re deciding which codec your output should use rather than just rewrapping, the H.264 vs H.265 vs AV1 comparison goes deep on the choice.)

The only cases where you need to re-encode:

• The MOV contains ProRes video and you need the output to play on a phone or browser. (ProRes is an editing intermediate; it’s huge and not supported in web players.)
• The MOV contains PCM audio (raw uncompressed audio from a DSLR mic) and you need MP4-friendly AAC.
• The MOV contains H.265 and you need it to play on a system that only supports H.264.

For most iPhone and Mac screen recordings — the most common cases — remuxing works perfectly.

The ffmpeg one-liner

If you have ffmpeg installed (brew install ffmpeg on Mac):

ffmpeg -i input.mov -c copy output.mp4

What this does, flag by flag:

• -i input.mov — read this file.
• -c copy — copy all streams (video, audio, subtitles) without re-encoding. This is the magic flag.
• output.mp4 — write to this file. The .mp4 extension tells ffmpeg to use the MP4 container format.

On a typical 1 GB MOV, this takes 1 to 3 seconds. The output file is the same size as the input (give or take container overhead), and the video quality is bit-identical to the source.

When the one-liner fails

A few cases where -c copy doesn’t work:

• HEVC with hev1 tag: some MOV files use the older hev1 tag for H.265. MP4 prefers hvc1. Apple’s QuickTime won’t play hev1 MP4 files. This is the same issue that breaks HEVC clips when sending iPhone video over iMessage — the fix is identical. Use -tag:v hvc1:

  ffmpeg -i input.mov -c copy -tag:v hvc1 output.mp4

• PCM audio: MP4 doesn’t allow PCM audio. You’ll see an error like “could not write header for output file.” Re-encode just the audio while still copying the video:

  ffmpeg -i input.mov -c:v copy -c:a aac -b:a 192k output.mp4

• ProRes video: ProRes is technically allowed in MP4 but no consumer player supports it. You almost certainly want to re-encode to H.264:

  ffmpeg -i input.mov -c:v libx264 -crf 23 -c:a aac -b:a 192k output.mp4

The Video Forge way

If you don’t want to run ffmpeg commands:

1. Open Video Forge (10 conversions free on macOS and Windows).
2. Drag your MOV in.
3. Pick the Web Optimized destination tile.
4. Look at the chip under the tile. If it says “Source already fits — will remux”, the app will copy the video stream straight into MP4 without re-encoding. Takes about 3 seconds.
5. Hit Convert.

Video Forge does the remux-vs-re-encode decision automatically based on the source codec, destination requirements, and any size cap. For MOV → MP4 where the source is already H.264 (very common), it always remuxes.

When you do need to re-encode

A few legitimate reasons to re-encode rather than remux:

• You need a smaller file. A 4K iPhone clip is 100+ MB per minute. To fit a WhatsApp 16 MB cap, you need to drop resolution and/or push CRF higher, which requires re-encoding. The same applies to Discord’s 10 MB free-tier cap and Gmail’s 25 MB email attachment cap.
• The source is ProRes. No phone or web player handles ProRes.
• You need a different codec. Older Windows systems may not support HEVC; re-encoding to H.264 fixes playback.
• You need to trim or speed-change. Either operation requires re-encoding the affected parts.

For all of these, the Video Forge flow is the same — pick a destination or set manual encoding params, the app picks remux or re-encode based on the math.

QuickTime’s built-in export

Built-in to macOS, no extra tools:

1. Open the MOV in QuickTime Player.
2. File → Export As → 1080p (or 4K, or 480p).
3. Pick a destination, click Save.

Caveats:

• QuickTime always re-encodes. It doesn’t have a “just remux” mode.
• The export uses H.264 with QuickTime’s own settings, not necessarily optimal for your use case.
• It’s slow — minutes for a typical clip, not seconds.
• Output is MOV by default. You can rename .mov to .mp4 and it’ll often work for web upload, but technically the container is still MOV-flavored.

QuickTime is fine if you don’t want to install anything else. It’s not the fastest or highest-quality option.

Comparison

Method	Time (1 GB MOV)	Quality	Tools needed
ffmpeg -c copy	1-3 s	Lossless	ffmpeg installed
Video Forge “remux”	1-3 s	Lossless	Video Forge installed
QuickTime Export	2-10 min	Slight loss	None
HandBrake encode	1-5 min	Slight loss	HandBrake installed

Remuxing wins on speed and quality. The only reason to re-encode is if you specifically need a different codec, resolution, or file size — in which case you weren’t really “converting MOV to MP4”; you were re-compressing.

FAQ

Is MOV the same as MP4? Almost — both based on the same ISO base media file format. MOV is Apple’s variant. Most MOV files convert to MP4 by changing only the container, no re-encoding required.

Can I convert MOV to MP4 without losing quality? Yes, if the codec inside is H.264 or H.265. The video stream is repackaged into MP4 without touching the pixels. Output is bit-identical to source.

How long does it take? For remuxing — 1 to 3 seconds per gigabyte. For full re-encoding — about the video’s duration on hardware-accelerated encoders.

Why won’t my MOV play on Windows? Usually because the codec inside is ProRes or HEVC tagged as hev1. Converting the container to MP4 and rewriting the codec tag fixes most playback issues.

Will the audio survive the conversion? Yes — AAC and ALAC audio passes through unchanged. PCM (raw uncompressed) audio from some cameras needs to be re-encoded to AAC for MP4 compatibility.

---

Video Forge auto-detects when MOV → MP4 can be remuxed and does it in 3 seconds instead of 3 minutes. 10 conversions are free on macOS and Windows. See the MOV → MP4 conversion page for the format-specific overview or browse all conversion pairs.