Convert AVIF images to PNG with lossless quality and full transparency preserved. Perfect for pixel-perfect output and systems that require PNG format.
Last updated: August 2026
Lossless
Quality
Full
Transparency
Batch
Multiple Files
Private
No Uploads
PNG is lossless. Output is pixel-perfect. PNG files are typically larger than AVIF.
Drop AVIF files here or click to browse
All processing stays in your browser. Nothing is uploaded.
Drop or select your AVIF file
One file or many. Nothing is uploaded, it stays on your device.
Conversion starts automatically
Decodes and re-encodes as lossless PNG the moment it's added.
Download your PNG
One file downloads directly, two or more can download together as a ZIP.
PNG is the best choice when transparency matters or when you need to keep maximum quality for further editing.
Transparent backgrounds
Logos, icons, product cutouts and UI elements with transparency must be saved as PNG. JPEG cannot preserve transparency.
Further editing needed
If you plan to open and modify the image later in design tools, use PNG to avoid any quality loss.
Systems that require PNG
Many academic submissions, print services and design workflows specifically ask for PNG files.
Design and branding assets
Brand assets, overlays and graphics used in Figma, Photoshop or Canva are usually kept as PNG.
Most AVIF files you encounter are lossy. The format supports both lossy and lossless encoding, but lossy AVIF is what cameras, image generators and websites produce because it achieves far better compression ratios. Lossless AVIF exists and is occasionally used for graphics and icons, but it's not the common case. This matters when you see the phrase "lossless PNG output" because the lossless part refers to the conversion process, not to the original image. What happens here is that the AVIF gets fully decoded to its raw pixel state and those pixels get re-encoded into PNG without any further modification. The PNG is a pixel-perfect copy of what the AVIF contained. Nothing additional is lost in the conversion. But whatever compression the original AVIF encoding applied when the file was first created stays baked in.
In practical terms this is exactly what you want. If you're taking an AVIF logo with a transparent background and converting it to PNG for use in a presentation or document, you get every pixel exactly as the AVIF had it, including the full alpha channel. If you're pulling a photograph out of AVIF format for further editing, the PNG has the same visual content the AVIF had, with no new artifacts added. The PNG is just a different container for the same decoded pixels, one that every piece of software on the planet knows how to open.
Choosing between PNG and JPEG as the output format comes with a real file size tradeoff worth understanding before you convert. PNG encodes the decoded pixels losslessly, which for photographs means storing a lot of per-pixel variation that DEFLATE compression handles poorly. A 150KB AVIF photograph will typically become 1.5 to 3MB as PNG and 300 to 500KB as JPEG at quality 85. If the image is a photograph with no transparent background and you just need it to open somewhere that rejects AVIF, JPEG is a much more practical output. The additional lossy compression JPEG applies on top of the AVIF source is minimal at quality 85 and usually invisible at the sizes these images get displayed.
PNG makes sense when either the transparency has to survive the conversion or the image will go through additional editing steps. For a logo with a transparent drop shadow, converting to JPEG fills those transparent pixels with a solid color, which makes the asset unusable on any non-matching background. For an illustration you need to modify in Figma or Photoshop, PNG means you can save it as many times as the editing requires without accumulating compression artifacts from repeated JPEG encoding cycles. If after editing you want to bring the file size back down for web delivery, converting the finished PNG to AVIF or WebP gets you back to a compact format for delivery.
If you're converting an AVIF photo to submit to a portal, attach to an email, or share with someone who can't open the original format, PNG is rarely the right output. The large file size it produces for photographs creates new problems: a portal that accepts PNG but has a 2MB file size limit will still reject a 6MB PNG from a converted photo. And many official systems that list PNG as accepted actually expect small, compressed PNGs, not multi-megabyte lossless photo files. For submissions and sharing, the AVIF to JPG converter produces a much smaller, universally accepted file that handles those cases more reliably.
Converting a photo to PNG when JPEG would be smaller
PNG's lossless encoding is great for transparency and further editing, but it's a poor choice for plain photographs. A 150KB AVIF photo can become several megabytes as PNG. If there's no transparency and no further editing planned, the AVIF to JPG converter produces a far smaller file.
Assuming a portal accepting PNG wants a large file
Many portals that list PNG as accepted actually expect small, compressed images, not multi-megabyte lossless photo files. Check the portal's size limit before assuming PNG is automatically safe.
Dropping a non-AVIF file and assuming something's broken
Files that aren't recognised as AVIF are silently skipped, no error message appears. If a drop seems to do nothing, check the file actually has a .avif extension.
Not checking for transparency before choosing JPEG instead
If the source AVIF has a transparent background and you convert to JPEG on a different page, that transparency becomes a solid fill and can't be recovered. Confirm the AVIF doesn't rely on transparency before picking JPEG over PNG.
Assuming a big batch will convert instantly
Decoding and encoding both happen in your browser. A large batch of high-resolution AVIF files will take noticeably longer than a handful of small ones, that's normal, not a stall.
Choose PNG when you need lossless quality or when the image has a transparent background. PNG supports full transparency while JPG does not. Converting to JPG would fill transparent areas with a solid color and add lossy compression on top.
Yes. The tool decodes the AVIF to raw pixels and re-encodes to PNG using lossless optimisation. Every pixel in the output matches what the AVIF decoded to, nothing further is lost in the conversion step itself.
AVIF uses much more advanced compression than PNG. A small AVIF file often becomes significantly larger when converted to PNG. This is normal when prioritising lossless quality and transparency over file size.
Yes. Full alpha channel transparency from the AVIF is preserved in the output PNG. This makes it a solid choice for logos, icons and design assets.
No. All processing happens locally in your browser using WebAssembly. Your images never leave your device.
Yes. Drop or select several AVIF files and each converts independently. With a single finished file, the download button saves it directly. Once two or more files finish, you get the option to download them all together as one ZIP archive.
There's no fixed file-count limit built into the tool. Very large batches simply take longer since every file decodes and encodes in your browser rather than on a server.
No. The AVIF is decoded down to raw pixel data before being re-encoded as PNG, so EXIF metadata, including GPS location and camera details, doesn't carry over to the output file.
This tool only accepts files it recognises as AVIF, either by file extension or file type. A file that isn't AVIF is silently skipped rather than showing an error, so if a drop seems to do nothing, double check the file is actually a .avif file.
Use this when submitting files to systems that specifically require PNG, when you need to edit the image further in design software without accumulating compression artifacts, or when the image has transparency that has to be preserved exactly.
No sign-up. No upload to server. Drop your AVIF file above and download the PNG in seconds.
