mov and mp4 are often the same file

renaming mov to mp4: check the codec first

1. select the file in Finder and press ⌘I for Get Info.
2. open More Info and read the codecs. h.264 is the easy case.
3. rename the file, replacing mov after the dot with mp4, and confirm «Use .mp4».

nothing is re-encoded, so nothing is lost and it is instant regardless of the file's size. Apple documents this itself, which is worth knowing when the site you were reading before this one went straight to a converter.

so the short version, before the detail: rename it if it is h.264 and nothing downstream is fussy. if anything rejected the file, or there is more than one of them, skip to a real repack — and the easiest real repack is a drag, not a command.

the same «what does the built-in route actually do» question runs through the photo side of this too, with a similar surprise at the end: convert heic to jpg

the official version of the trick, including where to read the codec: convert a MOV file to MP4 on Mac

what the rename actually changes

less than it looks, and this is the part nobody says out loud. a container declares what it is in its first bytes — a brand. a QuickTime file says `qt`; a real mp4 says `mp42`. renaming the file changes the extension and what your Mac thinks the type is. it does not touch those bytes.

checked on a system wallpaper here: the original reports `ftypqt`, and after copying it to a .mp4 name the `file` command still answers «Apple QuickTime movie». players do not care — they read the tracks. strict parsers do: an upload form, an Android phone, an editor that validates before importing.

so if the rename worked, keep it. if the file was rejected somewhere after renaming, that rejection is about the brand, and the next section fixes it properly.

convert mov to mp4 in Terminal, without re-encoding

macOS ships avconvert, and it has a preset that copies the tracks across into a new container instead of re-encoding them. no download, no Homebrew, no editor.

1. avconvert -s clip.mov -o clip.mp4 -p PresetPassthrough — one file.
2. for a folder: for f in *.mov; do avconvert -s "$f" -o "${f%.mov}.mp4" -p PresetPassthrough; done
3. avconvert --help lists the other presets, which do re-encode and are there when you actually want that.

the numbers make the point better than the description. an 82 mb clip came out in two seconds, at the same size — that is a copy, not an encode — and the result reports `ftypmp42` with compatible brands `isom mp41 mp42`. it is an mp4 by the file's own account, not by its name.

it works for hevc too, which matters because iPhone video is often hevc and every page on this subject sends you to a video editor at that point. hevc is perfectly legal inside an mp4; there was never anything to re-encode.

two honest limits. ProRes cannot go into an mp4 at all, and avconvert says so rather than producing something broken. and it reads what the system reads — so mkv and webm are outside its reach entirely.

avconvert is not the only capable thing in macOS without a window — the speed test is the same story, and just as unknown: the speed test already on your Mac

the manual page, if you want the full preset list before running anything: man avconvert

why doesn't QuickTime export mp4?

because Apple says it does not. QuickTime Player's export writes QuickTime movies — its own documentation states plainly that it does not export mp4 — which is why so many people conclude the system cannot do it and go looking for an app. the capability was in the command line the whole time.

the Finder has a third route worth knowing: Control-click a video and choose Encode Selected Video Files. it re-encodes at 720p, 1080p or 4K with a «Greater Compatibility» tick for h.264, leaves the original alone, and takes a multiple selection. it is a genuine converter, and it writes .m4v rather than .mp4.

Apple's own statement about what QuickTime export produces: export QuickTime Player movies

and where all three built-in routes stop dead is the container macOS does not read at all: open an mkv or webm on a Mac

how hop converts mov to mp4

every route above asks you to know something before you start: which codec is inside, which command to type, which preset to pass, whether this file is one of the ones that will be refused. that is the actual cost of the free options — not money, and not quality, but the part where you have to be the one who knows.

hop asks for none of it. drag the file into the converter window, read the size it will come out at, press the button. same lossless repack underneath where a repack is possible, no Terminal, and the answer to «will this work» arrives before you commit rather than after.

the first row is not a courtesy. if a rename solves your problem, it solves your problem and there is nothing here worth installing an app for. the rest of the table is where the built-in route starts charging you in attention, and that is the part hop is actually for.

• the squeeze has a level of its own when you do want it smaller, and the size promised before converting is the size you get — hop tests a sample rather than guessing.
• reframing for a platform happens in the same pass, if that is where the clip is going.
• originals stay where they are; results land beside them as copies.
• images, audio and documents go through the same window, so this is not one more single-purpose app in the Dock.

the module in full — images, audio and documents go through the same window: file converter on the features page

when the mp4 is rejected anyway

it plays here and is rejected there

the brand again. a renamed file passes every player you own and fails the upload form, because the form reads the header rather than the picture. repack it with the passthrough command and the same content goes through.

why are iPhone videos .mov and not .mp4?

history rather than technology: QuickTime is Apple's own container and predates mp4, which was in fact derived from it. the tracks inside are the modern ones — h.264 or hevc — which is why the rename works at all, and why the repack takes two seconds.

hevc is also the reason your photographs arrive in a format half the web refuses, and that story explains this one: why your photos are heic

• the result has no sound. the audio track was something an mp4 will not carry, or the source had none to begin with — check that the original plays with sound first.
• it plays on your Mac and not on the machine you sent it to. resolution or codec profile, not the container: a 4K hevc file in an mp4 wrapper is still 4K hevc, and older hardware will not decode it.
• the file has an alpha channel from a screen recording or a render. mp4 does not keep transparency; ProRes 4444 in a mov does, and that is why it was a mov.
• it is a screen recording several hours long. converting it is the wrong move — cut it first, then convert what is left.
• you need it smaller as well as compatible. that is a different operation: passthrough copies, it does not compress.

screen recordings are also the quietest way a disk fills up, and they are rarely the first place people look: what «system data» is actually using

and if the destination is a social platform, the frame matters more than the container: compress video for reels, TikTok and shorts

frequently asked questions

is renaming mov to mp4 safe?

yes — nothing inside the file changes and you can rename it back. what it does not do is make the file an mp4: the container still declares itself as QuickTime, which players ignore and stricter software does not.

how do i convert mov to mp4 without re-encoding?

avconvert -s clip.mov -o clip.mp4 -p PresetPassthrough. it ships with macOS, copies the tracks rather than re-encoding them, and finished an 82 mb clip in two seconds here.

why does QuickTime not export mp4?

Apple's documentation states that QuickTime Player does not export mp4 — its export writes QuickTime movies. the mp4 capability lives in the command line instead, and in the Finder's Encode Selected Video Files, which writes .m4v.

does it work for hevc from an iPhone?

yes. hevc is legal inside an mp4, so the passthrough preset repacks it without touching the picture. the advice to open an editor for hevc is left over from a limitation that does not exist.

does converting mov to mp4 lose quality?

a rename and a passthrough repack lose nothing at all — no pixel is re-encoded. a real conversion, which is what a video editor or an export preset does, loses a little.

what is the fastest way for a whole folder?

a shell loop around the passthrough command, if you are comfortable with Terminal. a converter that takes the folder in one drop is the same operation with the sizes shown before it runs.

why won't my Mac open mkv files?

macOS ships no support for the container, and avconvert cannot read it either. that is a different job — repacking mkv into mp4 — and it needs something outside the system.

the tool behind this

done with convert and compress

other things people do

• a folder of heic, and something that wants jpgfile converter
• QuickTime will not open it. the video is fine.file converter
• the pdf is 40 mb and the form accepts 10file converter