Picking the right FPS for a GIF: 10, 15, 24, or 30?
For regular video, higher frame rate is almost always better — 60 FPS looks smoother than 30, 120 beats 60. GIFs flip that intuition on its head: because GIF has no inter-frame compression, every additional frame per second is another full frame stored on disk. File size scales almost linearly with FPS. So the question isn't "which FPS looks best?" — it's "what's the lowest FPS that still looks right for this content?"
The math (briefly)
A GIF's file size is roughly proportional to duration × FPS × (width × height) × palette-efficiency. The first three multiply together — halve any one and you roughly halve the file. So:
- 30 FPS → 15 FPS cuts file size by ~50%.
- 15 FPS → 10 FPS cuts it by another ~33%.
- 24 FPS → 12 FPS cuts it by ~50%.
Those are rough numbers — the actual savings depend on how similar consecutive frames are (the GIF encoder compresses individual frames, which helps if many pixels don't change). But the linear-ish scaling is a reliable enough mental model for picking an FPS.
Match FPS to content type
Screen recordings, UI demos, code walkthroughs → 12–15 FPS
The human eye is pretty forgiving on stationary or slow-scrolling UI. Cursor motion at 12–15 FPS reads as smooth; text rendering is frame-independent. Going above 15 is almost always wasted file size unless you're demoing an animation-heavy interaction (drag-and-drop, spring physics).
Reaction GIFs, memes → 10–15 FPS
Most classic reaction GIFs on the internet are 10–15 FPS. The motion is fast enough at that rate to feel punchy, and the file stays small enough to share easily. Going higher is actively worse: a giant reaction GIF nobody can load quickly loses the joke.
Cinematic clips, film → 24 FPS
Traditional film is shot at 24 FPS. If you're clipping a movie or a professionally-shot video, encoding the GIF at 24 FPS preserves the original cadence perfectly (each GIF frame maps 1:1 to a source frame). Dropping to 12 FPS still works but you throw away half the frames, which looks slightly juddery in pans.
Sports, action, fast motion → 24–30 FPS
When the subject is moving fast and fills the frame, dropping FPS introduces motion blur artifacts that show. This is the one case where the default advice changes — pay the file-size cost, encode at 24 or 30 FPS, and compensate by trimming hard and dropping the width.
Why 15 FPS is the default
In localgif.app, the default FPS is 15. That's not arbitrary — it's the FPS that:
- Looks smooth for the most common GIF content (UI, reactions, short clips).
- Halves the file size versus 30 FPS without most viewers noticing.
- Is a clean divisor of most source frame rates — 30 FPS source gives you clean 2:1 downsampling, 60 FPS source gives 4:1.
If you don't know what FPS to pick, start at 15. Look at the output. Drop to 10 if it's close and you want a smaller file; only go up to 24 or 30 if the motion genuinely looks wrong.
A checklist for picking FPS
- Is it UI/text/cursor? Start at 12–15 FPS.
- Is it a reaction or meme? 10–15 FPS.
- Is it a film/cinematic clip? 24 FPS, or 12 if size is tight.
- Is it fast action/sports? 24–30 FPS and compensate with width/trim.
- Still too large? Drop 3 FPS at a time and re-check. Every step is ~15–20% smaller.
Try it
The FPS slider in localgif.app lets you re-encode the same clip at different frame rates in a few seconds so you can eyeball the trade-off directly. Everything happens in your browser — the source file never leaves your machine.