Animated WebP vs APNG vs GIF in 2026

GIF refuses to die. Every year someone writes its obituary, and every year it keeps turning up in Slack, in email campaigns, in product explainers. Meanwhile animated WebP has been ready since 2010 and APNG since 2008. Why does the 1987 format still get used?

The short answer: compatibility hangovers. The longer answer has actual tradeoffs, and they have shifted noticeably in the last two years.

The raw numbers

Here is a 720p, 4-second screen recording exported three ways with equivalent visual quality:

Format	File size	Colors	Transparency	Max FPS practical
GIF	8.2 MB	256 per frame	1-bit alpha	50
APNG	3.1 MB	24-bit	8-bit alpha	60
Animated WebP (lossy)	780 KB	24-bit	8-bit alpha	60
Animated WebP (lossless)	2.4 MB	24-bit	8-bit alpha	60
Animated AVIF	540 KB	10-bit+	8-bit alpha	60

Animated WebP at lossy settings undercuts GIF by 10x. Animated AVIF is even smaller but, as of April 2026, still has gaps (Safari added it in 17.4, Edge and Chrome have had it for a while, but email clients are nowhere).

Browser and email support, April 2026

• Animated WebP: Chrome, Edge, Firefox 65+, Safari 14+. All current browsers. Mail: Apple Mail yes, Gmail web yes, Outlook desktop no, Outlook.com yes.
• APNG: All modern browsers since Firefox re-introduced its lead. Chrome 59+, Safari 8+. Mail: Apple Mail yes, Outlook desktop no, Gmail web partial (first frame only in some configurations).
• GIF: Literally everywhere. Every email client since Eudora.
• Animated AVIF: Chrome 112+, Safari 17.4+, Firefox 113+ with a flag in some builds. Mail: basically no support.

If you are building for email, GIF is still the default. Outlook desktop renders the first frame of animated WebP and APNG as a static image, which is usable as a fallback but defeats the point.

When each format wins

Use animated WebP when:

• You control the viewing context (your own site, a SaaS dashboard, in-app explainers).
• File size matters (mobile, data-capped users, paid bandwidth).
• You need smooth gradients or photographic content. GIF's 256-color palette will dither these into mush.

Use APNG when:

• You need lossless animation with full 24-bit color and 8-bit alpha. Pixel art with transparency over arbitrary backgrounds, UI micro-animations.
• You want a format that degrades gracefully to a static PNG in unsupported environments. APNG's first frame is a valid PNG.

Use GIF when:

• Email. Still.
• Old forum software, legacy CMSes, MMS attachments.
• Tiny animations where the 256-color ceiling genuinely doesn't hurt (a 48x48 loading spinner).

Use animated AVIF when:

• You ship to Chrome and Safari 17.4+ only, can provide a WebP fallback via <picture>, and the savings justify the encoder time.

The dithering trap

Most "GIF looks fine" arguments come from people posting videos of cartoons or screen recordings with flat UI colors. Try exporting a 4-second outdoor landscape clip to GIF and the 256-color palette collapses. You will see banding on the sky, noise on foliage, and a file that is three times the size of the WebP version for half the visual quality.

If you must ship GIF and have photographic content, use per-frame local palettes and Floyd-Steinberg dithering. ffmpeg's palettegen and paletteuse filters with stats_mode=diff produce substantially better results than whatever your screen recorder exports by default.

A pragmatic 2026 workflow

1. Author in your source format (screen recording, After Effects, Lottie).
2. Export a master MP4 at 60fps, h.264 or h.265, CRF 18.
3. Generate derivatives: animated WebP for the web, animated AVIF where supported via <picture>, GIF only if an email campaign or legacy destination forces it.

For one-off conversions, dropping a clip into the converter and picking the target format takes under a minute. For content pipelines where you need to generate all four at once, a batch step with format fan-out is the cleaner approach.

The practical takeaway: default to animated WebP for anything rendered in a browser, keep GIF in your back pocket for email, and stop shipping 8 MB GIFs of product demos. If you need a primer on how WebP and AVIF stack up for still images, the AVIF vs WebP vs JPEG XL comparison covers the still-image side.