Convert GIF to AVIF — Free, Fast & Private
GIF was finalised in 1989. AVIF is derived from AV1, released in 2018. Converting between them is the widest technological gap you can cross in a single image conversion, and the file size reflects it — a photographic GIF frequently drops by 90% or more.
The output is a still image. AVIF supports animation in principle, but this converter works frame by frame, so an animated GIF yields one still AVIF. If the animation is the point, this is the wrong conversion.
Why the gap is so wide
GIF stores an indexed palette of 256 colours and compresses the index stream with LZW — a lossless dictionary algorithm that hunts for repeated byte runs. It has no concept of a pixel neighbourhood, an edge or a gradient.
AVIF inherits AV1’s full toolkit: directional intra prediction, variable block partitioning, and transforms tuned on enormous corpora of real images. It models what the picture is likely to do next and stores only the surprise. Against a codec that predates the idea entirely, the margin is not incremental.
The practical caveat is the same as for any GIF conversion: nothing recovers the colours GIF threw away. If a photograph was reduced to 256 colours and dithered, AVIF encodes the dithered result. And dither is a nuisance for a predictive codec, since fine speckle is exactly the high-frequency noise it finds hardest to model — so a heavily dithered GIF will not shrink as much as a clean one.
Where AVIF is genuinely worth it here
Old sites accumulate GIFs: diagrams, charts, banners, screenshots, logos that were converted once in 2004 and never revisited. They are often large for what they contain, and they are frequently the heaviest thing on the page. Batch-converting that archive to AVIF is a real, measurable page-weight win, and Core Web Vitals rewards it.
Transparency converts cleanly — AVIF carries a full 8-bit alpha channel against GIF’s single on/off flag — so cut-out logos keep their transparency and gain the ability to be antialiased properly afterwards.
Encoder availability, and serving the result
AVIF is encoded on your device, so the option appears only when your browser has a working AVIF encoder. MiniPx probes for it, and verifies the output by inspecting the file’s magic bytes — some browsers claim AVIF support and quietly return a PNG, which would otherwise leave you with a large PNG named .avif.
When you publish, serve AVIF inside a <picture> element with a WebP or PNG fallback. Display support is good across current browsers but a tail of older devices remains, and a GIF that had worked everywhere for twenty years deserves a graceful fallback.
If AVIF is unavailable or you would rather not manage fallbacks, GIF to WebP captures most of the benefit with fewer caveats, and GIF to PNG is the lossless option.