Convert GIF to MOV

A GIF is an image file that happens to move, and editing applications treat it as one. Premiere Pro will import it, and depending on the version and the file it will either give you the animation or give you frame one held for a few seconds. Final Cut and Resolve are less forgiving still. None of them will let you speed-ramp it, and none of them will conform it to your sequence properly, because none of them consider it footage.

A MOV is the container QuickTime defined in 1991 and the one every professional editing application on macOS was built around. Handing over a MOV moves the animation from the media pool’s awkward corner into the same category as everything else on the timeline: trimmable, retimeable, stackable, and with a duration the application agrees with.

MOV is a container, not a codec, and the format’s own trait list names three that turn up inside one: H.264, HEVC and ProRes. This conversion writes H.264 in the High profile, because that is the pairing every machine can decode without a codec pack and without hardware that only some editors have.

The honest consequence is that this is a delivery-grade clip, not a mastering one. ProRes exists so that a clip can be decoded, re-graded and re-encoded repeatedly without accumulating damage, and H.264 does not do that as gracefully. For a logo loop or a screen capture dropped onto a timeline it makes no practical difference. For something that will go through three more generations of colour work, transcode this MOV to ProRes once in your own application and work from that.

The GIF format stores a delay with every single frame, in hundredths of a second, and nothing requires those delays to match. Animations made by hand routinely hold the first frame for a second and then run the next twenty at 40 milliseconds each. The conversion carries each of those durations through rather than averaging them into a nominal frame rate, so the clip runs at the speed it was authored at.

What a fixed-rate sequence does with that is the part worth planning for. Dropping a variable-duration clip onto a 25 fps timeline means the application snaps each frame boundary to the nearest sequence frame, which is imperceptible on a slow animation and visible as a slight stutter on a fast one. Where a GIF stored a delay of zero — extremely common, and meaning "as fast as the display allows" — the conversion substitutes 100 milliseconds, which is what browsers have always done with it.

A GIF can be any size at all. Nothing in the specification objects to 401 pixels by 237, and web GIFs from the era when they were made by hand are full of dimensions like that. H.264 objects: the encoder requires an even width and an even height and refuses the job otherwise.

So the converter rounds both dimensions up to the next even number before the first frame is drawn. A 401-pixel width becomes 402. Rounding up rather than down is the choice that adds a column of pixels instead of cropping one off the edge of the animation, which on a tightly framed logo is the difference between a hairline border and a clipped letter.

A GIF has never carried sound and there is nothing for the conversion to invent, so the clip arrives with a video track and nothing else. In an editing application that is usually convenient — no empty audio channel to disable, no sync to worry about.

It is worth naming because it changes what happens downstream. Some review and approval platforms reject a video with no audio stream, and some broadcast delivery specifications require a silent stereo pair rather than an absent one. If the clip is going somewhere with a written specification, add the silent track in your editor before export rather than expecting it here.

A GIF frame holds at most 256 colours, chosen from a palette written into the file. Whatever gradient, glow or soft shadow the animation originally had was quantised down to that palette at the moment the GIF was made, and dithering was probably used to disguise it.

The MOV stores what it is given faithfully and does not impose a palette of its own, so nothing gets worse. It also cannot get better: no encoder recovers colours that were discarded before it saw the file. Where this shows up on a timeline is in grading — pushing contrast on a banded sky that has only a few distinct values in it exaggerates the bands rather than revealing detail.

A GIF can declare one palette entry transparent, which is how animated logos have sat on coloured backgrounds since the 1990s. The video track written by this conversion has no alpha channel, so that information is not carried through, and this pair offers no background-colour control the way the GIF-to-still conversions on this site do.

If the animation has a transparent background and you need it to stay transparent over a layer beneath it, this conversion is the wrong tool and no setting on it will help. The right answer is the project the GIF was exported from, or a format that carries alpha. If the GIF is all that exists, plan to key or mask the background in your editor.

A very large share of GIFs on the internet were cut from a video in the first place. If that video is findable — the original screen recording, the render out of After Effects, the file the GIF was trimmed from — converting it directly will beat this conversion on every measure, because it never went through the palette reduction.

This page exists for the ordinary case where the GIF is what you were sent and nothing else is coming. That case is common enough on brand assets and support tickets that it is worth doing well, and the conversion loses nothing further than the GIF already lost.

Reading an animated GIF frame by frame is done by the browser’s own image decoder rather than by a library this site downloads. That keeps the file on your machine and keeps the page light, and it is why the conversion starts immediately instead of fetching several megabytes of codec first.

The trade is that the decoder is not present everywhere. Where it is missing, the page says so and names the browsers that have it rather than failing quietly or handing the file to a server. Nothing about the GIF is uploaded in either case — the failure is a message, not a fallback.