GIF to WebP
Convert your entire GIF animation into an animated WebP.
Your files
Files stay on your deviceDrop files herePick a file to start
GIF · up to 20 MiB per file
Limits & supported formats
Input: 1 file · GIF · up to 20 MiB.
Images: up to 2,048 px per side and 400 animation frames.
Output: up to 2,048 px per side, 4,194,304 pixels per frame and 400 frames.
Detailed budgets: 40,000,000 decoded pixels, an estimated 192 MiB working allocation and 64 MiB per ZIP. These estimates help reject large jobs; they do not guarantee a browser process memory peak.
Add a file to get started.
Three steps. One moving picture.
01Choose a GIF
02Set WebP quality
03Convert & download
Keep the animation in WebP
Convert a GIF into animated WebP for a page or app that supports the format. Lower quality can reduce size but may blur detail. Lossless pixel encoding keeps the decoded colors and transparency; it does not guarantee a smaller file. Compare the download size with the original.
Choosing your settings
Lossy encoding may change colors and fine edges. Lossless applies to decoded pixels, not a byte-for-byte copy of the GIF. Check animation support in the place you intend to use the WebP.
If the result needs another pass
If WebP is larger, try lower quality or keep the original GIF. If conversion cannot start, use a browser with the required local image support.
GIF timing note: missing, 0 ms and 10 ms frame delays are read as 100 ms. Other supported delays are retained unless the task changes timing or the frame sequence. Re-encoded animation may therefore differ from a viewer that handles unusually short delays differently.
Good to know
Is this a still WebP image?
An animated GIF stays animated. A one-frame GIF remains a single-frame picture. Transparent areas are supported; unusually short GIF delays are normalized before conversion.
Will WebP always be smaller?
No. Compare the actual result. Lossless encoding preserves decoded pixels but can be larger.