Convert MOV to AVI on Windows

MOV files from iPhones, Mac colleagues, and screen recorders sometimes must become AVI for legacy Windows software, lab systems, or upload validators that never moved to MP4. Clipchamp exports MP4, not AVI, so FFmpeg is the reliable conversion path. Converting locally avoids re-recording and keeps sensitive clips off third-party upload sites.

MOV vs AVI

MOV is common on Apple hardware. AVI persists in older enterprise tools, industrial video capture, and training platforms built before HTML5 video.

	MOV	AVI
Common source	iPhone AirDrop, QuickTime, Final Cut	Legacy Windows apps, old archives
Modern upload portals	Usually accepted via MP4	Often legacy-only
Codec inside	H.264, HEVC	H.264, MJPEG, or older
Best first step	Re-encode to required AVI codec	Matches validator

Confirm the exact codec the destination requires before batch converting. Some tools want MJPEG AVI; others accept H.264 inside AVI. When modern formats work, prefer MOV to MP4 on Windows instead.

In daily workflows, MOV arrives from iPhone AirDrop, Zoom local recordings saved on a Mac, and screen captures shared through cloud sync. AVI is what the receiving app documentation still lists even though the rest of the organization moved to MP4 years ago. Ask whether the validator checks extension only or probes the codec inside; that answer saves hours of wrong batch settings.

See the video compression guide when the legacy portal also caps megabytes.

Export in Clipchamp

Clipchamp (built into Windows 11) cannot export AVI. Use it to preview and trim MOV before FFmpeg conversion.

1. Open the MOV in Clipchamp when import succeeds.
2. Trim the timeline to the segment the legacy tool needs.
3. Export MP4 temporarily if you want a trimmed intermediate, then convert to AVI with FFmpeg.

Skipping Clipchamp and trimming with FFmpeg -ss / -to flags is fine when you know the timecodes.

Situation	Approach
Visual trim needed	Clipchamp trim, then FFmpeg
Known timecodes	FFmpeg trim + convert in one step
Modern recipient	Use MP4, not AVI

Treat Clipchamp as a trim helper, not the final AVI exporter.

When Clipchamp cannot import the MOV at all, open it on a Mac once for trim export, or trim with FFmpeg timecodes. Most H.264 MOV files from recent iPhones import cleanly; older HEVC clips may need a full re-encode path through HEVC to H.264 on Windows before AVI conversion if the legacy tool rejects HEVC inside any container.

Convert with FFmpeg

FFmpeg in PowerShell handles MOV to AVI. Install with winget:

winget install --id Gyan.FFmpeg -e

H.264 inside AVI:

ffmpeg -i input.mov -c:v libx264 -crf 22 -preset medium `
  -c:a libmp3lame -b:a 192k output.avi

Legacy MJPEG AVI:

ffmpeg -i input.mov -c:v mjpeg -q:v 5 -c:a pcm_s16le output.avi

Batch every MOV in a folder:

mkdir avi-out
Get-ChildItem *.mov | ForEach-Object {
  ffmpeg -i $_.Name -c:v libx264 -crf 22 -preset medium `
    -c:a libmp3lame -b:a 192k "avi-out\$($_.BaseName).avi"
}

Symptom	Likely cause	Fix
Legacy app rejects file	Wrong AVI codec	Try MJPEG recipe
Huge AVI	Uncompressed PCM audio	Use MP3 audio
Slow encode	libx264 preset	Use -preset veryfast for tests

Test one output in the target application before batching the folder.

Document the recipe that worked in your team wiki: H.264 AVI with MP3 audio at -crf 22 is a common starting point. If the tool accepts only MJPEG, expect much larger files and plan disk space before migrating a whole archive drive.

Using GetCompress

GetCompress fits recurring convert MOV to AVI on Windows work when Mac-origin MOV clips must land in a legacy AVI pipeline every week.

Drop MOV files or a folder into the app. Choose AVI output where supported, set resolution and quality, and trim in the preview before export when the validator only needs part of the recording.

Useful workflow pieces in GetCompress:

• Batch queue: convert an AirDrop folder without writing PowerShell loops.
• Presets: save codec settings after you find a combination the legacy tool accepts.
• Preview and trim: export only the steps the lab system needs.
• Folder monitoring: watch a sync folder and auto-convert new MOV files from Mac teammates.
• Local processing: keep NDA footage on your machine instead of uploading to online converters.
• Target file size: shrink AVI outputs when the legacy portal caps megabytes.

Verify one converted AVI in the destination software, then run the batch. Adjust quality in the same window if files exceed size limits.