Convert WebP to GIF

They are pushed into it. A form rejects the file with a message listing three extensions. A forum refuses the upload. A content management system from 2014 does not recognise the format. A colleague’s software will not open it.

And nobody chose the WebP either — it arrived because a website served one and the browser saved what it was given. The whole exercise is getting back to a format that predates the problem, which is a legitimate thing to need and worth being clear-eyed about.

A GIF stores a palette of at most 256 colours and every pixel must be one of them. WebP stores millions. So the conversion has to choose 256 colours to represent the whole image and map everything onto them.

On a logo, an icon or a flat graphic that is plenty — the image may already use fewer. On a photograph it is not close: skies band into visible stripes, skin tones go blotchy, and smooth gradients break into steps. Dithering scatters the error to make the banding less obvious and adds a speckled texture in exchange. There is no setting that avoids the trade, because the limit is the format.

This is the second visible loss and it catches people out. WebP has a real alpha channel with 256 levels, so an edge can fade and a shadow can be half-present. GIF allows one palette entry to stand for "invisible", and the encoder on this page writes no such entry — so the GIF you download has no transparency of any kind.

What happens instead is a fill. The see-through areas take the background colour set above the drop zone, white unless you change it, and the palette is chosen afterwards, so a soft shadow blends into that colour rather than turning solid or vanishing. Set it to the colour the image will sit on and the cut-out still reads correctly; leave it wrong and the logo arrives inside a rectangle. If the transparency itself has to survive, PNG is the format to convert to instead.

Said plainly, because it changes what to expect from an upload. The decoder behind this page reads still images only — there is no component that unpacks an animation into frames — so an animated WebP does not produce a one-frame GIF. It produces a readable error, and the file is not converted at all.

That is deliberate: a clear refusal beats a silent GIF holding one frame nobody asked for. If a single frame is genuinely what is needed, open the WebP in a browser, pause it on the frame that matters and screenshot it — that still image converts here without any trouble. There is no conversion on this site that keeps the motion; a WebP that has to stay animated should stay a WebP.

GIF compresses with LZW, a general-purpose scheme from the 1980s that knows nothing about pictures. WebP uses techniques borrowed from video compression, twenty-three years later.

So the same image is usually bigger as a GIF, sometimes by several times, despite having fewer colours in it. That is worth expecting rather than treating as an error: this conversion trades quality and size for acceptance, and gets nothing back except the acceptance.

Before converting to GIF, check what the form or the program actually accepts. PNG and JPG are accepted essentially everywhere GIF is, and both are better in every dimension that matters here.

PNG keeps every colour and the full alpha channel, so a logo or a screenshot comes across untouched. JPG is right for a photograph — far smaller than a GIF and without the banding, at the cost of a small lossy step that a photograph absorbs easily. GIF is the right choice only when something specifically names it, which in 2026 usually means a system that has not been updated in a decade.

If a content system refuses WebP, it usually refuses all of them. Drop the whole folder: each file converts in turn on your own machine with its own progress, keeps its name with the extension swapped, and everything comes back as a single ZIP.

Keep the WebP originals. They are the better files, and if the system is ever updated — or the images are needed for something else — regenerating from the original beats converting a converted copy, which would compound the colour reduction that has already happened.

The conversion runs in the browser tab on your own processor, so the image never leaves your machine. There is no queue behind other people, no daily count and no account.

Watching the network tab while a batch converts is the honest way to confirm it: no request carrying a file goes out. That is the same property that makes converting a hundred images practical rather than an afternoon of uploads and downloads.