Does current Safari display WebP?

Current Safari versions support WebP, but confirm compatibility for the oldest operating systems and embedded browsers your audience uses.

Do I need a JPEG fallback for every WebP image?

That depends on your supported browsers and delivery setup. If older clients are in scope, provide a tested fallback, for example through a picture element or your image service.

Why does WebP work locally but fail on my site?

The production URL, content type, CDN cache, rewrite rules, or generated HTML may differ from local files. Inspect the production network request and verify the fallback path.

Does Safari Support WebP? How to Check Image Compatibility

Support depends on the Safari version you target

Current Safari releases support WebP, but a site may still serve visitors using older operating systems, embedded web views, or managed devices that behave differently. Avoid relying on a blanket statement such as “every Apple device supports this.” Define the oldest Safari and iOS versions you support, then test those environments or consult the compatibility data relevant to your audience.

Also distinguish the browser's ability to decode WebP from the way a site delivers it. A CDN, CMS plugin, service worker, or cached HTML response can affect which image URL is requested. When a picture appears broken, inspect the actual network request and response instead of assuming the format alone is responsible.

Use feature detection or a deliberate fallback

For responsive art direction or an explicit fallback, the HTML <picture> element can list modern formats before a broadly supported source:

&lt;picture&gt;
  &lt;source srcset=&quot;/images/product.avif&quot; type=&quot;image/avif&quot;&gt;
  &lt;source srcset=&quot;/images/product.webp&quot; type=&quot;image/webp&quot;&gt;
  &lt;img src=&quot;/images/product.jpg&quot; alt=&quot;Blue ceramic mug&quot; width=&quot;900&quot; height=&quot;900&quot;&gt;
&lt;/picture&gt;

The browser selects a supported source and falls back to the img element. Keep the fallback available at a working URL and make its dimensions and alternative text appropriate. If you use a framework or image CDN that generates sources automatically, follow its documented setup rather than adding a second competing rewrite layer.

Test the full path

Record the browsers and minimum OS versions that matter for your visitors.
Open the page in those browsers and confirm the image renders at desktop and mobile sizes.
Inspect the network panel for the chosen image URL, status code, content type, and dimensions.
Test with caches cleared and with the production CDN or image optimizer enabled.
Verify that the fallback source still works when the modern source is unavailable.

Choose formats based on the asset

WebP is a useful delivery format for many photographs and graphics, but it is not mandatory for every image. Compare the visual result, file size, transparency behavior, and the capabilities of your image pipeline. Keep source files so you can regenerate delivery assets if requirements change.

ImageTight can convert selected images to WebP for testing. Use the image tool on a small sample, then confirm the resulting file works in your actual site setup before converting a full library.