Convert MOV to MP4 — fast remux, honest re-encode (when you need it)

The short version

1. Drop the .mov file on the converter.
2. Leave the default settings. If your MOV is already H.264 or HEVC (most iPhone recordings), we do a container remux — no re-encode, no quality loss, takes a few seconds even on a 2 GB file.
3. If the video is in ProRes, DNxHD, or another codec MP4 can't carry, we auto-fall-back to H.264 re-encode. Slower, but still fully local.
4. Download. Done.

If that covers it, go. The rest of this post is for when the output won't play somewhere, when the file is too big, or when you're deciding between this and the paid desktop apps.

Why MOV and MP4 are the same file, almost

MOV and MP4 are both container formats — the outer wrapper that holds a video stream, one or more audio streams, subtitles, chapter marks, and metadata. They descend from the same specification: MP4 is formally ISO/IEC 14496-14, which was derived directly from Apple's QuickTime File Format (the MOV spec). The byte-level structure (boxes, atoms, sample tables) is almost identical.

What's inside the container is a separate question. A MOV file typically contains one of:

• H.264 (AVC) — the iPhone default until iOS 11, still the compatibility baseline. Playable almost anywhere.
• HEVC (H.265) — the iPhone default from iOS 11 onward (the "High Efficiency" camera setting). Roughly half the file size of H.264 at the same quality. Playable on modern devices, not-quite-everywhere on Windows without a codec add-on.
• ProRes — Apple's editing codec. Huge files, extremely fast to decode for pro NLEs. Used by Final Cut Pro, sometimes BlackMagic cameras.
• DNxHD / DNxHR — Avid's equivalent of ProRes. Same "big file, fast edit" trade.
• Cinepak, Sorenson, older codecs — you'll see these on legacy MOVs from the 2000s.

MP4 natively carries H.264, HEVC, AV1, and AAC/MP3/AC-3 audio. It does not carry ProRes or DNxHD. This is the only technical reason MOV → MP4 ever needs re-encoding. Container swap ("remux") for the 95% case. Re-encode for pro-footage edge cases.

Why every other site re-encodes anyway

Here's the thing the SERP results gloss over: CloudConvert, Convertio, Zamzar, FreeConvert, and the rest default to re-encoding your MOV. Even when it contains H.264 that would survive a remux unchanged. Three reasons:

• Simpler server code path. Always re-encode means one pipeline, not two. Engineering cost beats your download time.
• Predictable output size. A remux leaves the file at whatever bitrate the camera recorded. A re-encode lets them promise "we compress for you," which is good marketing but technically lossy.
• Forcing consistent codecs. If a quarter of your input MOVs are HEVC and the service can't guarantee every viewer's device plays HEVC, they re-encode to H.264 to eliminate complaints.

The trade: you wait 2–5 minutes for a conversion that could have taken 8 seconds, and you quietly lose a generation of quality. Our MOV to MP4 tool tries the remux path first and tells you when it's doing one vs a re-encode.

When you actually want the re-encode

A remux isn't always the right call. Three scenarios where you should re-encode on purpose:

1. Your target device can't play HEVC

Modern iPhones record HEVC by default. Windows 10 / 11 ships without an HEVC decoder unless you buy the $0.99 extension from the Microsoft Store. PowerPoint sometimes refuses. Older Android phones and some TVs choke. If any of those describe your playback target, re-encode to H.264 — the file will be bigger (roughly 2×) but it'll play on anything made this century. Our tool has a "Force H.264" toggle for exactly this.

2. The file is too big

iPhone HEVC at 4K/60 records at about 450 MB per minute. An hour-long clip is 27 GB. Gmail caps attachments at 25 MB; most Slack/Teams instances at 100 MB; YouTube is fine but your cell network isn't. A re-encode with a lower bitrate (or a resolution drop from 4K to 1080p) gets you from 27 GB to 1–2 GB with barely perceptible quality loss. For that workflow, pair this tool with our general video converter which exposes bitrate and resolution sliders.

3. Your editor wants MP4 specifically

Final Cut Pro happily edits MOV with ProRes. Premiere Pro, DaVinci Resolve, CapCut, and most other NLEs prefer MP4 containers with H.264 or HEVC. If you're handing footage to an editor, a re-encode to .mp4 at a known bitrate is the right move — and generates proxies much easier to scrub.

What the quality trade-off actually looks like

Container swap: zero loss. Identical bitstream, new file header. The MD5 of the video track doesn't change.

Re-encode from H.264 → H.264 at the same bitrate: a faint generational softening, mostly invisible. We default to -crf 23 which matches YouTube's upload re-encode — effectively transparent on a first pass.

Re-encode from HEVC → H.264 at the same visual quality: file approximately 1.8–2.2× larger. Compression is lossy, but HEVC and H.264 lose detail in similar ways, so artefacts rarely stack visibly on a single generation.

Real numbers from a 30-second 4K HEVC clip (iPhone 15 Pro, 170 MB original):

• Remux to MP4 (HEVC-in-MP4): 170 MB, ~4 seconds, identical quality. Plays on iPhone/Mac/modern Android/Chrome/Edge.
• Re-encode to H.264 at CRF 23: 310 MB, ~45 seconds on an M1 Mac. Plays literally everywhere.
• Re-encode to H.264 at CRF 28 + 1080p: 58 MB, ~40 seconds. Fits under most upload caps, plays everywhere.

What a remux actually does, byte by byte

Both MOV and MP4 organise their contents as a tree of "boxes" (called "atoms" in MOV-speak, though they mean the same thing). Each box has a 4-character type code, a length, and a payload. The top-level boxes you'll see in almost every file:

• ftyp — file type and compatibility tags. This is the main thing a remux changes: we swap the "major brand" from qt (QuickTime) to isom or mp42 (ISO MP4), and update the compatible-brands list.
• moov — movie metadata. Track definitions, durations, timescale, codec parameters, sample tables that map time → byte offsets. Almost all of this carries across unchanged.
• mdat — the actual media data. The compressed video and audio samples, untouched. A remux literally copies the bytes from the input mdat to the output mdat. This is why it's fast — modern SSDs stream a 2 GB copy in seconds.

The tiny wrinkle: in QuickTime-style MOV, the moovbox often sits at the end of the file (so recording can start before the metadata is known). In web-friendly MP4, you want moov at the front — that's what enables progressive playback / streaming start before the full file downloads. Our tool does the "faststart" reshuffle as part of the remux, so the output plays immediately in a browser video tag. This is one of those small things the competing server tools get wrong surprisingly often.

Real-world workflows that hit this conversion

Five situations that account for most of our MOV → MP4 traffic:

A. iPhone clip → WhatsApp or email

You AirDrop a clip off your phone, get a .mov that won't attach. Remux to MP4, attach the new file, send. No quality change, takes about as long as the AirDrop did. If the clip is over the recipient's inbox cap, follow up with a 1080p H.264 re-encode — same content, one-fifth the size.

B. Screen recording → slide deck

QuickTime's built-in screen recorder saves MOV. PowerPoint happily embeds MP4 in most versions, but older Office on Windows rejects MOV. Remux first; if the slide still won't play on a colleague's machine, force H.264 because old Office codecs don't know HEVC.

C. Camera footage → YouTube

YouTube accepts MOV uploads in theory, but the service is built for MP4 — upload a MOV and it quietly gets converted on their end, which tends to be a lossy second generation. Convert to MP4 first (remux if possible, H.264 re-encode if your camera recorded in something exotic) and YouTube's transcoder has less work to do, so the master quality on your side is better.

D. Podcast video → editor

Guest sends you a MOV recorded in a browser tool like Riverside or SquadCast. These typically record in H.264 already, so remux to MP4 lands without a re-encode and your editor (Descript, Premiere, Resolve) ingests it cleanly. The rare exception is when the recorder uses VP9 in MOV — unusual, but it forces an H.264 re-encode to fit MP4.

E. Security / dashcam / body-cam footage

Lots of vertical-market cameras save MOV wrappers but the codecs inside are all over the map (H.264, H.265, M-JPEG, proprietary). Remux succeeds for the common codecs and re-encodes the rest. If you're handing footage to a lawyer or a court, also run the clip through our video converter to strip private metadata before sharing.

How our tool compares (honestly)

MOV → MP4 is a solved technical problem — every serious video tool can do it. Here's what you're actually choosing between:

Honest summary: if you're doing hundreds of MOV files a week with precise encoder control, install HandBrake. If you already know ffmpeg, use ffmpeg (we use it ourselves — via ffmpeg.wasm, in your browser). For everything in between — one or two files, or a batch you want done in the next 30 seconds with no upload and no install — our MOV to MP4 tool is the shorter path.

Privacy: why in-browser matters for video

Every mainstream web converter uploads your full file to their server, processes it, and serves the output back. For a PDF or a JPG, that's no big deal. For video, three things compound:

• Video files carry more signal. GPS-tagged clips of your home, the faces of people around you, audio of conversations, timestamps that correlate with your calendar. That's a lot to hand to a stranger's server for a container swap.
• Upload is slow. A 2 GB clip on a typical home connection is 10–20 minutes just to send. The actual conversion on our end is seconds. Browser-side means you start from time zero.
• Retention is a moving target. Every cloud converter promises "files are deleted after X hours" and every breach disclosure reminds us that promise is only as good as the last auditor's visit.

We run ffmpeg.wasm in your browser, which means the exact same ffmpeg binary that the command-line tool uses — compiled to WebAssembly, sandboxed in your tab. Your file is read from disk (with a local-file permission you grant), decoded in memory, remuxed or re-encoded there, and written back as a download. No network round-trip on the file itself.

Where our tool works well — and where it doesn't

Works well

• iPhone screen recordings and camera-roll MOVs (HEVC or H.264 input)
• Files where you want the fastest possible conversion — remux is near-instant
• Quick H.264 re-encodes of HEVC clips for Windows compatibility
• Privacy-sensitive footage you'd rather not upload
• Batches up to 10–20 medium-length clips per session

Doesn't work (well) yet

• Files over the free-tier cap — paid tiers lift this to multi-GB per file
• Frame-accurate trim/cut before conversion — we re-encode the whole file; for trim-first pipelines, HandBrake or an NLE is cleaner
• ProRes 4444 with alpha channel — MP4 can't carry alpha; we'll flatten it, but that might not be what you want
• Very long clips on low-end phones — in-browser encoding is CPU-bound, and a 2-hour 4K re-encode on an old Android might not finish before the tab crashes

Tips for the best result

• Leave the default on. We try remux first and auto-fall-back. Nine times out of ten, remux is what you want — it's lossless and takes seconds.
• If the output won't play, toggle "Force H.264" and re-convert. The HEVC compatibility story is the #1 "my MP4 won't open" cause. H.264 plays everywhere.
• For upload-cap situations, pair with a resolution drop. 4K → 1080p at H.264 CRF 23 is typically a 5–8× file-size cut with barely perceptible quality loss. Our video converter has the resolution picker.
• For audio-only, don't convert to MP4. If you only need the audio track, use MP4 to MP3 or the broader Video to MP3 tool — both extract audio without touching the video at all.
• For social-media-ready short clips, consider GIF. Under 6 seconds, with no sound, MP4 is probably overkill. MOV to GIF gets you a broadly-shareable loop.

Common questions

Is MOV the same as MP4?

Structurally, almost. MP4 is based on Apple's MOV spec, so the underlying box/atom structure is near-identical. The practical difference is which codecs each container is allowed to carry and how widely each is recognised. MP4 is universally recognised; MOV is mostly recognised everywhere except some Windows default apps and a few legacy CMS platforms.

Will I lose quality converting MOV to MP4?

If the conversion is a remux (container swap only) — no. The video bits are copied across unchanged. If it's a re-encode (because the input codec isn't MP4-legal, or because you chose to re-encode for compatibility/size) — yes, some loss, but at default settings it's visually transparent on a first generation.

Why is my iPhone MOV giant?

iPhone 4K/60 HEVC records at ~400 MB/min. That's a raw choice — trading storage for quality. The MOV container isn't causing the size; the bitrate and resolution are. A re-encode to 1080p/H.264 typically shrinks a 1 GB phone clip to 120–200 MB with no practically visible loss.

Why won't my MOV play on Windows?

Usually one of two things. Either the default Movies & TV app doesn't ship with an HEVC decoder (Microsoft moved HEVC to a paid store extension), or the specific MOV uses an older codec the default decoder doesn't understand. Re-encoding to H.264 MP4 fixes both.

Do my videos get uploaded to your server?

No. ffmpeg.wasm runs inside your browser tab, sandboxed. Your file is read locally, converted in memory, and written back as a download. The bytes never leave your machine. If we ever need to fall back to server-side for very large files, we'll tell you first and give you the choice.

Can I convert MP4 to MOV?

Yes — the reverse direction works the same way (it's almost always a remux, since MP4-legal codecs are usually MOV-legal too). Use our general video converter, pick MOV as the output.

Is this tool really free?

Yes. Unlimited conversions per day, no watermark, no sign-up. The free tier caps per-file size; paid tiers lift that cap for larger files. Quality and speed are identical across tiers — paying only changes the ceiling on file size.

Ready?

MOV to MP4 →. Drop a file, we figure out whether to remux or re-encode, you download the result. Free, in your browser, no sign-up.