NiftyWebTools
Start free
Nifty Tools
Convert avif to png in your browser. Batch up to 50 images at a time. No upload, no signup, no watermark. Lossless from canvas pixels, alpha preserved.
Processing mode: Local Browser-local
Keep working
AVIF Converter — Free, In Your Browser
AVIF converter that runs in your browser. Convert avif to jpg or png in batches of 50. No upload, no signup, no watermark.
AVIF to JPG Converter — Free, In Your Browser
Convert avif to jpg in your browser. Batch up to 50 images at a time. No upload, no signup, no watermark. Quality slider, alpha flattens to white.
WebP to PNG Converter — Free, In Your Browser
Convert webp to png in your browser. Batch up to 50 files. No upload, signup, or watermark. Alpha preserved for editors and upload flows.
HEIC to PNG Converter — Free, In Your Browser
Convert heic to png in your browser. Batch up to 50 iPhone photos at a time. No upload, signup, or watermark. Lossless from the decoded pixels.
Convert Image Files
Convert images to WebP, JPEG, or PNG for websites, uploads, and sharing.
Compress Image
Make images smaller for websites, email, marketplaces, and forms.
Resize Images
Batch resize images by width, percentage, or common web-friendly dimensions.
PNG to PDF Converter Free Online
PNG to PDF converter that runs in your browser. Embed PNGs losslessly with alpha preserved — no upload, no signup, no watermark.
Images to PDF
Turn ordered JPG, PNG, WebP, and AVIF images into one clean PDF.
How to use it
Good for
People convert AVIF to PNG when the next tool, platform, or pipeline in their workflow needs an alpha-preserving raster format and AVIF isn't on its accepted list. AVIF lands smaller than WebP or JPEG at the same visual quality and renders inline in current Chrome, Edge, Firefox, and Safari, but the support story collapses the moment the file leaves the browser. Recent Photoshop versions support AVIF natively, but older perpetual-licence and CS-era installs cannot read it without a plugin or refuse it outright. Affinity Photo's AVIF handling varies by version and platform; older installs may reject the file. Many older or locked-down Office installs — perpetual-licence Office 2019-era deployments and enterprise machines without current Microsoft 365 image-format updates — fail to render AVIF reliably; the paste lands as a broken-image placeholder. Many common marketplaces and print-on-demand pipelines document JPG/PNG as accepted raster formats and do not list AVIF — Etsy's accepted list names `.jpg`, `.gif`, `.png`, `.svg`, and `.heic`; Society6, Redbubble, and Printful document JPG and PNG as their accepted raster formats. PNG is the right target whenever the source has intentional transparency that needs to survive the conversion — AVIF carries an alpha channel and so does PNG, so the round-trip preserves alpha at the canvas-pixel level. The conversion is lossless from the decoded canvas pixels (the encoder writes exactly what the canvas holds), but it is not a bit-for-bit metadata copy: ICC colour profiles, HDR signalling, and other container-side AVIF metadata do not carry through the browser's decode-into-canvas path, which works in sRGB on every current build. For ordinary screenshot, design-comp, logo, and product-photography work, that's the right trade — broad compatibility with whatever rejected the AVIF, alpha intact, and the file never leaves the tab.
Processing mode
Files are processed by your browser. They never reach our servers.
Questions
The format itself is the issue for that surface. Recent Photoshop versions support AVIF natively, but older perpetual-licence and CS-era installs reject the file without a plugin. Affinity Photo's AVIF handling varies by version and platform; older installs may reject the file. Slack's custom emoji uploader documents PNG, JPG, and GIF; Discord's custom emoji uploader documents JPEG, PNG, GIF, and WEBP (Discord stickers follow a separate format spec); neither surface documents AVIF as an accepted format. Converting to PNG removes the format dependency entirely while keeping the alpha channel that JPG would flatten — important when the AVIF is a logo cutout, custom emoji, or icon with intentional transparency.
Yes, from the decoded canvas pixels. The AVIF decodes into the canvas, and `canvas.toBlob("image/png")` writes exactly what the canvas holds — PNG is lossless, so the encoder does not re-compress. The alpha channel round-trips intact, hard edges stay sharp, and there are no JPEG-style halos around type or vector shapes. The caveat is that the canvas-pixel round-trip is not a bit-for-bit metadata copy of the source AVIF: ICC colour profiles, HDR signalling, and other container-side AVIF metadata are not carried through the browser's decode pipeline, which works in sRGB on every current build. For ordinary screenshot, design-comp, logo, and product-photography work that's the right trade-off, because the destination tool is going to render in sRGB anyway. If you need byte-identical preservation of an AVIF's container metadata, do not run it through any browser-based decode-and-re-encode tool.
Yes. AVIF carries an alpha channel and so does PNG, so transparent regions in the source come through as transparent regions in the output. The canvas is created in alpha-aware mode (no white-fill prepass), so the decoded pixels go straight into the PNG encoder without flattening — what you see in the AVIF is what comes out in the PNG. If your source has no transparency (a photograph, a screenshot of a solid-background app), the PNG will be larger than the equivalent JPG would be — that's expected, PNG is lossless and JPG is not. Pick the AVIF to JPG sister tool if file size matters more than alpha preservation for the destination.
Current Chrome, Edge, Firefox, and Safari. AVIF decoding rolled out across the major engines at different times — Chrome 85 (August 2020), Firefox 93 (October 2021), iOS Safari 16 (September 2022), macOS Safari 16.4 (March 2023 — earlier 16.x desktop builds shipped partial or no AVIF support), and Edge 121 (January 2024). The tool relies on the browser's built-in `<img>` decoder for AVIF, so any browser that renders an `.avif` inline on a webpage can also run this converter. The PNG encode step uses `canvas.toBlob("image/png")` — `image/png` is the HTML spec's mandatory canvas-export baseline, so every current Chrome, Edge, Firefox, and Safari encodes PNG from a canvas without any format-fallback story to guard against. If you are on an older build that pre-dates AVIF decoder support, the tool will surface a clear decode-failed error rather than producing a broken file — the workaround is to update to a current Chrome, Edge, Firefox, or Safari.
Each AVIF must be under 100 MB and a single batch can hold up to 50 images. The 100 MB cap protects lower-RAM devices from running out of memory during decode, since the browser materialises the full pixel grid into a canvas before re-encoding. The 50-file cap keeps the ZIP build responsive — for large batches the bottleneck is browser memory, not the conversion itself, since each image processes sequentially. If you need to convert more than 50 images, run the tool twice and stack the resulting ZIPs.
AVIF is tuned for compression density: it lands smaller than JPEG at the same visual quality, often by 20-50% for photographic content. PNG is a lossless format and does not compress photographic content nearly as tightly. For an AVIF that started life as a JPG, the PNG output will commonly be several times the AVIF's file size. That is expected and not a bug — you are unwinding a denser encode of the same image into a more broadly-supported, lossless container. If file size matters more than alpha preservation or lossless reproduction for the destination, use the AVIF to JPG sister tool instead — JPG is much closer to AVIF's compression target for photographic content.
The basic workflow is designed to stay free. Paid upgrades later will focus on bigger limits, batch work, OCR, saved presets, and ad-free use.