Guide

How to Make a GIF from Video or Images

Making your own GIF is easy: a favorite movie moment, a captioned meme, a mini tutorial, or an animation from a series of photos. To get a result that's crisp and light — not a blurry 20-megabyte brick — you really only need to get a few choices right. This guide takes you from source file to a finished looping GIF, no complicated software required.

Bright neon strokes of light in motion — an image of creating a lively animation
A good GIF starts with the right moment. Photo: Pexels

What a GIF is made from

Every GIF is assembled from a sequence of frames — that's its essence (if you're not yet familiar with how the format works, see "What Is GIF"). So there are really only two sources:

  • Video — the most common case. A short clip is cut from a video and automatically split into frames.
  • A set of images — individual pictures (photos, drawings, screenshots) shown in turn. That's how you make slideshows, frame-by-frame animation, and memes.

The assembly principle is the same; only the source prep differs. Let's cover both paths.

Guide 1: a GIF from video

This is the classic — animating a funny or striking moment from a clip. The steps:

1

Pick the clip

Find a 2–6 second moment. The tighter the trim, the lighter and punchier the GIF.

2

Set the frame rate

10–15 fps is enough. It cuts weight and barely affects how a short loop reads.

3

Adjust the size

Reduce the width to 320–480 pixels for chat, or 600 for an article.

4

Assemble and save

Turn on infinite looping — and your GIF is ready.

A quality tip

Professional tools like FFmpeg convert in two passes: first they build an optimal palette for the specific clip (the palettegen filter), then apply it (paletteuse). That noticeably clears up the "grime" on gradients. When scaling, choose the Lanczos algorithm — it's sharper than plain bilinear.

Guide 2: a GIF from a series of images

The second path is to assemble an animation from individual images: frames of hand-drawn animation, before/after photos, instructional slides. Here the prep matters:

1

Make frames the same size

All images must share one width and height, or the animation will "jump."

2

Set the order

Number the files (01, 02, 03…) — most assemblers go by name.

3

Set the frame delay

100 ms equals 10 frames per second. For a slideshow, use 500–1000 ms per frame.

4

Enable looping and build

Done: a set of images becomes a looping GIF.

Yellow-and-green diagonal strokes of light — a metaphor for frame-by-frame animation assembly
A GIF from images is essentially a digital flipbook: frame by frame. Photo: Pexels

Three settings that decide everything

The quality and weight of the finished GIF come down to a few numbers. Memorize them and most problems disappear:

Duration
2–6 seconds
Frame rate
10–15 fps
Width
320–640 px
Palette
64–256 colors
Loop
Infinite (0)
Scaling
Lanczos

The core rule: don't make a GIF bigger or longer than it needs to be. Weight grows with every one of these settings, so a spare second or an extra hundred pixels of width means extra megabytes.

Palette and motion smoothness

GIF is limited to 256 colors, and you should account for that during assembly. If the frame is a bright photo with gradients, keep more colors and enable dithering — it masks stair-stepped transitions. If it's flat graphics or a UI screenshot, do the opposite: cut the palette to 64 colors and turn dithering off, for a cleaner and lighter result.

Smoothness is set by the frame rate. 12 fps is the sweet spot: the motion reads well and the file stays compact. Below 10 fps the animation starts to "stutter"; above 24 fps the weight grows with no visible benefit.

A good GIF isn't "video stuffed into GIF" — it's a carefully chosen short moment that's a pleasure to watch on loop.

The finish: check and optimize

Before publishing, run the finished file through a lossless optimizer — it shaves off another 20–40% for free. If the GIF is still heavy, go back to the three settings above and trim the "fattest" one. All the compression techniques are covered in detail in the guide "How to Reduce GIF File Size".

One last thing: if your GIF is headed for a website rather than a messenger, it's almost always better to hand it over as WebP — same frames and loop, but about 64% lighter on average. We compare what to pick for each job in "GIF vs WebP and MP4".

Made a GIF? Lighten it for the web

Upload your finished GIF to the FormatZ converter and get an animated WebP 5–10× lighter, with every frame, timing and loop preserved.

Convert GIF to WebP

Common beginner mistakes

  • Too long a clip. A 15-second GIF weighs like a small video. Trim to the essence.
  • Giant resolution. A full-screen GIF in a chat is pointless — it's the main source of extra weight.
  • 30+ fps "for smoothness." The eye won't notice, but the file doubles.
  • Re-saving from an already-compressed GIF. Artifacts pile up — always work from the highest-quality source.

Need a single still frame from your finished GIF? Use GIF to PNG. All available conversions are on the all formats page.

Ideally 2–6 seconds. A GIF is meant to be a short looping moment, not a video: the longer the clip, the heavier the file. If your clip runs longer than 10 seconds, it's smarter to save it as MP4/WebM video rather than a GIF.
For most GIFs, 10–15 frames per second is enough. 12 fps is a good balance of smoothness and size. Above 24 fps the file gets much heavier, while in a short loop the eye barely notices the difference.
For a chat or feed, 320–480 pixels wide is usually plenty; for embedding in an article, up to 600–640. Width has the biggest impact on weight, so don't make the GIF larger than the spot where it will be shown.
Prepare frames of the same size, arrange them in the right order, and set each one's delay (e.g. 100–300 ms). Many online GIF makers assemble such an animation from a set of PNG/JPG files in a couple of clicks and let you enable looping.
First reduce width and frame rate — that's where the main savings are. Then cut the palette to 64–128 colors. If you need it even lighter, convert the finished GIF to WebP — that's about 64% off the size on average.