Initializing... drag & drop files here
Supports: APNG, PNG
You convert APNG to GIF for one reason: reach. An animated GIF plays in email clients, old forum software, legacy chat apps, and image viewers that still ignore APNG, so it is the safe choice when you cannot control where a file lands. The trade is real quality: GIF caps each frame at 256 colors and supports only on/off transparency, so smooth gradients band and soft edges turn jagged. If your animation is a flat-color graphic, sticker, or simple loop, that loss is usually invisible — and the GIF can even be smaller. If it is a photographic clip or a glow/shadow with feathered edges, expect visible degradation.
| Property | APNG (input) | GIF (output) |
|---|---|---|
| Colors per frame | 24-bit truecolor (16.7M) | 256 max (8-bit indexed palette) |
| Transparency | Full 8-bit alpha channel | 1-bit on/off (one index, no semi-transparency) |
| Compression | Lossless (PNG zlib) | Lossless LZW over an indexed palette |
| Best content | Photos, gradients, soft shadows | Flat-color graphics, line art, simple loops |
| Browser support | 94.68% globally (Chrome 59+, Firefox, Safari, Edge 79+) | Effectively universal — every browser, email client, and viewer |
| Where it fails | IE, Opera Mini, old Android Browser show frame 1 only | Almost nowhere |
| Typical file size | Smaller for true-color animation | Smaller for few-color graphics, larger for photos |
| First released | 2004 (Mozilla) | 1987 (CompuServe), 89a animation in 1989 |
.apng file onto the page or click "Add Files." Multiple files queue together.Need the reverse, or to compress an oversized result? See GIF to APNG to go the other way, or Compress GIF to shrink the output further.
Usually some. GIF allows 256 colors per frame versus APNG's 16.7 million, so any photographic content or smooth gradient will show banding, and the "By Color Reduction + Dither" option only masks it by scattering pixels. Flat-color graphics and simple loops convert with little or no visible loss.
GIF transparency is 1-bit — a pixel is either fully visible or fully gone — so the soft, semi-transparent anti-aliased edges APNG stores in its alpha channel get clipped to a hard outline. This is most obvious over colored or patterned backgrounds. If feathered edges matter, keep the APNG.
Yes, for the long tail. APNG reaches about 94.68% of browsers (caniuse), but GIF is effectively universal — it also plays in email clients, older chat apps, and legacy forum software where APNG often does not. That reach is the entire reason to convert.
It depends on the content. For flat-color or few-color animations the indexed GIF is often smaller. For photographic or gradient-heavy clips the GIF can be larger and look worse, because it must dither to fake colors APNG stored natively. In our testing, a flat-color logo loop shrank slightly as a GIF, while a gradient animation grew and showed visible banding.
Yes — frame delays and the looping behavior are read from the APNG and written into the GIF. You can override the playback speed with the FRAMERATE option if you want it faster or slower than the source.
No. Once the APNG is reduced to a 256-color GIF, the discarded colors and alpha data are gone; converting GIF to APNG re-wraps the same 256 colors in a PNG container and cannot reconstruct the original truecolor frames. Keep your source APNG if you may need full quality later.
No. An APNG is a valid PNG, so any viewer that does not understand the animation chunks simply displays the first frame as a static image. That is the graceful fallback APNG was designed for — and the situation converting to GIF avoids, since GIF animates everywhere.