Convert MOV to AVI on Mac

MOV screen recordings, iPhone clips, and Final Cut exports sometimes must become AVI for legacy Windows software, old LMS players, or enterprise tools that never updated their accepted format list. QuickTime Player does not export AVI, so FFmpeg is the usual path on Mac. Converting locally keeps unreleased demos off upload sites and lets you trim before producing a compatible file.

MOV vs AVI

MOV is Apple’s primary container for QuickTime and many Mac editors. AVI is an older Windows container that still appears in industrial capture tools, vintage editing kits, and strict corporate upload validators.

	MOV	AVI
Common source	iPhone, QuickTime, Final Cut	Legacy Windows apps, old archives
Modern web uploads	Accepted	Often rejected
Codec inside	H.264, HEVC, ProRes	Often H.264 or older MJPEG
Best first step	Re-encode to H.264 AVI for legacy tools	Matches old validator lists

In practice, MOV is what you record on Mac today. AVI is what a vendor portal, lab instrument, or aging training system still demands. Confirm whether they need a specific codec inside AVI (H.264 vs MJPEG vs XviD) before batch converting an entire folder.

When the recipient accepts modern formats, MOV to MP4 on Mac is usually the better direction. See the video compression guide when the legacy tool also caps file size.

Export in QuickTime

QuickTime Player cannot save AVI directly. Use it only to preview and trim before FFmpeg conversion.

1. Open the MOV in QuickTime Player.
2. Edit → Trim (⌘T) to mark the section you need.
3. File → Export As to MOV at 1080p if you want a trimmed intermediate, then convert that file with FFmpeg.

Alternatively, trim inside GetCompress or pass in/out times directly to FFmpeg with -ss and -to flags in Terminal. For most legacy AVI workflows, trimming in QuickTime first reduces encode time because FFmpeg processes fewer frames.

Situation	Approach
One clip for a legacy app	Trim in QuickTime, convert with FFmpeg
Batch folder	FFmpeg loop with optional trim flags
Modern recipient	Prefer MP4 instead of AVI

Do not spend time hunting for a QuickTime AVI export option; it is not part of the app. FFmpeg or GetCompress handles the container change.

Convert with FFmpeg

FFmpeg in Terminal is the standard MOV to AVI path on Mac. Install through Homebrew:

brew install ffmpeg

Modern H.264 inside AVI (works on many legacy tools that accept AVI with H.264):

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

Legacy MJPEG AVI when an old tool rejects H.264:

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
for f in *.mov; do
  ffmpeg -i "$f" -c:v libx264 -crf 22 -preset medium \
    -c:a libmp3lame -b:a 192k "avi-out/${f%.mov}.avi"
done

Flag	Plain meaning
-crf 22	Quality for H.264 output
libmp3lame	MP3 audio common in AVI workflows
mjpeg	Older AVI codec when required

Test one file before batching when the destination software is picky. If AVI is rejected but WMV works, see WMV to MP4 on Mac for related Windows-format context (you may still deliver MP4 instead when possible).

Using GetCompress

GetCompress fits recurring convert MOV to AVI on Mac work when legacy handoffs arrive on a schedule and Terminal batch scripts are not how your team works.

Drop MOV clips or a folder into the app. Choose AVI output (or the closest supported format your build lists), set resolution and quality, and trim in the preview before export when the legacy tool only needs a short segment.

Useful workflow pieces in GetCompress:

• Batch queue: convert a QA MOV folder without writing FFmpeg loops.
• Presets: save settings that match a picky legacy validator after you dial them in once.
• Preview and trim: export only the repro steps a lab tool needs, not the whole recording.
• Folder monitoring: watch an exports folder and auto-convert new MOV files when a Windows team still polls AVI.
• Local processing: keep NDA footage on your Mac instead of uploading to online converters.
• Target file size: shrink AVI outputs when the legacy portal caps megabytes.

After conversion, test playback in the target application before batching the rest of the folder. Adjust quality in the same window if the AVI exceeds size limits.