AVIF Conversion: How to Open AVIF Files and When to Keep Them

Modern sites negotiate formats: a browser that announces AVIF support gets the tiny AVIF version, and when you save an image from that page you save what was served — not the JPG the site owner originally uploaded. Add OSes that preview AVIF inconsistently and design software whose support arrived recently, and the format you never chose to collect is suddenly everywhere. (Android cameras shipping AVIF photo output adds a second pipeline for the same pile.)

The good news: AVIF is not encrypted or proprietary in any practical sense — it is a container, and every conversion tool that decodes it produces the exact pixels the AVIF was displaying. Nothing is trapped; you just need the right output choice.

PNG for anything you will open again. The AVIF → PNG conversion is a faithful one: the decoder produces pixels, the PNG encoder stores them losslessly, and you now have an editing master that survives re-saving. The bytes are dramatic — a 60 KB AVIF of a photograph may become a 1.5 MB PNG — because PNG is storing honestly what AVIF was guessing compactly.

JPG for a one-and-done share: the photo you are emailing, the form upload that refuses WebP, the print-shop submission. Quality 90 is visually identical to the AVIF for photographs; understand you have added one lossy generation, which matters only if the file will be edited and re-saved afterwards — in that case go through PNG.

WebP when the destination is a website that takes WebP but not AVIF — a browser-support matrix a few versions behind. The AVIF → WebP pass keeps you in efficient territory; the quality setting behaves the same as the other formats'.

AVIF carries alpha in both lossy and lossless modes — genuinely better than lossy WebP, which has none — so transparent AVIF logos and cutouts exist and are being served. Those convert to PNG to keep the alpha; to JPG they flatten against a matte like anything else. Check first: view the AVIF against a dark background, and if it shows through, treat it as a transparency source.

Animated AVIF is the newest of the family and the least supported downstream — old editors and viewers will not play it. Convert animated AVIF to animated WebP for web use (better support, still compact) or to GIF where paste-ability beats every other property — the animated images guide covers that format choice. The conversion decodes the frames you can see and re-encodes them honestly; per-frame AVIF quality quirks — the faint softness in fast motion — become baked into the output, because that is now what the animation contains.

If the images are for a site you control, the conversion direction reverses: ship AVIF at the top of a <picture> stack (AVIF → WebP → JPG fallback) and the same small files that frustrate your old software make your pages load fast on bad mobile connections — the size advantage over JPG runs 40-60%, which is the largest image-performance win available today without dropping quality.

The honest caveats for web use: AVIF encoding is slow (fine in a build pipeline, irritating on-the-fly), very large AVIFs decode slower on weak devices than their JPG equivalents, and a small slice of traffic — old Safari, old Android WebView, locked-down enterprise browsers — still needs the fallback row. Those are reasons to keep a fallback stack, not reasons to skip the format.

If a converter rejects a file your browser displays: the file is probably truncated (re-download), mislabelled (rename with the real extension by checking what the browser shows in the network tab — or just convert it; the converter reads the header, not the name), or genuinely HEIF-in-disguise (some cameras write .avif-named HEVC stills, which are a cousin format and need a HEIF-capable decoder). Every browser-native case converts with a decoder built into the browser, which is what local AVIF tools use.