AVIF to PNG, explained
Make a PNG copy of an AVIF image for an editor that cannot import AVIF. PNG retains decoded transparency and avoids an additional lossy output encode, but it cannot preserve every HDR or color characteristic of the source.
Select an AVIF that your browser can decode.
Keep PNG selected and inspect the preview, including transparent edges.
Download the still PNG and compare it with the original in its destination.
Use PNG for graphics workflows
A transparent AVIF asset may need a PNG delivery copy for a presentation or design tool. PNG can hold the decoded alpha channel. For an opaque photograph, compare JPG if the destination values compatibility and smaller attachments.
Native decoding with local fallback
AVIF uses the browser decoder first and a lazy WASM fallback for compatible sRGB still images. Unsupported color or orientation transforms are rejected by the fallback. A damaged or unusual AVIF can still fail; try a representative file before a batch.
Transparency versus background removal
Existing transparent areas can remain transparent. An opaque backdrop is still part of the image, even if it looks like a transparency checkerboard. Conversion does not select objects or erase pixels based on their color.
HDR and precision are not archival
The canvas raster workflow is not designed to retain original HDR signaling, high bit depth or embedded color profiles. A PNG extension alone is no assurance of those properties. Keep the AVIF and compare color-critical results.
Still output and larger files
The output is a single still image. It does not retain animation, and PNG can expand substantially relative to AVIF. Check the result size and keep the original when motion or compact web delivery matters.