Guide
Keeping AVIF graphics editable as lossless PNG
A transparent AVIF sticker, an AVIF screenshot or an AVIF logo is fine in a browser but awkward everywhere else. Design tools such as Canva uploads, older Photoshop versions, Keynote and many CMS image fields expect PNG when transparency matters. Converting gives you a file that keeps every pixel and its transparency and opens practically anywhere.
When PNG is the right choice
Pick PNG when you plan to edit the picture, place it over other content, or hand it to someone who will. PNG is lossless: saving it again and again never adds artifacts, which makes it the standard working format for graphics, interface elements, diagrams and screenshots. For a photo you only want to view or share, JPG is smaller; for the web, WebP keeps transparency while staying compact.
How the conversion works
The tool decodes the AVIF in your browser, or with a WebAssembly copy of the reference decoder when the browser lacks AVIF support, and asks the browser to write the pixels as PNG. You can drop many files at once, convert them together and download each result or a single .zip. Files keep their names with the new extension.
Why the PNG is so much bigger
AVIF describes a picture with an advanced, lossy codec; PNG stores every pixel with lossless compression that works well on flat colors but poorly on photographic texture. A 90 KB AVIF photo can become a 2 MB PNG. For graphics with large single-color areas the difference is much smaller. If size matters, switch on the size limit and set the longest side to what the picture will actually be displayed at, or convert to AVIF to WebP, which keeps transparency at a fraction of the bytes.
Transparency is preserved exactly
Every alpha value in the AVIF, including the soft partial transparency along anti-aliased edges and shadows, is written unchanged into the PNG. That is the main reason to choose PNG over JPG: the outline of a logo stays smooth on any background. Use the checkerboard preview after conversion to see which areas are transparent.
Checking the result
The row for each file shows the original size, the new size and the pixel dimensions; a preview appears below the list. If a file was not really AVIF, for example a PNG renamed by a website, a note says what it actually was, and it is converted all the same.
Related conversions
To go back to a small web format later, use PNG to WebP. For JPG output on a colored background, see AVIF to JPG. And to create AVIF files from your own images, Image to AVIF encodes them with the libavif encoder.
A quick checklist before you convert
Decide first what the PNG is for. For a slide or document, the original pixel size is usually more than enough, so limiting the longest side to around 2000 pixels keeps files light without any visible loss. For a design file you will keep editing, leave the size alone so nothing is thrown away. For a website, ask whether the picture really needs to be PNG: transparent product shots and logos often work better as WebP, and photos without transparency as JPG. Finally, look at the preview on the checkerboard to confirm that edges, shadows and glows came through as you expected; soft shadows that were baked into the AVIF stay semi-transparent in the PNG, exactly as they were drawn.
Checked against the current version of the AVIF to PNG on .

