Initializing... drag & drop files here
Supports: AVIF
AVIF compresses far better than GIF, but GIF is the format every browser, chat client, forum and email template has understood since the late 1980s — so when a clip simply has to work everywhere, you convert back. This tutorial walks through all three cases the tool handles (a still AVIF, an animated AVIF, and a batch of stills assembled into a loop), explains what the Colors, Image quality and Framerate controls actually change, and covers the size blow-up that catches everyone out the first time.
.avif files onto the page or click "Add Files". Uploads are content-probed, so an animated AVIF is recognised as an animation rather than treated as a single picture.Four controls decide the size and look of the output, and they pull against each other.
Under Image resolution (also in File Compression → Custom) you can also leave the default Keep original or scale by percentage, to a preset height, or to explicit dimensions. Halving the width is often a cleaner size win than mangling the palette.
| Property | AVIF (source) | GIF (output) |
|---|---|---|
| Released | 2019; spec v1.2.0 from AOMedia, October 2025 | GIF87a in 1987, GIF89a in 1989 (CompuServe) |
| Compression | AV1 coding, lossy or lossless | LZW, lossless over an indexed-colour image |
| Colours | 8, 10 or 12-bit; millions | Up to 256 per frame, chosen from a 24-bit space |
| Transparency | Full 8-bit alpha | One fully transparent palette index (1-bit) |
| Animation | Yes, as an AV1 image sequence | Yes, as sequential frame blocks with per-frame delays |
| Typical size | Smallest of the mainstream formats | Substantially larger for the same content |
| Support | ~94.7% of browsers; Chrome 85+, Firefox 93+, Safari 16.4+, Edge 121+ | Effectively universal, including ancient software |
| Colors setting | Looks right for | What you give up |
|---|---|---|
| ORIGINAL (default) | Anything — let the encoder decide | Least control over final size |
| 256 | Photographs, film clips, complex gradients | Largest palette, largest file |
| 128 | Mixed content, screen recordings | Slight banding in smooth skies and skin |
| 64 | Flat illustration, logos, UI motion | Visible banding in gradients unless dithered |
| 32 or fewer | Line art, pixel art, monochrome captures | Photographic content posterises badly |
GIF is the wrong target whenever quality or size actually matters. For a photographic still, AVIF to JPG keeps far more colour at a fraction of the bytes. For an animation with soft transparency, APNG is the correct modern answer. And if you already have a GIF that is simply too large, converting it again will not help — run it through the GIF compressor instead, which is built for exactly that. Convert to GIF when the destination is genuinely legacy: an old forum, an email client, a chat platform that rejects everything else.
Yes. Every upload is content-probed for an AV1 image sequence, and when one is found the animation track is transcoded frame for frame into a looping GIF rather than being flattened to the still image the same file also contains. A single-frame AVIF becomes a single static GIF.
Because the two formats are separated by roughly thirty years of compression research. AVIF uses AV1 coding with prediction between frames and high bit depth; GIF stores every frame as an LZW-compressed, 256-colour indexed image with no cross-frame prediction at all. A several-times size increase for the same clip is the normal outcome, not a sign of a bad conversion.
It posterises it. Each GIF frame is indexed to at most 256 colours, so smooth gradients, skies and skin tones break into visible bands. Dithering hides much of it by mixing adjacent palette entries, at the cost of a grainier and often larger file. For photographs, a still-image target such as AVIF to PNG preserves the original colour instead.
Partly. GIF can mark one palette index as fully transparent, so a hard-edged cutout survives — but there is no partial opacity. Anti-aliased edges that fade smoothly in AVIF become either fully opaque or fully transparent, which reads as a jagged fringe. APNG is the format to use when that matters.
It drives the encoder's lossy stage, which is expressed internally as the inverse of the value you set — the default 80 therefore applies a light lossy pass rather than none at all. Lowering it deliberately discards detail to shrink the file, and it is usually the least destructive of the three size levers on flat, illustration-style content.
Yes, and that is the default. Leave Combine? on Single animation, upload the images in the order you want them to play, and each is held for 1/Framerate of a second. Choose Individual files if you would rather get one GIF per source image.
It can. The Framerate control sets the output timing, so if an animated AVIF was authored at 24 FPS and you leave the default 10 FPS, the GIF plays back slower and with fewer frames. Raise the Framerate to keep motion close to the original, or lower it deliberately when file size matters more than smoothness.
No. Files travel over an encrypted connection, are processed on our servers, and are deleted automatically after a few hours together with the GIF we produce. There is no sign-up, no watermark, and nothing is shared or made public.