Open AVIF File Online — Instant AVIF Viewer

AVIF (AV1 Image File Format) is a modern image format built on the AV1 video codec. It is not some indie experiment — the format was released in February 2019 by AOMedia, the same industry alliance behind the AV1 video codec, and its founding members read like a list of the biggest bandwidth bills on the planet: Google, Netflix, Amazon, Microsoft, Apple, Intel and more than a dozen others. These companies were burning enormous sums delivering video and images to billions of users, so they commissioned a codec that compresses dramatically better than anything before it — AVIF images routinely come out 50% smaller than a comparable JPG, and sometimes 30–40% smaller than WebP at the same visual quality. The AV1 spec itself landed in 2018, and the image-container specification reached version 1.0 in 2022. That timeline matters for one very practical reason: any software written before roughly 2020 has never heard of this format, and even a lot of software written after that only caught up slowly.

The catch is compatibility on the receiving end. Chrome, Edge, Firefox and recent Safari versions open AVIF natively, which is why the web feels AVIF-friendly — but a long list of everyday software does not: older versions of Windows Photo Viewer, macOS Preview before macOS Ventura, many Android gallery flows before Android 12, iOS Photos before iOS 16, most desktop image editors released before 2021, classic email clients, and plenty of CMS upload pipelines. Netflix deserves a mention here because it proves how serious the format is: the company has been rolling out AV1-encoded video streams (the same codec family AVIF uses) across its catalog for years specifically because the bitrate savings translate directly into millions of dollars on delivery costs. When a website wants to load fast on a slow connection, serving AVIF is one of the most effective levers available — which is exactly why you keep receiving files you cannot open.

The viewer above uses your browser's built-in AVIF decoder to render the file locally — the same engine that displays AVIF images on modern websites. Click Open an AVIF file, pick the file, and it appears instantly with its pixel dimensions and file size. The preview never leaves your device: there is no upload step, no server, no queue. That makes it safe for private photos, unreleased client work, or anything else you would not hand to a random converter website. It also means the preview is fast — a 5 MB AVIF renders in a fraction of a second because the decoding happens on your own CPU, not after a round trip to somebody's data center.

• Check the content quickly — confirm what the file actually shows before deciding what to do with it. A lot of the time you just need to see whether it is the right screenshot before replying to an email.
• Verify the file is valid — if the preview fails to render, the file is likely corrupted or truncated rather than merely unsupported. A download that died at 80% produces exactly this symptom, and no amount of app-updating will fix it.
• Convert when ready — head to the AVIF to JPG converter or the AVIF to PNG converter to get a file every application can open.

Windows is where most people hit the AVIF wall, and the error messages are memorably unhelpful. On Windows 10 and earlier, the built-in Photos app refuses .avif files outright — double-click one and you get the classic "The File Open Operation Was Canceled" or, on some builds, error code 0x88982f07 from the Windows Imaging Component (WIC), which is the imaging subsystem declaring that it has no decoder for this format. Nothing is broken on your machine; the decoder simply does not exist yet. Microsoft shipped an optional "AV1 Video Extension" in the Microsoft Store that adds AV1/AVIF decoding, and it was free — but only for a period. At various points it cost $0.99, which caused a small internet revolt every time it resurfaced, and later Microsoft folded the codec into the free "AV1 Video Extension" updates again. Windows 11 builds from 2023 onward ship with AV1 support integrated, so on a recently-updated machine the file just opens.

The practical problem is that the corporate world does not run on recently-updated machines. A huge number of office PCs are still on Windows 10, locked down by IT, with no Microsoft Store access and no admin rights to install extensions. If you email an AVIF screenshot to someone on one of those machines, you have effectively sent them a broken file. Converting the AVIF to JPG before it leaves your outbox sidesteps the entire mess — JPG has decoded on every version of Windows since the 1990s and will keep working for decades. If you are the one stuck with the file, preview it here first to confirm it is intact, then convert it and move on with your day.

On macOS, AVIF opens natively in Preview, Quick Look and Safari starting with macOS Ventura (version 13), which shipped in late 2022. On an older Mac — Monterey, Big Sur or anything before — Preview shows a gray placeholder or claims the file is damaged. The same staggered rollout happened on mobile: iOS 16 and iPadOS 16 (September 2022) brought AVIF decoding to iPhone and iPad, so anything earlier displays an empty thumbnail in Photos and Messages. Safari itself only got full AVIF support in Safari 16.4, released in March 2023 — before that, even users who had updated to iOS 16 found that some AVIF images embedded in web pages failed to render.

This fragmentation is why "it works on my phone" is not a compatibility strategy. A designer on a Ventura Mac sends a client an AVIF proof; the client is on an iPhone 11 still running iOS 15 and sees a blank square. Nobody is at fault — the file arrived five years before the receiving device learned to read it. The zero-drama fix takes under a minute: convert the AVIF to JPG on this page, send the JPG, and the image opens identically on an iPhone 6s, a 2017 MacBook Air and a Windows 8 kiosk. If the source image has transparency you need preserved — a logo, a sticker, a cut-out product shot — use the PNG route instead, since JPG flattens transparent areas to white.

Support arrived on a staggered schedule across every platform, and knowing the exact cutoff version saves a lot of guesswork. Here is where each platform actually landed:

Windows 10 (version 1903 and later) can gain AVIF support by installing the "AV1 Video Extension" from the Microsoft Store — search for it by name, pick the result published by Microsoft Corporation, install, and the Windows Imaging Component picks it up without a reboot. File Explorer thumbnails, the Photos app, and any WIC-aware application then decode .avif files automatically. Windows 10 machines without Store access need an alternative path; administrator-deployed codec packages are available but require IT involvement. Windows 11 21H2 and later include the AV1 decoder by default, though enterprise images built from stripped base installations sometimes omit it — check Settings → Apps → Optional features → "AV1 Video Extension" to confirm.

macOS 13 Ventura (released October 2022) was the first version to support AVIF in Preview, Quick Look, and the system image framework. Monterey (12), Big Sur (11) and anything older have no native AVIF support regardless of which apps you install on top of them — the platform decoder is missing at the OS level. Safari 16.4 (March 27, 2023) completed the story by adding reliable AVIF decoding in web pages; Safari 16 introduced partial support in September 2022 but some files failed to render.

iOS 16 and iPadOS 16 (September 12, 2022) brought AVIF to the system image decoder, meaning Photos, Messages, and third-party apps that call the system framework all gained support at once. Devices stuck on iOS 15 or earlier see a blank square in every context. Android 12 (API level 31, October 2021) added AVIF decoding to BitmapFactory, Android's core image-decoding API. Android 13 and 14 improved edge-case handling. However, OEM gallery apps — Samsung Gallery on One UI before 5.0, MIUI Gallery, OPPO Gallery on ColorOS before 13 — often maintain their own format whitelists and still refuse AVIF even on hardware that technically supports it. If Chrome on the same phone opens an AVIF fine but the gallery app does not, that is the OEM gap rather than an Android version gap.

Browsers: Chrome 85 (September 2020) was first; Edge followed in version 92 (August 2021); Firefox 93 (October 2021); Safari 16 (September 2022). Internet Explorer never got AVIF support, and no update will add it. Opera 71 and Samsung Internet 14 both carry the Chromium engine that supports AVIF, so they work by inheritance.

Android gained native AVIF decoding in Android 12, released in October 2021, and support improved again in Android 13 and 14. On Android 11 and earlier, tapping an .avif file in a messaging app or file manager either does nothing or offers to open it in a text editor — which is exactly as useful as it sounds. Plenty of budget phones also ship with customized gallery apps that never enabled AVIF even on newer Android versions, so "my phone is from 2022, why won't it open?" is a fair question with an unfair answer: your manufacturer simply skipped it.

Email deserves its own warning. Attach an AVIF to an email and what happens next depends entirely on the recipient: a Gmail user on Chrome sees it fine, a user on classic desktop Outlook sees a broken-image placeholder or is told the file has no preview available, and someone forwarding the thread through a corporate mail gateway may find the attachment stripped entirely. A surprisingly common variant: the image arrives as an attachment named something like photo.avif, the recipient has no AVIF viewer, and now two people are stuck. The workflow that never generates a support reply: preview the file here to make sure it is the right one, convert to JPG, attach the JPG. One extra step at your end versus a confused reply asking "what is an AVIF and how do I open it?" — the math is not close.

Social platforms add another wrinkle. Uploading an AVIF to Instagram, Twitter/X, or Facebook triggers their media pipeline, which almost always re-encodes the image in its own format before displaying it to followers. The re-encoding is lossy — not dramatically, but a high-quality AVIF passed through a platform transcoder typically comes out at a noticeably lower quality than a JPG submitted directly. Platforms that process AVIF through a fallback path (rather than a native path) sometimes introduce banding in gradients and smear fine text. For anything where image quality matters — product shots, portfolio work, food photography — convert to JPG at 90% before uploading. The platform recompresses it again anyway, but at least you are starting from a known quality point rather than a format the pipeline handles as an afterthought.

Sometimes the AVIF file lands on your machine without you asking for it. Right-click and save an image from a modern website and there is a decent chance the file you get is .avif, because the site's CDN served you its smallest variant. Big platforms have been experimenting here: Instagram began piloting AVIF delivery through its CDN in 2023, following reports that its media pipeline was throttling and recompressing images aggressively — one widely-circulated analysis found some images delivered at roughly 30% reduced quality versus what users expected. Netflix, as mentioned above, uses the AV1 codec family for a growing share of its own video streams precisely because the savings compound across billions of playback hours. When platforms optimize at this scale, the bytes they save are real money — and the files they hand you are whatever format serves them best, not whatever opens on your machine.

If you saved an image from a site and it ended up as .avif, nothing is wrong with it — it is usually the highest-quality copy the site offered. Preview it here, then convert it to JPG or PNG depending on what you need it for. PNG if you want lossless quality for further editing, JPG if it is going into a document, a chat message or a WordPress upload. Either way you keep the pixels and lose the compatibility headache.

A scenario that catches people constantly: a file arrives named image.avif, it will not open in anything, and no amount of converting fixes it. Open the file in this viewer and it fails too — which is your first clue that something else is going on. In a meaningful share of these cases the file is not AVIF at all. The most common culprit is iPhone photos: when someone AirDrops, emails or cloud-syncs photos off an iPhone with "High Efficiency" enabled, the files are HEIC — and somewhere in transit the extension gets renamed or mislabeled to .avif by a tool that half-knows what modern formats look like. HEIC and AVIF are actually built on the same underlying container standard (ISOBMFF), which is why the two get confused so often, but they are different codecs and a decoder expecting one cannot read the other.

The viewer on this page doubles as a diagnostic. If it renders, your file is genuine, healthy AVIF and you simply need a conversion for the target app. If it fails while other AVIF files work, suspect either a corrupted download (re-download the file — a truncated AVIF will not decode) or a mislabeled HEIC that needs a different tool. Either way, you have learned in ten seconds whether the problem is the format or the file, instead of spending an evening installing viewers that all fail for the same hidden reason.

Operating system support and application support are two separate things, and the gap between them trips people regularly. You can be running Windows 11 with the AV1 extension installed, open GIMP 2.10.28, and get a blank canvas — because that version of GIMP predates its own AVIF decode path. GIMP 2.10.30, released in December 2021, was the first version to ship AV1/AVIF support. Anything older simply ignores the extension.

Photoshop is the most common name on this list. Adobe added AVIF to Photoshop 23.2 in January 2022; Photoshop 2021 (version 22.x) and every earlier release do not recognize the format at all — the codec is missing from the application, not the OS. Adobe Lightroom Classic gained AVIF import in version 11.0 (November 2021); the perpetual Lightroom 6 never received it. Adobe Illustrator followed in its October 2022 release, InDesign in 2023. CorelDRAW requires version 2023 or later. Old Affinity Photo 1.x handled AVIF reasonably early through a system call, but version-specific behavior varies by platform.

Beyond creative software, the list extends into places most people never think to check. Office 2019 and Office 2021 have no AVIF support — Microsoft 365 only gained it during 2023, and perpetual-license builds never received a backport. Thermal-print software, photo-kiosk systems, embroidery digitizers, sign-making tools, laser-cutter controllers: these applications update on hardware replacement cycles rather than web standards, and many of them will never support AVIF. The rule that survives all these exceptions — if the tool shipped before 2022, assume it cannot read AVIF until proven otherwise, and convert the file before you try.

Path 1 — Install the missing codec or extension. Best when you receive AVIF files regularly and need multiple applications to open them. On Windows 10, install the "AV1 Video Extension" from the Microsoft Store (free, published by Microsoft Corporation) — after installation the Windows Imaging Component picks it up and Photos, File Explorer thumbnails and any WIC-aware app decode .avif automatically, no reboot required. On macOS, upgrading to Ventura (13) costs nothing if your hardware supports it and adds AVIF to Preview and Quick Look permanently. For GIMP, update to 2.10.30 or later. This path requires admin rights or Store access; it is a one-time fix that solves the problem everywhere at once.

Path 2 — Use a viewer that already handles AVIF. You do not need a codec if you already have compatible software sitting on your machine. Drag the file directly onto a Chrome or Firefox window — modern browsers decode AVIF natively and display the image immediately, no extension needed. VLC media player version 3.0 and later opens AVIF without extra plugins. XnView MP (free, Windows/macOS/Linux) has supported AVIF since its 0.98 release. IrfanView opens AVIF after you install the HEIF/AVIF plugin from the official IrfanView plugins page — the base install without the plugin does not decode it. These are zero-cost installs that take under a minute.

Path 3 — Convert to JPG or PNG. The lowest-friction route for a file or two. No codec installation, no new software, works on any machine that runs a modern browser. Preview the file above to confirm it is intact, then go to the AVIF to JPG converter or the AVIF to PNG converter. JPG opens on every device made in the last 30 years; PNG preserves any transparency. If you only need to view a handful of files once — converting is faster than installing anything. If AVIF lands on your desk every day and goes into professional tools — install the codec and keep your originals.

Converting from AVIF to a more compatible format is not free. The costs are real but predictable, and knowing them in advance lets you make the right call for each file.

Lossy-to-lossless does not recover detail. If you convert an AVIF to PNG, you get a lossless PNG — but lossless relative to the AVIF, not relative to whatever was shot originally. The AVIF itself was almost certainly created with lossy compression, so the PNG faithfully copies the compressed pixels, artifacts included. A blurry AVIF converted to PNG is a blurry PNG at a larger file size. PNG is the right choice when you need to preserve transparency or avoid adding another generation of lossy compression; it does not make the image sharper.

Alpha channels and transparency. AVIF supports full alpha channels with the same AV1 compression applied to the color data. Converting to JPG drops the alpha entirely — transparent pixels are filled with white, which is the standard behavior and the right default for photos. If the AVIF has transparency that matters (a logo, a product cut-out, a sticker), use the AVIF to PNG path instead. The viewer above shows the image on a checkerboard background, making transparent areas obvious before you commit to a conversion path.

Color space: Display P3 to sRGB shift. AVIF natively supports wide color gamuts, including Display P3, which is the default color space for photos taken on iPhone 12 and later and on recent high-end Android cameras. When a Display P3 AVIF is converted to a sRGB JPG, colors are gamut-mapped — highly saturated greens and reds in particular can shift noticeably, appearing slightly less vivid. For most web and document use this is imperceptible. For print work or color-critical review, compare the converted JPG against the original in the software you will actually use it in and check that nothing looks desaturated. Converting from the original RAW or a sRGB source file instead of a Display P3 AVIF eliminates the problem entirely if you have the source.

If you are comfortable with a terminal and need to process a folder of files programmatically, several tools handle AVIF reliably without a browser. Each of the commands below runs on macOS, Linux and Windows (with WSL or native builds).

ffmpeg — converts between virtually every image and video format:

ffmpeg -i in.avif out.png
ffmpeg -i in.avif -q:v 2 out.jpg

The -q:v flag controls JPEG quality (2 is near-lossless; 31 is lowest). For a whole folder on macOS/Linux: for f in *.avif; do ffmpeg -i "$f" "${f%.avif}.jpg"; done

ImageMagick 7 (the magick command) — calls libavif internally when the library is present:

magick in.avif -quality 90 out.jpg
magick in.avif out.png

Confirm AVIF support is compiled in with magick -list format | grep AVIF. Install on macOS via brew install imagemagick.

avifdec — the reference decoder from the libavif project, produces an accurate lossless round-trip:

avifdec in.avif out.png

Install via brew install libavif on macOS or apt install libavif-bin on Debian/Ubuntu.

sharp-cli — an npm-based option that requires Node.js but no global install:

npx sharp-cli --input in.avif --output out.jpg --quality 90

These tools handle the same color-space and alpha-channel considerations the browser converter does. They are most useful for CI pipelines, batch jobs on a server without a display, or scripted workflows that need to hook into other build steps.

These three symptoms look different but each points to a specific cause:

Black screen or uniform gray rectangle after the file loads. The image decoded without error but the viewer is not tone-mapping it correctly — a sign the file was encoded with HDR metadata (PQ or HLG transfer curve) and the display pipeline is treating HDR headroom as clipped black. Open the same file in Chrome 94 or later or Firefox 92 or later, both of which handle HDR AVIF. If it renders there, the file is healthy; your other viewer simply lacks HDR support. Converting to a sRGB JPG is the fastest resolution: the browser converter tone-maps the HDR data to sRGB during export, and the resulting JPG looks correct everywhere.

Garbled pixels, checkerboard artifacts, or random noise across the image. This is a corrupted file. The compressed data was damaged in transit — a download that stalled, a clipboard paste that truncated, an email attachment mangled by a gateway. Re-download from the original source. If re-downloading is not possible, there is no recovering a corrupted AVIF; AV1's compressed streams are not self-repairing, and the garbage pixels are the decoder's best guess at what the missing data contained.

Only the top half or a partial fraction renders, then a hard edge. This is a truncated file — it arrived incomplete. The decoder renders every tile it received and draws a hard boundary where the data ends. Same cause as garbled pixels: the transfer stopped before the last bytes were written. Re-download or request a fresh copy from whoever sent it.

Loads fine in the browser viewer but fails in Photoshop, GIMP or Lightroom. Software version issue — the file is healthy, the application is too old. Check the version requirements in the section above, update the application if possible, or convert to JPG here and open the JPG in the existing version. No amount of codec installation fixes an application that was compiled before its own AVIF support was written.

If you run a website, the compatibility question flips: now you are the one sending files to other people's devices. WordPress core only started accepting AVIF uploads in version 6.5, released in March 2024, and even then the file is stored as-is — WordPress does not convert it for visitors whose browsers cannot decode it. Meanwhile, server operators who want the bandwidth savings typically configure their CDN or image optimization layer to serve AVIF to browsers that advertise support, with JPG as the fallback. That is the right architecture — but plenty of half-configured setups skip the fallback, and visitors on older browsers get broken images with no error anywhere.

The pragmatic rule that has emerged across the industry: AVIF is a delivery format, JPG is a compatibility format. Use AVIF where you control both ends; convert to JPG the moment the image has to survive contact with unknown software. If you have received an AVIF from a designer or exported one from an optimization pipeline and need to upload it to an older CMS, a theme with a hardcoded extension whitelist, or a client portal built in 2018, convert it first — our AVIF to JPG conversion guide covers the quality settings in detail, and the AVIF to JPG online overview compares the different routes.

Support for AVIF is not binary. A browser may decode a baseline AVIF but choke on a sequence (animated) AVIF or on an image with a wide-gamut color profile. The table below reflects the state as of 2025; "partial" means the decoder exists but animated AVIF, HDR, or alpha channel may be broken in some builds.

• Chrome 85+ / Edge 92+ (desktop & Android) — full support including animated AVIF and alpha. The first mainstream browsers to ship it.
• Firefox 93+ — full support on desktop. Android Firefox gained support in 113. Earlier versions show a broken-image icon even if the OS can decode it, because the browser bypasses the system codec.
• Safari 16.0+ (macOS Ventura, iOS 16) — static AVIF supported. Animated AVIF arrived in Safari 17. Older Safari on macOS Monterey or earlier shows nothing.
• Windows Photos / Paint — requires the AV1 Video Extension from the Microsoft Store (free). Without it, Photos shows "We can't open this file" and Paint saves a blank canvas.
• macOS Preview & Quick Look — supported from macOS Ventura (13.0). On Monterey or earlier, Quick Look shows the generic file icon and Preview refuses to open the file.
• GIMP 2.10.28+ — reads and writes AVIF via the built-in libavif plug-in. Earlier 2.10.x releases need a manual plug-in install; GIMP 2.10 on Windows shipped without it by default.
• Photoshop — native AVIF import arrived in version 23.2 (February 2022). Older Photoshop versions need a free third-party plug-in ("avif-photoshop") or a round-trip through a converter first.
• Lightroom Classic 11.4+ — imports AVIF as a raw-adjacent file. Earlier versions import it as an unrecognised format and show a grey thumbnail.
• Linux (GNOME Files / Eye of GNOME) — depends on whether gdk-pixbuf was compiled with AV1 support. Most rolling-release distros have had it since 2022; Debian 11 and Ubuntu 20.04 LTS do not.
• Android Gallery / Google Photos — Google Photos supports AVIF on Android 12+. The stock gallery app support varies by device manufacturer and may lag a year or more behind the OS release.

Even when the OS version and software versions are all in the supported range, AVIF files sometimes refuse to open. These are the failure modes浮浮酱 most often sees in the wild, and what to do about each one.

• Wrong file extension on a valid AVIF. Some cameras and apps write AVIF data but save the file as .heic or simply .img. Rename the file to .avif and try again. You can confirm the real format by opening the file in a hex editor and checking that the first bytes spell out ftyp followed by avif or avis.
• Corrupted download. A partial download produces a file that passes size checks but whose bitstream is truncated. Re-download and verify the checksum if one was provided. Truncated AVIF files commonly open to a black rectangle or show only the top quarter of the image.
• Missing AV1 codec on Windows. If Photos shows error code0x88982f07, the AV1 Video Extension is absent or its version is too old. Uninstall any existing AV1 extension first, then reinstall from the Microsoft Store. A corrupt or half-installed extension produces the same error as a missing one.
• Browser shows a broken image even though the OS supports it. Clear the browser cache — a cached failed response for that URL can prevent a retry. Also check that the server is sending the correct MIME type (image/avif); a server sending application/octet-stream causes some browsers to treat the file as a download rather than an image.
• Colour looks wrong after opening. AVIF supports both BT.601 and BT.709 colour matrices. A viewer that ignores the embedded colour profile renders saturated images with visibly shifted hues. Switch to a colour-managed viewer, or convert to sRGB JPG to guarantee consistent rendering across all tools.
• App crashes or hangs on open. Very large AVIF files (above 32 megapixels) can exhaust the memory of 32-bit applications or early 64-bit builds that were compiled before AV1 tiles were commonplace. Update to the latest release of the application, or convert to JPG first using a command-line tool that handles tiled AVIF correctly.

The most common reason to convert AVIF to JPG is compatibility, but it is worth understanding exactly what changes in the image data — and when the trade-off is worth making.

• File size increases by 30–60 % on average. AVIF's AV1 codec typically achieves the same perceived quality as JPG at roughly half the file size. Converting back to JPG therefore undoes that compression advantage. A 120 KB AVIF will commonly become a 200–220 KB JPG at equivalent visual quality.
• Perceptual quality loss is small at high JPG quality settings. Converting at JPG quality 90+ produces images that are visually indistinguishable from the source on typical photographic content. The loss becomes visible at quality 70 or below, especially in smooth gradients and skin tones where JPG's 8×8 block artefacts appear.
• Alpha channel is lost. JPG does not support transparency. Any transparent region in the AVIF is composited onto a solid background — white by default in most converters. If you need transparency, convert to PNG instead, or check whether the receiving application can accept WebP.
• HDR and wide-gamut data is clipped or tone-mapped. If the AVIF was created with a PQ or HLG transfer function (HDR content), converting to JPG collapses it into an sRGB container. Depending on the converter, highlights may blow out or colours may shift. For HDR source material, use a converter that applies proper tone-mapping rather than a raw colour space conversion.
• Animated AVIF becomes a still image or a series of stills. JPG has no animation track. Most converters extract the first frame. If the animation matters, consider converting to GIF (for small palettes) or MP4 (for video-like content) instead.
• Metadata is usually preserved. Exif and XMP blocks embedded in the AVIF are typically carried through to the JPG container by mainstream converters. GPS coordinates, camera model, and copyright fields survive the round-trip. IPTC data is less consistently copied and should be verified after conversion if it matters.