Drop images here, or click to choose
Drop AVIF files here. Transparency is kept.
Free · no sign-up · nothing uploaded. Your files are decoded and re-encoded on your own device, so a photo with a face or a location in it never leaves the machine.
Open an AVIF and save it as a PNG, with the transparency kept and no second round of compression applied. The decoder doing the work is the one already in your browser.
Drop images here, or click to choose
Drop AVIF files here. Transparency is kept.
Free · no sign-up · nothing uploaded. Your files are decoded and re-encoded on your own device, so a photo with a face or a location in it never leaves the machine.
Chrome, Edge, Firefox and Safari all read AVIF, so nothing needs installing and nothing is uploaded.
No quality slider appears, because PNG has no quality setting. It records what the decoder handed it.
Cards sit on a chequerboard so see-through areas are visible. Save one file, or the batch as a ZIP.
Expect the PNG to be very large. AVIF is the most efficient of the common formats and PNG is among the least, so the gap between them is the widest of any conversion on this site. A 400 KB AVIF photograph can land somewhere north of 4 MB as a PNG. That is not a fault in the conversion. It is the two formats doing exactly what they are designed to do.
PNG has to record every pixel exactly as it found it. AVIF was allowed to decide that a stretch of sky was near enough one shade and store it in a few bytes. Undoing that decision means writing all those nearly-identical pixels out in full.
The gap closes on flat artwork. A logo, an icon, a screenshot or a chart converts to a PNG of a reasonable size, because there was less detail to record in the first place. If your AVIF is a photograph and the file size matters more than the transparency, take AVIF to JPG instead and set the quality where you want it.
The picture has transparency. This is the decisive one. JPG has no alpha channel, so see-through areas would be filled with white and there is no way back.
You are about to edit it. Every lossy save costs a little quality, and they accumulate. Working from a PNG and exporting to JPG once at the end costs one lossy pass rather than one per save.
Something downstream demands PNG. Plenty of software, print workflows and upload forms accept exactly PNG and JPG, and asking for one specifically usually means it has a reason.
It is flat artwork. Logos, icons, diagrams and screenshots are what PNG was built for, and a JPG of the same thing puts a visible halo around every hard edge.
Worth knowing before you convert a folder and delete the originals. No browser will write an AVIF, so once you have PNGs, this tool cannot turn them back. Every browser reads AVIF and none of them writes it, which makes a browser a one-way door for this format.
Keep the AVIF files until you are certain you are done with them. If you genuinely need to produce AVIF, that is a job for a command-line encoder like avifenc, or for an image editor that has added an export option.
Two reasons, and if neither applies, take the JPG and the smaller file. The first is transparency: AVIF carries an alpha channel, PNG carries an alpha channel, JPG has none, so a picture with see-through areas only survives as PNG. The second is that PNG adds no compression of its own. AVIF has already been through one lossy pass, and converting to JPG puts it through a second. PNG stops the chain there, which matters if the file is going into an editor rather than onto a web page.
It is flattened to ordinary 8-bit sRGB, and there is no setting here that prevents it. AVIF can store 10 or 12 bits per colour channel and carry the metadata that describes a high dynamic range picture. The browser canvas this tool draws on is 8 bits per channel, so the extra precision is discarded and the highlights are mapped down into the normal range. On an ordinary photograph you will not see it. On a picture that was deliberately mastered as HDR, the result will look flatter than the original, and a proper HDR-aware tool is the right answer instead.
No, and nothing can make it one. A picture served on a web page has usually been resized to fit a layout and compressed hard to save bandwidth, often to a fraction of the resolution the photographer started with. Converting it to PNG preserves exactly what is in the file you have, which is that reduced version. The dimensions on each card tell you what you are actually working with. If those numbers are smaller than you expected, the original is somewhere else and worth chasing.