Convert GIF to MP4

The whole difference is one idea: motion compensation. A video encoder stores one complete frame and then, for each frame after it, records only what changed. An animation of a logo moving across a static background costs almost nothing after the first frame, because almost nothing is different.

GIF has no such mechanism. It stores every frame as a whole picture, one after another, with at most 256 colours each. That design is from 1989 and has never changed, which is why a five-second GIF can outweigh the minute-long video it was cut from. Converting does not compress the same file better — it stores the same animation in a fundamentally more efficient way.

Upload a GIF to Twitter, Reddit, Discord or most messaging apps and it does not stay a GIF. It is converted to video on arrival, silently, and served back as one. The little "GIF" label you see is a label; the file behind it is MP4.

They do this because bandwidth is their cost, not yours. Doing it yourself before uploading means you control the quality setting rather than accepting theirs, your page loads faster if you are hosting it, and you find out now rather than later whether the animation survives the conversion — which it does.

A GIF autoplays, loops and has no controls, and people reasonably expect a replacement to do the same. A video element does all of it, but only if you ask: `autoplay`, `loop`, `muted` and `playsinline`. The muted attribute is the one that catches people out — every browser refuses to autoplay video with sound, and a GIF replacement has no sound anyway, so there is nothing lost by declaring it.

Without `playsinline`, iOS opens the video full screen instead of playing it in place, which is the other common surprise. With all four, the result is indistinguishable from a GIF except that the page loads faster.

The colours were already reduced. A GIF holds at most 256 per frame, and whatever banding that caused is baked into the frames the encoder receives. The MP4 stores them faithfully and does not add a palette of its own, so the animation does not get worse — but it does not get back what the GIF discarded when it was made.

If you have the original video that the GIF was cut from, converting that directly will always look better than converting the GIF. This page is for the common case where the GIF is all you have.

Ten to thirty times smaller is the ordinary range, and it widens the more static the animation is. A screen recording of a menu opening — mostly unchanged pixels — can be fifty times smaller. A burst of confetti where every pixel moves is nearer five.

The other saving is the one people forget: a GIF has to be downloaded in full before it plays properly, while a video starts on its first frames. On a phone, that is often the difference anyone actually notices.

A GIF sets a delay per frame in hundredths of a second, and nothing requires those delays to be equal. So GIFs routinely run at rates no camera ever produced — 12.5 frames a second, or a mixture of rates inside one file.

The conversion holds that timing rather than rounding it to something tidy, which keeps the animation running at the speed it was made to run at. If it looked right as a GIF, it looks right as an MP4.

A GIF can declare one colour transparent. MP4 has none at all, so those pixels have to become something, and here they become black: each frame is drawn onto a cleared canvas and a fully transparent pixel reaches the encoder as zero in all four channels. This pair offers no background colour to choose — the only control on it is quality.

For most GIFs that changes nothing, because most have an opaque background already. For a logo animation meant to sit on a coloured page it changes everything, and a black rectangle is rarely the colour anyone would have picked. If the transparency is the point, animated WebP keeps it and still plays in every browser.

The honest limit on this conversion is that a few places still take only a GIF: some forums, older ticketing systems, certain email signatures, and any context where the thing has to be an image rather than an embedded player.

It is a shrinking list and worth checking rather than assuming. The major chat and social platforms all convert to video on upload anyway, so sending them a GIF only means they run this conversion instead of you.

The GIF is decoded and the video encoded inside your browser, using the machinery it already has for playing media. There is no server involved, no queue and no account.

That matters more than it sounds for this pair, because a great many GIFs are screen recordings — a bug being reproduced, a workflow being demonstrated — and a screen recording picks up whatever else happened to be on the screen.