How to convert MOV to MP4 on Mac (lossless, batch, 2026)

You recorded your screen with ⇧⌘5, or AirDropped a clip from your iPhone, or exported footage from a camera — and now the place it needs to go won’t take it. The upload form wants MP4. The Windows colleague’s player shrugs at it. The LMS, the CMS, the ad platform, the client’s ancient review tool: “unsupported format.” The file ends in .mov, and the world outside Apple wants .mp4.

Here’s the part most guides skip: MOV and MP4 are so closely related that in many cases you can convert between them in seconds, with zero quality loss, without re-encoding a single frame. This guide explains when that lossless path applies, how to take it, and what to do in the cases where a real re-encode is genuinely required — all of it on your Mac, offline.

MOV vs. MP4: same video, different box

MOV is Apple’s QuickTime container; MP4 is the international standard that was literally derived from it. Both are just boxes — the actual picture and sound inside are produced by codecs, and both containers commonly hold the exact same ones: H.264 or HEVC video with AAC audio.

That’s the key insight. When a MOV already contains H.264 or HEVC plus AAC — which covers iPhone footage, macOS screen recordings, and most consumer camera output — “converting to MP4” doesn’t require touching the video at all. The streams can be copied bit-for-bit into an MP4 box. That operation is called a remux (or stream copy), it runs at disk speed rather than encoding speed, and the output is pixel-identical to the input because nothing was decoded or recompressed.

A re-encode is only necessary when the contents of the box aren’t MP4-compatible — ProRes video from pro cameras and editors, PCM audio from some recorders — or when the destination is picky about codecs (more on the HEVC-on-Windows problem below).

One tempting shortcut to rule out first: renaming the file from .mov to .mp4. Because the containers are cousins, some players will happily play the renamed file — which is exactly why the trick is dangerous. The file is still a MOV inside, and stricter software (upload validators, editing suites, set-top boxes) will reject or misread it. Rename is a coin flip; a remux takes barely longer and is actually correct.

Check what’s actually inside your MOV (ten seconds)

Before converting, it pays to know which case you’re in — copy or re-encode. Your Mac will tell you without any extra software:

1. Select the .mov file in Finder and press ⌘I (Get Info), or open it in QuickTime Player and press ⌘I for the inspector.
2. Look at the codecs line. You’ll see something like H.264, AAC or HEVC, Stereo (AAC) — or Apple ProRes 422, Linear PCM.

Reading the result:

• H.264 + AAC — the best case. A pure remux works, and the resulting MP4 plays on essentially everything. macOS screen recordings (⇧⌘5) fall in this bucket.
• HEVC + AAC — a remux works and is lossless, but the output inherits the HEVC compatibility problem described below. Fine for Apple devices and modern platforms; re-encode to H.264 for unknown or older destinations. Default iPhone footage lives here.
• ProRes, PCM audio, or anything exotic — a straight copy into MP4 will fail or produce a broken file; this footage needs a real re-encode (or, for PCM audio, an audio-only re-encode with the video still copied).

If you’d rather not think about any of this, that’s precisely the decision Zumkor’s Universal MP4 preset automates per file — but even then, knowing how to read the codec line turns “it won’t play” mysteries into thirty-second diagnoses.

Why QuickTime Player isn’t the answer

The reflex is to open the clip in QuickTime Player and look for an export option. Two problems.

First, QuickTime Player’s File → Export As always re-encodes — even when the source is already H.264, it decodes and recompresses everything, which is slow and loses a little quality for no reason. Second, and more absurdly: its exports are saved as .mov files. QuickTime Player cannot actually produce an MP4. You can burn ten minutes exporting “1080p” and end up with a fresh MOV.

iMovie can genuinely write MP4 (create a project, drop the clip in, File → Share → File), and it’s free, so it’s a legitimate one-off route. But it re-encodes too, forces the clip through a project timeline, and does one video at a time. It’s a video editor being used as a converter, and it feels like it.

Method 1: ffmpeg (free, lossless, command-line)

If you’re comfortable in Terminal, ffmpeg (installable via Homebrew: brew install ffmpeg) does a perfect remux:

ffmpeg -i input.mov -c copy -movflags +faststart output.mp4

-c copy is the stream copy — no re-encoding, finishes in seconds even for large files. -movflags +faststart moves the index to the front of the file so the video starts playing before it fully downloads, which you want for anything going on the web.

If ffmpeg complains about an incompatible stream — typically PCM audio from a screen recorder or camera — re-encode just the audio and still copy the video losslessly:

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

And for a genuinely incompatible source like ProRes, or when you need maximum-compatibility H.264 output:

ffmpeg -i input.mov -c:v libx264 -crf 18 -preset medium -c:a aac output.mp4

ffmpeg is the power tool: free, scriptable, handles anything. The cost is that you are the logic — you have to inspect the source, know whether copy will work, pick flags, and handle each failure. For one file that’s fine. For a folder of mixed clips, you’re writing a shell script and debugging codec errors one file at a time.

Method 2: Zumkor (the same lossless trick, as a drag-and-drop)

Zumkor packages exactly this decision-making into its Universal MP4 preset (it needs macOS 14 or later on an Apple silicon Mac — any M-series machine):

1. Open Zumkor and drag in your MOV files — or the whole folder of them.
2. Pick MP4 as the output (the Universal MP4 preset is the default worth keeping).
3. Click Convert.

For each file, Zumkor checks what’s inside the box. If the video is already H.264, it stream-copies — the same lossless, seconds-fast remux as the ffmpeg command above, no flags to remember. HEVC iPhone footage, and genuinely incompatible sources like ProRes, are re-encoded to play-anywhere H.264 using VideoToolbox, the Mac’s hardware encoder — which both runs at Apple-silicon speed rather than software-encoding speed and solves the Windows-compatibility problem below in the same pass. Mixed folder of screen recordings, iPhone clips, and a stray ProRes export? Each file takes the fastest path that ends in an MP4 that plays anywhere.

Everything happens on-device — nothing uploads, it works offline, and your footage never sits on a converter site’s server. It’s free for 7 days, then a one-time $19.99 purchase rather than a subscription, and the same app covers the rest of the format matrix: MKV, WebM and AVI to MP4, video to MP3 or GIF, images, audio.

The honest trade-off: for a single file, once, iMovie is free and ffmpeg is free-plus-Homebrew. Zumkor is for when this keeps happening — weekly screen recordings for work, batches of iPhone footage for a Windows-based editor, a camera that stubbornly shoots MOV — and you want “drag folder, get MP4s” without maintaining a script.

The HEVC problem: when a correct MP4 still won’t play

One trap survives the container conversion. iPhones record in HEVC (H.265) by default — Settings → Camera → Formats → “High Efficiency.” A remuxed MP4 of that footage is a perfectly valid MP4… containing HEVC, which many Windows machines can’t play without a codec the user has to install (and historically, pay a dollar for), and which older smart TVs and some web platforms reject outright.

So if the recipient says “it’s MP4 but it still won’t open,” the fix is a re-encode to H.264, the codec that plays on effectively every device made in the last fifteen years. In ffmpeg that’s the libx264 command above; in Zumkor, the Universal MP4 and iPhone-compatible presets output H.264, so HEVC footage is re-encoded on the hardware encoder automatically. You trade a little file size (H.264 is less efficient than HEVC) for universal compatibility — the right trade whenever the destination is unknown.

Prevention, for the future: on the iPhone, Settings → Camera → Formats → Most Compatible records H.264 from the start. The same setting governs photos, which is why the same phone also floods you with HEIC images that need converting to JPG.

Sometimes MP4 isn’t actually what you need

Worth thirty seconds before you convert: a surprising share of “I need this MOV as MP4” tasks are really a different job wearing an MP4 costume.

If the goal is to listen to the clip — a recorded talk, an interview, a voice memo captured on video — you want the audio extracted, not the container swapped. Zumkor pulls the audio track out of a MOV to MP3, M4A, or WAV directly — the same audio engine that converts FLAC to MP3 — and when the source audio is already AAC it can stream-copy that too, losslessly. If the goal is a short looping clip for a chat or a README, the destination is an animated GIF, not an MP4 at all — that route is covered in how to convert MP4 to GIF on Mac. And if the file plays fine everywhere but is simply too big to send, the job is compression to a size cap, covered in the email-compression guide. Naming the actual destination first saves you from converting twice.

Getting the output right

• Prefer stream copy whenever it’s available. It’s not just faster — it’s lossless. Every re-encode of already-compressed video throws away a little quality permanently. Copy when you can, re-encode only when the destination demands it.
• Don’t “upgrade” the resolution. Converting 1080p MOV to “4K MP4” invents no detail; it just quadruples the file size. Match the source resolution unless you’re deliberately downsizing.
• Web-bound files want faststart. If the MP4 is going on a website, make sure the index is at the front (-movflags +faststart in ffmpeg) so playback starts immediately.
• If the MP4 also needs to be small, that’s a different job — compression to a size target, not format conversion. See how to compress video for email on Mac for hitting Gmail’s 25 MB, WhatsApp’s 16 MB, or Discord’s 10 MB caps.
• Need the trip in the other direction? Some Apple-centric tools ask for MOV. MP4→MOV is the same remux logic in reverse, and Zumkor writes MOV (plus M4V and MKV) as readily as MP4.

Bottom line

• One file, free, don’t mind re-encoding: iMovie → File → Share → File. Avoid QuickTime Player’s Export As — it re-encodes and still gives you a MOV.
• Comfortable in Terminal: ffmpeg -i input.mov -c copy -movflags +faststart output.mp4 — lossless, done in seconds.
• Batches, mixed sources, or a recurring chore: Zumkor — drag the folder, Universal MP4 stream-copies what it can and hardware-encodes what it must, entirely offline, for a one-time $19.99.
• “It’s MP4 and still won’t play”: the codec is HEVC — re-encode to H.264 and it plays everywhere.

The renaming trick is a gamble and web converter sites mean uploading gigabytes of your footage to someone else’s server to perform a job your Mac finishes locally in seconds. Convert the box, keep the pixels, stay offline.

FAQ

Can I just rename a .mov file to .mp4?

Sometimes it will play, because the two containers are close cousins — and that’s exactly why the trick is risky. The file is still a MOV internally, so stricter software (upload validators, editors, TVs) will reject or misread it. A proper remux takes seconds, is lossless, and produces a genuinely valid MP4; renaming saves you nothing but those seconds.

Does converting MOV to MP4 lose quality?

Not when the MOV contains H.264 or HEVC video with AAC audio — the common case for iPhone footage and Mac screen recordings. Those streams can be stream-copied into the MP4 container bit-for-bit with zero quality loss. A real re-encode, with its small generational loss, is only needed for MP4-incompatible contents like ProRes video or PCM audio, or when you deliberately convert HEVC to H.264 for compatibility.

How do I batch convert MOV files to MP4 on a Mac?

Terminal users loop ffmpeg over the folder with -c copy, handling any incompatible-stream errors per file. Otherwise drag the whole folder into Zumkor and pick MP4: each file takes the fastest correct path automatically — lossless stream copy where possible, hardware re-encode where required — offline, in one pass.