Chrome and Firefox can display JPEG XL images, but that does not mean Google Images or Google Discover will use them for search previews. Google currently lists BMP, GIF, JPEG, PNG, WebP, SVG, and AVIF as supported image formats for Search. JPEG XL is not on that list. For business owners, the practical move is simple: do not make JPEG XL the only public version of an image you expect Google to crawl, index, or show.
This is a compatibility problem, not a referendum on whether JPEG XL is technically impressive. A format can offer attractive compression or quality features and still be the wrong single delivery format for a revenue page. Browser support answers, "Can this visitor's browser display the file?" Search support answers a different question: "Can the search system reliably process and use it?" Those two answers do not always arrive together. Software has a gift for making one image require a committee meeting.
Browser Support Is Not Search Support
Search Engine Journal recently reported that Google Images and Discover previews do not support JPEG XL, even as modern browsers add display support (https://www.searchenginejournal.com/google-images-discover-previews-dont-support-jpeg-xl/593816/). Google's current image SEO documentation provides the more durable implementation boundary: Google Search supports images referenced in an img element when they use BMP, GIF, JPEG, PNG, WebP, SVG, or AVIF (https://developers.google.com/search/docs/appearance/google-images).
That distinction matters on pages where images contribute to discovery or conversion, including product pages, service galleries, location pages, case studies, recipes, news articles, and posts eligible for Discover. If the only useful image is delivered in an unsupported format, Google may have less usable visual material for image results and previews. The page itself might still be indexed, but the image opportunity can be weakened.
This does not mean every JPEG XL file will cause a ranking drop. Google has not said that using the format creates a page-level penalty. The narrower and more defensible conclusion is that an unsupported image format should not be trusted as the sole search-facing asset. That is less dramatic than declaring an image-format emergency, but considerably more useful.
Where the Risk Can Cost You Customers
An image-format decision becomes a business problem when visual search or a rich preview helps a buyer choose. A retailer needs products to look correct. A contractor needs finished-project photos to appear. A hotel needs rooms and amenities represented accurately. A restaurant needs its food photography, not a blank rectangle with excellent compression credentials.
Google Images can bring discovery traffic, while Discover may use large, relevant images to make eligible content more compelling. Google's Discover guidance recommends images at least 1,200 pixels wide and enabled through max-image-preview:large, with representative images supplied through page metadata where appropriate (https://developers.google.com/search/docs/appearance/google-discover). Size and metadata still do not rescue a file format the system does not support.
The immediate risks are practical:
- Important images may not be processed for Google Images as expected.
- Discover or other search previews may choose a different image or have no suitable image available.
- Teams may see the file working in a browser and assume search processing is equally healthy.
- A sitewide conversion can remove proven JPEG, PNG, WebP, or AVIF assets before replacement behavior is verified.
- Image monitoring may miss the issue because the page remains indexable and visually normal to a human tester.
That last point is the sneaky one. A normal page load proves the browser can render the experience. It does not prove Google selected the intended image, indexed the image URL, or used it in a preview.
Use JPEG XL as an Enhancement, Not the Only Door
The safest approach is progressive enhancement. Keep a supported fallback available and let compatible browsers use JPEG XL where your implementation and performance tests justify it.
A standard HTML picture element can present multiple sources while preserving a broadly supported image in the nested img element. Google's own image guidance shows this pattern with alternative formats and a fallback. Your developer should confirm the exact source order, MIME types, caching behavior, and rendered HTML for the site's stack rather than copying a generic snippet and hoping production enjoys surprises.
For search-critical images, the fallback should be a format Google currently documents as supported. WebP and AVIF can be good options when the site's browser, CMS, CDN, and editing workflows handle them correctly. JPEG and PNG remain reasonable in many situations. The correct choice depends on transparency, photographic detail, file size, quality requirements, and operational support. There is no trophy for choosing the newest extension while making the product photo disappear from search.
Keep these elements aligned:
- The
imgsource should resolve to a supported, crawlable image. - Alternative sources should use correct MIME types.
- The image URL should return a successful response without a login, bot challenge, or broken redirect.
- Alt text should describe the image for accessibility instead of functioning as a keyword storage locker.
- Nearby copy should explain what the image proves or represents.
- Structured data and social metadata should reference assets that the intended platforms can process.
- Image sitemaps, canonicals, and CDN transformations should use consistent final URLs where applicable.
Audit Before You Convert the Whole Library
Do not begin with a sitewide format migration. Begin with the pages where image visibility can influence revenue, then test a controlled sample.
1. Find search-critical images
Prioritize product images, project galleries, location photography, featured article images, case-study evidence, and visuals already earning Google Images impressions. Decorative backgrounds can wait. They have survived this long without a strategic planning retreat.
2. Record the current baseline
Use Google Search Console, analytics, server logs, and manual result checks to document which image URLs receive impressions or visits. Search Console data is aggregated and does not prove every rendering decision, but it gives you a baseline for spotting a meaningful change.
3. Verify the rendered page
Inspect the browser's rendered HTML and network requests, not only the CMS media record. Confirm that a supported image remains in the img source, that source elements resolve correctly, and that lazy loading does not hide the asset from normal crawling.
4. Test retrieval directly
Request the image URL without an authenticated session. Check the HTTP status, content type, redirect chain, cache headers, and robots rules. An elegant fallback that returns a challenge page to crawlers is not a fallback. It is decor.
5. Monitor after deployment
Watch important pages and image queries after the change. Compare Search Console impressions, image referral traffic, indexing observations, preview appearance, page speed, and conversion behavior. Do not credit or blame the file extension for every fluctuation. Search demand, page changes, seasonality, and ranking movement still exist.
Common JPEG XL SEO Mistakes
The first mistake is equating browser compatibility with Google Search support. A successful page view is useful testing evidence, but it answers only one part of the question.
The second is using JPEG XL as the only version of an important image. Until Google's documentation includes the format, preserve a supported search-facing source.
The third is treating this as a reason to avoid image modernization altogether. That swings from optimism to paralysis. Alternative sources and supported fallbacks let teams test newer formats without wagering the entire image library.
The fourth is focusing only on file weight. Faster images can improve user experience, but the smallest file is not automatically the best business asset. Quality, accessibility, crawlability, preview eligibility, and conversion context matter too.
The fifth is skipping monitoring because the migration "worked." If the definition of worked is "nobody filed a support ticket," the bar is under the floorboards. Check what search systems can retrieve and what customers actually see.
The Practical Recommendation
Keep JPEG XL optional for now on images that matter to organic search or Discover. Serve a documented Google-supported fallback, maintain descriptive alt text and useful surrounding context, and validate the rendered result after every CDN or CMS transformation. When Google adds official support, you can reassess with evidence instead of converting the library because a browser release note looked exciting.
This is the larger lesson behind technical SEO: your customer does not care which image format won the standards debate. They care whether they can find the product, see the proof, trust the business, and take the next step. A careful image setup protects that path while the platforms catch up with one another.
If you are unsure whether unsupported files, blocked assets, weak previews, or inconsistent image URLs are limiting search visibility, an AI Visibility Audit can turn the uncertainty into a prioritized fix list.
