Convert MOV to GIF

This is the advice that improves the result most and it is not a setting. The frames are taken from the start of the file with no offset available, and a phone clip essentially always begins with a hand moving away from the shutter and a half-second of the wrong thing in frame. The GIF opens on that, loops back to it, and looks like a mistake.

The Photos app on an iPhone and the Photos app on Windows both shorten a clip by dragging two handles, without re-encoding anything, in about ten seconds. Cut to the part that is actually funny or actually shows the fault, and everything else on this page becomes easier — the file is smaller, the ten-second default stops being a constraint, and the loop lands on the right moment.

The gap here is larger than for any other source. A recent iPhone records 4K at 30 or 60 frames a second: 3840 pixels wide, up to sixty complete images every second, in a codec that describes most frames as small differences from their neighbours. The GIF you are about to make is 480 pixels wide at twelve frames a second, with each frame stored whole and limited to 256 colours.

That is not the converter being conservative. It is the format: GIF was defined in 1987 for pictures of a few hundred pixels, has no motion compensation and no concept of a shared palette across a sequence. Twelve frames a second is the lowest rate that still reads as motion, 480 pixels is what fits in a chat window, and ten seconds is where the size curve turns unpleasant.

The three controls multiply against each other almost exactly. Doubling the frame rate from twelve to twenty-four doubles the number of complete images and roughly doubles the file. Going from 480 pixels wide to 800 is about 2.8 times the area and lands close to that in bytes. Doubling the length doubles everything.

So the cheapest improvement is almost never the frame rate. Twelve frames a second looks fine on anything that is not fast panning, and the same budget spent on width makes text legible and a face recognisable. Start at the defaults, look at the result, and change one thing.

A phone records landscape frames and attaches a note saying which way it was held. The frames are read here with that note applied, so a portrait clip becomes a portrait GIF at, for example, 480 by 854 rather than a landscape one lying on its side.

It is worth stating because it is not universal. Plenty of tools that build GIFs from video read the raw frames and ignore the rotation, and the sideways result gets blamed on the phone or on the person who filmed it. Here the only thing to watch is the file size, because a tall 480-pixel-wide GIF has more pixels per frame than a wide one at the same width.

The length control accepts up to sixty seconds and there is a hard limit of 600 frames behind it. At the default twelve frames a second that is fifty seconds; at twenty-four it is twenty-five; at thirty it is twenty. Ask for more and the GIF is simply shorter than you asked for, with no error.

The limit exists because the encoder holds the frames while it works and a browser tab runs out of memory before a longer sequence finishes. In practice it rarely binds, because a GIF long enough to hit it would be tens of megabytes and refused by whatever you were pasting it into. If you are near the ceiling, the honest answer is that you want a video.

A GIF frame indexes into a palette of at most 256 entries. Here a palette is computed for each frame separately rather than once for the whole clip, which costs a little size and is the only version that survives real footage — a single global palette renders everything after a cut in the colours of what came before it.

There is no dithering. Dithering hides banding by scattering pixels between two palette entries, and it also destroys the frame-to-frame similarity that makes a GIF compress at all, so a dithered GIF of video is substantially larger. The consequence is visible on gradients: a sky, a painted wall, a cheek in soft light will show bands. Footage with texture in it — grass, fabric, a busy room — hides the effect almost entirely.

GIF has no audio track and never has. On a screen recording that is usually irrelevant; on something filmed on a phone it frequently is not, because half of what made the clip worth keeping was somebody laughing or a thing making a noise.

Watch the clip once with the sound off before you convert. If it still works, the GIF is the right answer. If it does not, the destination is the thing to change rather than the format — most chat applications and issue trackers now accept an MP4 upload even when they only display GIFs inline, and an MP4 of the same clip is smaller, sharper and audible.

Places that render an image and refuse a video player: an old forum, a wiki that only allows images, a README on a service without a player, an email signature, a bug tracker whose preview only handles pictures, a chat client that autoplays GIFs and not video. In those, a GIF that plays without being clicked beats a video nobody can see.

Everywhere else, converting the same clip to MP4 gives a file perhaps a twentieth of the size with all its colours and its sound. It is worth checking what the destination actually supports before spending effort on the palette, because the answer has changed on most platforms in the last few years.

Every step runs locally: the MOV is demuxed, the frames are decoded by the machine’s own video decoder, each one is quantised to its palette and the GIF is assembled in memory. Nothing carrying the clip is sent anywhere, which the network tab will show you.

The usual alternative is worth naming. Most GIF-making sites upload the video, keep the result on their own domain and give you a link, which means a clip of your kitchen, your children or your employer’s software now lives on somebody else’s server with a URL that can be guessed. Here you get a file, and it is the only copy.