Why your GIF is huge (and why that's fixable)
GIF is an old, stubborn format. It can't do real video compression, so every frame is stored close to whole, and the file grows with four things at once: how long the clip runs, how many frames per second, how many colors, and how many pixels wide the thing is. Shrink any one of those and the file shrinks. Shrink them in the right order and it shrinks a lot, with almost no visible cost. To make a small GIF from video, you pull those four levers in sequence and watch the number move.
The mistake most people make is reaching for one big hammer (usually downscaling into a postage stamp) and calling it done. You don't need the hammer. You need a few small, deliberate cuts, each made while watching the live estimated size tick down. What the GIF runs the whole thing in your browser tab, so you can try a setting, read the number, and undo it in seconds. Nothing is uploaded, nothing is queued on a server, and there's no file-size cap waiting to reject your export.
The four levers, biggest payoff first
Pull them in roughly this order. Each one moves the size meter, and the first two cost you almost nothing in quality.
- Trim the clip. This is the lever nobody respects and it's the strongest one. A GIF that runs 8 seconds is roughly twice the file of the same GIF cut to 4. Use the frame-accurate timeline to set tight in and out points, nudging by single frames with the arrow keys so you keep only the beat that matters. Two seconds of the right thing beats six seconds of buildup.
- Drop the frame rate. GIFs are not film. Most clips read as perfectly smooth at 10 to 15 fps, and dropping from 30 to 12 can roughly halve the size on its own. Use the low end for slow or talky footage, the high end for fast motion where you'd otherwise see strobing.
- Cut the colors. A GIF tops out at 256 colors anyway. Reduce the palette to 64 or 128 and most footage looks identical while the file gets meaningfully lighter. If banding shows up in gradients or skin tones, nudge dithering up a touch to hide the seams.
- Downscale last. Halving the width quarters the pixel count, so resize is brutal and effective, but it's also the most visible change. Do it last, once trim, fps, and colors have already done their work. A demo at 720 or 600 px wide is usually plenty; you rarely need a GIF at full 1080.
Hitting a specific target size
Most real limits land in a narrow band. Reddit and Slack are comfortable under 2 to 5 MB. A GitHub README or a docs page wants the smallest thing that still reads. Email is the strictest room you'll work in: keep it lean and treat ~5 MB as a hard ceiling, because heavy GIFs trip Gmail's message clipping and burn mobile data.
The workflow is the same regardless of the number. Set your levers to a sane starting point (12 fps, 128 colors, trimmed tight), read the estimate, then pull the next lever and read it again. Because the math runs locally, the size readout updates as you go instead of after a slow round-trip to someone's server. If you're close, a slightly tighter trim or one more fps usually closes the gap. If you're way over, downscale and you'll drop a tier instantly. This is exactly the loop behind a clean Reddit GIF or a lightweight README demo that loads before anyone scrolls past it.
Don't oversmash it
Smaller is a means, not the goal. The goal is the smallest file that still does its job, and it's easy to overshoot into a muddy, juddery mess that nobody can read. A few guardrails:
- Don't go below ~8 fps unless the clip is nearly static; under that, motion starts to stutter and looks broken rather than economical.
- Don't drop under ~32 colors on anything with gradients or faces; that's where banding gets ugly and dithering can't fully save you.
- Resize, don't crop, when you only need fewer pixels. Cropping changes the composition; downscaling keeps the whole frame, just smaller. If you do want a tighter composition, the crop tool locks to exact ratios (1:1, 9:16, 4:5, 4:3, 16:9) so nothing stretches.
- If quality matters more than the last megabyte, trim length instead of crushing the palette, and let dithering carry the gradients.
Works with whatever you've got
You bring an already-recorded video file and drag it in. The converter reads MP4, MOV, WebM, AVI, MKV, M4V, and anything else your browser can decode, so a phone clip, a screen recording, or a meeting export all work the same way. It runs entirely client-side on Mac, Windows, ChromeOS, and Linux, in Chrome, Safari, Firefox, or Edge, with no signup, no watermark, and no install.
Once the page has loaded, you can even pull the tab offline and keep working; the conversion never touched a server to begin with. Drag in a file and start cutting size in the converter.