Which format has the highest compatibility?

JPG and PNG lead by a clear margin; both have been around for decades and are read in practice by every device, every operating system and every program. They work everywhere, from an old printer's menu to a corporate document system. WEBP has very broad modern support but can still cause problems in older desktop software and some upload forms. If you know nothing about the recipient's environment, JPG or PNG is the safest choice.

Is there any point converting to WEBP — isn't that a modern format too?

There are cases where it makes sense. Because WEBP is a generation older than AVIF, browser and tool support for it is more widely established; some content management systems and editing programs that reject AVIF open WEBP without a problem. It also stays smaller than JPG and supports transparency, so it preserves a significant share of AVIF's advantages. WEBP is a good middle ground only when your compatibility problem is with a specific, current tool; if the problem is an old device or old software, it will not be enough.

What are my options if I have transparency?

PNG and WEBP support the alpha channel, JPG does not. The safest choice is PNG because it opens in every environment and preserves transparency completely; the price is a larger file. WEBP offers the same transparency with smaller files, but the software on the other end has to recognise it. If you are forced to convert to JPG, know that transparent areas will be filled with a solid colour and that this will make most logos or cut-out product images unusable.

Would updating my program be better than converting?

If the problem is a single program and a current version of it supports AVIF, then yes, updating is the cleaner solution because no re-encoding loss occurs. But if the problem is on the other end rather than yours, updating is not an option; you cannot manage someone else's computer. The same applies to upload forms with file-type restrictions. In those cases converting is the only practical route.

AVIF Won't Open: Which Format Should You Convert To? JPG, PNG and WEBP Compared

The problem is not the file, it is the environment

You have an AVIF file and it does not work somewhere. But "does not work somewhere" is vague — and choosing the right target format depends on knowing exactly where it fails.

An AVIF might not open on an old phone, it might be rejected by a current but strictly configured e-commerce dashboard, and it might go unrecognised by a ten-year-old desktop program. The right answer is not the same for all three scenarios.

In this article we take an honest look at the three candidate formats: JPG, PNG and WEBP.

Meet the candidates

JPG. Lossy, 8-bit, no transparency, RGB. It has been around for more than thirty years and practically everything reads it. Very good with photographic content, weak with sharp-edged content.

PNG. Lossless, has an alpha channel, universal support. Excellent for graphics, screenshots and images containing text. File size balloons on photographs.

WEBP. The first generation of modern formats. Smaller than JPG, has both lossy and lossless modes, supports transparency. Current browser support is very broad; desktop tool support is better than AVIF's but weaker than JPG's and PNG's.

AVIF (the source). Next generation. Generally noticeably smaller than JPG at the same visual quality — the frequently cited roughly-half figure is an approximation and varies with content. Usually more efficient than WEBP as well. Supports transparency, HDR and high bit depth. Its weakness is ubiquity.

The decision depends on the source of the problem

If the problem is an old device or an old program

Answer: JPG or PNG.

We do not recommend WEBP in this scenario. An old phone or a ten-year-old viewer may not recognise WEBP either. In an environment like that, no member of the modern format family is safe.

If the content is photographic and there is no transparency, JPG. If there is transparency or the content has sharp edges, PNG.

If the problem is an upload form or a dashboard

Answer: look at the list it accepts.

Many e-commerce and content management systems control file types with a whitelist. That list frequently includes JPG and PNG, sometimes WEBP, rarely AVIF. The information is usually written in the dashboard's own documentation or in the note next to the upload field.

If the list includes WEBP and size matters to you, WEBP is a sensible middle ground. If it does not, go back to the classics.

If the problem is an editing program

Answer: PNG.

If you are going to edit the image, working in a lossless format is the right practice. In a lossy format, every save adds a new generation of degradation; in PNG that accumulation does not happen. Converting the AVIF to PNG, doing your editing there, and producing the delivery format separately at the end is the cleanest workflow.

If the problem is sharing and you do not know the recipient

Answer: JPG.

In the face of uncertainty, the oldest and most widespread format wins. For photographic content JPG still offers a reasonable quality-to-size balance, and the risk of rejection is practically zero. When you do the conversion, keep the quality setting high, because you are going from lossy to lossy and adding a second generation of loss.

Let's be clear about loss

There is a dimension of target selection that gets ignored: no conversion is free.

AVIF → JPG: Lossy to lossy. A second generation of compression is added. If you keep the quality setting high, the difference is indistinguishable in most images, but it is not zero. Transparency is lost.

AVIF → PNG: Lossy to lossless. No new loss is added, but existing artefacts are preserved exactly as they are — PNG does not repair, it freezes. The file grows noticeably. Transparency is preserved.

AVIF → WEBP: Lossy to lossy (unless you save in lossless mode). As with JPG, a second generation of loss is involved, but because WEBP is more efficient the file stays smaller at the same visual quality. Transparency is preserved.

None of the options improves quality. It is worth saying again, because the expectation that changing format will improve the image is a very common misconception.

Three sentences instead of a summary table

If there is transparency, PNG. If you are sending a photo to someone you do not know, JPG. If the problem is only a current but selective tool and you want to keep the size down, WEBP.

And one last note: do not delete the original AVIF. All of these formats can be generated from it, but not the other way round. If you realise you picked the wrong target, you will want to be able to go back to a clean source.

In summary

An AVIF that will not open is not a file problem, it is an ecosystem problem, and the solution depends on which ecosystem you are stuck in. On old hardware and software there is no alternative to JPG and PNG. On current but selective systems, WEBP strikes a good balance between efficiency and compatibility. In every case the need for transparency can decide the matter on its own; if you need an alpha channel, JPG is off the table. As you decide, remember that no conversion adds quality and some quietly take it away.