Choose 5–15 photos, put them in order, set a 300–800 ms delay, export at 480–640 px wide, and check the file size before sharing. GIF has no audio and only 256 colors per frame, so a short, simple sequence works better than a long, detailed one.
A photo slideshow is the most common reason people search for an image to GIF converter. The job sounds simple: put the photos in a row, press a button, get a GIF. The part that decides whether the result is usable is not the button. It is the frame count, the timing, and the width.
This guide walks through the decisions in the order that matters. The converter itself is on the home page; everything below is about getting a result you will actually want to share.
Start with 5–15 photos
A GIF is a sequence of still frames. Each frame is stored, compressed, and played back at a delay you choose. There is no motion prediction between frames like a video codec uses, so every additional frame has a real cost in file size.
Five to fifteen frames is a useful range:
- 4–8 frames for a reaction, a blink, or a simple product spin.
- 8–15 frames for a short story or a before/after sequence.
- 15+ frames only when the motion is the point and you are willing to trade file size for smoothness.
The tool accepts up to 30 frames. That cap exists to keep memory use bounded, not because 30 frames is a good default. A 30-frame photo GIF at 640 px can be several megabytes, which is often too large for a chat app or a page header.
If you are unsure, start with eight frames. It is enough to read as an animation and small enough to iterate.
Keep one aspect ratio
The first image sets the output aspect ratio. Every later frame is fitted into that canvas with one of two modes:
- Contain keeps the whole image and adds bars where the aspect ratios do not match.
- Cover fills the canvas and crops the overflow.
For a slideshow made from phone photos, contain is usually safer: nobody’s face gets cut off. If the photos are already the same aspect ratio, the choice barely matters. If you mix portrait and landscape photos, decide up front whether bars or crops are acceptable.
The alternative is to crop the photos to a common ratio before importing them. That gives you more control than letting the converter crop, especially if the subject is near an edge.
Put the frames in a readable order
A GIF loops. The last frame flows back into the first, so the transition from the final image to the opening image is part of the design. Two practical patterns:
- A story: frame 1 is the start, the last frame is the end, and the loop reads as a reset. This works for before/after sequences and simple tutorials.
- A cycle: the last frame is visually close to the first, so the loop feels continuous. This works for rotations, pulses, and product spins.
Drag the thumbnails to reorder them, or use the arrow buttons on each frame. The numbering starts at 01 because the first frame is also the one that defines the canvas.
Choose a delay that fits the content
GIF delays are stored in hundredths of a second. A 500 ms delay is written as 50, and the viewer holds each frame for half a second. The practical range for photo GIFs is roughly 200–1000 ms:
| Delay | Feel | Good for |
|---|---|---|
| 200–300 ms | Fast, almost flickery | Simple motion cues, blinking, quick cuts |
| 400–600 ms | Comfortable slideshow | Most photo sequences |
| 700–1000 ms | Slow and readable | Text, detail, before/after comparisons |
The converter uses one global delay for the whole GIF. If one frame needs to hold longer, duplicate it in the strip. Two identical frames at 500 ms are equivalent to one frame at 1000 ms for playback, and the encoder can compress the repeated frame heavily.
Very short delays are not reliable across viewers. Some GIF players clamp delays below a certain threshold, so a 10 ms frame may display much longer than you intended. If the animation looks slower than the setting, raise the delay and remove frames rather than pushing the number down.
Pick a width, then check the file size
Width is the biggest lever on file size. The pixel count grows with the square of the width: 640 → 480 px removes about 44% of the pixels per frame, and 640 → 320 px removes about 75%. The GIF gets smaller even if nothing else changes.
For photos, 480–640 px wide is a good starting range:
- 480 px: chat stickers, small embeds, slower connections.
- 640 px: a good default for a web page or a messaging app.
- 800–1200 px: only when the GIF will be viewed large and the file size is acceptable.
In a headless Chromium test on this machine, eight frames of a detailed 1600×1067 photo produced roughly 1.9 MB at 640×427, 1.1 MB at 480×320, and 0.5 MB at 320×213. That is one photo and one machine, not a universal rule, but it shows the direction: the smaller canvas is doing most of the work.
The result panel warns when a GIF passes 8 MB. If that happens, the order of fixes is: reduce width, remove frames, lower the palette, then turn off dithering for flat graphics. The file-size guide goes through each lever.
Test the loop where it will be used
The preview in the tool is the actual GIF file, so it is a fair check of the colors and timing. It is not a check of the destination. Some chat apps re-compress GIFs, some show only the first frame until tapped, and some platforms convert GIFs to video. Open the downloaded file in the app where you plan to use it before you send it to anyone.
Two things to look for:
- A visible jump at the loop point. Reorder or duplicate a frame to soften the transition.
- Banding in skies or skin. Try the smooth quality setting, a larger palette, or a smaller width. Dithering can make gradients read better at the cost of a little grain.
When a video is better
GIF is the right format for a short, silent, universally supported loop. It is the wrong format for a long sequence, a clip with audio, or high-resolution footage. A 30-second photo story with music belongs in MP4 or WebM. A 3-second product loop that must work in an old upload field belongs in GIF.
If the destination supports modern formats, animated WebP or APNG can keep more colors and full transparency at a smaller size. The trade-off is compatibility. GIF vs WebP vs APNG covers that decision without pretending one format wins everywhere.
A short checklist
- Pick 5–15 photos with a consistent subject.
- Choose contain or cover for mixed aspect ratios.
- Order the frames so the loop reads.
- Start at 500 ms and adjust by feel.
- Use 640 px unless the file is too large.
- Check the preview and the downloaded file in the target app.
- If it is still too large, read the file-size guide before adding more frames.
The converter is at image-to-gif.com. It runs in the browser, so the photos are not uploaded while you iterate.
Sources
Related guides
image-to-gif.com converts images to GIF in the browser; files are never uploaded.
FAQ
How many photos should I use for a GIF?
Five to fifteen is a practical range. Fewer than five can feel like a slideshow; more than fifteen grows the file quickly. This converter accepts up to 30 frames, but that is a ceiling, not a target.
What frame delay should I use?
Start at 500 ms. For a quick flicker, 200–300 ms works. For a sequence with text or detail, 700–1000 ms is easier to read. GIF stores delays in hundredths of a second, so the tool rounds to the nearest 10 ms.
Can I make a GIF from one photo?
Yes. One image produces a still GIF. That is useful when a platform requires GIF, but a single photo usually looks better and stays smaller as JPEG or WebP.
Why is my photo GIF so large?
Every frame carries its own pixels, and photos need a large palette and often dithering. Reduce the width first, then remove frames, then lower the color count. A 640 px photo GIF can be several megabytes.
Can I add music or a voiceover?
No. GIF has no audio track. For a longer sequence with sound, export a video such as MP4 or WebM instead.
Does this work on iPhone?
Yes, in Safari. If a photo is HEIC and the browser cannot decode it, export a JPEG copy first. The converter shows a clear error instead of failing silently.