Why is the audio out of sync after converting?

Common causes: (1) variable framerate source rendered as constant (use <code>-vsync vfr</code> to preserve VFR); (2) different audio sample rates not resampled (add <code>-ar 48000</code>); (3) container limitations (MP4 with variable framerate misbehaves — prefer MKV during editing, encode to MP4 only at the end). Always run <code>ffprobe</code> on both source and output to compare timing.

Why is the audio out of sync after converting?

Common causes: (1) variable framerate source rendered as constant (use <code>-vsync vfr</code> to preserve VFR); (2) different audio sample rates not resampled (add <code>-ar 48000</code>); (3) container limitations (MP4 with variable framerate misbehaves — prefer MKV during editing, encode to MP4 only at the end). Always run <code>ffprobe</code> on both source and output to compare timing.

Guide

AVIF Image Format: AV1-Powered Next-Generation Compression

PC By Pablo Cirre • Updated May 7, 2026

AVIF Image Format: AV1-Powered Next-Generation Compression

AVIF (AV1 Image File Format) is a modern image format based on the AV1 video codec's intra-frame encoding, standardized by the Alliance for Open Media (AOM) in 2019. It delivers exceptional compression efficiency — typically 40–50% smaller than JPEG at equivalent visual quality — while supporting HDR, wide color gamut, 12-bit color depth, and alpha transparency. With browser support exceeding 95% globally, AVIF has become the highest-compression choice for web image delivery.

Technical Foundation: AV1 Intra-Frame Coding

AVIF uses the HEIF container (ISO/IEC 23008-12, High Efficiency Image File Format — the same container as HEIC/HEIF used by Apple) with AV1 intra-frame compression. The compression pipeline:

Color space and chroma subsampling:
- YCbCr color space conversion (same approach as JPEG and HEVC)
- Supports 4:2:0, 4:2:2, and 4:4:4 chroma subsampling
- 4:4:4 (full chroma) is often used for high-quality web images to avoid color bleeding
Tiling: For large images or parallel encoding, the image is divided into tiles (power-of-2 dimensions). Each tile is encoded independently using AV1 intra prediction.
Intra prediction: 56 directional/smooth prediction modes predict each coding unit's values from already-decoded neighbors, generating a residual that requires fewer bits.
Transform: The residual is transformed using DCT or ADST (Asymmetric Discrete Sine Transform), with the transform type selected per coding unit for optimal efficiency.
Quantization: Transform coefficients are quantized (controlled by the quality parameter). AV1's quantization matrix can differentiate quantization strength between luma and chroma channels.
Loop restoration: Wiener filter + constrained directional enhancement filter (CDEF) smooth out block artifacts after decoding.
Entropy coding: Asymmetric Numeral Systems (ANS) — more efficient than CABAC used by HEVC.

The result: AVIF achieves compression ratios impossible with JPEG at the same perceptual quality, particularly at low-to-medium quality settings where JPEG shows heavy blocking and ringing artifacts.

HEIF Container Structure

AVIF uses the HEIF/ISOBMFF container:

[ftyp] File Type Box
  major_brand: 'avif'
  compatible_brands: ['avif', 'mif1', 'miaf', 'MA1B' or 'MA1A']

[meta] Metadata Box
  [hdlr] Handler: 'pict'
  [pitm] Primary Item: item_ID=1
  [iinf] Item Info:
    [infe] Item Info Entry: item_ID=1, type='av01' (AV1 image)
    [infe] Item Info Entry: item_ID=2, type='Exif' (EXIF metadata)
  [iprp] Item Properties:
    [ispe] Image Spatial Extents: width, height
    [av1C] AV1 Codec Configuration Record
    [colr] Color: nclx or prof (ICC profile)
    [pixi] Pixel Information: bits per channel
  [idat] or [mdat] Item/Media Data: AV1 bitstream

[mdat] Media Data Box (AV1 compressed image data)

For animated AVIF, a sequence of AV1 frames is stored similarly to HEIF image sequences.

AVIF Features Matrix

Feature	AVIF	JPEG	WebP	PNG	HEIC
Lossy compression	✅	✅	✅	❌	✅
Lossless compression	✅	❌	✅	✅	✅
Alpha transparency	✅	❌	✅	✅	✅
Animation	✅	❌	✅	❌ (APNG)	✅
HDR (10-bit+)	✅	❌	❌	❌ (8-bit)	✅
Wide color gamut	✅ (P3, BT.2020)	Limited	❌	❌	✅
12-bit color	✅	❌	❌	✅	✅
EXIF/XMP metadata	✅	✅	✅	✅	✅
Browser support (2024)	~95%	~100%	~97%	~100%	Limited
Royalty-free	✅	✅	✅	✅	❌ (HEVC patents)

Browser and Platform Support

Chrome: 85+ (Aug 2020)
Firefox: 93+ (Oct 2021)
Safari: 16+ (Sep 2022) — partial; AVIF animated not yet supported in Safari
Edge: 121+ (Jan 2024) full support
iOS Safari: 16+ (Sep 2022)

Notable exceptions: Internet Explorer (dead), older Safari versions, some embedded browsers. The <picture> element with AVIF + WebP + JPEG/PNG fallback covers all cases:

<picture>
  <source srcset="image.avif" type="image/avif">
  <source srcset="image.webp" type="image/webp">
  <img src="image.jpg" alt="Description" width="800" height="600">
</picture>

Encoding AVIF

avifenc (reference encoder from libavif)

# Basic lossy encoding (quality 0=worst, 100=best, default ~60)
avifenc --quality 60 --speed 6 input.jpg output.avif

# High quality (equivalent to JPEG ~90)
avifenc --quality 80 --speed 4 input.jpg output.avif

# Lossless encoding
avifenc --lossless --speed 6 input.png output_lossless.avif

# 10-bit HDR encoding
avifenc --quality 70 --depth 10 --cicp 9/16/9 input_hdr.png output_hdr.avif

# 4:4:4 chroma (avoids color bleed in text/graphics)
avifenc --quality 80 --yuv 444 input.png output_444.avif

# Animated AVIF from video
ffmpeg -i input.mp4 -vf "fps=15,scale=480:-1" frames/frame%04d.png
avifenc --fps 15 frames/frame*.png output.avif

ffmpeg

# Basic AVIF encoding
ffmpeg -i input.jpg -c:v libaom-av1 -still-picture 1 -crf 30 output.avif

# High quality
ffmpeg -i input.jpg -c:v libaom-av1 -still-picture 1 -crf 18 -cpu-used 4 output.avif

# With SVT-AV1 (much faster encoding)
ffmpeg -i input.jpg -c:v libsvtav1 -still-picture 1 -crf 30 output.avif

ImageMagick

# Convert to AVIF
convert input.jpg -quality 80 output.avif

# Batch convert JPEGs to AVIF
mogrify -format avif -quality 70 *.jpg

sharp (Node.js)

const sharp = require('sharp');

// High quality AVIF
await sharp('input.jpg')
  .avif({ quality: 80, speed: 4 })
  .toFile('output.avif');

// Lossless AVIF
await sharp('input.png')
  .avif({ lossless: true })
  .toFile('output_lossless.avif');

Quality vs. File Size Reference

Comparing AVIF quality to JPEG (using SSIM perceptual quality metric):

AVIF Quality	Equivalent JPEG Quality	File Size vs. JPEG
80	~95	~55% smaller
70	~90	~50% smaller
60	~85	~45% smaller
50	~80	~40% smaller

These ratios vary significantly by image content. Photos with gradients and complex textures show the largest improvements; already-compressed JPEGs show smaller gains.

AVIF Limitations

Encoding speed: libaom-av1 (the reference encoder) is extremely slow — encoding a single high-resolution image can take 30–60 seconds. SVT-AV1 is 5–10× faster but slightly lower quality.
Decoding speed: AVIF decoding is slower than JPEG and WebP but comparable to HEIC. Hardware decoders are increasingly available (Apple M1/M2 chips, Android Tensor chips).
Safari animated AVIF: Safari on macOS/iOS does not yet support animated AVIF (as of 2024).
Tooling: Not all image processing tools support AVIF. GIMP 2.10+ supports it; Photoshop requires a plugin.
Metadata handling: Some tools strip ICC profiles or EXIF when converting to AVIF — always verify with exiftool output.avif.

Summary

AVIF represents the current frontier of lossy web image compression. Its AV1-based compression achieves 40–50% smaller files than JPEG at equivalent quality, while supporting HDR, wide color gamut, 12-bit depth, alpha transparency, and animation. Encoding speed remains the primary barrier — for production pipelines, SVT-AV1 or cloud-based encoding services address this. With 95%+ browser support and adoption by Netflix, Facebook, and all major CDNs, AVIF is the format of choice for high-performance web image delivery when compression efficiency is the priority.

Related conversions

Common video conversions that pair well with this guide:

Related conversions

Put what you just learned into practice — convert your files now in seconds, free and without registration.

Convert →

Convert →

Convert →

Convert →

Convert →

Convert →

Frequently Asked Questions

AVIF files are typically 40-50% smaller than JPEG at equivalent visual quality. At AVIF quality 70 (roughly equivalent to JPEG quality 90 by SSIM metric), expect files about 50% smaller. The exact savings depend heavily on image content: photos with smooth gradients and complex textures show the largest improvements, while highly detailed images with many sharp edges show smaller gains. For thumbnails and web images, AVIF at quality 60-70 matches JPEG at quality 85-90 in perceptual quality.

AVIF arquivos são tipicamente 40-50% menor que JPEG at equivalent visual quality. At AVIF quality 70 (roughly equivalent to JPEG quality 90 by SSIM metric), expect arquivos about 50% smaller. The exact savings depend heavily on image content: photos com smooth gradients e complexo textures show the largest improvements, while altaly detailed images com many sharp edges show smaller gains. para thumbnails e web images, AVIF at quality 60-70 matches JPEG at quality 85-90 in perceptual quality.

AVIF Dateien are typically 40-50% kleiner als JPEG at equivalent visual quality. At AVIF quality 70 (roughly equivalent to JPEG quality 90 by SSIM metric), expect Dateien about 50% smaller. The exact savings depend heavily on image content: photos mit smooth gradients und complex textures show the largest improvements, while hochly detailed images mit many sharp edges show smaller gains. für thumbnails und web images, AVIF at quality 60-70 matches JPEG at quality 85-90 in perceptual quality.

AVIF archivos are typically 40-50% más pequeño que JPEG at equivalent visual quality. At AVIF quality 70 (roughly equivalent to JPEG quality 90 by SSIM metric), expect archivos about 50% smaller. The exact savings depend heavily on image content: photos con smooth gradients y complex textures show the largest improvements, while altaly detailed images con many sharp edges show smaller gains. para thumbnails y web images, AVIF at quality 60-70 matches JPEG at quality 85-90 in perceptual quality.

AV1 is the most efficient (royalty-free, ~30% smaller than H.265) but encoding is slow. H.265 (HEVC) saves ~30–50% over H.264 and is supported by every modern phone and desktop. H.264 remains the safest baseline for legacy compatibility. Rule of thumb: archives → AV1, daily use → H.265, broadest reach → H.264.

AVIF uses AV1 compression, which is computationally intensive by design — AV1 was optimized for quality per bit rather than encoding speed. The reference encoder libaom-av1 can take 30-60+ seconds per image at high quality settings. Solutions: (1) Use SVT-AV1 encoder (5-10x faster): ffmpeg -c:v libsvtav1 -crf 30. (2) Use avifenc --speed 8-10 for much faster but slightly lower quality. (3) Use cloud-based encoding services (Cloudflare Image Resizing, Imgix) that handle encoding at scale. Decoding AVIF is fast and comparable to other formats.

AVIF uses AV1 compressão, which is computationally intensive by design — AV1 was optimized para quality per bit em vez de codificação speed. The reference encoder libaom-av1 can take 30-60+ seconds per image at alta qualidade settings. Solutions: (1) usar SVT-AV1 encoder (5-10x faster): ffmpeg -c:v libsvtav1 -crf 30. (2) usar avifenc --speed 8-10 para much faster mas slightly baixaer quality. (3) usar cloud-based codificação services (Cloudflare Image Resizing, Imgix) that handle codificação at scale. Decoding AVIF is fast e comparable to other formatoos.

AVIF uses AV1 Komprimierung, which is computationally intensive by design — AV1 was optimized für quality per bit rather than Codierung speed. The reference encoder libaom-av1 can take 30-60+ seconds per image at hohe Qualität settings. Solutions: (1) verwenden SVT-AV1 encoder (5-10x faster): ffmpeg -c:v libsvtav1 -crf 30. (2) verwenden avifenc --speed 8-10 für much faster aber slightly niedriger quality. (3) verwenden cloud-based Codierung services (Cloudflare Image Resizing, Imgix) that handle Codierung at scale. Decoding AVIF is fast und comparable to other Formate.

AVIF uses AV1 compresión, which is computationally intensive by design — AV1 was optimized para quality per bit rather than codificación speed. The reference encoder libaom-av1 can take 30-60+ seconds per image at alta calidad settings. Solutions: (1) usar SVT-AV1 encoder (5-10x faster): ffmpeg -c:v libsvtav1 -crf 30. (2) usar avifenc --speed 8-10 para much faster pero slightly bajaer quality. (3) usar cloud-based codificación services (Cloudflare Image Resizing, Imgix) that handle codificación at scale. Decoding AVIF is fast y comparable to other formatoos.

CRF (Constant Rate Factor) is the best default for offline files: ffmpeg picks the bitrate frame-by-frame to maintain perceived quality. Two-pass is only better when you must hit an exact final size (DVD targets). Constant bitrate is for streaming with a fixed channel. For "smallest at quality X" always use CRF.

AVIF has approximately 95% global browser support as of 2024. Chrome (85+), Firefox (93+), Edge, and Chrome on Android all support AVIF fully. Safari gained support in version 16 (September 2022) for static AVIF but still lacks animated AVIF support. Internet Explorer (end-of-life) does not support AVIF. Always use the <picture> element with fallbacks: <source srcset="img.avif" type="image/avif"><source srcset="img.webp" type="image/webp"><img src="img.jpg">.

AVIF has approximately 95% global browser support as of 2024. Chrome (85+), Firefox (93+), Edge, e Chrome no Android all support AVIF fully. Safari gained support in version 16 (September 2022) para static AVIF mas still lacks animated AVIF support. Internet Explorer (end-of-life) does not support AVIF. Always usar the <picture> element com fallbacks: <source srcset="img.avif" type="image/avif"><source srcset="img.webp" type="image/webp"><img src="img.jpg">.

AVIF has approximately 95% global browser support as von 2024. Chrome (85+), Firefox (93+), Edge, und Chrome auf Android all support AVIF fully. Safari gained support in version 16 (September 2022) für static AVIF aber still lacks animated AVIF support. Internet Explorer (end-of-life) does not support AVIF. Always verwenden the <picture> element mit fallbacks: <source srcset="img.avif" type="image/avif"><source srcset="img.webp" type="image/webp"><img src="img.jpg">.

AVIF has approximately 95% global browser support as de 2024. Chrome (85+), Firefox (93+), Edge, y Chrome en Android all support AVIF fully. Safari gained support in version 16 (September 2022) para static AVIF pero still lacks animated AVIF support. Internet Explorer (end-of-life) does not support AVIF. Always usar the <picture> element con fallbacks: <source srcset="img.avif" type="image/avif"><source srcset="img.webp" type="image/webp"><img src="img.jpg">.

Common causes: (1) variable framerate source rendered as constant (use <code>-vsync vfr</code> to preserve VFR); (2) different audio sample rates not resampled (add <code>-ar 48000</code>); (3) container limitations (MP4 with variable framerate misbehaves — prefer MKV during editing, encode to MP4 only at the end). Always run <code>ffprobe</code> on both source and output to compare timing.

Yes, AVIF supports true lossless compression (avifenc --lossless). AVIF lossless is typically 20-40% smaller than equivalent PNG files, making it a strong replacement. However, encoding speed is much slower than PNG compression. For practical use: if encoding speed matters, stick with PNG or WebP lossless. If maximum lossless compression matters (large archives, static assets with long cache lifetimes), AVIF lossless is worth the encoding time. AVIF lossless also supports 10-bit and 12-bit color depths which PNG supports but PNG lossless does not compress HDR content as efficiently.

Sim, AVIF suporta true sem perdas compressão (avifenc --lossless). AVIF sem perdas is tipicamente 20-40% menor que equivalent PNG files, making it a strong replacement. Porém, codificação speed is much mais lento que PNG compressão. para practical use: if codificação speed matters, stick com PNG ou WebP sem perdas. If máximo sem perdas compressão matters (large archives, static assets com long cache lifetimes), AVIF sem perdas is worth the codificação time. AVIF sem perdas also suporta 10-bit e 12-bit color depths which PNG suporta mas PNG sem perdas does not compress HDR content as efficiently.

Ja, AVIF unterstützt true verlustfrei Komprimierung (avifenc --lossless). AVIF verlustfrei is typically 20-40% kleiner als equivalent PNG files, making it a strong replacement. Jedoch, Codierung speed is much langsamer als PNG Komprimierung. für practical use: if Codierung speed matters, stick mit PNG oder WebP verlustfrei. If maximal verlustfrei Komprimierung matters (large archives, static assets mit long cache lifetimes), AVIF verlustfrei is worth the Codierung time. AVIF verlustfrei also unterstützt 10-bit und 12-bit color depths which PNG unterstützt aber PNG verlustfrei does not compress HDR content as efficiently.

Sí, AVIF soporta true sin pérdidas compresión (avifenc --lossless). AVIF sin pérdidas is typically 20-40% más pequeño que equivalent PNG files, making it a strong replacement. Sin embargo, codificación speed is much más lento que PNG compresión. para practical use: if codificación speed matters, stick con PNG o WebP sin pérdidas. If máximo sin pérdidas compresión matters (large archives, static assets con long cache lifetimes), AVIF sin pérdidas is worth the codificación time. AVIF sin pérdidas also soporta 10-bit y 12-bit color depths which PNG soporta pero PNG sin pérdidas does not compress HDR content as efficiently.

Yes if you only change the container: <code>ffmpeg -i in.mkv -c copy out.mp4</code>. This remuxes the stream without re-encoding, takes seconds even for hours of footage. Limitations: codec must be supported by the target container (e.g. you cannot put H.264 in WebM, only VP8/VP9/AV1). To shrink size you must re-encode.