Why an AVIF File Won't Open (and How to Fix It)
By Andrew Butson · July 2, 2026 · 6 min read
You save a picture from a website, or someone sends you a photo, and the file lands as a .avif. Now it won't open: a blunt error, a blank thumbnail, an editor that refuses to import it. Nothing about the picture is wrong. AVIF is a genuinely new image format, several years younger than WebP and well over a decade younger than JPEG, and a lot of the software people run every day simply hasn't caught up to it yet.
That's a solvable, dated problem rather than a mysterious one. AVIF's support gap is closing browser by browser and app by app, and there's a fix at every level: your browser, your operating system, the specific app that's rejecting it, or the file itself.
What AVIF is, and why it's suddenly showing up everywhere
AVIF, the AV1 Image File Format, wraps a still image in a single frame of AV1, the royalty-free video codec built by the Alliance for Open Media, a group whose members include Google, Amazon, Netflix and Mozilla. Compared with JPEG, and generally with WebP too, AV1's compression is markedly more efficient, so an AVIF can hold a photo at visibly the same quality in a meaningfully smaller file. It also carries proper HDR and wide-colour support and, like WebP, transparency, which is why major websites, camera apps and photo libraries have been switching their default image format to it as browser support has matured.
The catch is exactly what made WebP awkward for a couple of years after Google shipped it in 2010: being newest cuts both ways. AVIF is among the best-compressing mainstream image formats available today, and also the one the smallest slice of installed software actually understands, because a meaningful share of the browsers, operating systems and editors in daily use predate it.
Where it currently fails
The gap shows up in a few predictable places:
- Older browsers: every current version of Chrome, Firefox, Edge and Safari can display AVIF, but that support arrived at different times (Chrome and Firefox first, Safari considerably later), so a browser that hasn't updated in a while, or an embedded browser inside another app, can still fail on it.
- Windows: File Explorer and the Photos app need AVIF support installed before they'll show a thumbnail or open the file directly. It isn't guaranteed to be built in, the same kind of gap HEIC hits for a licensing reason and AVIF hits simply for being new. Check the Microsoft Store rather than assuming the file itself is broken.
- Older photo editors: AVIF support has only recently landed in mainstream tools like Photoshop, and only in versions from the last couple of years, so an editor that hasn't been updated since AVIF became common will refuse the file outright.
- Upload forms and CMSes: some sites still validate against a fixed list of accepted image types written before AVIF existed, and will reject the upload regardless of whether the file itself is perfectly valid.
Uses your browser's own AV1 decoder to read the AVIF, then re-encodes it as JPG locally, no upload.
Runs entirely in your browser — nothing is uploaded.
Every fix that actually works
Which one to reach for depends on whether the problem is your machine, someone else's, or one specific file:
- Update your browser: this is the single most universal fix, since so much AVIF viewing now happens inside a browser tab rather than a dedicated image viewer. A current version of Chrome, Firefox, Edge or Safari opens AVIF directly, no extra install required.
- Add the OS-level decoder on Windows: check the Microsoft Store for an AVIF or AV1 image extension before assuming the machine can't handle it. Many PCs already carry the underlying AV1 decoder for video, which an image extension can reuse.
- Update the specific app that's rejecting it: if it's an editor or a plugin refusing the file, check whether a newer version added AVIF support before working around the problem.
- Convert the file to JPG or PNG: the fastest way to make one specific file open absolutely anywhere, immediately, without touching a browser, an OS setting or an app version, since JPEG and PNG are readable by essentially everything.
Where converting locally helps — and what Morphr honestly can't do yet
Morphr converts AVIF to JPG or PNG entirely in your browser: nothing is uploaded, and a whole folder of AVIFs comes back as one ZIP. Because there's no pure, from-scratch AVIF decoder built into Morphr's own engine, this particular conversion leans on your own browser's built-in AV1 decoder to do the actual decoding. In practice that means it works in any current version of Chrome, Firefox, Edge or Safari, the same browsers that can already display an AVIF directly. If your browser is old enough that it can't open an AVIF on its own, updating it is the fix either way.
It's also worth being upfront about the direction this goes: Morphr reads AVIF but can't write it. You can convert an AVIF into JPG or PNG, but there's currently no path the other way. Turning a JPG or PNG into an AVIF isn't offered, because a real AVIF encoder is a heavier piece of engineering than the pure-Rust decoders the rest of Morphr's image pipeline is built on. If AVIF-out is what you actually need, a dedicated image editor with AV1 encoding support is the only route today.
Frequently asked questions
- Is my AVIF file corrupted?
- Almost certainly not. AVIF opens fine in any current browser and a growing number of apps, so a file that won't open is usually a software-age problem, not a sign of a broken image, unless it also fails in an up-to-date browser, which would point to genuine corruption.
- Why did a website give me an AVIF when I just wanted to save a normal photo?
- Your browser told the site it could decode AVIF, and the site sent the smallest file that satisfies that, often AVIF now, since it tends to beat WebP and JPEG on file size at a similar visual quality. You didn't choose the format; your browser did, on your behalf.
- Can Morphr convert a JPG or PNG into AVIF?
- Not currently. Morphr can decode an AVIF and turn it into JPG or PNG, but it doesn't yet write AVIF files. That direction needs a full AV1 encoder, which is a considerably larger piece of engineering than the format's decoding side.
- Will converting AVIF to JPG make it worse?
- There's a small quality cost, the same as converting between any two lossy formats, though it's rarely visible at a high quality setting. What definitely changes is the file size: AVIF's compression is generally tighter than JPEG's, so the JPEG copy will usually be larger for a comparable visual quality.