How to Export a Screen Recording as a GIF on Mac

GIF is an ancient format with a 256-color palette limitation. Recording directly to GIF means your tool is making real-time color quantization decisions that reduce quality. Recording to mp4 first (which supports millions of colors and better compression) and converting afterward gives you more control over the output quality.

That said, direct GIF recording is faster — fewer steps, and tools like Kap do it well for simple content. The decision depends on your content: for UI recordings with mostly flat colors and minimal motion, direct GIF is fine. For anything with gradients, photos, or complex animation, record to mp4 first.

Important note: Limelight exports to mp4 (or 9:16 vertical mp4), not GIF directly. If you're using Limelight, you'll need a conversion step.

Kap is a free, open-source screen recorder for macOS that can export directly to GIF, mp4, WebM, or APNG. It's the cleanest solution if you want a GIF without a conversion step.

Setup: Download Kap from getkap.co. Open it, select your recording region by dragging the frame, and hit record. When you stop, Kap opens a preview window where you choose your export format. Select GIF, configure frame rate (8-15fps is usually enough for UI demos), and export.

Kap produces solid GIFs for most use cases. The frame rate controls help keep file size manageable. The main limitation: Kap doesn't have auto-zoom, cursor spotlight, or keystroke display. It's a clean, minimal recorder focused on output format flexibility.

This is the best workflow for GIFs that need to look good. Limelight gives you auto-zoom, cursor spotlight, and keystroke display baked into the recording. Gifski is a high-quality GIF encoder (free, open-source) that produces significantly better output than most converters.

Step 1 — Record in Limelight: Open Limelight, set up your recording region, enable any effects (auto-zoom, cursor spotlight, keystrokes), and record. Use the built-in editor to trim the clip to exactly the segment you want in your GIF. Export as mp4.

Step 2 — Convert with Gifski: Install Gifski from the Mac App Store or gifski.app (free). Drag your mp4 into Gifski. Set your output resolution (320px wide is usually enough for README GIFs; 640px for Slack or documentation), frame rate (10-15fps), and quality. Export.

Gifski uses a superior color quantization algorithm compared to FFmpeg's default GIF mode or most online converters. The output GIFs are noticeably sharper, especially for text-heavy UI recordings.

If you have FFmpeg installed (brew install ffmpeg), you can convert any mp4 to GIF from Terminal. The two-pass approach with a palette generates much better output than a single-pass conversion.

Pass 1 — Generate palette: ffmpeg -i input.mp4 -vf "fps=12,scale=640:-1:flags=lanczos,palettegen" palette.png

Pass 2 — Encode GIF: ffmpeg -i input.mp4 -i palette.png -filter_complex "fps=12,scale=640:-1:flags=lanczos[x];[x][1:v]paletteuse" output.gif

Adjust fps (frames per second) and scale (width in pixels) to control file size. Lower fps = smaller file, smoother motion = higher fps. The palette approach is what makes FFmpeg-generated GIFs look as good as Gifski for most content.

FFmpeg is free and produces excellent results, but the command-line interface isn't convenient for occasional use. If you're converting GIFs regularly, Gifski's drag-and-drop interface is faster.

Shorter is better. GIFs shouldn't be longer than 15-30 seconds. Past that, file size becomes impractical and viewers won't watch the full loop anyway. If your demo is longer, split it into multiple GIFs or use mp4 instead.

Lower frame rate than you think. Most UI demos look fine at 10-12fps. The motion in button clicks and menu navigation doesn't require 30fps to read correctly. Cutting from 30fps to 12fps roughly triples the compression ratio.

Width controls size more than quality settings. A 400px wide GIF at high quality is usually smaller and sharper than a 800px wide GIF at low quality. Scale down first, then tune quality.

Record a small region. If your demo only involves one panel of a large app, record just that panel rather than the full window. Fewer pixels means smaller file.

GIF doesn't support transparency in animations well. If you want a GIF on a transparent background (for a README), PNG or WebM is a better format than GIF.

For GitHub READMEs and documentation where you want fast, simple GIFs: use Kap directly. It's free, handles the common cases well, and requires no conversion step.

For product demos, Slack shares, or any GIF where the visual quality matters and you want auto-zoom/cursor effects: record in Limelight → trim → export mp4 → convert with Gifski. More steps but significantly better output.

For scripted batch conversion or CI pipelines that auto-generate GIFs: FFmpeg with the two-pass palette method. Automatable, free, consistent.