Initializing... drag & drop files here
Supports: AVIF
AVIF and APNG are both animation-capable still-image formats, but they solve different problems. AVIF is an AV1 payload in an ISO base media container and is built for bandwidth; APNG is an extension of PNG itself, and its animation degrades gracefully — a decoder that does not understand it simply shows the first frame as an ordinary PNG. Converting AVIF to APNG is what you do when an editor, chat client, sticker pipeline or older viewer plays animated PNG but chokes on animated AVIF, and when you need the alpha channel to survive intact.
| Property | Value |
|---|---|
| Full name | AV1 Image File Format |
| Published by | Alliance for Open Media (AOM); spec v1.2.0, 16 October 2025 |
| Base container | ISO/IEC 14496-12 (ISO base media file format) |
| Payload codec | AV1 |
| Colour depth | 8, 10 or 12-bit; YUV 4:4:4, 4:2:2, 4:2:0 and greyscale |
| Transparency | Yes — a dedicated AV1 alpha image item |
| Animation | Yes — AV1 image sequences stored as a track |
| Browser support | ~94.7% of users: Chrome 85+, Firefox 93+ (animation from 113), Safari 16.4+, Edge 121+ |
| Best for | Web delivery where every kilobyte counts |
| Property | Value |
|---|---|
| Full name | Animated PNG |
| Standardised in | W3C PNG Specification (Third Edition), Recommendation of 24 June 2025, section 4.9 |
| Animation chunks | acTL (animation control), fcTL (frame control), fdAT (frame data) |
| Payload codec | DEFLATE-compressed PNG image data — lossless per frame |
| Colour depth | Up to 24-bit truecolour |
| Transparency | Yes — full 8-bit alpha per pixel |
| Browser support | ~95.9% of users: Chrome 59+, Firefox 3+, Safari 8+, Edge 79+, Opera 46+ |
| Fallback behaviour | A decoder without APNG support renders the first frame as a static PNG |
| Best for | Soft-edged stickers, UI micro-animations, logos and anything with real alpha |
Under Image resolution you can also leave the default Keep original or scale the output by percentage, to a preset height, or to an explicit width and height. Because the assembler requires uniform frame dimensions, differently-sized uploads are normalised onto a common canvas at that scale before assembly.
acTL/fcTL/fdAT animation chunks. It opens everywhere a PNG does; if you need genuine animation, supply a sequence of frames.It is part of the standard now. Animated PNG began as a Mozilla proposal in the mid-2000s and lived outside the specification for years, but the W3C PNG Specification (Third Edition), published as a Recommendation on 24 June 2025, folds it in: section 4.9 defines frame-based animation and the acTL, fcTL and fdAT chunks. It also keeps the original backward-compatibility promise — a static-only decoder ignores those ancillary chunks and shows the base image.
Yes, and this is the main reason to pick APNG over GIF. AVIF carries alpha as a dedicated auxiliary image item; APNG carries full 8-bit alpha per pixel. Soft, anti-aliased edges and partial opacity survive with no visible change. GIF, by contrast, only has one fully transparent palette index, which turns those same edges into a hard 1-bit cutout — see AVIF to GIF if legacy reach matters more than edge quality.
Yes. Animated AVIF files (sometimes saved with an .avifs extension) store their frames as an AV1 image sequence in a track, and our converter probes each upload for exactly that structure. When it finds one, the animation track is transcoded rather than the single still image the same file also exposes — a distinction that trips up naive tools and silently gives them a one-frame output.
Because the two use completely different compression. AVIF applies AV1's video-grade coding, including prediction between frames; APNG applies DEFLATE to each frame independently and is lossless, so it stores far more data for the same picture. A multiple-times size increase is normal. To bring it down, reduce the output resolution or lower the Framerate so there are fewer frames to store.
The per-frame delay is exactly 1 divided by the Framerate you choose, so 10 FPS gives a 0.1-second delay and 25 FPS gives 0.04 seconds. Our pipeline passes that value straight to the assembler and sets the loop count to zero, which the APNG specification defines as looping forever. There is no separate "delay" field to fight with.
No. This converter keeps the frames at their full truecolour data and 8-bit alpha; there is no palette step to opt into, and no quality slider either. If the result needs to be smaller, the APNG compressor is the page with size targets and an Auto Scale option. After assembly we run a lossless optimisation pass (Zopfli-based) that shrinks the file without touching a single pixel value.
They show the first frame as a normal PNG. That graceful degradation is written into the format and is the practical reason to prefer APNG over animated AVIF for wide distribution: current data puts APNG at roughly 95.9% browser support versus about 94.7% for AVIF, and the AVIF figure includes browsers that handle still AVIF but not animation — Firefox only gained animated AVIF in version 113.
APNG when fidelity and predictable fallback matter: it is lossless, truecolour, and degrades to a clean first frame. Animated WebP when size matters more, since it supports lossy frames and typically lands much smaller. Note that our AVIF to WebP converter writes still images, so assembling an animated WebP takes a dedicated tool such as webpmux from Google's libwebp.
No. Your files travel over an encrypted connection, are processed on our servers, and are deleted automatically after a few hours together with the APNG we generate. There is no sign-up, no watermark, and nothing is shared or made public.