What the GIFvideo → gif, the way creatives need it
// size intent

Make a small GIF from video without making a bad one

A clip running 8 seconds at 30 fps holds 240 frames. Trim it to 3 seconds at 12 fps and 36 remain, an 85 percent cut before you have touched colors or width. Small GIFs are made with arithmetic, not luck.

Drop a video, get a GIF free · frame-perfect · nothing leaves your browser Open the converter →

How to make a small GIF from a video

What the GIF does the whole thing locally, right in your browser: nothing here ever leaves your machine.

  1. Load a clip. Drop the file in. If the browser can play it (MP4, MOV, WebM, AVI, MKV, M4V), the tool can shrink it, and local decoding means no queue and no transfer time.
  2. Cut the length first. Runtime is the strongest multiplier. Tighten the trim around the single beat that matters; for the boundaries, the arrow keys move one frame per tap.
  3. Halve the frame rate. Take 30 fps footage down to around 12. The motion still reads, and the frame count, and with it the file, drops by more than half.
  4. Thin the colors. Set the palette at 128, or 64 for flat footage. If a gradient starts striping, a little dithering papers over the seam.
  5. Downscale if still over. Cutting the width in half removes three quarters of the pixels. It is the most visible lever, which is why it goes last rather than first.
  6. Check the number, then export. When the size readout sits under your target, often 2 to 5 MB, convert and save. Nothing was uploaded at any point in the process.

File size is four multipliers

GIF cannot compress motion the way video codecs do, so each frame is written out close to complete. The consequence is a file that grows as the product of four quantities: seconds of runtime, frames per second, pixels per frame, and colors in the palette. Reduce any one and the whole product falls; reduce them in the right order and it collapses, mostly without visible damage.

The common mistake is swinging one giant hammer, usually scaling the clip into a postage stamp, and accepting the mush. You get better results from several small cuts, each checked against the size readout before making the next. What the GIF keeps that loop fast because everything runs locally: change a setting, read the new number, keep or revert, with no round trip to anybody's server between attempts.

Pull the levers in this order

Working to a number

Real-world ceilings cluster tightly. Slack and Reddit stay comfortable somewhere under 2 to 5 MB. A GitHub README just wants the smallest file that still communicates. Email is the strictest room of all: senders commonly aim for roughly 500 KB to 1 MB per GIF, because total message weight drags on deliverability and every kilobyte counts against it.

Whatever the target, the procedure does not change. Start from sane defaults (tight trim, 12 fps, 128 colors), read the estimate, pull the next lever, read again. Close to the line? One more second off the trim or a couple of fps usually finishes the job. Far over? Downscale and you drop a whole tier at once. And when even a disciplined GIF refuses to duck under the ceiling (a busy ten-second clip that has to land near 1 MB, say), stop arguing with 1989: the Output Format switch exports the same edit as a silent H.264 file, where motion compression does the shrinking for you and a bitrate control sets the budget directly. The switch shows up in browsers with a built-in encoder (Chrome, Edge, Safari, with Firefox varying), and the encode is as local as the GIF one.

Where small tips into broken

The goal is the smallest file that still does its job, and overshooting is easy. Guardrails worth keeping:

Any file, any machine

Bring whatever recording you have: MP4, MOV, WebM, AVI, MKV, M4V, plus whatever more obscure formats your browser happens to decode. Phone clips, screen captures, and meeting exports all follow the identical four-lever path, on Mac, Windows, ChromeOS, or Linux, in any of the major browsers, without an account or a watermark entering the picture. An overweight GIF itself qualifies too: drop it in and the same four levers re-encode it lighter, no original video required.

The processing never involved a network to begin with, so after the page loads you could cut the connection entirely and keep exporting. Your video stays on your disk, your GIF appears next to it, and nothing in between saw either one.

Pick a number, then hit it.

Trim, drop the frame rate, thin the palette, and downscale until the readout ducks under your target. The whole loop runs free in your tab.

Open the converter

Keep going

High-Quality Video to GIFhigh quality video to gif
Video to GIF Without Uploadingconvert video to gif without uploading
MP4 to GIFmp4 to gif
1080p Video to GIF1080p video to gif
4K Video to GIF4k video to gif
Vertical Video to GIFvertical video to gif

Questions, answered

How much can I realistically shrink a GIF?
The same clip can swing from 15 MB to under 2 MB purely through trimming, 12 fps, a 128-color palette, and a narrower width. The floor depends on content: short, calm, simple footage compresses hardest, while long busy full-color video resists. The readout tells you when you have arrived.
Which lever shrinks the file most?
Length, by a comfortable margin, since size scales almost directly with runtime. Frame rate comes second. Downscaling is the most powerful per click but also the only change viewers see immediately, so it earns its place at the end of the sequence.
Will the quality fall apart as it shrinks?
Not if the order is respected. Trimming and 10 to 15 fps are essentially invisible, and 64 to 128 colors passes unnoticed on most footage. Damage appears at the extremes: under about 8 fps motion stutters, and under about 32 colors gradients and faces band.
What target size should I pick?
Let the destination decide. Chat platforms like Slack sit happily under 2 to 5 MB, a README wants the leanest file that still reads, and email is tightest at roughly 500 KB to 1 MB per image. Fix the number first, then pull levers until the estimate slips beneath it. If no combination of levers gets you there, switch the output to MP4 instead; many chat and social destinations take a short silent video just as happily.
Does any of this shrinking happen on a server?
None of it. The decode, the settings math, and the final encode all execute in your browser tab, and the source file never leaves your disk. The only capacity limit is your own machine's memory, and the tool keeps functioning offline once the page is open.
Can I set a target size and have it auto-compress?
No, and deliberately so. A magic target button has to pick which quality to sacrifice for you. Here you get the four real levers plus a live estimate, so you decide whether the file loses length, smoothness, colors, or pixels. It takes a minute longer and produces a better GIF.