Convert MOV to MP4 Free (Without Uploading It)
By Mark Fulton · 2026-08-25 · 11 min read
Before you convert anything, find out what is inside the file. MOV and MP4 are both containers, and a MOV recorded by an iPhone or a modern camera almost always holds H.264 or HEVC video with AAC audio, which is exactly what an MP4 holds. In that case there is nothing to convert: the video and audio streams can be lifted out of the QuickTime wrapper and dropped into an MP4 wrapper untouched. That is a rewrap, sometimes called a remux, it takes about a second on a file of any size, and not a single pixel changes. A real re-encode is only necessary when the streams themselves are the problem: ProRes, which MP4 has no sensible way to carry, uncompressed PCM audio, or HEVC that the machine on the other end cannot decode. Every upload-and-download converter charges you the same wait for both cases because on their side the work is the same. On your side it is not.
So the useful order is diagnose, then act. Below is how to tell which case you are in, what each symptom actually means, and the five routes to an MP4 depending on whether you are on a Mac, on Windows, on a phone, in a browser, or at a command line.
What is a MOV file really?
A .mov file is a QuickTime movie: a container Apple designed in the early 1990s to hold synchronised media tracks. It says nothing about how the video inside was compressed. The same extension can wrap H.264, HEVC, ProRes, Motion JPEG, Apple Animation, or uncompressed frames, with AAC, PCM, ALAC or something else for audio.
MP4 is the same kind of thing, and the family resemblance is not a coincidence. MDN's guide to media container formats states it plainly: "The MP4 file format is derived from the ISO base media file format, which is directly derived from the QuickTime file format developed by Apple." MP4 is QuickTime's standardised descendant. The box structure, the atom names, the way tracks and sample tables are laid out, all of it is recognisably the same design.
That shared ancestry is why the rewrap works so cleanly, and it is also why converting MOV to MP4 feels like it should be trivial. It usually is. What it is not is a rename. Changing the extension from .mov to .mp4 leaves QuickTime-specific structures in the file that some players tolerate and others reject, and it gives you no signal about whether the codecs inside are legal MP4 payloads. Some apps will open it. An upload form validating the file properly will not. Do the rewrap; do not do the rename.
Do you need a conversion or just a rewrap?
Work backwards from the symptom. What is going wrong tells you a lot about what is inside.
| The symptom | What is usually inside | What actually fixes it |
|---|---|---|
| Plays fine on your Mac, black screen or "unsupported" elsewhere | HEVC (H.265) video, often 4K or HDR | Re-encode the video to H.264. A rewrap keeps HEVC and changes nothing |
| Upload form rejects it, or a web page refuses to play it | H.264 in a QuickTime wrapper | Rewrap. The codec was never the problem, the container was |
| Editor imports it but scrubbing crawls, or it refuses the file | ProRes, or a high frame rate HEVC capture | Re-encode to H.264. ProRes cannot travel in an MP4 |
| The file is enormous for its length (gigabytes per minute) | ProRes, Animation, or uncompressed | Re-encode. This is the one case where the size drops dramatically |
| Video plays, audio is silent or missing | PCM, ALAC or a track MP4 will not carry | Rewrap the video, re-encode only the audio to AAC |
| Everything works but you want one consistent format | H.264 and AAC already | Rewrap. Re-encoding here costs quality for nothing |
Two rows are worth dwelling on because they are the ones people get backwards.
Enormous files are almost never an H.264 problem. If your MOV is 2 GB for ninety seconds, it is not compressed video in any meaningful sense. Apple's own documentation for ProRes recording on iPhone gives you the scale of it indirectly: on a 128 GB iPhone, ProRes capture is limited to 1080p at 30 or 25 frames per second, and only models with 256 GB or more can record ProRes at 4K. Apple imposes that limit because of what the format costs per second. If that is your file, a re-encode is genuinely what you want, and the size will fall by an order of magnitude.
HEVC files do not get fixed by a rewrap. Putting an HEVC stream into an MP4 container produces a perfectly valid MP4 that still will not decode on a machine without HEVC support. If the complaint is "it won't play on my colleague's laptop", the container is innocent and the codec is the culprit. That decision has its own page: H.264 vs H.265 covers where HEVC quietly fails and why "plays everywhere" usually beats "smaller" for a file you are handing to someone else.
How to see what is inside without installing anything
On a Mac, open the file in QuickTime Player and press Command-I for the movie inspector. It names the format directly, something like "H.264, 1920 x 1080" or "Apple ProRes 422 HQ".
On Windows, right-click the file, choose Properties, and open the Details tab. Look for the video and audio compression fields.
If you have FFmpeg installed, ffprobe yourfile.mov prints every stream with its codec, profile, resolution, frame rate and bitrate in about a second. It is the fastest answer of the three.
Why won't a MOV open on Windows or in your editor?
There are three separate failures hiding behind "MOV doesn't work on Windows", and they need different fixes.
The container is unfamiliar to the app. Plenty of older software, upload validators and embedded players accept MP4 and nothing else. Nothing is wrong with your video. A rewrap solves this outright.
The codec is HEVC and the system cannot decode it. Windows does not ship HEVC decoding for every configuration, which is why the same file opens on a Mac and shows a black frame on a PC. MDN's web video codec guide documents how conditional HEVC support is: browser support depends on version floors, operating system builds, and in Edge's case on the HEVC video extensions being installed from the Microsoft Store. AVC has none of those conditions attached. If your recipient's machine is the constraint, encode H.264.
The codec is ProRes and the app is not an editor. ProRes is an intermediate format built for editing, not for delivery. Consumer players and browsers have no reason to support it. Convert before you send.
If your iPhone is producing HEVC and you would rather it did not, Apple lets you change it at the source. In Settings, Camera, Formats, the choice is between High Efficiency and Most Compatible, and Apple's guide to using HEIF or HEVC media on Apple devices confirms that choosing Most Compatible makes all new photos and videos use JPEG or H.264 instead. It costs you storage. It saves you this conversation every time you send a clip to someone.
How do you convert without uploading it?
Five routes, and which one is right depends less on your taste than on what the diagnosis said.
| Route | Rewrap or re-encode | Best for |
|---|---|---|
| VidClip in your browser | Re-encode to H.264 and AAC | Any machine, any operating system, no install, file stays local |
| FFmpeg at the command line | Either, your choice | The genuinely lossless rewrap, and batches |
| QuickTime Player, Export As | Re-encode | Mac users who already have it open |
| Photos or Clipchamp on Windows | Re-encode | A one-off on a PC with nothing installed |
| iPhone or iPad | Re-encode, via an app | Files already on the phone |
In the browser. VidClip's MP4 converter runs FFmpeg compiled to WebAssembly inside the page. Your file is read from disk into the tab's memory, processed on your own CPU, and written back to your disk. There is no upload, no queue, and no copy of your footage on anybody's server. Be straight about what it does: it re-encodes, at CRF 21 with H.264 video and 128 kbps AAC audio, with the index moved to the front so the result starts playing before it finishes downloading. That is a quality-preserving setting for camera and phone footage rather than a bit-for-bit copy. Free exports carry a small corner watermark and cap the input at 200 MB; Pro lifts both.
At the command line, if you want the true no-loss path:
ffmpeg -i input.mov -c copy -movflags +faststart output.mp4
That is the whole rewrap. The FFmpeg documentation describes what -c copy does: it selects the copy encoder, "that is copying one input elementary stream's packets without decoding, filtering, or encoding them," which means "it is very fast and there is no quality loss." It is explicitly useful for "changing the elementary stream count, container format, or modifying container-level metadata," which is precisely our job here.
If it fails, the error will tell you which stream MP4 refused. Usually it is the audio, and this handles it:
ffmpeg -i input.mov -c:v copy -c:a aac -b:a 192k -movflags +faststart output.mp4
Video untouched, audio re-encoded, done in seconds.
For a real re-encode, from ProRes or from HEVC that needs to become H.264:
ffmpeg -i input.mov -c:v libx264 -crf 20 -preset medium -c:a aac -b:a 192k -movflags +faststart output.mp4
On a Mac, QuickTime Player's File, Export As menu will write an MP4-family file, and iMovie will do it too. Both re-encode. They are convenient rather than lossless.
On Windows, the Photos app and Clipchamp will both export MP4 without an install. Both re-encode, and Clipchamp's export options are worth reading before you commit.
On an iPhone, there is no built-in rewrap. The realistic options are to change the capture format to Most Compatible so the problem stops recurring, or to move the file to a computer and handle it there.
What settings preserve the quality you have?
If you are rewrapping, this section does not apply. Nothing is being re-encoded, so there is nothing to preserve. That is the entire point of checking first.
If you are re-encoding, four settings carry the weight:
- CRF, not a bitrate target. Constant rate factor lets the encoder spend bits where the picture needs them. Somewhere between 18 and 23 is the useful range for 1080p; 18 is visually indistinguishable from a good source, 23 is a sensible default, and every step up is roughly a 10 percent size change in either direction.
- Leave the resolution and frame rate alone. Converting a container is not the moment to downscale. If you also need the file smaller, do that as a deliberate second decision.
- Audio at 192 kbps AAC if the source audio is decent, 128 kbps if it is speech. Re-encoding already-compressed audio costs you a generation of quality, which is another argument for copying the audio stream when MP4 will take it.
-movflags +faststart. This moves the index to the front of the file. Without it, a browser has to download the whole thing before it can start playing. It costs nothing and takes one extra pass over the file.
One more thing worth knowing if you are trimming as well as converting: a stream-copy cut cannot land on an arbitrary frame, because it can only start at a keyframe. Why lossless trimming snaps to keyframes explains what that means in practice and when it is worth accepting a re-encode to get a frame-accurate cut instead.
Frequently asked questions
Is MOV the same as MP4?
Not the same, but closely related. Both are containers, and MP4's specification descends from the QuickTime file format. In practice a MOV from a phone or a camera usually holds the same H.264 and AAC streams an MP4 would hold, which is why moving between them is often a rewrap rather than a conversion. The differences that matter are which codecs each container is allowed to carry and which apps agree to open which extension.
Does converting MOV to MP4 lose quality?
Only if it re-encodes. A rewrap copies the compressed streams across untouched, so the output is bit-for-bit identical video and audio in a different wrapper, and there is no loss at all. A re-encode decodes and re-compresses, which always costs something, though at CRF 18 to 21 from a decent source the cost is not visible at normal viewing distance. The way to avoid the loss is to check what is inside the container first and rewrap when you can.
Why is my iPhone MOV so large?
Two likely reasons. If you are recording 4K at 60 frames per second, the file is large because there is a lot of video in it, and that is normal. If it is startlingly large, in gigabytes per minute, you are probably recording ProRes, which Apple offers on Pro models as an editing format and restricts by device storage precisely because of its appetite. ProRes is the one case where converting to H.264 makes a dramatic difference to file size, and also the one case where you should keep the original if the footage is going into an edit.
Can I convert a MOV on Windows for free?
Yes, several ways, none of which require a purchase. The Photos app and Clipchamp both ship with Windows and both export MP4. FFmpeg is free and gives you the lossless rewrap that the graphical apps do not offer. Or open the converter in this browser tab, which needs no install at all and never sends the file anywhere. What you should avoid is renaming the extension and hoping, because that produces a file that works in some players and fails validation in others.
Got a MOV that needs to be an MP4? Convert it in the browser. The file is read from your disk into the page and processed on your own CPU, so nothing uploads, nothing queues, and no copy of your footage exists anywhere but your machine. The rest of the toolkit, trim, compress, resize and the others, is on the tools page and works the same way.