MOV to MP4 Converter

The video is thirty-one seconds of your daughter taking her first unassisted steps across a kitchen floor. Filmed on an iPhone in 4K, because that's what the phone does when you press the red button. Texted to her grandfather, it arrives as a gray thumbnail that will not play — his three-year-old Android wants nothing to do with a file ending in .mov. Emailed to an aunt, same story. Dropped into the Windows video editor your cousin swears by, the import silently fails.

Apple records video as QuickTime Movie — .mov, the house format since the early nineties. Apple's own ecosystem plays it flawlessly, which creates a quiet illusion that it's universal. It isn't. The moment an iPhone video crosses to Android, Windows, older smart TVs, or a long list of web tools, that extension becomes a wall — and the wall gets blamed on the phone, the app, or the recipient's device, when the actual problem is one format's assumption meeting another's licensing.

The fix is smaller than the frustration. This converter takes .mov files and hands back .mp4 files that play essentially everywhere — and because MOV and MP4 are close cousins at the structural level, the fast path is a remux: the video and audio streams are copied out of one container and into the other without being decoded, recompressed, or touched in any way that costs quality. An hour of 4K footage repackages in seconds. If the file inside is HEVC and the destination is old, the tool tells you and offers the one conversion that actually requires computing.

1. 1

   Bring in the .mov

   Drag the file onto the page or tap to browse — AirDrop it to a Mac first, or pull it straight from the phone's storage. Nothing is transmitted; the file opens in your browser's media stack.

2. 2

   Check the stream summary

   The report identifies the video codec (H.264 or HEVC), resolution, frame rate, audio format, and flags timing quirks like slow-motion ramps before anything happens.

3. 3

   Accept the remux default

   H.264 sources convert by stream copy — identical bits, new container. HEVC sources show a choice: keep the codec with a compatibility note, or re-encode to H.264 for older playback targets.

4. 4

   Set the fallback options only if you need them

   For re-encodes you choose quality level and, optionally, a resolution step-down — 4K HEVC to 1080p H.264 is the classic grandfather-compatible recipe.

5. 5

   Download the MP4

   Remuxes finish at storage speed; re-encodes run at encoder speed with a progress meter that means something. The output lands in faststart layout so streaming and sharing platforms preview it instantly.

Here's the twist that makes this conversion unusually cheap: MP4 is, structurally, a QuickTime descendant. When the Moving Picture Experts Group standardized MPEG-4 in the late nineties, it adopted the QuickTime File Format's architecture as the basis for what became the ISO Base Media File Format — the standard MP4 is built on. Both formats organize data as a tree of boxes (Apple called them atoms): an ftyp brand marker, a moov box indexing every sample, and an mdat box holding the actual media.

So when your iPhone writes an H.264 .mov and this tool writes an H.264 .mp4, the encoded video stream in both files is the same stream, and the surrounding scaffolding is near-identical in shape. Remuxing is a matter of re-labeling brands and re-stamping the sample tables — the compressed frames pass through like passengers changing to a differently painted train. That's why a two-gigabyte iPhone video converts in about ten seconds on an SSD rather than in twenty minutes of encoding.

The differences that remain are matters of diet and policy. QuickTime's format is permissive — it will carry ProRes, animation codecs, timecode tracks, and whatever else Apple's pro tools invent. MP4's ISO standard is narrower and far more widely licensed: H.264 and AAC form the baseline every consumer device agrees to decode, with HEVC as the semi-optional second tier. For family footage and social clips, the narrow diet is the whole point — it's the format the world agreed on.

If you arrived here from the media-library side of the house, the same box-structure kinship explains why the MKV to MP4 Converter runs the same kind of copy path from Matroska — containers are folders, and this family of tools mostly moves files between folders without rewriting them.

Since iOS 11 in 2017, iPhones record in HEVC — H.265 — by default, because it stores the same visual quality in roughly half the space of H.264. That decision was correct for phone storage and mildly catastrophic for compatibility: an iPhone-era HEVC file plays beautifully on recent Apple gear, recent flagship Android, and modern browsers, then hits a wall at older smart TVs, pre-2018 laptops, budget devices, and an embarrassing number of web upload pipelines.

Switch the camera setting to "Most Compatible" and the phone records H.264 instead — instantly more shareable, roughly double the file size. A minute of 4K60 HEVC runs around 400 MB on current iPhones; the same minute in H.264 approaches 800 MB. Most people don't know the setting exists, which is why millions of families are quietly accumulating HEVC libraries and discovering the wall one grandfather at a time.

Audio is the easy half: iPhones record AAC stereo at 48 kHz, and AAC is the single most universally supported audio codec in existence. Whatever this tool does to your video stream, the audio almost always rides along untouched, bit-for-bit.

A remux, in iPhone terms, works like this. The tool reads the .mov's box tree, extracts each compressed HEVC or H.264 access unit and each AAC audio frame, and writes them into a fresh MP4 with its own moov index up front. No frame is ever decoded to pixels; no sample is re-compressed. Run a checksum on the video stream before and after and you get the same answer, because the stream is the same data.

For HEVC files the tool writes the hvc1 brand rather than hev1 — the variant where the codec's header parameters live in the sample entry instead of streaming in-band. It's a one-line technicality with real consequences: Apple devices have historically accepted only hvc1, so files branded the other way bounce off iPhones and iPads despite containing perfectly valid HEVC. A disturbing fraction of "this MP4 won't play" reports trace back to exactly that branding byte.

The faststart layout deserves a mention because it changes how the file feels. A QuickTime file keeps its moov index wherever it happens to sit; an MP4 meant for streaming should have it at the front so a player can start buffering immediately without downloading the whole file first. The converter writes the index up front by default, which is why the MP4s it produces start playing over a network connection with no dead air.

When the destination is old — a 2015 television, a hand-me-down laptop, a projector at a school reunion — HEVC will not play no matter what container carries it. Then the honest move is re-encoding to H.264: every frame decoded, compressed again in the older codec, and wrapped in the universal MP4 diet. This is real computation, and it takes real time: roughly two to five minutes of encoding per minute of 4K video on a typical laptop, less for 1080p.

The quality cost of that step is modest when done at a good setting — one generation of lossy re-compression at a quality level high enough that most people cannot find the difference on phone footage, on phone screens. "Most people, on phone footage" is doing honest work in that sentence: if you're delivering to a broadcast suite or archiving for decades, keep the HEVC original and re-encode only the sharing copy.

The recipe that solves ninety percent of family sharing problems: re-encode HEVC to H.264, keep the original resolution and frame rate, leave audio untouched. The result is a file with maybe 1.8× the size of the HEVC source that plays on effectively anything with a screen — the compatibility your grandfather's Android wanted all along, at a quality level nobody at the reunion will interrogate.

The remux line is the default and the right call when the recipient's hardware is from this decade: six seconds, zero loss, same 4K detail. The re-encode line is the insurance policy: under a quarter of the size — 118 MB fits comfortably in an email-adjacent upload or a messaging app that hates attachments — and compatible with hardware old enough to predate the wedding it filmed.

Notice what didn't appear anywhere: a quality slider mystery, a watermark, a queue. The numbers above come from a 2020-era laptop with an SSD; your results scale with your storage speed for remuxes and your CPU for re-encodes, but the shape of the trade stays the same. Copy when you can, encode when you must, and know which one you're doing.

• Slow-motion timing. An iPhone slo-mo clip is one variable-frame-rate stream — 30 fps with 240 fps bursts — plus a metadata track telling Photos when to slow down. A plain remux preserves every frame; whether the receiving player reproduces the automatic speed ramps depends on it honoring that timing track. When it matters, re-encoding at a constant rate bakes the effect in.
• Cinematic-mode focus. Apple's depth-aware focus transitions live in auxiliary metadata; the MP4 keeps the rendered frames but can drop the editability, so the focus decisions you made on the phone become permanent rather than adjustable.
• Dolby Vision HDR. Current iPhones tag HDR10-compatible Dolby Vision metadata onto the HEVC stream. It rides the remux fine, and modern TVs glow accordingly — but an old destination playing that same file will look washed out or dark, because tone mapping is the destination's job, not the container's.
• ProRes sources. Camera or Final Cut .mov files in ProRes are professional intermediates — a one-hour 1080p ProRes 422 HQ master weighs roughly 90 GB. They must re-encode to become playable MP4s, and that conversion is an evening-length job, not a seconds-length one. Keep the ProRes original; ship the MP4.
• Rotated footage from third-party apps. Some camera apps encode portrait video as landscape with a rotation flag. The remux carries the flag; a rare player ignores it and shows sideways footage. Re-encoding physically rotates the pixels if you ever meet one of those players.
• Live Photos exported as video. The three-second Live Photo video component converts like any other clip; just expect a file that's mostly before-and-after breathing room around the actual moment.

• Families sharing moments across the Apple/Android divide, which is to say most families — grandparents on hand-me-down hardware are the single largest constituency of this converter.
• Real-estate agents whose MLS and listing portals demand MP4 uploads for walkthrough tours filmed on phones.
• Social media managers normalizing a mixed camera roll into one deliverable format before scheduling.
• Journalists and field researchers moving phone footage into newsroom or lab tools that only ingest MP4.
• Wedding and event videographers sending review copies to clients — while ProRes masters stay on their own disks.
• Teachers collecting student video projects who need one format that opens on every Chromebook and projector in the building.

It slots into a small pipeline when it needs to. Trim the dead air before a clip goes public with the Audio Silence Remover, pull a three-second loop out for a chat message with the Video to GIF Converter, or hand voice memos — the other thing iPhones produce in an Apple format — to the M4A to MP3 Converter. One browser tab, the whole phone-to-the-rest-of-the-world pipeline.

Apple's format earned its reputation; it carried professional video for three decades and still does. But a format's virtue in the edit bay and its virtue in a group message are different virtues. The workflow worth keeping is boring and reliable: Apple originals in Apple's container, MP4 copies for everyone else, originals never deleted.

Every so often, a video goes viral precisely because somebody uploaded a private family clip to a converter service and it ended up somewhere it should never have been. Your child's first steps is not the kind of content you want on a third-party server under a retention policy you've never read. This tool's architecture makes the question moot: the file opens in your browser, converts on your silicon, and downloads from your own disk. There is no upload, because there is no server to upload to.

The page works offline once loaded, which has a practical edge beyond paranoia — airplane Wi-Fi, a cabin with a hotspot that bills by the megabyte, a school device on a locked-down network. A converter that needs the cloud needs all of those things to cooperate. One that runs locally needs only the machine in front of you, which was already holding the video.

When the whole camera roll needs processing, the bench is stocked: the MKV to MP4 Converter for the media-library side of the family, the Video to GIF Converter for turning moments into looping replies, and the M4A to MP3 Converter for the voice memos. Every one of them runs the same way this page does — in the browser, on your machine, with your files staying yours.