Convert Mac screen recording to MP4
macOS Screen Recording (CMD+Shift+5) and QuickTime Player's Record Screen both save as .mov because Apple's ecosystem is QuickTime-native. Wave rewrites the container to MP4 without re-encoding a single frame - so the recording plays on Windows, Discord, and every upload pipeline that refused it.
What actually changes
CMD+Shift+5 opens Screenshot.app (added in macOS Mojave, 2018), which handles both stills and screen recordings. Recording saves to Desktop by default as a .mov file. Video is H.264 for compatibility (Apple made this choice deliberately - HEVC would have produced smaller files but broken sharing to Windows and third-party services); audio is AAC when the microphone or an audio input is selected in the options menu. Both codecs are natively MP4-compatible, so converting is a container swap.
QuickTime Player's Record Screen (File → New Screen Recording) predates Screenshot.app and produces the same file format - H.264 video, optional AAC audio, .mov container. The two paths are interchangeable; the file layout is identical. iMovie exports of screen recordings, Final Cut deliveries of screencast timelines, and Motion renders all default to .mov as well.
The container rewrite Wave performs is bit-for-bit safe. Every video frame and audio sample reaches the output unchanged. Wave rewrites the identifying label (from QuickTime to MP4), moves the moov atom - the file's index of where each frame lives - to the front for fast-start playback, and copies the video and audio data through untouched. On a modern Mac, a 30-minute screen recording converts in about 3 seconds because Wave is only rewriting header bytes; the multi-gigabyte sample data isn't re-processed. This is a "remux" - the mechanics of remuxing vs. re-encoding are covered in Remux vs re-encode.
The delivery-side reason Mac users convert to MP4 is asymmetric ecosystem coverage. Sending a .mov to a Windows recipient often fails silently (Windows Media Player and Films & TV both refuse .mov), and the same behaviour shows up in Discord's embedded player, LinkedIn video uploads, WhatsApp Web, some Slack channels, and most CMS attachment pipelines. Converting to MP4 in the browser fixes all of those in seconds without needing to re-record, re-export from Screenshot.app, or ask the recipient to install VLC.
Three steps.
-
01
Step 1
Locate your .mov recording (Desktop by default from CMD+Shift+5, wherever you saved it from QuickTime Player).
-
02
Step 2
Drop it onto Wave. Wave confirms Fast copy - no re-encoding needed.
-
03
Step 3
Convert and save the MP4. The container rewrite takes a few seconds regardless of recording length.
Answers, specifically.
Why does macOS save screen recordings as .mov?
macOS uses QuickTime's container as its native default. Every Apple recording, capture, or export defaults to .mov for consistency inside the ecosystem. The MP4 conversion exists because the rest of the world - Windows, Discord, most upload pipelines - still expects MP4 as the lingua franca.
Can I set macOS to record directly to MP4?
Not through CMD+Shift+5 or QuickTime Player. Third-party recorders (OBS Studio, Loom desktop, Snagit) let you choose MP4 up front. For Apple's built-in tools, .mov is the only output; the fastest path is to record as usual and convert with Wave.
Will the audio survive the conversion?
Yes. AAC-in-MOV becomes AAC-in-MP4 with no re-encoding. Every audio sample reaches the output unchanged.
What if I recorded with the Selection option, not Entire Screen?
The .mov is the same format regardless of capture area. Wave converts it identically. The recorded region is baked into the video (Screenshot.app crops during recording), so no metadata work is needed.
Chunked recordings from long sessions - anything special?
Screenshot.app doesn't chunk. QuickTime Player doesn't chunk. A single continuous recording produces a single .mov file, however long. If you paused and restarted (which creates a new file), each file converts separately.
Can I combine several recordings into one MP4?
Not in the current build - a dedicated merge tool is on the Wave roadmap. Today, ffmpeg from the command line does it in one pass: `ffmpeg -f concat -safe 0 -i files.txt -c copy output.mp4` where files.txt lists each .mov on its own line prefixed with `file `.
The recording is 2 GB - will it convert?
Yes. Wave handles up to 8 GB per file. The container rewrite is streamed - Wave doesn't need to load the whole file into RAM.