Initializing... drag & drop files here
Supports: PNG, APNG
If the image is going onto a web page and your audience is on current browsers, AVIF is almost always the better file: it is the AV1 codec applied to still pictures, it carries a real alpha channel, and it collapses photographic detail that PNG has no way to compress. If the image is a master copy, needs to survive repeated re-editing, or has to open in software that predates broad AVIF support, keep the PNG. The short version: convert for delivery, keep the PNG as the source.
| Property | PNG | AVIF (from this converter) |
|---|---|---|
| Compression | Lossless (DEFLATE) | Lossy AV1 intra coding at every quality preset |
| Standard | PNG Specification Third Edition, W3C Recommendation, 24 June 2025 | AV1 Image File Format, Alliance for Open Media, v1.2.0 (October 2025) |
| Container | PNG chunk stream | ISO base media file format (ISO/IEC 14496-12), using the HEIF structure (ISO/IEC 23008-12); ftyp brand avif |
| Transparency | 8-bit alpha | 8-bit alpha, stored as a separate AV1 Alpha Image Item — preserved by this converter |
| Bit depth | 1–16 bits per sample | The format allows 8, 10 and 12-bit; this converter writes 8-bit |
| Animation | Only via APNG | Yes (a still is written here) |
| Browser support | Universal | ~94.7% globally: Chrome 85+, Firefox 93+, Edge 121+, Opera 71+, Safari 16.4+ (16.1–16.3 partial), iOS Safari 16+ |
| Desktop editor support | Everything | Patchy — many older editors still cannot open it |
| Best for | Masters, screenshots with fine text, anything that gets re-saved | Web delivery, photos, large transparent artwork, app assets |
<picture> element and can list AVIF first with a PNG or WebP fallback behind it..apng is accepted too..avif. No sign-up, no watermark; files are uploaded over an encrypted connection, processed on our servers, and deleted automatically after a few hours.| Preset | Encoder quality value | Reasonable use |
|---|---|---|
| Highest | 100 | Archival-ish delivery copy — still lossy, and much larger |
| Very High (Recommended) | 95 | The default; visually indistinguishable from the PNG in normal use |
| High | 90 | Good balance for photographic hero images |
| Medium | 80 | Standard web content where bytes matter more than pixel-peeping |
| Low / Very Low | 70 / 60 | Thumbnails, background textures, previews |
| Lowest | 50 | Placeholders and low-priority assets only |
There is no lossless switch on this page and no bit-depth control — every preset, including Highest, runs the AV1 encoder in lossy mode at 8 bits per sample.
Yes. The AVIF specification stores alpha as a separate auxiliary picture — an "AV1 Alpha Image Item" encoded at the same bit depth as the main image — and this converter carries it through. In our testing a 1920 × 1080 logo on a fully transparent background came out of the converter with all four channels intact and its corner pixels still reading as completely transparent, so soft edges and drop shadows survive rather than picking up a matte.
No, and this is worth being clear about. AVIF as a format supports a lossless mode, but this converter does not expose it: the seven presets map to encoder quality values from 100 down to 50 and all of them run lossy AV1 intra coding. "Highest" means quality 100, not bit-exact. If you need a pixel-for-pixel copy, keep the PNG — that is exactly what PNG is for.
It depends entirely on the picture. In our testing a photographic 1920 × 1080 PNG of 1,501,179 bytes became a 233,747-byte AVIF at the default Very High preset — about 84% smaller. A flat 1920 × 1080 logo on transparency, which PNG already stores efficiently, went from 21,244 bytes to 11,722 bytes, roughly 45% smaller. Detailed and photographic content saves the most; flat-colour artwork saves the least.
No. The AVIF specification allows 8, 10 and 12-bit samples and supports wide-gamut and HDR signalling, but this pipeline writes 8-bit output regardless of the source — a 16-bit PNG comes out as an 8-bit AVIF. Treat this as a delivery converter for standard-range images, not a route into an HDR workflow.
Around 94.7% of global browser traffic, per current caniuse data: Chrome 85+, Firefox 93+, Edge 121+, Opera 71+, and Safari 16.4+ on the desktop with partial support in 16.1–16.3, plus iOS Safari from version 16. Internet Explorer and Opera Mini never will. Desktop image editors are further behind than browsers, so if a colleague needs to open the file in older software, hand them the PNG or run AVIF to PNG.
AVIF generally compresses better than WebP at matched visual quality, particularly on photographs and smooth gradients, and both formats carry an alpha channel. WebP's advantages are wider support in older software, faster encoding, and a genuine lossless mode. If your audience is on current browsers and bytes are the priority, AVIF wins; if you need a broader safety net or a lossless option, use PNG to WebP instead. Serving both through a <picture> element with a PNG fallback is the belt-and-braces answer.
They very nearly are. Both wrap coded still pictures in the ISO base media file format using the HEIF structure; the difference is the codec inside. AVIF carries AV1 and is royalty-free, which is why browsers adopted it. HEIF as produced here carries HEVC, which browsers outside Safari do not decode. On the same source and the same quality setting, our AVIF output was substantially the smaller of the two. Choose HEIF only when the destination is an Apple photo library — see PNG to HEIF.
You get a still. AVIF can hold an image sequence, but this page produces a single picture, so an animated source is decoded to its first frame and that frame is encoded. If you want the animation preserved, keep it as an APNG or convert it to a format this site animates — APNG to WebP or APNG to GIF.
They are uploaded over an encrypted connection, converted on our servers, and both the upload and the AVIF are deleted automatically after a few hours. No sign-up, no watermark, and nothing is shared or made public.