How to Convert MOV to MP4 on a Mac (Without Installing Anything)

Why Macs make MOV files in the first place

If you have a Mac and an iPhone, MOV files appear everywhere. The screen recorder writes them. iMovie exports them. Photos hands them to you when you AirDrop a video. iPhone recordings arrive as MOV unless you have explicitly changed the camera settings. The reason is historical: Apple created the QuickTime Movie format in 1991, and the macOS multimedia stack has been built around it ever since.

The trouble starts when you try to send the file somewhere that isn't another Apple device. Windows Media Player handles MOV inconsistently. Android phones often refuse to play it. Most web platforms either reject MOV uploads or convert them server-side. Many older smart TVs ignore the file entirely. The fix is to convert to MP4 — a container that plays on essentially every consumer device made in the last decade.

The good news is that the conversion is almost always trivial, because MOV and MP4 are technically siblings. The video stream inside both is usually the same; only the wrapper changes.

Four options, ranked by friction

Option one: a browser tab. The MOV to MP4 tool on this site runs FFmpeg compiled to WebAssembly. Drop the file in, click convert, download the MP4. Nothing installs, nothing uploads. The default mode is a stream copy — the encoded video and audio are lifted from the MOV container and dropped into an MP4 container without re-encoding. Output is bit-identical to the source in everything but the wrapper. For most users, this is the right answer.

Option two: QuickTime Player. QuickTime is built into macOS. Open the MOV, choose File → Export As → 4K or 1080p (depending on source), and Quick Time writes an MP4. The downside is that Apple gates several useful options behind a paid QuickTime Pro license, and the export is a re-encode rather than a stream copy — slow, and slightly lossy. It also limits codec choice to whatever QuickTime currently supports.

Option three: HandBrake. HandBrake is a free, open-source desktop video tool that wraps FFmpeg with a friendly GUI and preset library. Install it from handbrake.fr, drop your MOV in, pick the "MP4 Fast 1080p" preset, click Start. Excellent results, especially for batch conversions. The downside is the install, the moderate learning curve, and the fact that HandBrake is a re-encoder — it does not do stream copies, so even when the source could just be re-wrapped, you wait through a full re-encode.

Option four: command-line FFmpeg. Install FFmpeg with Homebrew (brew install ffmpeg) and you have the full engine available in any Terminal window. The MOV-to-MP4 stream copy is a one-liner:

``

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

`

This is the fastest possible conversion and the most flexible — you can script it, batch it, hook it into other tools. The downside is that you have to be comfortable with the command line and you carry the responsibility of installing and updating FFmpeg yourself.

What "stream copy" actually does

The phrase comes up because it is the key to fast, lossless MOV-to-MP4 conversion, but it is rarely explained well.

A video file has two main parts: a container (MOV, MP4, MKV) and the streams inside (video, audio, subtitles). When the codecs inside are compatible with the target container — and for MOV-to-MP4 they almost always are, because both containers descend from the same ISO base media file format — the conversion is just a re-write of the outer structure. The encoded H.264 video stream and the AAC audio stream are copied byte-for-byte; only the index and headers are regenerated.

This means the conversion takes seconds even on hour-long source files, because no encoding work happens. The output file size is within a fraction of a percent of the source. There is zero quality loss. There is no opportunity for the converter to "improve" your file because nothing is being decided — the bytes are just being re-shelved.

The browser tool defaults to stream copy. The command-line equivalent above does the same via -c copy`. HandBrake and QuickTime Pro do not have a stream-copy mode; they always re-encode.

When stream copy fails

A handful of edge cases will make stream copy refuse:

• The MOV contains a codec MP4 cannot wrap. Rare in 2026, but old MOV files sometimes carry PCM audio, ProRes video, Apple Lossless, or other formats the MP4 container does not officially support. The fix is to re-encode — both the browser tool and the command line have options for this.

• You actually need to change the codec. If your iPhone MOV contains HEVC (H.265) video and you need to send it to someone on a 2016 Android phone that does not decode HEVC, you need to re-encode to H.264. Stream copy preserves HEVC; only re-encoding can change codecs.

• The source is broken. Sometimes MOV files come out of failed recordings or interrupted exports in a slightly corrupted state. Stream copy is brittle to this — it expects valid streams. Re-encoding is more forgiving because it re-builds everything from scratch.

For all three, the browser tool exposes a "re-encode to H.264" checkbox that switches modes. It is slower (every frame has to be decoded and re-encoded) but it handles all of the above.

iPhone HEVC: the modern wrinkle

Recent iPhones record video in HEVC (H.265) inside a MOV container, not H.264. HEVC is about forty percent smaller than H.264 at equivalent quality, which is great for phone storage but introduces compatibility questions.

For most modern recipients — recent iPhones, recent Macs, recent Windows, modern smart TVs, modern web browsers — HEVC inside MP4 plays fine. The browser tool's default stream-copy mode produces an MP4 with HEVC video, which is correct and compact. For older Android devices, older laptops, older browsers, you need H.264. Enable the re-encode checkbox; the output will be larger but universally playable.

If you are not sure what the recipient has, default to re-encoding. The size penalty is real but the compatibility upside is total.

The privacy comparison

Of the four options above, only one (the browser tool) is comparable to the also-popular fifth option: uploading to an online converter. That fifth option is what most users actually do because it requires no install and no command line, but it has the cost of sending your video to a stranger's server.

The browser-based tool gives you the same install-free, command-line-free experience while keeping the file on your machine. The FFmpeg engine downloads to your browser cache once (about thirty megabytes) and runs locally from then on. For a single MOV-to-MP4 conversion on a Mac you are not sure you want to do twice, it is the right answer.

Related reading

• The MOV to MP4 tool — the in-browser version of this article.
• Browser vs desktop FFmpeg — when each option makes sense.
• Video codecs explained — why HEVC files are smaller and when to use it.
• How FFmpeg works — the engine behind all four desktop options.