ffmpeg: Convert video to optimized GIF on macOS

ffmpeg: Convert video to optimized GIF on macOS

Whenever I need to turn a video into a GIF, most search results lead me to upload-based websites. These usually have strict file size or length limits, and I prefer not to upload my raw files to a third-party server. Since I use a Mac mini with Apple Silicon, I wanted a way to do this locally.

ffmpeg: Convert video to optimized GIF on macOS

To get started, you need Homebrew (a package manager for macOS). If you don't have it, install it via the terminal:

/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"

Verify the installation with brew --version. Once that is sorted, install ffmpeg, a powerful tool for handling almost any video or audio task:

brew install ffmpeg

Run ffmpeg -version to confirm it's working. On my M1 Mac mini, the installation took less than a minute.

My first attempt was to keep it simple. I found a basic one-line command and tried it on a 15-second Full HD (1920x1080) video:

ffmpeg -i input.mp4 output_single_pass.gif

The result was a "capacity bomb." The GIF ended up being 25.1 MB, even though the source was just a simple smartphone clip. While usable for very short clips, the file size becomes impossible to share for anything longer.

The issue is that GIFs only support 256 colors. Trying to preserve every color from a high-resolution video causes the file size to explode. To fix this, you must first generate a custom color palette.

Using a two-step conversion for optimization

To dramatically reduce the size, you need to extract an optimized color palette from the source video and then use that palette to render the GIF.

Step 1: Generate the palette

First, extract the best 256 colors from input.mp4 and save them as palette.png.

ffmpeg -i input.mp4 -vf "fps=10,scale=480:-1:flags=lanczos,palettegen" palette.png

Here is what the -vf (video filter) options are doing:

  • fps=10: Sets the frames per second to 10. Standard video is usually 24–30 fps, but 10–15 is plenty for a GIF and saves significant space.
  • scale=480:-1: Resizes the width to 480 pixels. The -1 tells ffmpeg to calculate the height automatically to maintain the aspect ratio.
  • flags=lanczos: A high-quality scaling algorithm that minimizes quality loss during resizing.
  • palettegen: The filter that creates the optimized 256-color palette.

On my 15-second clip, this step took about 4 seconds to produce palette.png.

Step 2: Convert using the palette

Now, combine the original video and the palette to create the final GIF.

ffmpeg -i input.mp4 -i palette.png -filter_complex "fps=10,scale=480:-1:flags=lanczos[x];[x][1:v]paletteuse" output_optimized.gif

In this command, -filter_complex is used because there are two inputs. The video stream [x] (processed with the same fps and scale) is combined with the palette stream [1:v] using the paletteuse filter. This final step took about 5 seconds.

Performance Comparison

To see the actual difference, I tested both methods using the same 15-second 1080p MP4 (original size: 8.7 MB).

MethodFile SizeConversion Time
Single-pass25.1 MB3.2s
Two-step (Optimized)2.5 MB9.0s (3.8s palette + 5.2s GIF)

The optimized version is over 10 times smaller than the single-pass version. While it takes about three times longer to process, that is a small price to pay for such a massive reduction in file size.

A few things to keep in mind: fps is critical; pushing it above 20 will cause your file size to skyrocket. Also, reducing the scale is the most effective way to cut size—dropping from 960px to 480px reduces total pixels by a factor of four. I once tried to turn a full hour of footage into a GIF, and my Mac mini fans started screaming; keep your clips short for the best results.

It was a good reminder that simply finding a command that "works" isn't enough. Taking the time to measure results and understand the underlying logic—like how the GIF color palette works—saves a lot of frustration in the long run.

Related posts

This post is the English edition of a Korean write-up: 원문 보기

Comments

Post a Comment

Popular posts from this blog

Codex CLI 401 Unauthorized and Installation Fixes

Image
I recently spent several frustrating hours troubleshooting the Codex CLI on my Mac. It was a classic developer trap: fixing one problem immediately revealed another. Broken symlinks, expired tokens, and directory permissions converged, making it feel as though the tool was simply broken. Since "codex 401 unauthorized" is one of the most searched terms on my blog, it's clear many others are hitting these same walls. I have documented the exact sequence of failures and fixes I encountered on my Mac mini to help you avoid the rabbit hole. Why does codex --version say No such file or directory? When I first installed Codex via Homebrew Cask, the installation appeared successful. However, running codex --version returned No such file or directory . It turned out that while the symbolic link existed, the executable it pointed to was missing. The shell had a map to the binary, but the destination was empty. To fix this, you must restore both the link and the executable vi...
Read more

npm command not found on Windows: fix the PATH

Image
I recently hit a wall while configuring my development environment on Windows. It's one of those subtle issues that can waste an afternoon if you don't know what to look for. Here's exactly how I diagnosed and fixed a 'command not found' error after a successful global install. The Problem I decided to add a markdown processing tool to my toolkit by running: npm install -g markdown-it-cli The terminal output confirmed the installation succeeded, displaying a message about added packages. Satisfied, I tried to use it by typing markdown-it-cli in the command line. Windows immediately responded with: 'markdown-it-cli is not recognized as an internal or external command, operable program or batch file.' This error means Windows looked through every folder in its search list and couldn't find an executable with that name. Attempts and Failures My initial reaction was to suspect the package itself might be broken. I tried running it using npx , wh...
Read more

uv install: How much faster is it than pip?

Image
While running automation scripts on my Mac Mini, the constant bottleneck in my workflow was the time spent installing Python packages. Whether starting a new project or updating an existing environment, those few seconds of waiting added up—especially with larger packages like polars , which has a distribution file of around 40MB. To reclaim this lost productivity, I decided to test uv , a Rust-based Python package manager designed to replace pip and venv . How much faster is uv compared to pip? To get a realistic benchmark, I ran the same setup five times on my Mac Mini to calculate the average. The process involved creating a fresh virtual environment and installing polars . With pip , environment creation took 1.202 seconds and installation took 2.338 seconds, totaling 3.54 seconds. Using uv version 0.11.6, the environment was ready in 0.150 seconds and installation finished in 0.383 seconds, totaling 0.533 seconds. This makes uv roughly 6.6 times faster than pip . Looking a...
Read more