Video to GIF

GIF is a format from the late 1980s that was designed for still pictures and small animations, not video. Each frame is stored as its own indexed-color image, compressed with a method that works well on flat areas and poorly on photographic detail. Modern video codecs, by contrast, save a full picture now and then and only record what changes in between. That difference is why a few seconds of video can turn into a GIF many times larger.

Three settings decide most of the size. Width sets how many pixels each frame has, and doubling the width roughly quadruples the pixels. Frame rate sets how many frames there are per second. And the clip's length multiplies everything. Cutting the length in half is often the single most effective change, and nobody watches a ten-second GIF to the end anyway.

Content matters as well. A screen recording with a still background and a moving cursor compresses well, because most of each frame stays the same. Handheld footage, where every pixel shifts a little each frame, is the hardest case. If a GIF of shaky footage comes out too large, lower the frame rate first, then the width.

Batches work the same way as single files. Drop up to 20 clips at once and every one of them gets the same width, frame rate and color settings, which is handy for a set of tutorial steps or product shots that should look consistent next to each other.

The GIF89a specification allows a color table of at most 256 entries for each image, so every frame of your clip has to be described with that small palette. Video frames easily hold hundreds of thousands of distinct colors. The converter builds the best palette it can for the clip and maps every pixel to the nearest entry, which works well for cartoons, interfaces and text, and less well for sunsets, skin and fog.

Colors lets you go lower than 256, to 128, 64 or 32. Fewer colors make a lighter file but show bands where smooth gradients used to be. That can be a reasonable trade for a logo animation or a simple screen capture, and a poor one for a photo-like clip. To hide the bands, the converter can mix palette colors in small patterns:

Width runs from 16 to 1,920 pixels, starts at 480, and the height follows the shape of the video, so a vertical phone clip stays vertical. Think about where the GIF will be seen. In a chat window or a forum post it is shown small, and 480 pixels is already more than most people will notice. In documentation or a bug report where people need to read text on screen, go wider, but keep the clip short to make up for it.

Screen recordings deserve special care. A full desktop recording at its native width makes a heavy GIF with text that is still hard to read once it is scaled down on a phone. Crop or record only the window that matters before converting, then pick a width close to that window's real size. Text stays sharp, and the file stays small because most of the frame does not change.

Going wider than the source never adds detail. If the video is 720 pixels wide, a 1,080-pixel GIF only repeats pixels and adds weight. When in doubt, try the default first, look at the result in the place it will be posted, and step up only if it looks soft.

Speed plays the clip at 0.5×, 1×, 1.5×, 2× or 4×. Speeding up is a neat way to fit a longer action into a short GIF: a 2× clip covers the same events in half the frames, so the file is lighter as well. Slowing down to 0.5× is good for showing a quick moment in detail, at the cost of twice as many frames.

Loop decides whether the GIF repeats forever or plays once and stops on the last frame. Repeating is the norm for reactions and product demos; playing once suits a short tutorial that should end on its final screen. Boomerang plays the clip forward and then backward, which hides the jump between the last and first frame. It doubles the length, so pair it with a short start and end time.

Start at and End at accept seconds such as 12.5 or minutes and seconds such as 0:12. Leave End at empty to run to the end of the video, but for anything longer than a few seconds it is worth setting both.

GIFs play almost everywhere without a play button: chat apps, forums, wikis, bug reports, README files, slide decks and many email clients. That is their main advantage over video. Most social platforms and chat apps, however, set their own limits on GIF size and sometimes convert uploaded GIFs into short videos behind the scenes. If a platform rejects a file, lower the width or the frame rate and try again.

When you control the page, as on your own website, a short muted MP4 or WebM that loops is usually much lighter than a GIF and keeps full color. Video Converter makes such clips and can also save animated WebP or AVIF, which keep more colors than GIF in a smaller file. For a GIF that is already made but too large, the image tools under Image can help, and the most common source format has its own page at MP4 to GIF.

Start by cutting the clip to the few seconds you need with Start at and End at. Keep Width at 480 and Frame rate at 12, then convert once and look at the size. If it is still too large, lower the frame rate to 10 or 8 before touching anything else; slow content hardly changes. Next, lower the width step by step. Only after that, try 128 colors, and switch Dithering to Bayer or None if you need the last bit of savings and the clip has flat colors.

If the GIF has to stay rich in color or longer than a few seconds, it is a sign that a looping video would serve better. Many places that show GIFs also play short muted clips, and they look far better at a fraction of the size.