Add your AVIF file
Drop one or more .avif files onto the converter above, or browse for them. They load into browser memory only — nothing is uploaded, so there is no size-based pricing and no server queue.
Converting a .avif image to .png re-encodes the pixels for a different balance of size, quality, and support. Free, private, and validated — the file never leaves your browser.
Batch files can each use a different output. Nothing uploads for local conversions.
Working inputs include camera RAW, browser-local audio/video, PDF, CBZ/CBR comics, office documents, ebooks, markup, 3D models, structured text, images, and archives.Converting a .avif image to .png re-encodes the pixels for a different balance of size, quality, and support. An .avif file stores a still image (or sequence) coded with the AV1 video codec inside a HEIF-derived container. It is currently among the most efficient image formats deployed on the web, routinely beating JPEG by half at similar quality while adding HDR, wide gamut, and alpha.
A .png file is a losslessly compressed raster image with full 8-bit alpha transparency, making it the standard choice for graphics that must stay pixel-perfect. Screenshots, logos, UI assets, and diagrams are the classic .png territory, since sharp edges and flat color survive without compression artifacts. For this route the practical draw is perfectly lossless, so files can be opened and re-saved indefinitely and true 8-bit (or 16-bit) alpha channel — balanced against photographic content produces files several times larger than JPEG or WebP, which is worth knowing before you commit a large batch.
The practical trigger for this conversion is usually a mismatch: with .avif, encoding is much slower than JPEG or WebP, especially at high effort settings. Switching to .png buys you perfectly lossless, so files can be opened and re-saved indefinitely, which is why it is the better fit for screenshots and screen recordings exported as stills. Because the conversion runs locally, trying it costs nothing but a few seconds of compute on your own machine.
| Aspect | AVIF image (.avif) | PNG image (.png) |
|---|---|---|
| Format type | Lossy — discards detail it judges invisible to shrink files | Lossless — every pixel or sample is preserved exactly |
| How it stores data | encodes AV1 intra frames; both lossy and a mathematically lossless mode are defined | uses DEFLATE compression preceded by per-scanline prediction filters (None, Sub, Up, Average, Paeth) |
| Strongest at | serving hero images and photo galleries where bandwidth savings are significant | screenshots and screen recordings exported as stills |
| Weak spot | encoding is much slower than JPEG or WebP, especially at high effort settings | photographic content produces files several times larger than JPEG or WebP |
| Metadata | eXIF and XMP are stored as metadata items in the HEIF container alongside ICC profiles or CICP color signaling, and mainstream encoders preserve them on conversion | text metadata lives in tEXt/iTXt chunks and XMP can be embedded there; standardized EXIF arrived late via the 2017 eXIf chunk, so many tools still drop EXIF when writing PNG |
Drop one or more .avif files onto the converter above, or browse for them. They load into browser memory only — nothing is uploaded, so there is no size-based pricing and no server queue.
Select .png in the output menu next to each file. The menu only offers targets this engine can genuinely produce, so if PNG is selectable, the route is real and validated.
Press Convert. Decoding and re-encoding happen on your device using the browser's native image pipeline and hand-tuned encoders.
Each result is signature-checked before the download unlocks, so a failed encode can never masquerade as a valid PNG file. Outputs keep the original filename with the .png extension.
No new loss is introduced — since avif is lossy-oriented and png is lossless-oriented, everything the .avif file still contains is carried over exactly. What was already discarded by the original lossy encode cannot be recovered, though; converting to .png does not "restore" quality.
Yes — the .avif file is processed inside your browser tab and never uploaded. Decoding and re-encoding happen on your device using the browser's native image pipeline and hand-tuned encoders. Close the tab and the file is gone from memory.
Every modern browser has rendered PNG with full alpha since Internet Explorer 7 fixed its transparency bug in 2006, and native OS support is universal on Windows, macOS, Linux, iOS, and Android. It is also the required format in many contexts, such as iOS app icons and favicon fallbacks.
Larger, sometimes much larger. A lossless .png must store every pixel or sample the decoder produced, without the perceptual shortcuts .avif used. Use this route for editing headroom, not for saving space.
In .avif, eXIF and XMP are stored as metadata items in the HEIF container alongside ICC profiles or CICP color signaling, and mainstream encoders preserve them on conversion. Re-encoding through the browser pipeline does not carry embedded metadata into the output, which doubles as a privacy scrub — check the exported file if you specifically need tags preserved.
Yes — the reverse route exists as a separate tool. Bear in mind that round-tripping .avif → .png → .avif is not a perfect undo when any lossy step is involved; keep your original if fidelity matters.