What does GIF to WebP Converter do?
GIF to WebP keeps the animation. The GIF is composited frame by frame, then every changed area is compressed with libwebp and written into an animated WebP container with its own duration and a loop count you can see. Lossless keeps the GIF’s pixels exactly; lossy usually makes a smaller file but colors can shift. A frame identical to the one before it is stored as extra time on that frame, so playback timing stays the same. Transparency is kept unless you flatten it onto a background color. Converting cannot restore colors the GIF palette already removed. The page measures both files, so you can see whether WebP is smaller for this animation.
How to use GIF to WebP Converter
- 1Upload a GIF and check its frames, size, duration and loop.
- 2Choose lossy with a quality, or lossless with a compression effort.
- 3Optionally resize with the aspect locked, flatten transparency, or set the number of plays.
- 4Convert. The first run downloads the media engine. Check the decoded result and the measured sizes, then download the WebP.
Supported inputs and outputs
Inputs
Animated GIF, Static GIF
Outputs
Animated WebP (VP8X, ANIM and ANMF chunks), Still WebP for a static GIF
Practical uses
- Using a smaller animation on a website that accepts WebP
- Keeping GIF transparency in a WebP
- Comparing lossy and lossless sizes for the same animation
Browser and media limitations
- The WebP is not always smaller than the GIF. The page shows both measured sizes.
- Lossy compression can shift colors. Lossless keeps the GIF pixels but is often larger.
- Conversion does not restore colors the GIF palette already removed.
- GIF delays of 0–10 ms are written as 100 ms, the speed browsers use for such GIF frames.
- Some apps and older software do not play animated WebP. Keep the GIF if you need it everywhere.
- The libwebp encoder is part of FFmpeg.wasm (about 30 MB, downloaded on first use). Limits are 30 MB, 300 frames, 2048 pixels on a side and 24 million total pixels.
How local processing works
Your GIF is decoded in this browser and compressed by libwebp inside FFmpeg.wasm, which is downloaded on first use. The GIF is not uploaded to Tubelexity or a processing server. Page navigation and analytics still use network requests.
How the WebP is built and checked
The GIF is composited first, so partial frames and disposal are applied before compression. The first WebP frame covers the whole canvas. Each later frame stores only the rectangle that changed, starting on an even pixel as the WebP container requires, and replaces those pixels exactly, including transparency. Durations are written in milliseconds and the loop count is written in the ANIM chunk, where 0 means forever.
After encoding, the page decodes the WebP again in the browser and compares it with the GIF frames: the frame count, every duration and every transparent pixel must match, and lossless colors must match exactly. If any check fails, no file is offered.
Frequently asked questions
Does the WebP stay animated?
Yes. Every frame is written into an animated WebP with its own duration. A static GIF becomes a still WebP.
Is WebP smaller than GIF?
Often, but not always. Simple flat-color GIFs can be larger as WebP, especially lossless. Convert, then compare the two measured sizes shown on the page.
Is the conversion lossless?
Choose Lossless to keep the GIF’s pixels exactly. Lossy makes smaller files but colors can shift. Neither brings back colors the GIF palette already removed.
Does WebP keep GIF transparency?
Yes. Transparent pixels stay transparent unless you choose a background color to flatten them.
