Why does this fail on some WebP files?

A static (non-animated) WebP has no ANIM chunk in its RIFF container, so there's no animation to extract; the tool detects this and reports it as a clear, expected error rather than a bug — upload an animated WebP instead.

How are the actual pixels decoded?

This tool parses the WebP RIFF container by hand to find each frame's compressed payload, but hands that payload to the browser's own createImageBitmap to do the real VP8/VP8L pixel decompression, the same way modern browsers decode WebP natively.

Are frame dispose and blend modes handled correctly?

Frame compositing (whether a frame clears to background before drawing, and whether it blends over or replaces the previous frame) is approximated with straightforward canvas clear-then-draw operations, which correctly handles the vast majority of real-world animated WebP files.

Is the resulting file a real, valid APNG?

Yes — it's a genuine PNG chunk stream with acTL/fcTL/fdAT extension chunks, DEFLATE-compressed with the browser's own CompressionStream, so it opens correctly in any APNG-aware viewer or browser.

WebP to APNG Converter - Convert Animated WebP to Animated PNG

Overview

Introduction

This tool converts an animated WebP file into a real Animated PNG (APNG), entirely in your browser, for contexts where APNG is the format you need instead.

Every frame is decoded and recomposited locally using the browser's own WebP decoder; nothing you upload ever leaves your device.

What Is Webp to APNG Converter?

A client-side WebP-to-APNG converter that hand-parses an animated WebP's RIFF/VP8X/ANIM/ANMF chunk structure to locate each frame's compressed payload, offset, dispose mode, and blend mode, then decodes each payload's actual pixels with the browser's native createImageBitmap.

Decoded frames are composited onto a persistent canvas following each frame's dispose/blend settings, then the resulting sequence of full-canvas RGBA frames is handed to this category's shared APNG encoder.

How Webp to APNG Converter Works

The WebP RIFF container is walked chunk-by-chunk (pure byte parsing, no pixel decoding) to recover the ANIM header's loop count and canvas size, plus each ANMF sub-chunk's frame offset, dimensions, delay, and dispose/blend flags.

Each frame's embedded WebP image data is decoded into real pixels via createImageBitmap, drawn onto a shared canvas (clearing to background or the frame's own region first depending on its dispose/blend flags), then read back and passed to this category's shared APNG creator, which DEFLATE-compresses each frame and wraps it in acTL/fcTL/fdAT chunks.

When To Use Webp to APNG Converter

Use it when a tool, platform, or workflow requires APNG specifically and you only have an animated WebP source file.

It's also useful for inspecting an animated WebP's frame-by-frame content in a more universally-viewable format.

Often used alongside APNG to Webp Converter, APNG Creator and APNG Checker.

Features

Advantages

Runs entirely client-side; the uploaded WebP is never sent to a server.
Uses the browser's own real WebP decoder for accurate pixel decompression rather than a hand-rolled approximation.
Produces a genuine, standards-compliant APNG file with correct per-frame timing and loop count.

Limitations

Frame compositing (dispose-to-background and blend-over-vs-replace) is approximated with simple canvas clear-then-draw operations, which covers typical animated WebP files but may not perfectly reproduce very unusual dispose/blend sequences.
Pixel decoding relies entirely on the running browser's own WebP decode support via createImageBitmap; if a browser can't decode a particular frame's WebP data, the tool reports that clearly rather than fabricating pixels.

Examples

4-frame loading spinner

Input

A 64x64 animated WebP, 4 frames, 200ms delay each

Output

A 64x64 APNG, 4 frames, 200ms delay each

Frame count, dimensions, and timing carry over directly from the WebP's ANIM/ANMF chunks.

Static (non-animated) WebP upload

Input

A single-image WebP file with no ANIM chunk

Output

Error: an explanation that this WebP has no animation to extract

The tool checks for the ANIM chunk before attempting any frame extraction, so this is reported as an expected, honest failure.

Best Practices & Notes

Best Practices

Confirm the source file is actually an animated WebP (not a static one) before uploading, since only animated WebPs have frames to extract.
Preview the resulting APNG's playback before relying on it, especially for WebPs using less common dispose/blend combinations.

Developer Notes

The WebP RIFF/ANIM/ANMF container parsing is a pure, synchronous function operating on raw bytes with no DOM dependency, fully unit-testable under Node; only the surrounding component touches createImageBitmap and <canvas> to perform the real per-frame WebP pixel decoding and dispose/blend compositing, since those APIs only exist in the browser.

Webp to APNG Converter Use Cases

Converting an animated WebP asset for a pipeline or platform that requires APNG instead
Migrating an animated icon or badge from WebP back to APNG for broader legacy compatibility
Inspecting an animated WebP's individual frames in a widely-viewable format

Common Mistakes

Uploading a static WebP and expecting an animation — this tool specifically requires an animated WebP with an ANIM chunk.
Assuming pixel-perfect frame compositing for every possible dispose/blend combination — the approximation covers common cases but isn't a full WebP animation renderer.

Tips

If extraction fails, verify the source WebP is genuinely animated (multiple frames) and not just a single still image.
Check the resulting APNG's file size — full RGBA APNG frames are often larger than the original WebP's more specialized compression.

Webp to APNG Converter