Why Your Converted WebP Isn’t Animated (GIF vs WebP Honestly)

You converted a GIF to WebP, downloaded the result, opened it — and nothing moves. The picture is there, it looks fine, but the animation is gone. The natural conclusion is that something went wrong. Usually, nothing did. Your file stopped moving because the converter you used kept only one frame of the animation, and a single frame cannot move, no matter what format it is saved in.

That distinction — between what a format can do and what a particular converter does — answers almost every GIF vs WebP question. WebP as a format supports animation. A first-frame converter does not produce it. Once you keep those two ideas separate, the rest of the comparison falls into place, including which format you should pick next time.

The short answer

GIF and WebP are both image formats that can hold animation, but they come from very different eras and make very different trade-offs. GIF is the older, simpler format: it works everywhere, but it is limited to 256 colours per frame and its transparency is all-or-nothing. WebP is the modern format: it holds millions of colours, smooth transparency, and both lossy and lossless compression, and it usually produces much smaller files.

If your converted WebP is a still image, that is not a WebP problem. It is a converter behaviour: the tool took the first frame of your GIF and saved that one frame as a WebP. To keep an animation, you need a converter that encodes all the frames — and you need to keep the original GIF until you have checked the result.

What GIF actually is

GIF, the Graphics Interchange Format, was introduced by CompuServe in 1987, long before the web as we know it existed. It became the internet’s default animation format almost by accident: it was one of the first formats that could store several frames in a single file and play them in sequence, and every browser supported it.

Its limits are the price of that age. Each GIF frame is an indexed-colour image, which means every pixel points to an entry in a palette of at most 256 colours. A photograph, which may contain millions of colours, has to be squeezed into that palette, and the result is the banding and dithering you see in GIFs of skies and skin tones. Transparency is binary too: a pixel is either fully opaque or fully transparent, so soft edges and shadows come out jagged.

GIF’s compression itself is lossless — it does not throw detail away the way JPEG does — but that label is misleading for photographs, because so much colour information is already lost when the image is reduced to 256 colours. As explained in Lossy vs Lossless Compression: What Actually Changes, GIF is a poor fit for photos despite the “lossless” label.

What GIF has, and has never lost, is universality. It plays in every browser, every email client, and every messaging app, including ones that have never heard of WebP. For a short, simple animation that must work absolutely everywhere, that is still a real advantage.

What WebP actually is

WebP is Google’s modern image format, released in 2010 as a replacement for JPEG, PNG and GIF in a single container. Where GIF is limited to 256 colours, WebP supports full 24-bit colour — about 16.7 million colours — and where GIF transparency is on-or-off, WebP supports smooth, variable transparency, so edges and shadows blend cleanly into any background.

WebP also offers both kinds of compression in one format: a lossy mode for photographs, where a little invisible detail is discarded for a much smaller file, and a lossless mode for graphics, where every pixel is preserved exactly. MDN’s image format guide calls WebP an excellent choice for both still and animated images, and lists support in Chrome, Edge, Firefox, Opera and Safari.

Animated WebP support arrived later than still WebP support — Safari, for example, added it in version 14 in 2020 — which is why older advice still warns about compatibility. In current browsers that warning is largely out of date: every major modern browser now plays animated WebP. The places where compatibility still bites are not browsers but email clients and older apps, which is a distinction worth keeping in mind when you choose.

On file size, animated WebP is usually dramatically smaller than the equivalent GIF at similar visual quality. Google’s own reported figure is that lossy animated WebP is about 64% smaller than the equivalent GIF; other explainers report a range depending on the animation, roughly half to four-fifths smaller. Treat those as reported figures for typical animations, not promises for your file: a simple two-colour spinner will save less than a colourful, detailed clip, because there is less waste to remove in the first place.

GIF vs WebP side by side

Neither format wins in general. GIF wins on universality; WebP wins on quality and size. The right question is where the image is going, not which format is newer.

So why did your converted WebP stop moving?

Because a WebP file is a container, and a container can hold one frame or many. A converter that only reads the first frame writes a perfectly valid WebP file — it just contains a single still image. Open it, and there is nothing to animate.

This is a common behaviour in browser-based converters, and it is easy to see why once you know the mechanism. Drawing an animated image onto a canvas in a browser paints one frame of it; exporting that canvas as WebP therefore produces a still image. The format is not at fault, and neither is your original GIF. The converter simply never encoded the remaining frames.

The fix depends on what you actually wanted. If you wanted a smaller still image — a banner, an icon, an illustration that happened to be saved as a GIF — then a first-frame WebP is exactly the right result, and the animation was never part of the job. If you wanted a smaller animated image, you need a different tool: one that explicitly promises animated WebP output and encodes every frame, with its timing and looping preserved. Check the result frame by frame before you delete the original, because a file that opens as a still image in one viewer may still be an animated file that the viewer cannot play — and vice versa.

One more trap to avoid: converting a GIF to WebP and back, or through several formats, will not restore what was lost along the way. A GIF already reduced to 256 colours does not gain colours back when it becomes a WebP, just as a damaged JPEG does not heal when saved as a PNG. Every conversion preserves the file you have, not the file you wish you had.

Which one should you use?

For a website you control, use animated WebP. The file is much smaller, the colours are better, transparency is smoother, and every major modern browser supports it. Your pages load faster, and on a page with several animations the saving adds up quickly. If a small share of very old browsers matters to you, serve a GIF fallback alongside it; that is a solved problem, not a reason to stay on GIF.

For email, keep GIF. Many email clients still do not reliably render WebP, and an animation that does not play — or worse, does not display at all — is worse than a larger file that works. Until the client you are actually sending to is confirmed to support WebP, GIF remains the safe choice for animated email content.

For sharing and messaging, check the platform. Some platforms accept WebP uploads and display them animated; others convert uploads to GIF, or show only a still preview. If the animation must survive the share exactly as made, GIF is the format least likely to be mangled in transit. If the platform is your own site or app, WebP is the better default.

For simple, low-colour animations — a loading spinner, a blinking icon, a logo loop — either works. A well-optimised GIF of a simple animation is already small, and its universality costs nothing. WebP will usually be smaller still, but the difference on a tiny, simple file is rarely worth agonising over. Pick the one your platform handles best and move on.

For a still graphic that happens to be a GIF, convert it to WebP. A static banner or illustration saved as GIF out of habit gains nothing from GIF’s animation support and pays for it in file size. A still WebP of the same picture is usually smaller, with better colour, and it is the one case where a first-frame converter is exactly the right tool.

Trying it: converting a still GIF to WebP honestly

The GIF to WebP Converter on this site does one job, and it states its limit plainly on the tool page itself: it converts a GIF into a WebP file using the first frame of animated GIFs. That makes it the right tool for still graphics, and the wrong tool for preserving an animation. Used with that limit in mind, it works like this:

1. Choose a GIF file, up to 10 MB. Pick a still graphic, or check the first frame of an animated GIF and make sure that frame is the picture you actually want — because that is the only frame you will get.
2. Set the quality slider. It is shown at 85, a sensible starting point for a still graphic: a clear size saving over GIF with detail that is hard to fault at normal sizes. Step it down only if the result is still larger than you need, and step it back up if edges or text start to look rough.
3. Click Run and download the WebP. Compare the result with the original before you replace anything. If the picture is a photograph, remember that a still WebP is a good web format, but a photograph converted from a 256-colour GIF will still carry the GIF’s colour limits — conversion cannot invent colours that were already discarded.
4. Keep the original GIF if the animation matters. If you open the WebP and it does not move, that is the expected result from this tool, not a fault in the file. Keep the GIF for anything that needs to animate, and use the Image Converters category if a different pairing — GIF to PNG or GIF to JPG, also first-frame — fits the job better.

Two honest limits are worth knowing before you start. The tool cannot create animated WebP, so the animation is lost by design, not by accident. And the conversion runs entirely in your browser, on your own device — your GIF is never sent to the site’s server, and the WebP is created and downloaded straight from your device.

Frequently asked questions

Does WebP support animation?

Yes. Animated WebP is a real, supported part of the format, with multiple frames, timing and looping, in full colour with smooth transparency. The confusion comes from converters: a tool that only reads one frame produces a still WebP, which says nothing about what the format can do.

Will my GIF keep animating after conversion?

Only if the converter encodes all of its frames. A first-frame converter, including the one on this site, produces a still WebP of the opening frame. If animation is the point of the image, keep the original GIF or use a converter that explicitly promises animated WebP output, and check the result before deleting anything.

Is WebP smaller than GIF?

Usually, and often by a lot for animation — Google reports about 64% smaller for lossy animated WebP against the equivalent GIF — but the saving depends on the animation. Simple, low-colour animations save less than colourful, detailed ones, and a still WebP of a simple graphic may save only modestly over the GIF. Measure your own file rather than trusting a headline figure.

When should I still use GIF?

When the animation must work absolutely everywhere, especially in email, or when the platform you are sharing to does not reliably handle WebP. GIF’s universality is its one remaining decisive advantage, and for a short, simple animation it is often the pragmatic choice.

A still file, or a moving one — check before you convert

GIF vs WebP is not a contest with a single winner. WebP is the better format for most web work: smaller files, millions of colours, smooth transparency, real animation support. GIF is the safer format when compatibility cannot be compromised, above all in email. And a converted file that stops moving is usually neither a broken file nor a broken format — it is a first-frame conversion doing exactly what it said it would.

So before you convert, ask which of the two you need: a smaller still image, or the animation itself. If it is the still image, try the GIF to WebP Converter, and browse all free tools if the job needs a different tool. If it is the animation, keep the original GIF — and make sure the tool you pick promises every frame, not just the first.