History Lesson: What Is an .avif File? The Open Rival to HEIC

What is an .avif file?

An .avif file is a still (or sequence-capable) image from the AV1 Image File Format — usually shortened to AVIF. Spell AV1 as the open video codec from the Alliance for Open Media (AOMedia); spell HEIF as High Efficiency Image File Format; spell ISOBMFF as ISO Base Media File Format (the nested-box container family behind MP4). The Internet media type is image/avif. On disk you typically meet the extension .avif; the still/collection brand is avif, and the sequence brand is avis (sequences have historically been discussed with .avifs and a sequence MIME — later practice often consolidates under image/avif, so treat sequence MIME claims carefully).

The official AVIF specification v1.0.0 is dated 19 February 2019 (AOMediaCodec/av1-avif). The spec stores a subset of an AV1 bitstream inside a generic image file format based on HEIF / ISOBMFF, with extra constraints for interoperability. An AVIF file is designed as a conformant HEIF file for image items and image sequences. High-level capabilities called out in AOMedia / Netflix technical writing include stills, sequences/animation, alpha, and HDR / WCG (High Dynamic Range / Wide Color Gamut) — keep those claims at that altitude; do not invent “X% smaller than JPEG” market-share numbers here.

Is AVIF the same as HEIC?

No — and that mix-up is why “what is an .avif file” searches collide with iPhone HEIC threads. Both formats hang stills on the same HEIF / ISOBMFF cupboard (MP4-style boxes). The tin inside differs. Typical HEIC photos are HEVC (High Efficiency Video Coding, also H.265) coded images in HEIF. AVIF is AV1 coded images in that same container family. HEIC is a brand/extension story for HEVC-in-HEIF packaging — not “the codec.” For the container-and-brand deep dive, see History Lesson: HEIC, HEIF, and the Photo That Is Not a JPEG.

So the plain map is: HEIF = the cupboard; HEVC or AV1 = the compressed payload; HEIC vs AVIF = which branded story you usually meet on disk. Renaming .avif to .heic (or .jpg) does not convert anything. A tool that only understands HEVC-in-HEIF will not magically decode an AV1 payload.

Why won’t Windows open .avif?

Windows Photos and Explorer often fail on .avif without Microsoft’s AV1 / AVIF-related Store extension. The file can be a perfectly good image while the PC lacks a decoder — blank preview, generic icon, or “format not supported.” That gap is why downloads from the web, design handoffs, and Android/web exports keep landing as legacy files on Windows machines that never installed the optional codec pack.

This History Lesson is not the Store install walkthrough. For the practical how-to — extension vs batch-convert — see Why Windows Won’t Open Your AVIF Images. Upload forms that reject .avif keep people converting to JPG or PNG so every machine and every form can open the picture.

Where AVIF came from (AOMedia, AV1, then stills)

The Alliance for Open Media (AOMedia) announced on 1 September 2015 as a Joint Development Foundation project. Founding members were Amazon, Cisco, Google, Intel, Microsoft, Mozilla, and Netflix. The stated goal was open, royalty-free media formats and codecs in the public interest — widely read as an alternative path after HEVC royalty uncertainty and multiple patent pools. Hedge patent slogans: “royalty-free intent” is not a courtroom promise written into every file you download.

AOMedia’s first major project was the AV1 video codec. AVIF came later as AV1 image coding packaged for stills (and sequences) in the HEIF family. Browser decode support in Chrome, Firefox, and Edge, plus sites chasing bandwidth, pushed .avif onto the open web. Phones and cameras vary: some ecosystems export or save AVIF; others stay on JPEG, HEIC, or WebP. Netflix engineering writing discussed AVIF as next-generation image coding — useful context for adoption, not a claim that every consumer camera defaults to AVIF.

Why .avif files still show up in 2026

By 2026, .avif shows up as saved-from-web images, design handoffs, Android and web exports, and downloads that keep the original extension. Sites adopted it to save bandwidth; browsers learned to decode it; many Windows desktops did not. The result is a folder of modern-looking photos that behave like legacy files the moment you leave a supporting browser or phone.

A blank Photos window is not proof the image is empty. A cousin relationship to HEIC is not proof you can rename the extension and move on. These are AV1-in-HEIF packages from the AOMedia line — useful on the web, awkward on machines without a decoder, and frequently forced through a convert-to-JPG/PNG step for forms and everyday sharing.

Legacy File Converter converts AVIF locally on Windows to JPG or PNG — see Convert AVIF to JPG and Convert AVIF to PNG. Nothing is uploaded. For the HEIC companion lesson, see History Lesson: HEIC, HEIF, and the Photo That Is Not a JPEG; for the Windows how-to, see Why Windows Won’t Open Your AVIF Images; for another “looks like a photo, won’t open” wavelet story, see JPEG 2000 (.jp2) Files That Won't Open.