Batch Compress and Convert on Mac: 3 Methods

Same export folder every Friday? Automation saves clicks. One random file once a month? Just use Preview. Batch compress and convert on Mac makes sense when settings repeat and file counts climb past what manual export tolerates.

You spend time once on presets, folder rules, or scripts so every future Friday is one step instead of thirty. Stop automating when the settings change every job.

When automation is worth it

If the pain is occasional email bounces, read the email attachment size limits guide first. You may only need a one-time batch, not a permanent watch folder.

Common patterns:

Write down max width, codec, and target folder before you automate. For video-heavy batches, see the video compression guide for Mac . Sensitive client work should stay local; see are online file compressors safe .

Method 1: GetCompress

Best for: Mixed PNG, MP4, and PDF folders, reusable presets, and “new file landed” watches.

1. Open GetCompress and drop an entire folder into the queue.
2. Pick output format and quality per media type, or load a saved preset.
3. For video with a hard megabyte cap, set target file size (video only).
4. Preview one file, then export the batch to a folder you choose.
5. Optional: turn on folder monitoring so the same preset runs when new files appear.

Processing stays on your Mac. Pair monitoring with MCP when you also want Cursor to trigger presets on demand.

Method 2: Shortcuts and Automator

Best for: Simple macOS glue without a dedicated compressor UI.

Shortcuts (Applications → Shortcuts): build a workflow that runs a shell script you paste in, or opens the apps you use every time.

Automator: create a Folder Action that runs when new files land in a folder. Look for “Run Shell Script” or “Encode Media” on your macOS version.

Keep a manual fallback for deadline weeks. Automator folder actions break occasionally after macOS upgrades. Document which folder action maps to which export preset so a teammate can fix it when paths change.

Limitation: Limited preview, trim, and mixed-media presets compared with a dedicated app.

Method 3: Terminal or Hazel

Best for: Teams that already maintain FFmpeg or sips scripts.

Install FFmpeg through Homebrew if needed:

brew install ffmpeg

Example loop:

cd ~/Exports/in
for f in *.jpg; do sips -Z 1920 "$f"; done
for f in *.mov; do
 ffmpeg -i "$f" -vf scale=-2:1080 -c:v libx264 -crf 23 \
 -c:a aac -b:a 128k ~/Exports/out/"${f%.mov}.mp4"
done

Hazel (paid) watches a folder and runs a script when files appear. It shines when you need conditions beyond “new file appeared” (only PNG over 5 MB, only on weekdays).

Limitation: Someone technical must maintain codec flags. Scripts do not give you preview or mixed PDF plus video in one queue unless you write that logic yourself.

Which method should you use

For deeper watch-folder setup, see automatic folder compression on Mac .

When a one-off export is enough

Preview, QuickTime, or a single drag into GetCompress can work when the job is one folder once.

GetCompress also helps when Friday exports repeat, presets need names the team can share, or folder monitoring should run without scripts. Processing stays local. It does not replace Hazel for complex rules, and it does not replace a full design or video suite. For the Windows workflow, see batch compress and convert on Windows .