AVIF to PNG — Save AVIF Losslessly as PNG Online, Keep Every Pixel and the Alpha Channel for Editing and Archiving, Processed Locally

AVIF is among the most efficient image formats available, often half the size of a JPG at the same quality, so many new devices and sites save photos as .avif by default. But it is so new that almost every editor, asset library, content management system and upload endpoint still recognises only PNG or JPG, leaving you stuck when you want to edit, cut out or make a transparent asset. This page decodes the AVIF fully in your browser and saves it losslessly as PNG: every pixel is preserved exactly and the alpha channel comes along too, making it ideal as an editing intermediate you can re-save repeatedly without quality loss. A PNG is usually the largest file, traded for its lossless nature and transparency; if you only want a smaller file, switch the dropdown to JPG or WebP at any time. Drag in several files at once, watch each one’s status and size in the batch list, step through the preview with Previous and Next to compare side by side, then download one image or pack the whole batch into a ZIP. The target-format dropdown switches at any time, and already-decoded images re-export automatically without being imported again. Decoding uses the browser’s own capability, nothing is uploaded and the page still works offline; the result is a clean new file that does not automatically carry over EXIF shooting time, camera model or location. An animated AVIF contributes only its first frame, and the batch list also lets you retry a failed file on its own or download just a few images.

Import images

Drop AVIF images here, or click to choose filesImport several at once, or press Ctrl+V to paste an image from the clipboardJPG, PNG and WebP are accepted too · up to 40.00 MB per file · 30 files maxChoose images

Target format

Output format

All three formats reuse the same decoded pixels, so switching re-exports automatically — no need to import again.

PNG keeps every pixel losslessly and preserves alpha. Best for further editing, assets and archiving, but usually the largest file.

Compression quality

PNG is lossless, so there is no quality setting for it.

Extra rotation

A few AVIF files carry an orientation flag and decode sideways. Correct them here.

Filename suffix

Leave it empty to keep the original name; the extension is replaced with the output format.

Preview and export

Import an image to compare the original and converted result side by side or with a draggable split.

Batch list

0 / 0 Done

No images imported yet.

How to use

Drag .avif images into the import area, or click Choose images to select several at once; Ctrl+V pastes a screenshot too. The tool identifies the real format from the file header, so a wrong extension does not matter.
Keep the target format on PNG and do not touch quality — PNG is lossless, so the slider is disabled. If you only want a smaller file, switch the dropdown to JPG or WebP.
A few AVIF files carry an orientation flag and decode sideways, so correct those with Extra rotation; transparent areas are preserved fully by PNG, with no fill colour needed.
Use Previous and Next in the preview to check both panes image by image, then download the current one, download individual rows from the batch list, or pack everything into a ZIP. Changing the dropdown re-exports the already-decoded images automatically.

Frequently asked questions

Does converting to PNG lose quality?

No. PNG is lossless: this page first unpacks the AVIF into full pixels and writes them back with PNG’s scheme, so every decoded point is kept and nothing goes soft or banded from re-encoding. The information truly lost in compression happened at the very first step that created the AVIF; turning it into PNG only freezes a lossless copy and cannot recover what that first compression discarded.

Will the transparent background be kept?

Yes. AVIF’s alpha channel is carried intact into PNG, so cut-out product shots and logos with rounded or feathered edges stay transparent and can be dropped onto any background for further use. This differs from JPG, which has no transparency dimension and can only fill transparent areas with a solid colour.

Why not just edit the AVIF directly?

Because most editors, design tools and asset libraries still have no AVIF read or write support, and importing fails or shows a blank. Convert the asset to PNG first and almost any editor can open it, process it, and export a final. A PNG is larger, but as an intermediate it buys universality and losslessness; if you need a smaller file for delivery, re-save as WebP or JPG at the end.

Why did the file get larger after conversion?

PNG does no lossy compression, so a detail-rich photo can swell well beyond a heavily compressed AVIF — that is the size price of being lossless. If your only goal is a smaller file, switch the dropdown to JPG or WebP; if the goal is further editing or keeping transparency, PNG is still the safest intermediate.

Are my images uploaded to a server?

No. Decoding, orientation correction, packaging and export all happen in the browser, AVIF pixels are unpacked by the browser itself, image data never leaves your device and the page has no upload endpoint. Once it has loaded you can even keep converting offline. The flip side is that the list is gone when you close the tab, so keep your own backup of important originals; the output is a brand-new file and no EXIF shooting data is carried over.

What is it

The trade-off between AVIF and PNG is really about how they compress. AVIF, launched in 2019 with AV1 video coding, packs data into a HEIF container; its lossy mode uses intra-frame prediction and adaptive quantisation to push size extremely low — often half a JPG at the same perceived quality — but by default it is lossy, and repeated saves accumulate loss. PNG, finalised in 1996, is a lossless format that compresses pixel data with DEFLATE and stores each pixel’s transparency in a separate alpha channel that any editor can read directly. Turning AVIF into PNG means the browser first unpacks the AVIF into full pixels and then writes them back with PNG’s scheme — a lossless repackaging: every decoded pixel is kept and transparent areas come along, without going soft from re-encoding. The cost is file size; PNG has no lossy mode, so the same content is usually far larger than AVIF or WebP, which makes it better as an editing intermediate or a transparency-needing asset than as a web-delivery format. EXIF, ICC and animation frames in the container do not come along, and a multi-frame AVIF contributes only its first frame. The tool identifies the real format from the file header, so a wrong extension does not matter.

Origin & history

Lay the timeline out and two formats built for different purposes meet on the same machine. PNG comes first: in 1996 the W3C published Portable Network Graphics as a recommendation, using DEFLATE for lossless compression and writing an alpha channel into a general image format for the first time. It was quickly adopted by nearly every browser, editor and operating system, becoming the de-facto standard for editing intermediates and transparent assets, at the cost of larger files and no lossy mode. The other strand begins in February 2019: Netflix, with several partners, released AVIF, built on the open AV1 video codec and packed into a HEIF container, borrowing video intra-coding’s high compression for still images. The first version already offered lossy, lossless, alpha and animation, and libavif was adopted by mainstream browsers and server-side toolchains. Then came the slow rollout: Chrome supported it by the end of that year, Firefox only caught up in 2021, and Safari completed the set in 2024, so picture elements and server-side content negotiation by request header were effectively mandatory for a few years. The interesting twist is that once AVIF spread, the trouble moved from inside the web to outside it: design software, content management systems, print workflows and upload forms long recognised only PNG or JPG, and the growing pile of .avif files in site directories could barely take a step beyond the browser, especially when further editing was impossible. The real solution needed no new algorithm: canvas toBlob had long accepted image/png, so the encoding side was never the obstacle, and once browsers could unpack AVIF pixels natively, local decoding plus local re-encoding became the most dependable combination — one that does not even need an upload endpoint. Today a single click losslessly lands a new format back into a universal one; what looks like merely skipping one upload is in fact handing a piece of computation that should have stayed local back to the local device.For design work meant to be kept long term, this lossless relay is more dependable than repeated compression.