Convert GIF to animated WebP
Replace animated GIF with animated WebP — 30–60% smaller files, full 24-bit colour, and smooth alpha transparency.
GIF-to-WebP converter in development
Animated WebP encoding needs a dedicated WebAssembly encoder. We're integrating libwebp-wasm — the rest of the page below describes how the conversion will work and what to expect.
In the meantime: PNG to WebP, JPG to WebP
How conversion will work
- Step 1
Select your GIF files
Click the upload area or drag and drop one or more GIF files. Multiple files supported.
- Step 2
Choose a quality setting
Use the slider to set the WebP quality (10–100). 80 is a safe default for animated content.
- Step 3
Convert and download
Click convert. Each GIF is decoded and re-encoded as animated WebP. Download each result individually.
How GIF-to-WebP conversion works
The conversion reads each frame of the animated GIF, decodes its palette and pixel data, and re-encodes the frame sequence as animated WebP using the VP8 codec. Each frame can be encoded as lossy or lossless; per-frame timing and disposal methods are preserved exactly.
The size win comes from two sources. First, WebP's prediction-based compression is dramatically more efficient than GIF's LZW per-frame compression — typical content compresses 30–60% smaller. Second, animated WebP stores frame-to-frame deltas rather than full independent frames, exploiting redundancy across the animation.
Two technical advantages over GIF survive the conversion: full 24-bit colour (instead of GIF's 256-colour palette per frame, which causes banding on smooth gradients) and full 8-bit alpha transparency (instead of GIF's 1-bit binary transparency, which produces jagged matte edges).
For more detail, see WebP format overview, GIF Format, and the WebP vs GIF comparison.
When to convert GIF to WebP
Site performance
Animated GIFs are often multi-megabyte. Converting to animated WebP can halve page weight on pages with animation, with no visible quality difference.
Product demos
UI walkthroughs, product explainers, and feature demos encoded as GIF look noticeably better as animated WebP — smoother gradients, cleaner text, smaller files.
Marketing graphics
Hero animations and feature highlights that ship as GIF are visible quality regressions vs. animated WebP. Full-colour gamut matters for brand presentation.
GIF library migration
Sites that inherited GIF-heavy content consistently see multi-megabyte page-weight reductions from bulk conversion.
Modern delivery with fallback
Use a <picture> element with animated WebP primary and GIF fallback. The 97% of browsers that support WebP get the smaller file.
Mobile-first audiences
For mobile audiences on metered connections, every megabyte matters. Animated WebP gets the same content on screen for half the bytes.
File size benchmarks
Typical relationships, holding content constant. Larger GIFs see larger relative savings:
| GIF size | Animated WebP (q=80) | Reduction |
|---|---|---|
| 500 KB | 200–300 KB | 40–60% |
| 2 MB | 700–1100 KB | 45–65% |
| 5 MB | 1.5–2.5 MB | 50–70% |
| 12 MB | 3–5 MB | 60–75% |
For animations longer than ~3 seconds, consider short MP4 or WebM video instead — typically another 5–10× smaller than animated WebP for the same content. See the WebP Optimisation guide.
Common issues and solutions
Output is barely smaller than the GIF
Short, simple GIFs (under 1 second, few frames) compress less efficiently. The dramatic wins (50–70%) come from longer GIFs with smooth motion.
Colours look different after conversion
Possible — GIF's 256-colour palette gets expanded to WebP's full 24-bit colour. The conversion shouldn't change colours, but some palette quirks (custom dithering patterns) may not round-trip identically.
Animation timing seems off
GIF stores frame delays in 1/100ths of a second; some old GIFs use values below 2, which most browsers clamp to 10. The animated WebP preserves source timing exactly, which may look faster than the GIF rendered in some browsers.
Transparency edges look smoother in WebP
Correct — WebP supports 8-bit alpha (smooth anti-aliased edges) vs GIF's 1-bit transparency (jagged matte edges). The WebP output is the higher-fidelity version.
Some clients won't play the animated WebP
Older browsers, some email clients, and many chat apps don't render animated WebP. For broad-distribution content, ship both formats via the <picture> element with the GIF as fallback.
I want to convert WebP back to GIF
Use the reverse direction: WebP to GIF converter.
Frequently asked questions
Related resources
Convert animated WebP back to GIF for cross-platform sharing (chat, email, social).
Side-by-side: animation, file size, transparency, colour depth, and where each format wins today.
Container structure, codec details, animation support, and implementation patterns.
GIF's structure, limitations, and the cultural ubiquity that keeps it relevant despite technical obsolescence.
Encoder settings, responsive delivery, lazy loading, and Core Web Vitals impact for WebP.
Compatibility for static and animated WebP, plus fallback patterns for the long tail.
Re-encode the resulting animated WebP at a different quality to trade fidelity for further size reduction.