What is AVIF?
AVIF is an open, royalty-free image format that stores images or image sequences using AV1 compression. It supports lossy and lossless encoding, transparency, animation, and high dynamic range.
How AVIF works
AVIF stores AV1-compressed still images or sequences inside a HEIF-based container structure. The format can represent transparency, animation, wide color, and high dynamic range in addition to ordinary photographic images. It is distinct from AV1 video delivery even though both share coding technology. Web image pipelines negotiate AVIF at delivery time, preserve a compatible fallback, and tune encoders because decode cost and artifact behavior vary with content.
Key facts
- 1AVIF uses ISO Base Media File Format structures inherited through HEIF, so parsers must understand item properties and references rather than treat it as a raw AV1 bitstream.
- 2Both lossless and lossy coding are possible, but a “lossless” setting does not restore detail already discarded by a previously compressed JPEG source.
- 3Alpha, color profile, bit depth, animation, and HDR support can differ across decoders and transformation tools even when basic single-image AVIF decoding works.
When AVIF matters
Generate AVIF variants when smaller transfers or advanced image features justify extra encoding work. Retain JPEG or WebP alternatives where client compatibility or decoding performance remains a concern.
Common use cases for file formats & compression
These examples cover file formats & compression broadly, not specifically AVIF.
- Accepting heterogeneous uploads while producing a controlled set of delivery formats.
- Moving assets between cameras, editors, browsers, archives, and downstream APIs.
- Separating long-lived source files from compact derivatives optimized for a particular channel.
Working with file formats & compression
This guidance covers file formats & compression broadly, not just AVIF.
A parser reads the file structure, identifies contained streams and metadata, and exposes them to a decoder or application. Conversion usually decodes the source representation and writes compatible information into a different structure or encoding.
This category covers file and bitstream formats, their structures, and the compression methods they use. A filename extension can be misleading, so evaluate the detected format, decoding support, metadata, transparency, color, timing, patents, and archival needs before choosing an output.
What you gain
- A suitable format preserves the properties a workflow actually needs.
- Standardized structures allow files to move between compatible tools and systems.
- Format conversion can improve delivery size, editability, or long-term accessibility.
What it costs
- Modern formats can save bandwidth but may need fallbacks for older clients and production tools.
- Converting to a simpler format can discard transparency, animation, metadata, color precision, or editability.
- Archival suitability, browser support, and editing support often favor different choices.
Before production
- 1Inspect the detected container, codec, MIME type, and magic bytes instead of trusting a suffix.
- 2Verify decoder support and preserve metadata, color, transparency, or timing when required.
- 3Retain the source when the chosen delivery format is lossy or tied to current software.