How to turn a video into a GIF

The short version

1. Drop the clip into the converter.
2. Drag the trim handles to the few seconds that matter.
3. Set the width to 480px and the frame rate to 12.
4. Create, look at the preview, save.

Those two numbers are most of the job. The rest of this explains why, so you know when to break them.

Why GIFs get enormous

GIF was designed in 1987 and it does not compress across frames. A modern video codec stores one full frame and then only what changed; GIF stores every frame as its own image, palette and all. That is why a five-second clip that is 400 KB as an MP4 can be 8 MB as a GIF.

Three levers control the size, and they multiply rather than add:

• Length. Doubling the clip doubles the file. Trim ruthlessly. Almost every GIF worth sharing is under four seconds.
• Width. Halving the width quarters the pixel count. 480px is plenty for a chat window or a README.
• Frame rate. 10 to 15 fps looks smooth for screen recordings and dialogue. Below 8 it stutters. Above 20 the file grows fast for almost no visible gain.

The 256 colour problem

Every GIF frame is limited to a palette of 256 colours. For a screen recording of an interface, that is usually invisible, because a UI genuinely uses few colours. For anything with a gradient, a sunset, skin tones or a blur, you will see banding: smooth transitions turn into visible steps.

If your source is a real-world video and the result looks blotchy, that is the palette and not the encoder. Nothing in any tool fixes it, because it is the format. The answer is to use a video.

When not to make a GIF

GIF has one genuine advantage left: it plays automatically, silently and inline anywhere an image can appear, including email clients and old forums. If you do not need that, a short MP4 or WebM is smaller, sharper, and supports sound.

• For a README or documentation: GIF, because GitHub renders it inline and a video needs a click.
• For a website: a muted, looping, autoplaying MP4 or WebM. It will be a fraction of the size and will not look banded.
• For a chat or a message: GIF, usually, because it loops without being tapped.
• For anything with sound: not a GIF. GIF has never supported audio and never will.

Doing it without uploading the clip

Most free converters upload your video, encode it on a server, and hand back a file with a watermark or a length cap. That is a reasonable business model and a bad idea for a screen recording of your own dashboard, an internal demo, or anything under NDA.

Encoding in the browser avoids all of it. There is no upload, no queue, no watermark and no length cap beyond what your device memory can hold. On a phone, keep the width at or under 480px, because GIF encoding is memory-hungry and a long clip can exhaust a mobile browser.

Getting a good source clip

Most GIFs start as a screen recording. Record at the size you intend to publish rather than recording the whole 4K display and scaling down afterwards, because the downscale softens text. Record the window, not the desktop. If you need a recorder that does not install anything or stamp a logo on the output, the browser screen recorder handles it.

Questions