Free APNG to WebP Converter
Upload APNG files and produce animated WebP without leaving this URL. IMAGEEE resolves APNG blend and disposal behavior, carries frame timing and loop metadata into WebP, preserves alpha by default, and checks animation complexity before allocating the full decoded sequence.
Supported extensions (expand/search)
Supports many aliases including jpeg.
Input extensions
How the APNG timeline is preserved in WebP
An animated format change is a timeline conversion, not a sequence of independent screenshots. Each visible frame can depend on the previous canvas through APNG blend and disposal rules. The pipeline reconstructs those displayed canvases before any resize or WebP encode step.
-
Describe the animation
The decoder separates a default poster from playback frames and collects source count, playable count, durations, loop value, blend mode, disposal mode, canvas dimensions, and alpha state.
-
Bound the workload
Frame count, total decoded pixels, estimated RGBA bytes, and remaining job time are checked before and during decoding. Oversized animations fail explicitly instead of exhausting the worker.
-
Composite displayed frames
Every APNG frame is resolved against the prior canvas according to its blend and disposal operations. Resize, color, mosaic, watermark, or other enabled transforms then receive complete displayed frames.
-
Encode one WebP timeline
The composed frames are saved with per-frame millisecond durations, the normalized loop count, and alpha unless flattening was requested. Target-size probing remains bounded and checks the job deadline.
Animation limits and normalizations
| Constraint | Converter behavior | What you should do |
|---|---|---|
| Playback frames | The default ceiling is 240 playable frames. | Longer sequences are rejected with an animation-complexity error before unbounded decode work. |
| Decoded pixels | The default total is limited to 64 million frame-pixels. | Canvas width × height × frame count is budgeted separately from the single-image limit. |
| Decoded memory | RGBA planning uses one eighth of Lambda memory, capped at 256 MiB by default. | The worker checks the estimate and every frame stage so memory pressure is predictable. |
| Timing and loops | A zero-duration frame becomes 1 ms; WebP loop values are capped at 65,535. | Both normalizations are disclosed in output animation metadata. |
Playback comparison before publishing
| Check | Method | Pass condition |
|---|---|---|
| Frame sequence | Step through source and output one frame at a time. | The same number of displayed frames appears in the same order. |
| Timing | Compare short holds, long holds, and the total cycle duration. | Per-frame durations match unless a documented 0 ms normalization was required. |
| Disposal and blend | Inspect overlays, cleared regions, and partial updates on a contrasting background. | No stale canvas pixels or missing underlay appears between frames. |
| Loop and alpha | Replay in the actual browser, CMS, or app and examine translucent edges. | Loop behavior and transparency survive where the receiver supports animated WebP. |
Choose animated WebP for a verified receiver
This route fits sites and product surfaces that reject APNG but explicitly support animated WebP for stickers, status illustrations, lightweight UI motion, or catalog demonstrations. Browser support alone is not enough: the CMS, optimization proxy, CDN, moderation step, and consuming app must all preserve animation rather than extracting a static thumbnail.
Batch release discipline
Test the most complex asset first, not the smallest. Select one file with partial-frame updates, varied delays, several loops, and translucent edges; compare its decoded timeline on the delivery surface. Once that sample passes, reuse the settings for animations with a similar size and frame budget while retaining the original APNG files.
Related maintained workflows
Free APNG to WebP Converter FAQ
Does APNG to WebP keep animation and transparency?
Yes by default. Playback frames, durations, loop count, and alpha are carried into animated WebP after APNG blend and disposal are resolved.
Why can an APNG be rejected before conversion?
The service bounds frame count, total decoded pixels, estimated RGBA memory, and job time. These checks prevent one animation from exhausting the processing worker.
Why does the WebP appear still in one destination?
Some upload systems accept the WebP file type but retain only a thumbnail or first frame. Verify animated WebP playback in every step of the real delivery chain.