Turn a video clip into a GIF, free and in your browser

Why a GIF still beats a video sometimes

GIF is an old format. It was designed in 1987, it holds a maximum of 256 colours per frame, it has no sound and it compresses badly by any modern standard. By every technical measure a short MP4 is better.

It survives anyway, and for one reason. A GIF plays instantly, everywhere, without a play button. Drop one into a chat, a bug report, a pull request or a forum post and it starts moving the moment somebody scrolls past. A video sits there as a still frame waiting for a click that often never comes.

That is the whole trade. You are giving up colour depth, sound and file size in exchange for something that shows itself without being asked. For a three second demonstration of a bug, a reaction, or a quick before and after, that is usually worth it.

What people actually make GIFs for

• Bug reports and support tickets. Showing the crash is faster than describing it, and every issue tracker displays a GIF inline.
• Product and feature demos. A five second loop of a button doing its job explains more than a paragraph.
• Documentation and tutorials. A short loop of the exact click sequence saves readers from guessing.
• Reactions and jokes. The original use, still the most common one.
• Social posts. Some platforms autoplay video, others do not. A GIF moves regardless.
• Email. Video does not play in most email clients. A GIF does.

The three settings that decide everything

File size is where GIFs go wrong, and it comes down to three numbers that multiply together rather than add. Understanding them turns an eleven megabyte accident into a tidy one megabyte loop.

Width

The strongest lever by a distance. Halving the width also halves the height, so you remove roughly three quarters of the pixels in one move. Going from 640 to 320 does more for file size than any other change you can make. Most GIFs are viewed in a small column on a phone, so a width you think is too small is usually about right.

Frame rate

Frames a second is a straight multiplier. Twenty frames is twice the data of ten. Screen recordings of interfaces look perfectly fine at ten, because flat colours moving in straight lines do not need smoothness. Anything with real motion, a person walking or a camera panning, starts looking jerky below fifteen.

Length

Also a straight multiplier, and the easiest to be disciplined about. Almost every GIF is longer than it needs to be. Find the moment that matters and cut a second before and a second after it. Under four seconds is a good target and under two is often enough.

Aiming for a size that actually gets accepted

Most chat apps and forums start refusing or silently downgrading somewhere around five megabytes. Issue trackers and email are stricter, often around two. If your GIF is going anywhere near an email, treat two megabytes as the ceiling and be pleased when you land under one.

The estimate on this page updates as you change the settings, which is the point. You find out that 640 pixels at 20 frames for eight seconds will be enormous before you sit through building it, not after. If the finished file still comes out heavy, work through the levers in order: shorten it first, then drop the width, then lower the frame rate. That order preserves the most of what makes the clip readable.

Why it looks grainier than the video did

A GIF can show 256 colours in a frame. Your video holds millions. Squeezing that down is not something a better tool can avoid, because the limit is written into the format itself.

Where it shows is predictable. Smooth gradients break into visible steps. Skies band. Skin tones go patchy. Shadows turn blotchy. Flat colours, on the other hand, survive perfectly, which is why screen recordings of software look almost identical to the original while footage of a sunset does not.

One thing does help, and it is what this tool does. Each frame gets its own palette of 256 colours chosen for that frame, rather than one palette stretched across the whole animation. It costs a little in file size and it removes a great deal of the banding, especially when the scene changes as the clip plays.

Things that make a clip harder to convert

• Camera movement, because every pixel changes on every frame.
• Film grain and video noise, which look random and compress terribly.
• Slow fades and dissolves, which are pure gradient.
• Dark scenes, where banding is most visible.
• Anything already heavily compressed, since the artefacts get preserved faithfully.

Clips of interfaces, text, diagrams and flat illustration are the opposite. They convert beautifully and stay small.

Trimming well

Drag the two handles to the section you want, or scrub the video to a moment and mark the start or end from where you are. That second method is usually faster when you are hunting for a precise instant.

Two habits are worth building. Start slightly before the action rather than exactly on it, because a loop that begins mid movement is disorienting. And end on a frame that resembles the first one, since the GIF jumps straight back to the beginning. A clip that ends where it started loops seamlessly. A clip that ends somewhere completely different flickers on every repeat, which viewers notice even when they cannot say why.

What GIFs cannot do

Being clear about this saves time.

There is no sound. The format has no provision for audio at all, so no tool can add it. If the sound matters, use a short video, or pull the audio out separately with our video to MP3 tool and share it alongside.

There is no partial transparency. A pixel in a GIF is either fully visible or fully invisible, which is why cutouts saved as GIF get hard jagged edges. PNG and WebP handle soft edges properly, so anything needing a clean cutout belongs in one of those.

Long clips do not work. Not because a tool forbids it, but because a thirty second GIF is a file nobody wants to load. This one stops at 450 frames and tells you before you start rather than after you have waited.

Which formats open here. MP4, MOV, M4V and WebM, because those are what browsers can play. MKV, AVI, WMV and FLV are not supported anywhere in a browser and need converting to MP4 first.

How the frames are taken, and why it matters

There are two ways to get frames out of a video in a browser. You can play it and grab whatever the screen shows as it goes, which is fast, or you can move the video to each exact timestamp and take the picture there, which is slower.

The quick method produces uneven results. Frames arrive whenever the browser happens to deliver them, which varies with the device, the codec and how busy the machine is. On some browsers it drops frames silently and the GIF plays at the wrong speed.

This tool seeks to each timestamp instead. It takes longer on a long clip, and in exchange the frames are evenly spaced on every browser, so the finished GIF runs at the speed you asked for rather than approximately.

Nothing is uploaded

It is worth pausing on what people usually turn into GIFs. Screen recordings of internal software. Unreleased features. Customer support sessions. Bug reproductions that show real account data on screen. That is company material, and the ordinary route is to upload it to a free website you know nothing about.

Here the clip is opened by your own browser and the GIF is written on your own machine. Nothing goes out. You can open the network panel in your developer tools and watch while it runs if you would rather see it than be told. Once the page has loaded it keeps working with the connection off, and there is nothing to delete afterwards because nothing was stored anywhere.

There is also no watermark, no account, no queue and no length limit sold back to you as a premium tier. When the GIF is finished, the rest of the video and audio tools handle whatever comes next, and if you need still images rather than a loop the image compressor is the one you want.