GIF to WebP Converter
Drop in one or more animated GIFs and get animated WebP files back — usually a fraction of the size, converted entirely in this tab.
Applies to every file in the batch. 80 is a solid default — lower it for a smaller download, raise it if fine detail starts banding.
Everything runs locally in your browser. Nothing is uploaded to any server — close the tab and your files are gone.
How to use
Drop in your GIFs
Add one file or a whole batch of animated GIFs at once. Each one gets its own row in the queue below, tracked from decoding through to a finished WebP.
Set the quality
One slider applies to the whole batch, from 50 to 100. 80 is a reasonable starting point — drop it further if a file still feels too big once it’s done.
Watch each file convert
Files decode and encode one at a time, so the tab stays responsive even with a long queue. Frame count and the before/after size show up on a row as soon as that file finishes.
Download one file, or all of them
Grab a single WebP straight from its row, or zip up everything that finished once two or more files are done.
Frequently asked questions
How much smaller does a GIF get after converting to WebP?
It depends on the content, but it’s rarely small. GIF caps every frame at 256 colors and compresses with LZW, a scheme from 1987 that barely accounts for what changed between frames. Animated WebP keeps full 24-bit color per frame and uses a modern predictive codec built for exactly that job, so the same animation typically lands 30–70% smaller — and photographic or gradient-heavy GIFs, which suffer most under 256 colors, often shrink even further.
Which browsers can play an animated WebP?
All current versions of Chrome, Edge, Firefox and Safari play animated WebP natively, and have for years — this isn’t a niche format. The real gap is elsewhere: a handful of older chat apps, forum uploaders, and legacy CMS themes still only accept .gif. If you know exactly where the file is going and it takes WebP, converting is close to a free win.
Why does this tool need Chrome, Edge, or Safari to run?
Decoding the GIF here uses the ImageDecoder API — it hands back every frame, its timing, and the loop count without this site having to ship its own GIF parser. Firefox hasn’t implemented that API yet, so the page shows a plain notice there instead of quietly failing. Everything else about the tool is identical once you’re on a browser that supports it.
Is there a limit on how many frames a GIF can have?
Yes — 300 frames per file. A GIF with more than that still converts, but only its first 300 frames are used, and the row for that file says so once it’s done. In practice this only matters for very long loops; most GIFs people share are well under it.
Does a plain, non-animated GIF still convert?
Yes. A single-frame GIF goes through the exact same decode-and-encode path and comes out as an ordinary still WebP — useful on its own if you’ve got a large static GIF (a screenshot or meme exported the wrong way, say) and just want it smaller.
Does converting a GIF here send it to a server?
No. The ImageDecoder reads the file, the frames are drawn to a canvas, and the WebP is assembled — all of that happens in this browser tab, on your own machine. There’s no upload at any point, so nothing is sent anywhere, and closing the tab throws away everything you added.