Convert MOV to MP4 on Windows

Screen recordings, iPhone AirDrops, and camera exports often arrive as MOV. Upload forms, older Windows apps, and many web portals expect MP4 with H.264 instead. You notice when SharePoint rejects the attachment, a client portal shows a format error, or a ticket system silently drops the file. The same friction shows up in Teams chat, LMS uploads, and ad platform review tools that list accepted formats in small print. Converting locally avoids re-recording, keeps unreleased demos off third-party upload sites, and lets you trim or resize in the same pass when the portal also caps megabytes.

MOV vs MP4

MOV and MP4 are both containers. They can hold the same H.264 or HEVC streams. What changes is compatibility with the tool on the other end. Think of the container as the envelope: the video inside can be identical while one recipient accepts the package and another does not.

	MOV	MP4
Common source	iPhone, screen recorders, some editors	Web uploads, Android, most Windows apps
Built-in Windows apps	Opens in some apps, not all	Widely accepted
Upload forms	Often rejected	Usually accepted
Best first step	Clipchamp export at 1080p	Same workflow, MP4 output

In practice, MOV appears in QA bug videos, marketing screen captures, and phone clips shared with a Windows team. MP4 is what you send for Slack, Teams, CMS uploads, and client review links. If the clip already plays and only the extension blocks upload, export is enough. If the portal also caps megabytes, trim first and consider lower resolution or tighter quality.

Workflow	Typical MOV source	Why MP4 helps
QA bug repro	OBS, phone screen record	Ticket forms accept MP4 more often
Marketing demo	iPhone, Camtasia export	CMS and ad tools expect H.264 MP4
Client review	Zoom local recording	OneDrive and SharePoint previews reliably

When audio matters (voiceover in a demo), confirm the export keeps AAC audio. A silent MP4 after conversion usually means the source used a codec Clipchamp or FFmpeg did not map; re-encode with explicit -c:a aac rather than -c copy.

See the video compression guide when file size is the real blocker.

Export in Clipchamp

Clipchamp (built into Windows 11) handles one or two clips when you do not need batch queues or exact megabyte targets.

1. Open the MOV in Clipchamp.
2. Trim the timeline to remove dead air at the start and end.
3. Export at 1080p (or 720p for email and chat attachments).

That gives you H.264 in an MP4-friendly file. Screen recordings with small UI text benefit from 1080p. Talking-head clips that play in a small embed often look fine at 720p with much smaller files.

Situation	Export choice
One clip for a ticket	720p after trim
Client review in OneDrive	1080p
Portal with a hard MB cap	Trim first, then compress further

Clipchamp does not batch twenty files or set a megabyte target. When export one-by-one gets old, use FFmpeg or GetCompress.

For screen recordings with small UI text, export at 1080p first and only drop to 720p if the upload still fails. Trimming ten seconds of idle cursor at the start often saves more bytes than dropping resolution. Save exports to a new folder so you keep the original MOV if a second portal asks for different settings.

Convert with FFmpeg

FFmpeg in PowerShell gives codec control, batch loops, and web-friendly output flags. Install with winget:

winget install --id Gyan.FFmpeg -e

Standard re-encode for sharing:

ffmpeg -i input.mov -c:v libx264 -crf 22 -preset medium `
  -c:a aac -b:a 128k -movflags +faststart output.mp4

Flag	Plain meaning
-crf 22	Quality (lower = better, bigger; try 20 to 26)
-preset medium	Speed vs compression tradeoff
-movflags +faststart	Better for web playback start

Batch every MOV in a folder:

mkdir mp4-out
Get-ChildItem *.mov | ForEach-Object {
  ffmpeg -i $_.Name -c:v libx264 -crf 22 -preset medium `
    -c:a aac -b:a 128k -movflags +faststart `
    "mp4-out\$($_.BaseName).mp4"
}

If the source is already H.264 inside MOV, try remux first:

ffmpeg -i input.mov -c copy output.mp4

When remux fails, use the libx264 command above. For MKV sources, see MKV to MP4 on Windows .

Symptom after remux	Likely cause	Fix
Video plays, no audio	Audio codec not MP4-compatible	Re-encode audio with -c:a aac
Upload still rejects file	Wrong profile or missing faststart	Add -movflags +faststart, try H.264
File huge but short clip	High bitrate source	Lower -crf or scale to 720p

VLC can transcode too, but export settings are easy to misconfigure if you rarely use it. Stick to one FFmpeg recipe per team and document the CRF value in your wiki so QA and marketing use the same output.

Using GetCompress

GetCompress fits recurring convert MOV to MP4 on Windows work when Clipchamp export per file is too slow or when an upload form enforces a megabyte cap.

Drop MOV screen recordings, phone clips, or a whole folder into the app. Choose MP4 output, set resolution and quality, or use target file size when the portal states a limit. Trim in the preview before export if the recording includes idle time at the start.

Useful workflow pieces in GetCompress:

• Batch queue: process an entire export folder from a capture session without opening each file in Clipchamp.
• Presets: save “1080p client review” or “720p ticket video” and reuse next week.
• Preview and trim: confirm UI text stays readable before sending a bug repro.
• Folder monitoring: watch an exports folder and auto-convert new MOV files when your team drops recordings there regularly.
• Local processing: keep unreleased product demos and NDA footage on your machine instead of uploading to online converters.
• Clipboard flow: paste a file from the clipboard when you copied it from another app and want a quick MP4 without hunting for the source path.
• Target file size: when SharePoint or a client portal states a megabyte limit, hit the cap without guessing CRF values in PowerShell.

After conversion, if the MP4 is still too large, adjust quality or resolution in the same window rather than starting over in PowerShell. Save a preset when your team ships the same screen recording format every sprint: same resolution, same trim habit, same upload destination.