AVIF
An image format based on the AV1 video codec, encapsulating a single AV1 video frame as an image. It can reuse video hardware acceleration infrastructure and has gained support from major browsers including Chrome and Firefox.
Core Facts
Timeline (last 90 days)
WebP and AVIF formats are generally smaller than JPEG/PNG at the same quality, but browser compatibility must be considered, and a fallback can be provided via the `<picture>` element with `srcset`.
Jake Archibald compared JPEG XL and AVIF in common web use cases.
AVIF is based on AV1 intra-frame compression, and at equal subjective quality its file size can often be compressed to about sixty percent of WebP.
AVIF has high encoding complexity and takes a long time to build, and its CPU usage cannot be ignored when batch-processing large images.
In the short term, AVIF is the safer default choice, while JPEG XL's value still holds in specific scenarios.
For sites serving open-internet users with frequently updated images, AVIF with a WebP fallback is currently the safest option.
You can use the `picture` element with the `type` attribute of `source` to output both AVIF and JPEG XL formats for content negotiation, but this increases build complexity and storage overhead.
JPEG XL encoders are generally considered more speed-friendly than AVIF, especially since lossless transcoding can be done almost effortlessly.
For new projects, WebP can be used as the default directly; for pages requiring extreme performance, the picture tag can be used with AVIF as the first choice, WebP as the fallback, and JPEG as the final fallback.
At the same quality score, AVIF often saves 20%–50% in file size compared to WebP.
8 more timeline events
All Facts (19)
AVIF is essentially the single-frame output of the AV1 video codec packaged as an image format, enabling hardware acceleration by reusing the AV1 hardware decoding capabilities of video chips.
65%UnverifiedAVIF基于AV1视频编码，压缩效率比WebP再提升约20%，但编解码计算开销更大，目前仍处于普及过渡期
85%UnverifiedWebP and AVIF formats are generally smaller than JPEG/PNG at the same quality, but browser compatibility must be considered, and a fallback can be provided via the `<picture>` element with `srcset`.
50%UnverifiedJake Archibald compared JPEG XL and AVIF in common web use cases.
50%UnverifiedIn the short term, AVIF is the safer default choice, while JPEG XL's value still holds in specific scenarios.
50%UnverifiedYou can use the `picture` element with the `type` attribute of `source` to output both AVIF and JPEG XL formats for content negotiation, but this increases build complexity and storage overhead.
50%UnverifiedAVIF is based on AV1 intra-frame compression, and at equal subjective quality its file size can often be compressed to about sixty percent of WebP.
50%UnverifiedAVIF has high encoding complexity and takes a long time to build, and its CPU usage cannot be ignored when batch-processing large images.
50%UnverifiedJPEG XL encoders are generally considered more speed-friendly than AVIF, especially since lossless transcoding can be done almost effortlessly.
50%UnverifiedFor sites serving open-internet users with frequently updated images, AVIF with a WebP fallback is currently the safest option.
50%UnverifiedFor new projects, WebP can be used as the default directly; for pages requiring extreme performance, the picture tag can be used with AVIF as the first choice, WebP as the fallback, and JPEG as the final fallback.
50%UnverifiedAt the same quality score, AVIF often saves 20%–50% in file size compared to WebP.
50%UnverifiedThe encoding computation for AVIF far exceeds that of WebP, and generating a single AVIF image can sometimes require several times the CPU time of WebP.
50%UnverifiedAVIF is still in the toolchain catch-up stage; Squoosh, Cloudflare Images, and others already support it, but not all build tools and CMS plugins have natively integrated it.
50%UnverifiedThe author re-encoded the decrypted images in AVIF format, compressing the original 4.5 GB of images down to 1.6 GB.
50%UnverifiedAVIF's progressive decoding support is relatively limited, resulting in a less smooth experience than JPEG XL in large image loading scenarios.
50%UnverifiedAVIF encoding speed is relatively slow, especially time-consuming for high-resolution images, and its block-based encoding characteristic tends to produce blocky artifacts in smooth gradient areas.
50%UnverifiedAVIF has gained support from browsers including Chrome and Firefox.
50%UnverifiedAVIF is based on AV1 video encoding, and Google is the primary driver of the AV1 ecosystem.
50%