Convert PNG to AVIF

Drop PNGs below and get AVIF back, transparency included. AVIF is already selected, and files go up to 16 MB as a guest or 32 MB with a free account. Free. No account, no watermark.

  • Transparency kept
  • Sharp edges on graphics
  • AVIF already selected
Compression Level
None
No compression, only apply settings on image
Lossless
Without any visual change in the image quality
Ultra
Max compression with some quality loss
Smart
Balance between the image quality and compression
Change Format Will allow you to convert images to different extensions
Auto WEBP AVIF PNG JPG Auto tries every format your image can be saved as and gives you the smallest one
Resize Will allow you to change the width, height or scale of images
Keep EXIF Will allow you to preserve meta data in images
Maximum file size is 16 MB per image and supported formats are: PNG, JPG, JPEG, WEBP, GIF, HEIC, HEIF, TIFF, TIF
Guests get 10 images a day, 10 left today. A free account gets 40 a day.
Delete this image?
The image and its optimized copy will be removed from storage. This cannot be undone.

Rename this image
Choose the name the optimized image downloads with. Its format stays the same.

Uploaded as

Rename the selected images
Each image gets this name and a number, counted in the order they were uploaded. Their formats stay the same.

Share this image
Choose the compression level that suits your images
Level What it promises What happens Pick it when
Lossless
Not one pixel changes in a JPEG, PNG or GIF The file is repacked, never re-encoded. JPEGs get an optimised Huffman table and progressive scan, PNGs a tighter deflate pass, GIFs a lossless gifsicle run. A lossy WebP has no repack step, so it is re-encoded at the highest quality the level allows. A sideways phone JPEG is rotated losslessly on the way through and keeps its colour profile. The one exception to the promise is a PNG or WebP tagged with a wide-gamut profile such as Display P3: its colours are converted to sRGB, so the values change but the picture doesn't. Logos, line art, anything you'll edit again, or when the file is evidence.
Smart
No visible change, targets 40 dB PSNR and a perceptual score of 70 A quality search runs per image and stops at the lowest quality that still clears the PSNR target. That answer is then scored on the SSIMULACRA 2 scale, because an average over every pixel lets a mostly flat picture through at a quality its detail doesn't deserve, and when it falls under 70 the search moves back up until it doesn't. Photos and graphics end up at different qualities because they need different ones; an image that cannot reach the targets inside the quality ceiling is encoded at the ceiling. Almost everything on a website. This is the default for a reason.
Ultra
Smallest file, targets 34 dB PSNR and a perceptual score of 50 The same two-stage search with lower targets. Fine texture softens a little; edges and text stay sharp. Thumbnails, backgrounds, email images, anything shown small or blurred anyway.
None
No compression at all Only the resize, conversion or metadata setting you chose is applied. An untouched upload comes back byte for byte. You only wanted to resize or convert, and quality is someone else's decision.

Measured, not estimated

What PNG to AVIF did to four real graphics

Two screenshots, a social card and an icon with transparency, all from our showcase, converted by the pipeline your upload goes through. Read the Lossless column closely: it's the one place this conversion goes wrong.

Sample Original Lossless Smart Ultra
Social card 1200 by 630 208 KB PNG 234 KB 12.5% larger 11 KB 94.7% smaller 11 KB 94.9% smaller
Phone screenshot 1170 by 2532 0.9 MB PNG 1.0 MB 7.3% larger 155 KB 83.9% smaller 90 KB 90.7% smaller
App icon 1600 by 1600 113 KB PNG 120 KB 5.7% larger 7 KB 93.8% smaller 7 KB 94% smaller
Desktop screenshot 1440 by 900 303 KB PNG 303 KB 0% larger 212 KB 30.1% smaller 133 KB 56.1% smaller

Metadata stripped, no resize. The desktop screenshot is the odd one out: it is mostly text, and at Smart a quantised PNG of it comes out smaller than this AVIF does.

Where it shines

Lossy AVIF on a graphic is the big win

A PNG stores every pixel exactly, which is why a full-screen screenshot can weigh a megabyte. Most of the time you don't need exact. A lossy AVIF of the same screenshot looks identical at normal size and is a fraction of the weight.

Graphics are hard on lossy codecs because of their edges. Iminify checks whether your PNG is a drawn image or a photograph, and a drawn one gets full-resolution colour (4:4:4) so red text on white doesn't smear. Photos get 4:2:0, which is smaller and shows no difference on them.

Lossless is the honest exception. AVIF has a lossless mode, but it isn't an efficient one: on three of our four samples the lossless AVIF came out bigger than the PNG it started from. If you need every pixel, convert to WebP instead or compress the PNG as a PNG.

What survives

What a PNG keeps on its way to AVIF

  • Transparency

    AVIF carries an alpha channel, so a logo on a transparent background stays that way at every level.

  • Hard edges

    Drawn images keep full colour resolution, so text and icon outlines stay crisp where a photo setting would blur them.

  • EXIF, when you switch it on

    Rare in a PNG, but if yours has an EXIF block and Keep EXIF is on, it's written into the AVIF.

  • Animation

    An animated PNG becomes its first frame. AVIF output here is a still image.

When not to

When to leave the PNG alone

  • You need a lossless copy. Lossless AVIF is usually larger than the PNG; lossless WebP is usually much smaller.
  • The image is mostly text or flat UI. A quantised PNG can beat AVIF there, as the desktop screenshot above shows. Auto tries both and keeps the winner.
  • The file is a source asset you'll edit again, or it must open in software that predates AVIF.

How to

PNG to AVIF in three steps

  1. 1

    Drop your PNGs

    Screenshots, logos, exports. AVIF is already chosen under Change Format.

  2. 2

    Stay on Smart

    Smart and Ultra are where AVIF pays off. Skip Lossless for this pair.

  3. 3

    Check the edges

    Open Compare, zoom to actual size and look at the text. Then download.

Questions

PNG to AVIF questions

From the blog

What we've measured so far

We run the encoders on real photos and screenshots and publish the numbers: when WebP beats AVIF, what quality 80 means in each encoder, and how many kilobytes an image on a web page should weigh.

All posts
ComfyUI's Flux Dev example render of a fox-eared girl in a maid dress holding a cake, captioned: 1,215,064-byte PNG to 125,684-byte WebP, and the workflow still loads in ComfyUI.

ComfyUI PNG to JPG loses the workflow. WebP and AVIF can keep it

ComfyUI's Flux Dev example image is a PNG of 1,215,064 bytes, and the two text chunks holding its prompt and workflow take 12,240 of them. The rest is 1024x1024 pixels stored without loss. Across the 92 PNGs in ComfyUI's examples repository that carry a workflow, the text was no more than 3.32 percent of any file, with a median of 0.62 percent. Converting to JPG shrinks the file, but ComfyUI's own loader can't read a workflow back out of a JPG. A WebP or AVIF can keep it, at about a tenth of the size. We took the text-to-image examples of ten models from ComfyUI's examples repository, made smaller copies several ways, and dropped the copies back onto ComfyUI 0.37.0's canvas to see which ones still held the workflow.

6 min read
Bar chart of one photograph in bytes: 852,461 as served, against Lighthouse's target of 45,084 at its phone slot and encodes of 47,876 (JPEG), 46,320 (WebP) and 41,735 (AVIF).

Improve image delivery in Lighthouse: what it replaced and how it counts savings

PageSpeed Insights ran Lighthouse 13.5.0 on our home page on 22 September 2026 and flagged "Improve image delivery" in the mobile report: "Est savings of 1,300 KiB". All of it came from one photograph. The fjord shot in our before-and-after comparison is on the page twice, as the 832.5 KiB original and as our own compressed copy at 555.3 KiB. Both files are 1800x1200, and the report says they're displayed at 637x425. Three later runs that day said 1,359 KiB and 364x243. If your old notes say "Serve images in next-gen formats" or "Properly size images", this is where they went: Lighthouse 13 folded four image audits into this one insight. And its savings aren't measured: each figure is arithmetic on bytes and pixels. We reproduced every number in that insight, made the file it asks for, and traced one reason the same page gets two answers.

8 min read
The harbour picture Nano Banana 2 generated at 4K, 5504x3072: 10.51 MB as sent, a quality-100 JPEG, and 1.58 MB re-encoded as a quality-82 JPEG holding 40 dB.

How big is a Nano Banana image? 52 files measured, from 512 px to 4K

We asked Nano Banana 2 for a 4K, 16:9 picture of a fishing harbour through the Gemini API on 23 September 2026. It came back as a 5504x3072 JPEG of 10.51 MB. The same request again gave 11.10 MB. Both files were saved at JPEG quality 100, the top of the scale. So, how big is a Nano Banana image? From Nano Banana 2 or Pro, a detailed picture is roughly 1 MB at 1K, 4 MB at 2K and 10.45 to 12.13 MB at 4K, and a flat illustration less. The original Nano Banana sends a PNG instead, about 2.1 MB for the same prompt at 1024x1024. Here are the 52 images of our test set, from all four Nano Banana models, and what five of them shrink to.

9 min read

Shrink your PNGs with AVIF

Drop a screenshot and compare the text at actual size before you download.

Convert PNG to AVIF Open the full tool