Convert PNG images to AVIF in your browser. AVIF keeps transparency and usually produces the smallest file of any web format, which makes it a strong choice for heavy PNGs.
Drop images or browse
JPEG · PNG · WEBP · AVIF · HEIC · max 30 MB
Auto tunes each image.
A hard cap for “under 50 KB” portals.
Empty side keeps the ratio. Never enlarges.
PNG · 1.3 MB
AVIF · 68 KBPNG is lossless. It faithfully stores every pixel, which is why photographic PNGs are enormous. AVIF stores what your eye actually uses. Two very different source files, same conversion:
| Source | PNG | AVIF | WebP | AVIF saves |
|---|---|---|---|---|
| Photograph | 1382.4 KB | 69.8 KB | 110.4 KB | −95% |
| Flat-colour graphic | 7.4 KB | 0.8 KB | 1.3 KB | −89% |
Auto quality. The photographic PNG is the dramatic case; flat art starts small and still drops ~90%.
How these numbers are measured: every byte count on this page is the size of the actual encoded file our engine produced from the named source image. Those are the same bytes you would download, not an estimate or a best case. Rerun any of them yourself: drop your own file into the tool above and the meter reports your real result.
Yes. Here is the support table the "works in all browsers" claims never come with: Chrome 85+ (2020), Firefox 93+ (2021), Safari 16.1+ (2022), Edge 121+ (2024). That covers about 95% of global page views. Outside browsers: Windows 11 Photos opens AVIF with the free AV1 extension, macOS Preview from Ventura, GIMP natively, Photoshop via plugin. For the last few percent, serve a fallback:
<picture> <source srcset="logo.avif" type="image/avif" /> <source srcset="logo.webp" type="image/webp" /> <img src="logo.png" alt="…" /> </picture>
Browsers take the first source they support. Nobody ever sees a broken image, and 95% of visitors get the smallest file.
AVIF carries a full alpha channel, so this is the conversion that finally lets transparent assets shrink. Logos, product cutouts, UI elements and stickers keep their transparency at a fraction of PNG's size. Semi-transparent pixels survive too: drop shadows, glows, anti-aliased edges. That is exactly where naive converters band or fringe. Check any edge in the compare slider against the checkerboard.
Bit-exactness, not appearance. The conversion is perceptually tuned: at Auto quality the AVIF is built to be indistinguishable at normal viewing, and the savings above are the reward. The honest workflow: keep the PNG as your master, ship the AVIF. You can regenerate the AVIF anytime, at any quality, from the untouched source. For screenshots where individual pixels are data (thin 1px lines, small text), inspect at 100% before committing, or leave those specific files as PNG.
Drop 50 at a time, download one ZIP, upload to your CMS. The ZIP preserves filenames, so references keep matching. WordPress accepts AVIF uploads natively since 6.5. Shopify serves AVIF through its CDN. Hero images and photography give the headline wins (ours: −95%). Icons and flat art shrink ~90% from an already-small base. Compressing rather than converting? Compress PNG keeps the format, and PNG to WebP is the middle rung of the fallback chain.
Short answers specific to this page. The tool above settles most of them in a second.
Every route in and out runs on the same engine and the same rules. Each card is its own page.
Roughly half the bytes of WebP on most photos. Slower to encode, worth it at scale.
For photographic PNGs that never needed transparency. We flatten any alpha onto a solid background.
Keeps the alpha channel and still cuts real weight. The least disruptive way off PNG.
One more step down the size curve for pages already on modern formats. Keep WebP as the fallback.
When something rejects the upload, this is the format it wants. Photos only, no transparency.
Keeps alpha and gives every editor something to open. Expect a large file. That's the trade.
Drop it in above. The meter reports the exact saving before you download anything.