How Many Images Should a GIF Have?
There's no single answer. A meme needs 2–4 images. A product rotation needs 24–60. A slideshow might use 8–24. The right number depends on what you're making, how long it should run, and how big you can afford the file to be.
How many images for your use case?
Pick what you're making. We'll suggest a frame range, FPS, and duration. Then build it in Image → GIF.
What are you making?
Photo slideshow
10–12 FPS feels natural. 8–24 images keeps it snappy. More = heavier file.
Frames
8–24
FPS
10
Duration
~2s
Rule of thumb: keep total frames under 100 for web. Under 200 max. More = bigger file.
The math: frames, FPS, and duration
Three numbers define your GIF: frame count (how many images), FPS (frames per second), and duration (seconds). They're linked: duration ≈ frames ÷ FPS. So 24 frames at 12 FPS ≈ 2 seconds. 48 frames at 12 FPS ≈ 4 seconds.
GIF timing helper (images → animation)
Tell us how many images you have and how long the GIF should feel. We’ll suggest an FPS (and an approximate per-frame delay).
Suggested
5 FPS
Approx delay per frame: 200ms
Raw math: 12 frames ÷ 2.0s ≈ 6.0 FPS
Rule of thumb:
- 5–8 FPS: stop-motion vibe, easy to follow
- 10–12 FPS: “normal” motion for slideshows
- 15–24 FPS: smooth, but bigger files
By use case: quick reference
Frame count by use case
| Use case | Frames | FPS | Duration |
|---|---|---|---|
| Slideshow | 8–24 | 10–12 | ~2s |
| Stop-motion | 12–48 | 5–8 | 2–4s |
| Product rotation | 24–60 | 10–12 | 2–5s |
| Meme / reaction | 2–8 | 8 | <1s |
| Before/after | 2–4 | 5 | ~2s |
| Step-by-step | 6–20 | 10 | 2–3s |
Why frame count matters
More frames = more data. GIFs store each frame as a full image. 60 frames is roughly 60× the data of 1 frame (before compression). So frame count directly drives file size. Keep it under 100 for web when you can. Under 200 max. If you need a longer or smoother result, consider lowering resolution or FPS instead of adding frames.
Pro tips
- Duplicate for pauses: Want a frame to linger? Add it twice (or more). Same image, multiple frames.
- Remove duplicates: Identical consecutive frames add size without visible change. Delete them.
- Name files for order: 01, 02, 03… before selecting so they load in the right sequence.
- Compress after: Made your GIF? Run it through Compress GIF if the file is too big.
Drop your images and try it
Pick your frames (at least 2), drop them below. We'll take you straight into Image → GIF with your files loaded. Reorder, set FPS, export. Free, no upload, no signup.
Drop your images here
Or click to browse
JPG, PNG, WebP, HEIC, AVIF & more • At least 2 images
You can also paste images from clipboard
Quick takeaways
Remember
- Minimum: 2 images. No exceptions.
- Sweet spot: 30–100 frames for most web GIFs.
- Max: Under 200. More = huge files.
- Match FPS to duration: Frames ÷ FPS ≈ seconds.
- Use case matters: Memes need few; product rotations need more.
Frequently asked questions
At least 2. A GIF needs at least 2 frames to animate. Single-image "GIFs" are just static images.
For web, keep it under 100 frames when possible. Under 200 max. More frames = bigger file, slower load. Platform limits (email, Slack, Twitter) vary—check before you go heavy.
Smoothness depends on FPS (frames per second), not just frame count. 12 images at 12 FPS = 1 second, smooth. 12 images at 4 FPS = 3 seconds, choppy. Match frame count to your target duration and FPS.
24–60 frames usually works. At 10–12 FPS, that gives 2–5 seconds of smooth rotation. More frames = smoother spin = bigger file. Start with 24 and add if it looks jerky.
8–24 images at 10–12 FPS. Each image gets ~0.1 second. For a slower "pause on each" feel, use 5–8 FPS. More images = longer duration or higher FPS = bigger file.