Skip to main content

AVIF to PNG converter

Convert AVIF images to PNG format

No watermarkFree & unlimited
All processing happens in your browser. No data is sent to any server.

Most people arrive here because something refused to open an AVIF: an image editor, a content system, a colleague on an older laptop. PNG is the universal answer. The decode is done by your browser's own AV1 image decoder, and the PNG that comes out is lossless, meaning it captures exactly what the AVIF decoded to, artefacts included. It does not undo the AVIF compression, and it will be much larger than the source.

Key facts about AVIF to PNG converter

Key facts about AVIF to PNG converter
Decoding requirementYour browser must read AVIF. Chrome 85, Firefox 93 and Safari 16 and later can; older builds fail with a load error rather than a wrong picture.
Size deltaFive to twenty times larger. A 120 KB AVIF of a full HD photograph commonly becomes a two to four megabyte PNG.
Artefacts are baked inPNG preserves what it is given. AV1 block artefacts and softened detail from the original encode are copied faithfully and cannot be recovered.
TransparencyFully preserved. AVIF holds alpha as a separate auxiliary item and PNG stores an alpha channel, so cut-outs come through with the same per-pixel values.
High bit depth is flattenedAVIF can carry 10 or 12 bits per channel, but the browser canvas is 8-bit, so a high-bit-depth source is reduced before the PNG is written.
HDR and wide gamutAn AVIF tagged with a PQ or HLG curve, or BT.2020 primaries, is converted during decode. The PNG carries no profile and is read as sRGB.
Animated AVIFReduced to one frame. AVIF image sequences exist, but the canvas captures a single picture and PNG has no timeline.
Opens the resultEverything, including the Windows 10 machines, older Photoshop installs, email clients and CMS uploaders that reject AVIF outright.

What happens to your file

The decode happens in your browser and the encode does too. Your AVIF is exposed through an object URL, an Image element asks the browser's AV1 still-image decoder for pixels, and those pixels are painted into a canvas this page created. canvas.toBlob then produces the PNG with the browser's own Deflate-based encoder. There is no upload step and no server behind this page.

About this tool

  1. 1

    Add the AVIF files

    Drag up to twenty .avif files onto the drop area or click to browse. Each file may be up to 500 MB.

  2. 2

    Confirm the preview renders

    If nothing appears, your browser cannot decode AVIF and the conversion will fail; try a current Chrome, Firefox or Safari.

  3. 3

    Resize if you only need a smaller copy

    Presets cap the long edge before encoding, the only way to stop a full-resolution PNG becoming enormous.

  4. 4

    Convert and download

    Press Convert and save the PNG, or take converted-png-files.zip which is built inside the browser.

Specs & compatibility
Input and outputTakes .avif only (image/avif) and returns .png with the image/png type; any other extension is refused before decoding.
Conversion pathAVIF to PNG runs in three steps: an <img> element decodes the AVIF, which the browser itself must be new enough to read; the pixels land on a 2D canvas in this tab; then canvas.toBlob with the image/png type returns the finished file.
Browser supportThe AVIF side needs Chrome 85, Firefox 93 or Safari 16.4 to decode, while writing the PNG is just as universal, canvas.toBlob having produced it since canvas existed.
Controls for this pairNo quality slider, PNG not being a lossy target here, so the max-dimension presets from 3840 down to 200 px are the only way to hold the PNG down in size against the AVIF.
Batch, caps and namingTwenty AVIF files per run at 500 MB each; one result downloads as a single PNG, several as converted-png-files.zip, zipped by JSZip 3.10 in page memory.
Device ceilingThe canvas caps it: past roughly 16,384 px a side Chromium refuses the bitmap and iPhone Safari gives up sooner, so an oversized AVIF fails before any PNG bytes exist.
  • If the PNG is uncomfortably large, run it through a palette optimiser such as pngquant, or convert to WebP instead.
  • Convert at the size you need; a full-resolution PNG of a photo is often ten times the disk cost for no visible benefit.
  • Keep the original AVIF for delivery and use the PNG only for the tool that could not open it.
  • Transparency survives exactly, so this is the right route when a cut-out product image has to reach a design tool intact.
  • Browser AV1 decode to lossless PNG
  • Alpha channel preserved pixel for pixel
  • Pre-encode resize presets down to 200 px
  • Twenty AVIFs decoded in a single pass
  • Opening AVIF images from a modern website in an editor that has never heard of the format.
  • Supplying artwork to a client or printer whose intake rejects anything but PNG and TIFF.
  • Getting a transparent AVIF product shot into a design tool without flattening the background.
You are moving from one of the most efficient lossy codecs in existence to a lossless one. AVIF discards information the eye is unlikely to miss and predicts the rest with AV1; PNG keeps every pixel and compresses only through Deflate. A five to twenty times increase is normal rather than a fault.
No, and it is important not to expect that. PNG reproduces exactly what the browser decoded, including any blocking, banding or lost fine detail from the original AVIF encode. Lossless is a guarantee about what happens next, not a repair of what happened before.
That means your browser cannot decode AVIF, so nothing here can proceed. Support arrived in Chrome 85, Firefox 93 and Safari 16 and is absent from older builds and some embedded browser views. The failure is loud rather than silent, so you never receive a blank PNG.
No. AVIF can carry EXIF and XMP in dedicated boxes, but that never reaches the canvas; only pixels do. The PNG is written from those pixels alone, so camera model, exposure, GPS and orientation are absent. Extract the metadata with exiftool first if you need it.
It is flattened. The browser decodes into the 8-bit sRGB format a 2D canvas uses, applying whatever tone mapping it implements for HDR curves. The PNG stores those values with no profile, so software assumes sRGB and the extra range is gone permanently.

Related tools

View all

Need the opposite? Try PNG to AVIF

Updated

We use anonymous analytics to improve ToolChamp. No personal data is stored or sold. Privacy Policy