A GIF is the internet’s universal “watch this” — it autoplays inline in chat, issue trackers, and docs with no player and no click. It’s also, technically, a terrible video format that can produce a 40 MB blur if you’re not careful. Here’s how to make one that’s small, sharp, and worth sending.
Short answer: Keep it short (under ~6 seconds), shrink the dimensions, and drop the frame rate to 10–15 fps. Feed your clip to the Video → GIF tool, trim to the moment that matters, and it converts in your browser — no upload.
Why GIFs get huge and grainy
A GIF isn’t really compressed like a video. It stores frames as a sequence of images, each limited to a 256-color palette, with none of the motion-based frame-to-frame compression that makes MP4 efficient. Two consequences:
- Size explodes with length, pixel dimensions, and frame rate. Double the length or frame rate and the file roughly doubles; double the width and it roughly quadruples, because dimensions scale with area.
- Color suffers. Video footage and smooth gradients get banded or speckled (dithered) down to 256 colors.
That’s why a GIF of real video can be larger than the video it came from, and look worse. The art is spending your bytes wisely.
The four dials that control size
| Dial | Effect | Good default |
|---|---|---|
| Length | Biggest lever — linear with size | Under 6 seconds |
| Dimensions | Size scales with area (2× width ≈ 4× bytes) | 480 px wide or less |
| Frame rate | Fewer frames = smaller file | 10–15 fps |
| Content | Flat UI compresses well; busy video doesn’t | Prefer simple motion |
The single most effective move is trimming. A GIF exists to show one repeating moment — cut to exactly that, and everything else gets easier.
Making a good one
- Open the Video → GIF tool and load your clip.
- Trim to the few seconds that matter.
- Keep the width modest (480 px is plenty for inline viewing) and the frame rate low (10–15 fps looks fine for most motion).
- Export. It converts locally, so a private screen recording never gets uploaded.
Where GIFs come from
The most common source is a screen capture — a bug repro, a “click here then here” demo. Record it first (see how to record your screen, no install), then convert the short clip to a GIF for pasting into an issue or a chat. GIF is perfect for that: silent, looping, no player needed.
When a GIF is the wrong tool
Reach for something else when:
- It has sound. GIFs are silent. If the audio is the point, keep the video — or if you only need the audio, extract it to MP3.
- It’s long or color-rich. A 30-second product demo or anything with rich footage should stay an MP4 — dramatically smaller and sharper. Most chat apps autoplay short muted videos now anyway, eroding the GIF’s old advantage.
- You need crisp text or detail. The 256-color limit smears fine detail; a video or even a still image serves better.
Use a GIF for what it’s uniquely good at — a short, silent, looping moment that plays anywhere — and it’s unbeatable. Push it past that, and you’re emailing a grainy 40 MB file that a 3 MB video would have beaten on every axis.