Convert PNG to AVIF
Shrink transparent PNG logos, cutouts and illustrations into AVIF files a fraction of the size — encoded by your own browser, one file or a whole folder.
Your images
Settings
Generated images
- Nothing uploaded
- Free, no sign-up
- Strips EXIF
- Batch files
Transparent PNGs are the heaviest files on almost any site. A 1,500 px product cutout or hero illustration exported from Figma or Photoshop lands at 1–3 MB, because PNG stores every pixel losslessly and cannot do otherwise. Converting that file to AVIF keeps the transparent background exactly and, at this page's default quality of 82, typically cuts it by 80–90%: a 2.4 MB cutout comes back somewhere around 250 KB.
That is a bigger drop than PNG to WebP delivers, because AVIF's AV1-based encoder discards far more of what the eye can't distinguish while still carrying a full 8-bit alpha channel. On graphics with transparency, AVIF usually lands 20–50% under WebP at the same visible quality, and both sit far below the lossless original.
One caveat before you drop files in: the AVIF is written by your browser's own encoder, not by a server. Chrome, Edge, Opera and other Chromium browsers have one; Safari and Firefox generally don't, and on those the output quietly becomes a JPG with a white background. Step 3 below is a two-second check for that, and the last section covers the cases where WebP is the safer pick.
How it works
AVIF is preselected on this page as soon as the browser confirms it can write it. What's left is the quality number and confirming that this browser can write the format.
Add the PNGs
Drag in the files, pick them from a folder, or paste a screenshot with Ctrl+V. There's no file limit, only your device's memory, but AVIF encoding is several times slower than WebP per pixel, so feed a laptop a few dozen large files per round rather than a few hundred.
Set the quality for the content
The slider runs from 30 to 100 and opens at 82, which suits photographic cutouts and 3D renders. Push it to 90 or above for logos, flat illustrations and any screenshot with small text, since text is the first thing lossy compression softens.
Generate, check the extension, download
Press Generate images. Each card shows the original size next to the new one, and Compare puts a before/after slider over a checkerboard so you can inspect the transparent areas. A name ending in .avif means the transparency made it; .jpg means this browser has no AVIF encoder and the background was filled white. Download files one at a time or all of them as a .zip.
How much smaller a transparent PNG gets as AVIF
The AVIF written here is lossy: the slider decides how much detail is discarded, and there is no lossless mode. That trade is where the savings come from; on photographic cutouts and renders it is invisible at 82.
The saving depends on what the PNG contains, not its pixel dimensions. Typical results at the default quality:
| PNG content | AVIF at quality 82 | Worth checking |
|---|---|---|
| Photo or 3D render saved as PNG | 85–95% smaller | Nothing |
| Product cutout with transparency | 75–90% smaller | Soft edge on a dark background |
| UI screenshot, chart, diagram | 50–80% smaller | Small text; use 90+ if it blurs |
| Logo or flat-color illustration | 60–85% smaller | Fringe along hard edges |
| Indexed icon under about 5 KB | Often larger | Keep the PNG |
The transparency survives; the encoder is the risk
AVIF has a full alpha channel, so fully and partially transparent pixels pass through unchanged, including the anti-aliased rim of a cutout logo: no jagged edge, no white halo. The slider only touches the color under that rim; if a flat logo shows a faint fringe in Compare, regenerate at 95.
This page checks on load whether the browser can write AVIF and shows the AVIF button only if it can: Chrome, Edge, Opera and Brave on desktop and Chrome on Android pass; Safari, iPhone and iPad browsers, and usually Firefox do not. Without the encoder the output falls back to JPG, which has no alpha channel, so the transparent area is filled white with no warning. Sides over 10,000 px are downscaled first, and EXIF is dropped.
When WebP is the safer choice
AVIF is smaller, but not always the right choice. Switch the format bar to WebP when:
- You are on Firefox. Safari and every iPhone browser write neither AVIF nor WebP from a canvas — keep PNG there. WebP's fallback here is PNG, which keeps the transparency.
- The file has to open anywhere. WebP displays in roughly 97% of browsers and most CMS plugins and viewers accept it; AVIF sits near 94% and older desktop software refuses it.
- You have hundreds of large PNGs. WebP encodes several times faster, and AVIF's extra saving on graphics is about 20–50%, not another order of magnitude.
- The images are small icons or sprites. AVIF spends a few hundred bytes on its container before the first pixel, so WebP or the original PNG ends up lighter.
Where the .avif files will and won't open
- Browsers: Chrome 85+, Firefox 93+, Safari 16+ and Edge 121+ display AVIF; serve it in a picture element with a WebP or PNG fallback for the rest.
- WordPress takes .avif uploads from 6.5 (April 2024) if the host's image library was built with AVIF; a rejected upload means it wasn't.
- macOS Preview opens AVIF since Ventura; Windows Photos needs the free AV1 Video Extension; older viewers show nothing.
- Email signatures, forms that only take JPG and PNG, and print shops: send the PNG.
Frequently asked questions
Does converting PNG to AVIF keep the transparent background?
Yes, provided your browser writes AVIF. The format has a full alpha channel, so transparent and semi-transparent pixels come through, soft edges included. If the downloaded name ends in .jpg rather than .avif, the encoder was missing and the background was filled white.
Why did I get .jpg files instead of .avif?
Your browser has no AVIF encoder: Safari on a Mac, any browser on an iPhone or iPad, and usually Firefox. Open this page in Chrome, Edge or Opera on a desktop or in Chrome on Android, or switch the format bar to WebP where the browser supports it (Firefox and Chrome do; Safari does not).
Can I make a lossless AVIF here?
No. The AVIF this page writes is always lossy; the slider (30–100, default 82) only sets how much is discarded. If you need pixel-exact output, the right format is still PNG.
What quality should I use for a logo, a screenshot or a product cutout?
Logos and flat illustrations: 90 or higher, then check the edge in Compare on a dark background. Screenshots with small text: 90–95, zoomed in. Photographic cutouts and renders: 70–82 is usually indistinguishable from the PNG.
Why is the AVIF bigger than my PNG?
The PNG was almost certainly a small indexed image: an icon, a bullet, a map pin with a handful of colors. Those are already tiny, and every AVIF spends a few hundred bytes on its container before the first pixel. Compare the two sizes on the card and keep the smaller one.
AVIF or WebP for the transparent PNGs on my site?
AVIF if your visitors are mostly on current browsers and you serve a fallback through a picture element; it is typically 20–50% smaller than WebP on graphics. WebP if the files must open in older software, email or a CMS without AVIF support, or if you are converting on a browser that can't write AVIF.
Can I upload the .avif files to WordPress?
Yes, from WordPress 6.5 (April 2024) onward, as long as the host's Imagick or GD library supports AVIF. If the media library rejects the file, ask the host to enable it or upload the WebP version instead.
These are unreleased product renders. Do they leave my computer?
No. Decoding, AVIF encoding and building the .zip all happen in your browser on your own machine; no PNG or AVIF is sent to a server, and there is no account or history to clear. EXIF is stripped from the output as well.