Compress Video on Mac Without Losing Quality

Blurry text in a screen recording usually means the file was squeezed too hard, not that you should never compress.

What quality loss actually means

Term	Plain meaning
Master	Best file you keep
Review copy	Smaller file you send
Visible loss	Blocky areas, soft UI text

Compress a copy. Keep the master elsewhere. “Without losing quality” really means without visible loss on the screen your reviewer uses. A 4K master downscaled to 1080p for email is not quality loss if UI text stays sharp at laptop size.

Lossy codecs always discard some data. The goal is to discard what reviewers will not notice on a laptop or phone, not to match the master byte for byte. Screen recordings with code, dashboards, or UI chrome need higher effective quality than a talking-head clip at the same resolution.

Bitrate, resolution, and frame rate basics

Quality and file size trade off through three main controls.

Setting	Quality impact	Size impact
Resolution	Less detail when downscaled	Large drop from 4K to 1080p
Bitrate / CRF	Blockiness and soft edges when too low	Main lever at fixed resolution
Frame rate	Motion smoothness	60 fps to 30 fps can halve frame data

For screen recordings, resolution and bitrate matter most. UI text needs enough pixels and enough bits per frame. Lower CRF (better quality) before you crush bitrate on a 1080p export. On 4K sources, downscale first, then tune CRF.

If the upload site rejects MOV but accepts MP4, convert without re-compressing twice. The MOV to MP4 guide walks through a clean pass.

Export from QuickTime and iMovie

QuickTime: trim, then 1080p for client review, 720p for email.

iMovie: Share → File, raise quality until size hurts, then back off one step.

Screen recordings need more care than a face camera. Always preview at 100% zoom on text. Gradients and thin lines show compression before faces do. If QuickTime 1080p still looks soft on text, try 720p at higher effective quality rather than a tiny file at full resolution.

iMovie gives a little more room to tune export quality than QuickTime alone. Export a test copy, check file size in Finder, and compare side by side with the master in QuickTime before you send the review link. One extra minute of checking beats a client reply asking for a clearer re-export.

Finer control with FFmpeg

When QuickTime presets are too coarse, FFmpeg with CRF is a common next step.

Open Terminal (Applications → Utilities → Terminal). Install FFmpeg through Homebrew (if brew is not found, install Homebrew first):

brew install ffmpeg

Then run:

ffmpeg -i master.mov -c:v libx264 -crf 21 -preset medium \
  -c:a aac -b:a 160k review.mp4

Try crf 20 for important review, crf 24 for internal shares. Downscale to 1080p before lowering CRF on a 4K source:

ffmpeg -i master.mov -vf scale=-2:1080 -c:v libx264 -crf 22 \
  -c:a aac -b:a 128k review-1080p.mp4

Preset affects encode time and compression efficiency: slow or medium often beats ultrafast for the same CRF at the cost of wait time. For a single review copy, medium is a sensible default.

Audio rarely drives size on short review clips, but -b:a 128k to 160k keeps voice clear without bloating the file. If the clip has no speech, consider -an to drop audio entirely and save a few megabytes on long screen recordings.

Email and upload size limits

Even a high-quality review copy must fit the destination.

Destination	Typical limit	Quality-safe approach
Email	10 to 25 MB	720p, crf 22 to 24, trim tight
Slack / Drive	Often 1 GB+	1080p, crf 20 to 23
Client portal	25 to 100 MB	1080p first; trim before lowering CRF
Issue tracker	10 to 50 MB	Short segment, 720p, check text zoom

When the limit is tight, shorten the clip before you lower quality. A two-minute sharp clip beats a ten-minute blocky one. For exact megabyte targets on video, target file size in a dedicated app beats guessing CRF by trial and error.

If you must hit 25 MB for email and the full walkthrough is ten minutes, export the key two-minute segment instead of crushing quality on the whole timeline. Reviewers rarely need the full raw capture on first pass.

Common mistakes

• Compressing your only copy (keep the original).
• Making a 30-minute file tiny instead of cutting it shorter.
• Skipping a quick watch-through before upload.
• Re-encoding the same file multiple times (each pass adds generation loss).
• Lowering CRF on 4K when 1080p downscale would look better at the same size.
• Sending the master because the review copy “looked too big” in Finder without trying a proper export first.

For a full walkthrough of built-in and command-line options, see how to compress video on Mac .

Using GetCompress

GetCompress helps you compress video on Mac without losing quality on the review copy while keeping the master untouched:

• Pick High or Original quality presets and preview text, gradients, and motion before export.
• Set target file size on video when a portal lists a megabyte cap; the app encodes toward that limit instead of manual CRF guessing.
• Trim dead air in the same window so reviewers see only the relevant segment.
• Queue multiple MOV or MP4 review copies with one saved preset for repeat client sends.
• Process locally on your Mac when the clip shows staging UI, NDAs, or unreleased product screens.

GetCompress is an easier alternative when QuickTime tiers are too blunt and you want preview plus presets without maintaining FFmpeg scripts for every handoff.

Open the master and review copy in the online video comparison tool to check bitrate artifacts and frame pacing with one synchronized timeline.