JPEG XL Google Images Support: A Safe SEO Migration Guide
JPEG XL can remain a browser-delivery experiment, but sites relying on Google Images or Discover should keep a supported image URL available while Google does not support .jxl on those surfaces.
· 12 min read
Google Search currently lists seven supported image formats in its image SEO documentation, and JPEG XL (.jxl) is not one of them. JPEG XL Google Images support is therefore not available for Google Images or Google Discover previews, so this guide gives SEO teams a practical way to test browser delivery without replacing the supported image assets that protect search visibility.
John Mueller recently confirmed that JPEG XL is not currently supported for Google Images or Discover previews. The useful operational response is not necessarily to abandon JPEG XL, but to separate a front-end format experiment from the image URLs that Google Search is expected to process.
The operational answer on JPEG XL Google Images support
A website should not make a .jxl file its only meaningful image URL when the image matters for Google Images or Discover. Google Search Central’s documented formats for images referenced in an img element are BMP, GIF, JPEG, PNG, WebP, SVG, and AVIF; JPEG XL is absent from that list as of October 25, 2026.
That conclusion applies specifically to the Google surfaces Mueller addressed: Google Images and Discover previews. It does not mean a compatible visitor browser cannot render a JPEG XL image. It means browser rendering and Google Search support must be assessed as separate questions.
For a controlled implementation, teams should retain at least one supported image resource for prominent editorial, product, category, and landing-page images. A conservative approach is to use JPEG XL as an optional resource while preserving JPEG, WebP, or AVIF as the conventional fallback.
The immediate audit question is straightforward:
- Does each important page expose a supported image URL in its HTML?
- Is a
.jxlURL the only image reference intended to represent the page? - Has a sitewide CMS or CDN change altered the fallback that templates previously supplied?
- Do high-value pages, such as a publisher’s article templates or an ecommerce product template, need visibility from Google Images or Discover?
A site with 5,000 product pages should not infer safety from a successful test on one browser. The same template can affect thousands of image references at once, which makes template-level review more valuable than checking individual files after launch.
Browser support, Google indexing, and previews are different layers
Chrome support for JPEG XL, including references to Chrome 155 in current discussion, answers a browser capability question. It does not establish that Google Search supports JPEG XL for Google Images or Google Discover previews. Google’s image documentation and Mueller’s public statement are the more relevant sources for those Search surfaces.
At minimum, a migration involves three distinct layers:
- Browser selection and decoding. The browser evaluates HTML and may select a source it understands.
- Page markup. The page supplies image URLs through elements such as
imgand, where used,pictureandsource. - Google Search handling. Google Search has its own published supported-format list, while Google Images and Discover have their own presentation and eligibility decisions.
A browser test in Chrome can confirm only the first layer. It does not prove that the asset can appear in Google Images or as a Discover preview.
Google Search Central specifically documents images in the src attribute of an img element. It also documents use of responsive images and recommends providing a fallback src when using responsive-image features. That documentation is the basis for preserving a standard image URL rather than treating a JPEG XL-only image as an equivalent replacement.
The distinction prevents an avoidable reporting error. A team may see a visually correct hero image in Chrome and report the release as successful, while the actual Search question—whether the supported fallback remained available—has not been tested at all.
The Google Search formats to retain
Google Search Central lists these formats for images referenced through img src:
- BMP
- GIF
- JPEG
- PNG
- WebP
- SVG
- AVIF
JPEG XL, generally identified by the .jxl extension, is not included in that documented list. The practical migration choice is normally between AVIF, WebP, and JPEG for photographic content, although the appropriate choice varies by the website’s existing image pipeline and its audience requirements.
AVIF and WebP are both documented supported formats, which makes either a reasonable fallback candidate in a JPEG XL experiment. JPEG remains useful where a team needs an especially conventional asset for older systems or workflows. Google’s documentation does not state that one of these formats receives a ranking advantage over another; format selection should not be framed as a Google ranking shortcut.
A safe implementation should also avoid misleading file handling. If a URL is named hero.jpg, the responsible team should be able to establish what it actually returns and whether it remains a supported image resource. This is a QA issue, not a claim that every filename discrepancy causes an indexing failure.
For broader diagnosis, format support should be kept separate from general indexing problems. A URL that is not indexed can have causes unrelated to image format, such as page-level indexing controls or crawl access. The workflow in Google Search Console only one page indexed is a useful reminder to isolate the actual indexing signal before assigning blame to one technical change.
Using a picture element: a cautious implementation pattern
The following pattern presents JPEG XL as an optional browser source and keeps a JPEG fallback in the nested img element:
<picture>
<source srcset="/images/mountain-lake.jxl" type="image/jxl">
<source srcset="/images/mountain-lake.avif" type="image/avif">
<source srcset="/images/mountain-lake.webp" type="image/webp">
<img
src="/images/mountain-lake.jpg"
width="1600"
height="900"
alt="Sunrise over a mountain lake">
</picture>
This is a sensible progressive-enhancement hypothesis: a browser that understands the JPEG XL source can select it, while the HTML still includes a supported img src fallback. Google’s image documentation supports the narrower point that Google can find images referenced in img src, including when the img is inside a picture element.
However, this should not be described as a Google-validated guarantee that the JPEG XL source itself is processed, indexed, or eligible for Google Images. Mueller’s statement establishes that JPEG XL is unsupported for Google Images and Discover previews. The defensible objective of this pattern is to preserve the supported fallback, not to claim search support for .jxl.
Checks for the HTML fallback
An audit should inspect the literal template output, rather than merely confirm that a picture tag exists. At a minimum, it should check that:
- the nested
imghas a non-emptysrcvalue; - that
srcidentifies a Google-documented supported format; - the fallback is a real, publicly usable image asset in the production environment;
width,height, and meaningfulalttext are present where appropriate; and- JPEG XL is offered as a
source, rather than used as the onlyimg src.
The source order in the example is a browser-delivery decision. Its presence does not alter Google’s documented format list. Teams should test their chosen markup in their target browsers and separately validate that the supported fallback remains in the page source after deployment.
What a JPEG XL migration audit should flag
The core audit finding is not “a .jxl file exists.” A .jxl resource used in a private experiment or as an optional source is different from a .jxl resource that replaces the only supported image reference on an important page.
High-priority findings
The following conditions deserve immediate review because they directly conflict with the documented supported-format list or Mueller’s statement about Google Images and Discover previews:
- JPEG XL as the only
img src. For example,<img src="/campaign/hero.jxl">gives Google no documented supported image format in that attribute. - A
picturefallback that is also JPEG XL. A page with severalsourceelements but a final<img src="/hero.jxl">has not retained the intended fallback. - A template replacement across high-value pages. Replacing the sole hero image reference on 500 article pages carries more potential exposure than a single test URL.
- A Discover-focused page whose representative visible image is JPEG XL-only. Mueller’s statement explicitly covers Discover previews, so that setup should be changed or held back.
Review items rather than confirmed defects
Some locations need review, but the available evidence does not justify calling every .jxl reference a confirmed Google visibility defect. For example, an image sitemap entry, og:image value, or structured-data image property might matter to a site’s publishing workflow, but the supplied confirmation is specifically about Google Images and Discover previews—not a blanket statement about every metadata field.
The prudent action is to inventory those references, identify where they point to JPEG XL-only assets, and retain supported versions for important Google-facing content until Google publishes broader JPEG XL support. That is risk management, not a claim that a particular metadata URL has already caused a loss of traffic.
Discover: keep the documented requirements in scope
JPEG XL support is only one part of Discover readiness. Google Search Central states that Discover is automatic for indexed content that follows its policies; meeting technical guidance does not guarantee that an article will appear.
Google’s Discover documentation recommends using high-quality, compelling images that are relevant to the content. For large-image previews, Google’s documented guidance includes images that are at least 1,200 pixels wide and the use of max-image-preview:large, or AMP. A page-level robots meta tag can be written as follows:
<meta name="robots" content="max-image-preview:large">
The 1,200-pixel and preview-directive guidance should be checked against the current Google Search Central documentation at the time of a release, since platform guidance can change. This article does not rely on unsupported universal rules about a mandatory 16:9 crop, a 300,000-pixel threshold, or specific metadata behavior.
For a publisher, a practical check might be: an article uses a 1,600-pixel-wide AVIF or JPEG fallback as its featured image, the page permits large previews, and the image is genuinely representative of the article. Those conditions still do not promise Discover distribution, but they avoid confusing a known JPEG XL support gap with the separate requirements for large previews.
Decision matrix: separate experiments from exposure
A format experiment should be proportionate to the site’s dependence on Google image surfaces. The table below distinguishes supported-fallback preservation from unverified claims about every image-related metadata channel.
| Site situation | Sensible JPEG XL approach | Main audit priority |
|---|---|---|
| Publisher with Discover reporting | Use JPEG XL only as an optional browser source | Supported img src, 1,200px+ representative image, preview directive |
| Ecommerce site with product-image traffic | Test a limited template set first | Ensure product images retain JPEG, WebP, or AVIF fallbacks |
| Agency staging environment | Test markup before production rollout | Compare page source before and after template changes |
| Portfolio site with low image-search reliance | Use progressive enhancement if desired | Avoid JPEG XL as the sole meaningful image URL |
| CDN or CMS format-default change | Pause broad replacement until fallbacks are verified | Check a sample across every affected template |
For example, an agency could choose 20 staging URLs covering article, category, product, and service templates. It can then verify that every page retains a supported img src before allowing JPEG XL delivery to a broader browser-compatible audience.
Audra is a local-first desktop auditing app for technical SEO, performance, accessibility, and related site checks. It can be used as part of that pre-release review to crawl a controlled URL set and produce a shareable technical audit; teams should define the JPEG XL-specific checks in their audit scope rather than assume that any tool automatically certifies Google Images or Discover eligibility.
A focused pre-launch testing workflow
A useful JPEG XL review does not need to become a sprawling, speculative audit. Start with the page markup and the format distinction Google has actually documented.
- Select a representative sample, such as 10 to 20 URLs across each affected template.
- Inspect page source and record the nested
img srcfor each important image. - Confirm that the fallback uses JPEG, PNG, WebP, AVIF, SVG, GIF, or BMP as appropriate—not
.jxlalone. - Review every
pictureimplementation to ensure JPEG XL is optional rather than the final fallback. - For Discover-oriented editorial pages, check that the representative image is at least 1,200 pixels wide and that
max-image-preview:largeis present where the site intends to permit large previews. - Document any
.jxlreferences in sitemaps or metadata as review items, then decide whether a supported alternative is needed for the page’s business purpose.
After launch, teams can monitor their usual Google Search reporting for material changes, while recognizing that Search visibility varies for many reasons and Discover is not guaranteed. The narrow success criterion is clear: browser experimentation has not removed the supported image fallback that Google Search currently documents.
This audit-first approach resembles the distinction made in AI search optimization versus visibility audits. An implementation change is not the same as evidence that a visibility outcome occurred; both require their own checks.
FAQ
Does Google Images support JPEG XL images?
No, not according to the current public confirmation covered here. John Mueller recently stated that JPEG XL is not currently supported for Google Images or Google Discover previews. Google Search Central’s supported list for images referenced in img src includes BMP, GIF, JPEG, PNG, WebP, SVG, and AVIF, but not JPEG XL.
Can JPEG XL images appear as previews in Google Discover?
JPEG XL should not be the only image asset a site relies on for Discover previews. Mueller’s statement specifically includes Discover previews. Sites targeting large Discover images should retain a supported format and also follow Google’s separate guidance, including a relevant high-quality image at least 1,200 pixels wide and max-image-preview:large where applicable.
Does Chrome JPEG XL support mean Google Search supports it?
No. Browser decoding support and Google Search support are different systems and should be tested separately. A compatible Chrome version may render a .jxl resource, but that does not change Google Search Central’s current supported-format list or Mueller’s statement that JPEG XL is unsupported in Google Images and Discover previews.
Can a site use JPEG XL in a picture element and keep Google Images visibility?
A picture element can retain a supported nested img src while offering JPEG XL as an optional source. Google documents that it can find an image referenced in img src inside picture. This preserves a documented fallback, but it is not a guarantee that Google processes the JPEG XL source itself.
Which image requirements still apply for Google Discover previews?
A supported image format is only one consideration. Google says Discover is automatic for eligible indexed content and does not guarantee appearance. Its guidance recommends compelling, relevant images; for large previews, it specifies an image at least 1,200 pixels wide and max-image-preview:large, or AMP. Check the current Google documentation before deployment.