Skip to content
Getting started

How to Make a GIF — A Complete Beginner Walkthrough

Making a GIF is three decisions — what goes in it, how fast it plays, and how many colours it gets. Everything else is detail. This walks through all three with the numbers that actually matter, using a browser-based editor so nothing gets uploaded along the way.

12 September 2026 · 7 min read

Start from the ending

Before importing anything, decide where the GIF is going. A GIF for a README, a Slack reaction, an email newsletter and a Twitter post have different size budgets and different sensible dimensions, and every later decision follows from that one.

The two numbers to fix first are the width and the length in seconds. Width sets the pixel count, which drives file size more than any encoder setting; length sets the frame count, which drives it almost as hard. A four-second clip at 480 px wide is a comfortable target for most destinations. Ten seconds at 800 px is not, and no amount of tuning will make it one.

DestinationWidthLengthBudget
README / docs600–800 px5–15 sUnder 5 MB
Slack, Discord400–600 px2–6 sUnder 2 MB
Email newsletter480–600 px2–4 sUnder 1 MB
Twitter / X480–640 px2–6 sUnder 15 MB
Reasonable starting targets by destination

Email is the tight one. Many clients show only the first frame, so put the message in frame one and treat the animation as a bonus.

Get your frames in

There are two routes. From video: import the clip, trim to the moment you want, then choose a sampling rate — the editor seeks to evenly spaced timestamps and captures each one. From images: drop the files in and each becomes a frame you can hold for as long as you like.

Trim before anything else. Frames are only extracted for the range you keep, so cutting a six-second moment out of a ten-minute recording is six seconds of work rather than ten minutes of it. This is also the single biggest thing you can do for file size, and it costs no quality at all.

Pick a frame rate the format can represent

GIF has no frame rate field. Each frame carries its own delay in hundredths of a second, and the player waits that long before advancing. A tool that asks for "FPS" is writing the same delay into every frame.

That rounding is why 30 fps is not really available: one thirtieth of a second is 3.33 hundredths, which becomes 3 (about 33 fps) or 4 (25 fps). Choosing a rate that divides cleanly gives you playback that matches the preview.

  • 10–12.5 fps — screen recordings, UI demos, talking heads. The default worth trying first.
  • 20–25 fps — hand movement, fast cuts, anything where 12 fps looks like a slideshow.
  • Above 25 fps — rarely worth it. You pay linearly in bytes for motion most viewers will not notice.

Choose the colour count last

A GIF frame can hold at most 256 colours, drawn from a palette that either covers the whole file or is rebuilt per frame. Fewer colours means a smaller file and, past a point, visible banding.

The useful habit is to step down from 256 and stop at the first setting where you can see the difference. Flat material — screen recordings, illustration, anything with large areas of one colour — often survives 32 colours untouched. Photographic footage usually wants 128 and dithering to smooth what is left.

Dithering can make the file larger. It trades flat, highly compressible areas for fine noise, buying smoother gradients with bytes. On flat graphics, turn it off.

Check the size before you export, not after

Most tools make you export to find out how big the result is, which turns tuning into guesswork with a download between each attempt. An estimate built by genuinely encoding a few sample frames and extrapolating across the timeline removes that loop entirely.

With the number in front of you the order of operations becomes obvious: shrink the canvas, cut the frame count, then reduce colours, checking after each. Usually the first two get you where you need to be and the third is not necessary.

When not to make a GIF at all

GIF is a 1987 format with a 256-colour ceiling and no motion compensation between frames. A five-second video clip that is 3 MB as a GIF is often under 300 KB as MP4 or WebM, at better quality.

If the destination accepts video — and Slack, Discord, most documentation tools and every social platform now do — exporting MP4 instead is a ten-fold improvement you cannot reach by tuning. Keep GIF for the places that genuinely need it: email clients, old wikis, and anywhere a file has to play inline and loop with no player at all.

Try it in the editor

Everything described here runs in your browser, on your machine.

All guides