Does PNG to ICO accept animated PNG files?
In this local run, the 16 × 16 still PNG produced a 4276-byte ICO; the 16 × 16 APNG showed “Animated PNG is not supported. Export one still PNG frame first.” and had no download link.
This records one paired test on the local converter copy in Chrome/156.0.8078.80. It does not establish how every APNG encoding or another browser behaves.
What the two files returned
| Input | Observed result |
|---|---|
| still-control.png | 115 input bytes; decoded as 16 × 16. Status: ICO ready: 16 × 16 input; 7 frames; 4276 bytes. Transparent padding keeps the original proportions. Downloaded still-control.ico (4276 bytes). |
| animated-two-frame.png | 256 input bytes; decoded as 16 × 16. Status: Animated PNG is not supported. Export one still PNG frame first. The download control stayed hidden; no ICO file was emitted. |
The APNG fixture declares 2 frames. The local fixture check found 2 frame-control chunks, 1 frame-data chunk, valid CRCs for all chunks, a valid PNG signature, and a complete IEND chunk.
The still control succeeded before the animated sample was tested. Its status reported 4276 output bytes, and the downloaded file on disk measured the same 4276 bytes. The APNG case returned the quoted message and had no download URL or saved ICO.
How to repeat this pair
- Download both PNG fixtures and open the PNG to ICO converter.
- Choose the still control, create the ICO, and compare the status with the saved still-control.ico file.
- Choose the APNG fixture and create again. Record the displayed status and whether the download control appears.
The raw run record and both inputs, plus the still output, are in the APNG evidence package. The record includes the browser version, input hashes, exact status text, output hash and byte count.
Boundary: this result covers these two generated 16 × 16 inputs on the tested local browser copy. It is not a test of other APNG layouts, remote deployment or every browser.