The fastest free way to make a GIF from a video: open a client-side converter like the MP4 to GIF tool, drop the clip in, trim to a few seconds, set the width to 480 px and the frame rate to 12 fps, and download. No watermark, no sign-up — and because the conversion runs in your browser, the file never gets uploaded anywhere.
That covers 90% of GIF-making. The rest of this guide covers the settings that decide whether the GIF looks good and stays small, plus the two power methods — FFmpeg’s palette technique and Photoshop — and the case where the right answer is not making a GIF at all.
What Settings Make a Good GIF?
GIF is a 256-color format from 1989 with no motion compression, so file size explodes with resolution, frame rate, and length. Every good GIF is a deliberate trade across those three:
| Use case | Width | Frame rate | Length |
|---|---|---|---|
| Chat reaction (Discord, Slack) | 360–480 px | 10–12 fps | 2–6 s |
| GitHub README / docs demo | 640–800 px | 10–12 fps | 5–15 s |
| Tutorial snippet with UI text | 800 px | 12–15 fps | Under 10 s |
| Smooth motion showcase | 480 px | 15–20 fps | Under 5 s |
Two useful non-obvious facts hide in that table. First, 12 fps looks fine in a GIF even though it would stutter as video — viewers read GIFs as loops, not footage. Second, text stays sharp at low widths because GIF is lossless per frame; a 640 px screen recording keeps its UI text readable where a 640 px H.264 video would smear it.
Method 1: In-Browser Converter (Fastest, Private)
The MP4 to GIF and WebM to GIF converters run FFmpeg compiled to WebAssembly inside your browser tab:
- Drop in the video (MP4/M4V in the first tool; WebM screen recordings in the second).
- Trim to the exact seconds you need — this is the biggest file-size lever you have.
- Set width and frame rate from the table above.
- Convert and download.
Two things distinguish this from the ad-cluttered upload sites that dominate search results. The files are processed on your own device — nothing is uploaded, which matters for anything work-related or private. And the conversion uses the two-pass palette technique (below), generating a custom 256-color palette from your actual footage instead of a generic one, which visibly reduces banding.
iPhone footage note: these tools take MP4 and WebM, so run a MOV clip through the MOV to MP4 converter first — same tab, same no-upload deal.
Method 2: FFmpeg with a Custom Palette
On the command line, the naive ffmpeg -i in.mp4 out.gif produces the murky, dithered GIFs that give the format a bad name, because FFmpeg maps your footage onto a generic palette. The fix is a two-pass encode — generate a palette from the footage, then encode with it:
ffmpeg -i input.mp4 -vf "fps=12,scale=480:-1:flags=lanczos,palettegen" palette.png
ffmpeg -i input.mp4 -i palette.png -filter_complex "fps=12,scale=480:-1:flags=lanczos[x];[x][1:v]paletteuse" output.gifAdjust fps= and scale= to taste, and add -ss/-t before the input to trim. The palettegen filter documentation covers the deeper options — stats_mode=diff prioritizes moving areas, and paletteuse dithering modes trade grain patterns for banding. This is the method behind most “how does that GIF look so good” results, and it’s fully scriptable for batch work.
Method 3: Photoshop
Photoshop earns its place when you want to edit frames — add text, crop non-destructively, delete a stray frame, tweak timing per frame:
- Open the video directly (File → Open); it arrives as a video layer with a timeline.
- Trim the work area to the seconds you want.
- File → Export → Save for Web (Legacy) → GIF, 256 colors, and set Looping Options to Forever.
- Watch the size readout in the corner of the dialog and drop colors to 128 or the image size down until it’s acceptable.
The obvious catch: Photoshop is subscription software, so it’s only “free” if you already pay for it. For straight video-to-GIF conversion, it produces no better result than the palette methods above.
Which Method Should You Use?
| In-browser tool | FFmpeg | Photoshop | Upload sites | |
|---|---|---|---|---|
| Cost | Free | Free | Subscription | “Free” |
| Watermark | None | None | None | Often |
| Privacy | File stays on device | File stays on device | Local | Uploaded to server |
| Control | Trim, size, fps | Everything, scriptable | Frame-level editing | Varies |
| Best for | Nearly everyone | Batch and pipelines | Frame edits, text | Nothing, honestly |
Making the Loop Look Intentional
Whichever method you use, the loop point is where good GIFs separate from lazy ones. Trim so the last frame nearly matches the first — the end of a repeated motion, a hand leaving the frame, a UI returning to its resting state — and the GIF reads as a designed loop instead of a clip that runs out and snaps back. When the footage offers no natural loop point, the palindrome trick works on almost anything: play the clip forward then reversed (FFmpeg can concatenate a reversed copy), and the motion rocks back and forth seamlessly forever.
When You Shouldn’t Make a GIF at All
If the destination is a website, Twitter/X, or anywhere that accepts video, an MP4 does the same job at 5–10% of the file size — H.264 stores differences between frames while GIF stores every frame whole, in 256 colors. A muted, looping, autoplaying <video> tag behaves exactly like a GIF and loads ten times faster; most platforms silently convert uploaded GIFs to video anyway. The full breakdown of when each format wins is in GIF vs MP4: Which Is Better for Animations?
GIF still wins where autoplay-without-a-player is the point: GitHub READMEs, Slack and Discord chat, docs, and email — the places the table at the top of this article is built for.
FAQ
How do I make a GIF from a video without a watermark?
Use a client-side converter (the MP4 to GIF tool above adds no watermark and never uploads your file) or FFmpeg’s two-pass palette method. Watermarks are a monetization tactic of upload-based converter sites, not a technical requirement of the format.
Why is my GIF bigger than the video it came from?
GIF has no motion compression — every frame is stored as a full indexed image, so a GIF routinely runs 5–10× the size of the source MP4. Shorter clips, smaller widths, and lower frame rates are the only real levers.
What frame rate should a GIF be?
10–12 fps for most content; up to 15–20 fps only for short, smooth-motion showcases. GIFs read as loops rather than footage, so frame rates that would look choppy in video look normal here — and each dropped frame is a direct file-size saving.
How do I make a GIF from an iPhone video?
Convert the MOV to MP4 first (a client-side MOV to MP4 converter keeps it off any server), then run the MP4 through the GIF converter with the usual settings — 480 px wide, 12 fps, a few seconds long.
Can a GIF have sound?
No — the format has no audio track at all. If the clip needs sound, share it as an MP4 instead; every chat platform that autoplays GIFs also plays short MP4s, just with a tap or click.
