Convert AVIF to PNG With No Quality Loss
Convert AVIF to PNG in your browser. PNG guarantees nothing is lost from here on — it cannot recover what AVIF already discarded, and this page is honest about which of the two you are getting.
Your images never leave your device
Nothing to delete later
Secure connection
Works in every modern browser
How it works
- 1
Add your AVIFs
Drop the files onto the page or click to browse and select them.
- 2
Convert
Each image is decoded and re-encoded as PNG in your browser, with the size change shown.
- 3
Download
Save the PNGs individually or all at once as a zip.
Why use this tool
Opens where AVIF cannot
The real reason to do this: older editors, print workflows and internal tools still reject an AVIF outright.
No further loss added
PNG re-encodes without a quality setting, so nothing degrades again no matter how often you save it.
Alpha channel carried across
AVIF stores transparency as a separate plane, and that plane is mapped into the PNG rather than flattened.
Banding risk reported
A 10-bit or wide-gamut AVIF loses colour depth on the way to 8-bit PNG, and you are told when that applies.
Size increase shown upfront
A photographic AVIF usually grows several times over as a PNG, so the number appears before you download.
Nothing is uploaded
Decoding and re-encoding both happen on your device, so the picture never becomes someone else’s copy.
A lossless destination does not undo a lossy source
This is the single most misunderstood thing about converting to PNG, and it is worth being blunt about. PNG is lossless, which means it will not throw anything away — but that guarantee only applies from the moment of conversion onward. If the AVIF you started with was encoded lossily, and almost every AVIF on the web is, then the detail it discarded is already gone. The PNG faithfully preserves the compressed result, artefacts included; it does not reconstruct the original. What actually changes is size, in the wrong direction: AVIF is one of the most efficient formats ever standardised, so a photograph that occupied 300 KB as an AVIF routinely becomes two or three megabytes as a PNG. You are paying five to ten times the bytes to store exactly the same information. That is a reasonable trade when you need compatibility or an editable master, and a poor one when you were hoping the picture would somehow improve.
Where this conversion genuinely loses something: colour depth
There is one respect in which AVIF to PNG is not merely inefficient but actually lossy, and it catches people who assumed lossless meant identical. AVIF inherits its capabilities from the AV1 video codec, so it can store 10-bit and 12-bit colour, wide gamuts such as BT.2020 or Display P3, and HDR transfer curves. A standard PNG as written by browsers and by this page is 8-bit per channel in sRGB. When a 10-bit source is reduced to 8 bits, a smooth gradient that had 1024 steps has to fit into 256, and the eye sees that as banding — visible stripes across a sky, a studio backdrop or a soft shadow. Wide-gamut colours outside sRGB are clipped to the nearest colour that fits, so saturated reds and greens shift slightly. Neither problem shows up in a photo of a busy street; both are obvious in anything with a large area of gentle transition. If the AVIF is HDR, this conversion is the wrong tool, and keeping the original is the better answer.
AVIF transparency is its own plane, and it may already be lossy
Alpha behaves differently in AVIF than most people expect from PNG. A PNG stores transparency as a fourth channel alongside red, green and blue, compressed by the same lossless algorithm as the rest. AVIF stores the alpha channel as a separate monochrome image and can compress it lossily, at a quality setting that need not match the colour channels. The practical consequence is that a semi-transparent edge — the anti-aliased outline of a logo, the soft boundary of a cut-out, a drop shadow fading to nothing — can arrive with its own compression artefacts baked in before PNG ever sees the file. Converting to PNG locks those in exactly as they are. This is why a logo that looked crisp on a dark web page can show a faint halo once the PNG is placed on a white background: the halo was in the AVIF all along, and only the new background revealed it. Worth checking the edges after conversion rather than assuming.
The honest reason to do this is compatibility, not quality
It helps to be clear about what you are buying, because the answer is narrower than most converter pages suggest. AVIF has been supported in every major browser for several years, so if the destination is a web page, converting to PNG usually makes things worse — a heavier file for no visible gain. The genuine cases are elsewhere. Plenty of desktop software still refuses AVIF: older versions of Photoshop and Illustrator, most print and prepress workflows, a lot of internal enterprise tooling, many content management systems, and a surprising number of file-upload forms that validate by extension. Embedded and industrial systems tend to read PNG and nothing newer. In those situations PNG is not a downgrade, it is the only thing the other end can open. Choose it for that reason, keep the AVIF as the master, and go back to the original whenever you need the small file again.
Why the conversion is slower than you expect
If a batch takes longer than converting the same number of JPEGs would, nothing is wrong — the cost is inherent to what AVIF is. An AVIF is a still frame encoded with AV1, a video codec designed to spend a great deal of computation at encode and decode time in exchange for very small files. Decoding one is closer in effort to decoding a frame of video than to reading a JPEG, and browsers only recently gained hardware acceleration for it on some devices. On a phone or an older laptop, a folder of large AVIFs will work through visibly slower than the same folder of PNGs would, and the tab may feel busy while it does. That is the format doing what it was designed to do. The re-encode into PNG is comparatively quick; the decode is where the time goes.
Converting on your own machine, and why it matters for this format
AVIF turns up in a particular way: it is what a modern site serves you when you save an image, what a phone camera may now produce, and what design tools increasingly export. That means the AVIF sitting in your downloads folder is often something personal rather than something public — a photo saved from a private album, a screenshot of an internal dashboard, a design comp that has not shipped. Hosted converters take that file, send it to a server, decode it there and offer a deletion promise as reassurance. Nothing here is sent anywhere: the browser decodes the AV1 frame and writes the PNG using its own image pipeline, so the file is read from disk and written back without a single network request. You can confirm it the direct way — open the network panel before you drop the files in, and watch it stay empty while the conversion runs.
Common mistakes to avoid
- Expecting PNG to restore quality. Lossless applies from the conversion onward — whatever the lossy AVIF discarded is already gone, and the PNG preserves the compressed result, artefacts included.
- Converting an HDR or 10-bit AVIF without checking. Standard PNG output is 8-bit sRGB, so smooth gradients band and wide-gamut colours clip — this is the one place the conversion truly costs you.
- Assuming a semi-transparent edge is clean. AVIF compresses its alpha plane separately and can do so lossily, so a halo around a cut-out may have existed before PNG ever saw the file.
- Converting for the web. Every major browser has read AVIF for years, so replacing it with a PNG several times the size makes the page slower for no visible benefit.
- Throwing away the AVIF afterwards. It is the smaller file and the better master — keep it, and treat the PNG as the compatibility copy you generated for one destination.
How it compares
| Feature | This tool | Typical online converters |
|---|---|---|
| Images uploaded to a server | Never — converted in your browser | Usually uploaded |
| Warns about bit-depth loss | Yes | Rarely |
| Shows the size increase | Before you download | Usually not |
| Watermark on output | No | Sometimes |
| Image-count limit | Unlimited | Often capped on free tier |
| Price | Free | Free / paid tiers |
Features
Standard PNG output
Ordinary 8-bit RGBA PNG that every editor, browser and operating system already reads.
Alpha plane preserved
Transparent and semi-transparent areas are mapped across instead of composited onto a background.
Colour depth warning
High bit depth and wide-gamut sources are flagged, because that is where this conversion actually costs you something.
Batch conversion
Add a folder of AVIFs and convert them in one pass without an upload queue.
Dimensions unchanged
Width and height stay exactly as they were — only the container and the encoding change.
No installation
Nothing to download or install — it runs on the web page.
Arabic and RTL friendly
Full interface in eight languages, including right-to-left Arabic.
Secure by default
Served over HTTPS, with no file tracking and no third-party upload.
Who uses it
Designers and editors
Getting an AVIF into software that refuses to open one, with transparency intact.
Print and prepress
Producing a file a prepress workflow will accept, since almost none of them read AVIF.
Developers
Turning a downloaded AVIF into something a legacy pipeline or upload validator will take.
Anyone with a saved AVIF
Making a file usable in an app that rejects the format, without sending it to a server.
Frequently Asked Questions
Use PNG when you need lossless quality, transparency support, or when working with graphics and design assets. PNG preserves every pixel exactly, while JPG uses lossy compression.
Yes. If your AVIF file contains transparent areas, they will be fully preserved in the PNG output.
AVIF is supported in Chrome 85+, Firefox 93+, Safari 16.4+, and Edge 85+. Our tool shows a notification if your browser cannot decode AVIF files.
Yes. AVIF offers excellent compression while PNG is lossless, so PNG files will typically be larger. This is the expected trade-off for lossless quality.