Initializing... drag & drop files here
Supports: WEBP
WebP and APNG solve the same problem in two different eras: a full-colour image with real 8-bit transparency that can also animate. WebP wins on bytes; APNG wins on how gracefully it fails. Where APNG is not supported the file still shows as a normal still picture, whereas an unsupported animated WebP renders as nothing at all — which is why editors, older desktop tooling and archival workflows still ask for APNG. Files upload over an encrypted connection, are processed on our servers, and are deleted automatically after a few hours — no sign-up, no watermark.
This is the part most converters do not tell you. The .apng extension does not force an animation into existence; what comes out depends entirely on what went in.
| What you upload | What comes out | Why |
|---|---|---|
| One animated WebP | An animated APNG covering the whole animation | The animation is decoded and re-timed to the framerate you pick, holding the original duration |
| One static WebP | A valid but still PNG image — no animation chunks | One frame is not a sequence; the assembler collapses the duplicate and writes an ordinary PNG |
| Several WebP files, Combine? = Single animation | One animated APNG, one frame per file, in upload order | This is the animation maker — upload order is playback order |
| Several WebP files, Combine? = Individual files | One output per input | Each file is converted on its own |
The still-image case is not a failure — the file opens everywhere and keeps its transparency. It simply will not move, so do not expect a one-frame upload to loop.
.webp input is accepted here. If you want a multi-frame animation from separate pictures, add them all now — the order you add them is the order they play.| Property | Animated WebP | APNG |
|---|---|---|
| Compression | Lossy or lossless, with inter-frame prediction | Lossless only |
| Transparency | 8-bit alpha | 8-bit alpha |
| Colour | 24-bit RGB plus alpha | Full colour, no palette ceiling |
| Typical size | Smallest animated format in common use | Several times larger for the same frames |
| Where unsupported | Nothing renders | The still image renders instead of the animation |
| Standard | Google WebP container specification | W3C PNG Third Edition Recommendation, 24 June 2025, §4.9 |
| Global browser support | 96.18% (caniuse) | 95.94% (caniuse) |
| Best for | Delivering animation over the web cheaply | Editors, docs, archives, anything that must degrade to a picture |
No, it is the expected result. An animation needs at least two distinct frames; a single still image gives the assembler one frame, so it writes an ordinary lossless PNG under the .apng name. The file is completely valid, keeps its transparency and opens in anything that reads PNG. To get movement, upload several images with Combine? set to Single animation, or start from a WebP that is genuinely animated.
The APNG stage itself is lossless, so whatever the WebP decodes to is what gets stored — no new artifacts are introduced. What it cannot do is undo damage: if your source was saved as a lossy WebP, the detail discarded at that point is gone for good and APNG will faithfully preserve the compressed result, artifacts and all. Starting from a lossless WebP gives you a pixel-for-pixel match.
Yes, completely. Both formats carry a full 8-bit alpha channel, so semi-transparent pixels and soft anti-aliased edges come through unchanged rather than being cut to a hard on/off mask. We checked this end to end: the mean alpha of a transparent WebP was identical in the finished APNG. This is the main reason to convert to APNG rather than GIF, whose 1-bit transparency leaves jagged fringes.
Lossless compression with no lossy inter-frame prediction cannot compete with WebP's lossy encoder. In one check, a 480×270 transparent WebP of about 2.2 KB became an APNG of roughly 7.6 KB. Reduce the gap by lowering the Image Resolution or the Framerate; if you want the small file back afterwards, APNG to WebP reverses the conversion.
The output's real-time length is preserved. The frames are resampled to the Framerate you select and each APNG frame is written with an exact 1/N-second delay, so a one-second animation still runs for one second regardless of the rate you choose — you are trading frame count against smoothness, not changing the speed.
Yes, that is exactly what Combine? = Single animation does. Add the files in the order you want them to play, pick a Framerate, and each image becomes one frame. Images of different sizes are scaled and centred onto a shared canvas first, since an APNG requires every frame to share one dimension.
Chrome from version 59, Firefox from version 3, Safari from version 8, Edge from version 79 and Opera from version 46 — about 95.94% of global traffic according to caniuse. Anything older, and most non-browser software that only understands baseline PNG, shows the still image instead. The W3C PNG Third Edition Recommendation of 24 June 2025 defines that fallback behaviour explicitly.
Only if you genuinely need it. GIF is the one animated format that essentially never fails, but it caps each frame at 256 colours and offers only on-or-off transparency, so gradients band and soft edges pick up a halo. If the destination is an old email client or a platform that rejects APNG, WebP to GIF is the right call; otherwise APNG keeps the picture intact and still degrades to a static image rather than breaking.