AVIF in Image SEO: Why Does Google Still Ignore This Format in Search Images?

What Does It Mean That AVIF Is Excluded From Image Search?

John Mueller confirms what many have suspected: AVIF does not appear anywhere in the official documentation for Image Search, and the format is probably not currently supported. The term "probably" leaves room for interpretation, but the absence of the format in public docs is a clear signal.

Evergreen Googlebot — the modernized version of the bot that utilizes a recent Chrome rendering engine — can theoretically display AVIF images during crawling for traditional web search. This means that your visuals will be visible in the context of an indexed webpage but not in the dedicated Images tab.

Why Is There a Distinction Between Web Search and Image Search?

Google uses different pipelines to index and serve text-based web results and image results. Image Search relies on specific infrastructures and indexing criteria, with constraints regarding decoding, storage, and large-scale thumbnail generation.

Despite its excellent compression performance, AVIF requires more CPU resources for decoding than WebP or JPEG. At the scale of billions of images crawled and stored, this difference matters. Google evidently has not yet deemed the adoption/benefit ratio sufficient to integrate it into Image Search.

Do Browser Support and Adoption Justify the Wait?

Mueller specifies that support could come as usage and browser support increase. Safari has supported AVIF since iOS 16 (late 2022), and Chrome and Firefox for several versions now. As for adoption, we are seeing a gradual but still timid rise.

The message between the lines? Google is waiting for the format to reach a critical mass of real usage before investing in the necessary infrastructure. No timeline, no commitment — just a possibility conditioned on market evolution.

• AVIF is not supported for Image Search, even though evergreen Googlebot can render it for text-based web search.
• No official timeline for integration — Google conditions this on the growing adoption of the format.
• WebP and JPEG remain the recommended formats to maximize visibility in Google’s Images tab.
• Rending for web search is not enough: if Image Search is a key channel for you, AVIF alone is currently not a viable option.
• The official documentation remains the reference — the absence of AVIF from the public docs is not an oversight, it’s a choice.

Is This Statement Consistent With Observations on the Ground?

Yes, totally. Tests conducted by several practitioners show that AVIF images are not appearing in Google Images, even on perfectly crawled sites. However, those same images do appear well in the context of an indexed webpage — confirming the rendering by evergreen Googlebot.

What’s striking is the lack of proactive communication on this point. Many sites have switched en masse to AVIF for performance gains without realizing they were sacrificing a portion of image organic visibility. [To be verified]: the actual impact on total traffic obviously depends on the weight of Image Search in your acquisition sources — but for visual sectors (e-commerce, recipes, decor, fashion), it’s rarely negligible.

Does the Official Discourse Leave Any Gray Areas?

The "probably" from Mueller is cautious, but in practice, the absence in the official documentation amounts to a non-support. What’s missing is an indication of the adoption threshold that would trigger integration. 10% of sites? 30%? A certain volume of image queries? No data.

Another unclear point: does Google still index the metadata of the AVIF image (alt, context, structured data ImageObject) even if it doesn’t display it in Image Search? [To be verified] on concrete cases, but the most likely hypothesis is that without the ability to generate a thumbnail, the image is simply ignored for this channel.

Should We Expect a Quick Evolution or Play It Safe?

Let’s be honest: Google took years to integrate WebP into Image Search after its launch. AVIF is likely to follow the same slow trajectory, even though browser adoption is progressing faster this time.

The risk? Switching too early and losing image traffic without compensation. The opportunity? Wait for a clear signal from Google — an update to the documentation, an official blog post — before migrating en masse. In the meantime, a dual format strategy (AVIF as a fallback for browsers that support it, WebP/JPEG for Google Images) remains the safest.

Should You Abandon AVIF or Use It Anyway?

It depends on your priorities. If Image Search represents a significant portion of your organic traffic, exclusively using AVIF is a strategic mistake. However, for sites where performance (Core Web Vitals, loading times) takes precedence over image visibility, AVIF remains a powerful lever.

The hybrid solution: use the <picture> tag with multiple sources. You offer AVIF to modern browsers that support it (size gain, better UX), while maintaining a WebP or JPEG fallback that Googlebot Image Search can index. It’s more technically complex, but it covers all cases.

How Can I Check the Real Impact on My Image Traffic?

First step: isolate the share of traffic coming from Google Images in your analytics. If it’s marginal (< 5%), the image format matters little for this channel. If it exceeds 15-20%, each format decision becomes strategic.

Then, test. Switch a portion of your key images to AVIF only, monitor impressions and clicks in Search Console (filter by search type: Images). If you notice a decline, you have your answer. Warning: the test should last at least 4-6 weeks to smooth out seasonal variations.

What Mistakes Should Be Avoided in Image Format Migration?

Classic mistake: completely removing legacy formats (JPEG, WebP) in favor of AVIF alone, assuming that "modern browsers are enough." You lose Image Search, and potentially other crawlers (social networks, third-party tools) that do not yet support AVIF.

Another trap: not testing the rendering on mobile. AVIF can have compression artifacts different from JPEG/WebP — what could go unnoticed on desktop might be problematic on a 6-inch screen. Visually validate before deploying at a large scale.

• Audit the share of traffic coming from Google Images in your analytics before any decision
• Implement a dual format strategy with <picture> (AVIF + WebP/JPEG fallback)
• Test the impact on a sample of images before complete migration
• Monitor Search Console (type: Images) for 4-6 weeks post-migration
• Check AVIF's visual rendering on both mobile and desktop
• Maintain alt tags, structured data ImageObject, and semantic context regardless of the format strategy