QuickTime to GIF on Mac: 3 Free Methods (2026)

Your Mac can do this with nothing installed, using Shortcuts. Build a one-action shortcut called Make GIF, set it to accept files, and it shows up when you right-click a .mov in the Finder. Ten seconds of setup, then it is always there.

That covers most cases. The rest of this is for when the output looks bad, when the file comes out enormous, and for the question worth asking first: whether you want a GIF at all.

One thing to understand up front, because it explains every complaint people have about GIF conversion. GIF has a 256-color palette and stores nearly every frame in full. There is no motion compensation the way there is in a video codec. So the output is always much larger than the source video, and the only levers that really matter are frame rate and width. Every method below is a different way of pulling those two levers well.

Method 1: Shortcuts (built in, no install)

macOS Shortcuts has a Make GIF action. It is the fastest route and nothing needs installing.

1. Open Shortcuts.
2. File > New Shortcut.
3. Search the action list for Make GIF and drag it in.
4. In the shortcut settings (the info panel on the right), tick Use as Quick Action and Finder.
5. Name it something like “Make GIF” and close.

Now right-click any .mov in the Finder, go to Quick Actions, and pick it.

Expand the Make GIF action’s arrow and you get the controls that matter: seconds per frame, auto size or a fixed width, and whether the GIF loops. Turning auto size off and setting a width around 700 px is usually the difference between a 30 MB file and a 6 MB one.

Best for: almost everyone. It is built in, it is a right-click away, and it is good enough.

Method 2: ffmpeg with a real palette (best quality, free)

If Shortcuts gives you a banded, dirty-looking GIF, this is why: a naive conversion picks one generic 256-color palette. The fix is to let ffmpeg look at your specific clip and build a palette for it. This is two commands instead of one, and the difference is not subtle.

Install ffmpeg once:

brew install ffmpeg

Then generate a palette from the clip, and use it:

ffmpeg -i recording.mov -vf "fps=15,scale=720:-1:flags=lanczos,palettegen" palette.png

ffmpeg -i recording.mov -i palette.png \
  -lavfi "fps=15,scale=720:-1:flags=lanczos [x]; [x][1:v] paletteuse" \
  recording.gif

Change fps=15 and scale=720 in both commands, they have to match. Lower the fps first when the file is too big, it is the cheapest saving you can make.

To trim while you convert, add -ss 5 -t 8 before -i to start at 5 seconds and take 8 seconds.

If the result is still too heavy, gifsicle squeezes it further:

brew install gifsicle
gifsicle -O3 --lossy=80 recording.gif -o smaller.gif

Best for: screen recordings with text and flat UI colors, where banding is obvious, and anything you want to script.

Method 3: gifski (best for detailed footage)

gifski takes a different approach: it builds a palette per frame rather than one for the whole clip, which handles gradients and video footage much better than a single shared palette can.

brew install gifski
gifski --fps 15 --width 720 -o out.gif recording.mov

It is slower than ffmpeg and the files are not always smaller, but on anything with photographic content or smooth gradients it usually looks the best of the three.

Best for: camera footage, gradients, anything where the ffmpeg output still bands.

Should it be a GIF at all?

Worth asking before you convert anything, because a lot of GIFs should not be GIFs.

Use a GIF when the destination expects one. GitHub READMEs, Slack, Notion, chat apps, most social platforms. In those places a GIF autoplays and loops with no player chrome and no click, and that is genuinely what you want.

Use a video when you control the page. For your own site or documentation, a muted, autoplaying, looping MP4 or WebM does everything a GIF does, plays in every current browser, and is commonly five to twenty times smaller at better quality:

<video autoplay loop muted playsinline src="demo.mp4"></video>

That single swap will do more for your page weight than any amount of GIF tuning. If you have already made GIFs and regret it, converting the other way, GIF to MP4, is a real and useful move.

Which method to choose

When a free method stops being worth it

All three above are free and all three work. Be honest about which situation you are in.

For one clip, use Shortcuts. For a handful where quality matters, the ffmpeg palette pair is two lines and costs nothing. Neither of those is worth paying to replace.

Where it gets old is a folder of recordings, converted repeatedly, at a consistent size, as part of your actual job. Then the commands need re-running per file, the fps and scale have to be kept in sync in two places, and you are eyeballing every output.

That is what Picmal is for. Drag in the clips, set frame rate and width once, convert the batch. It also goes the other way and handles MOV to MP4 and MP4 to GIF from the same window, runs entirely on your Mac with no upload and no file-size cap, and is $39 once. If you make a GIF twice a year, the Shortcuts action is genuinely the better answer.

For everything else video on the Mac, the video converter for Mac page covers the rest of the formats.