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

Balance between the image quality and compression

Output format

Auto tries every format your image can be saved as and gives you the smallest one

Resize

Change the width, height or scale of every image you upload

Original Dimensions Percentage
px
px

Set one side to keep the proportions, or both for an exact size.

Percentage
%

Size limit

Fit every image under a file size, for a form or a site with an upload limit

Any size Under a size
KB

Saved as JPG, WebP or AVIF. When quality alone can't get there, the image is made smaller to fit.

How the size limit works

Responsive image set

Pro

The image at several widths, with a srcset to paste into your page, so each screen loads the size it needs

One size Responsive set
px

Up to 8 widths, each in the format and at the level of the result. A width wider than the image stops at its own width, so nothing is enlarged.

How responsive sizes work

See Pro
Keep EXIF Keeps details such as the camera, the date and the location in each file. Leave it off to remove them and save space.
Write alt text with AI Describes each image for screen readers and search engines, and suggests a file name
Alt text language
No language matches
English
Spanish
French
German
Italian
Portuguese
Dutch
Polish
Swedish
Turkish
Russian
Ukrainian
Arabic
Persian
Hebrew
Hindi
Indonesian
Vietnamese
Thai
Japanese
Korean
Simplified Chinese
Traditional Chinese
Rename files Downloads take the suggested name instead of the one you uploaded

Pro
Uploading a zip comes with Pro: the browser opens it and uploads its images in the folders they sat in, and the zip of the results keeps them. On your plan, unzip it and drop the images here. How folders and zips work
See Pro

Up to 16 MB per image PNG, JPG, WEBP, GIF, HEIC, TIFF, or a ZIP of them on a paid plan

Guests get 10 images a day, 10 left today. A free account gets 40 a day and 7 days of Pro.

Upload a folder, or a zip

Pro

Pick a folder and every image in it uploads, with the folders inside it, and Download Selected gives them back in the same folders. A zip of images dropped on the box works the same way, opened in your browser.

How folders and zips work

See Pro
Auto-start
On, each image starts compressing as soon as it uploads. Off, images wait in the box so you can check the settings, then start together.
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
AI alt text
Alt text

Paste it into the alt attribute of the image on your page.
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. Without a resize or a conversion every pixel comes back as it was: the file only loses its metadata, and with Keep EXIF on it 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 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

Next

Related tools

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
Ten squares: 4 filled for tools that kept the IPTC AI tag at their defaults, 6 hollow for tools that dropped it, beside the title Does compression remove the AI tag?

Does compression remove the AI tag Merchant Center asks for? 10 tools, WordPress and Iminify tested

Google's Merchant Center help says: "Don't remove embedded metadata tags such as trainedAlgorithmicMedia from such images. All AI-generated images must contain the IPTC DigitalSourceType trainedAlgorithmicMedia tag." (Merchant Center's help page is dated February 2024; we read it on 26 October 2026.) So we put that tag on two AI images, a harbour scene from Nano Banana 2 (a JPEG) and a bakery illustration from the original Nano Banana (a PNG), ran them through 42 command-line runs and Iminify, added three larger JPEGs for a WordPress 7.1.3 site, and read the tag back with ExifTool each time. Each tool's default decides whether the tag survives, and neither lossy nor lossless predicts it. Of the ten tools in our table, four keep the tag at their defaults and six drop it, and for nine of them we found an option that flips that. Iminify, which is our product, lost it at every level that compresses: it survived in 6 of 51 uploads, and those six came back byte for byte unchanged. One ExifTool command puts the tag back for 514 to 568 bytes and, on the nine files we checked, leaves every pixel alone.

8 min read
Two white cards on a blue gradient: WebP at quality 75, 35.1 KB, score 68.0, and AVIF at quality 47, 25.5 KB, score 68.8, beside the headline "A quality of 75 ships as WebP 75, or AVIF 47 if enabled".

What image quality does Next.js ship? WebP 75, AVIF 47 if you list it, and by default a 90 becomes 75

We built a Next.js 16.4.3 app with four images on one page, two of them declared with quality={90} and quality={100}. All 36 image addresses in the page's HTML said q=75. We also asked the image endpoint for q=90 directly, and it answered HTTP 400: "q" parameter (quality) of 90 is not allowed. That is Next 16's default: the list of allowed qualities is [75], and the component moves anything else to the nearest entry. This post follows the 75 to the encoder, in WebP and in AVIF if you switch it on, across 867 requests to a self-hosted /_next/image on nine source images. The default WebP puts one of our five photographs at 1080 px above 70, the "high quality" mark on SSIMULACRA 2, a perceptual score. AVIF at the same setting was 36.5 percent smaller across our 27 image and width combinations, and more than 3 points below WebP on score in 8 of them.

7 min read
Two enlarged crops of the same red text saved as JPEG at quality 80, one at 4:2:0 and one at 4:4:4, beside the title. The 4:2:0 crop has a duller, browner red.

Why is red text blurry in JPG and WebP? Chroma subsampling, measured

On a test page we made full of red text, no quality from 30 to 100 lifted a plain 4:2:0 encode (no -sharp_yuv) past 58.2 on the SSIMULACRA 2 scale, which runs to 100: JPEG (cjpegli) reached 57.9, WebP 55.2, AVIF (avifenc) 58.2. The same JPEG written at 4:4:4 scored 81.6 at quality 90. That gap is chroma subsampling: 4:2:0 keeps colour at a quarter of the detail that brightness gets, and 4:4:4 keeps all of it. It's why red text looks blurry in a JPG or a WebP. The fix is 4:4:4 for JPEG and AVIF, -sharp_yuv for lossy WebP (which narrows the gap), or lossless WebP on a flat page; What we'd use has the numbers and commands.

6 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