Why Is My WebP Not Loading? – WebP Troubleshooting Guide

Quick Answer

WebP images usually fail to load because of an outdated browser (pre-2020), a wrong MIME type on the server, a corrupted file, or a content security policy. Check browser support first, then the server headers, and convert to JPG or PNG if WebP still won't work.

How to Fix WebP Loading Issues

Fix 1: Check Browser Support

WebP is supported in Chrome 32+, Firefox 96+, Edge 18+, Safari 14+, and Opera 19+. Older browsers won't display WebP images. To confirm the file itself is valid, open it directly in Chrome or Firefox.

Fix 2: Verify Server MIME Type

Your web server must send WebP files with the correct Content-Type header:

Content-Type: image/webp

If the server sends a different MIME type (like application/octet-stream), browsers won't render the image. Add the WebP MIME type to your server configuration.

Fix 3: Add a Fallback Format

Use the HTML <picture> element to give browsers without WebP support a JPG or PNG instead:

<picture>
  <source srcset="image.webp" type="image/webp">
  <img src="image.jpg" alt="Description">
</picture>

Fix 4: Convert to a Compatible Format

If you need the images to work everywhere right now, convert them to JPG or PNG: JPG for photographs, PNG for graphics with transparency. Our converters do this in your browser.

Common Causes and Solutions

Cause	Symptoms	Solution
Old browser	Broken image icon	Update browser or use fallback
Wrong MIME type	Broken image or download prompt	Configure server headers
Corrupted file	Partial rendering or error	Re-export or re-convert
CSP restrictions	Blocked by security policy	Update Content-Security-Policy
CDN caching	Old headers cached	Purge CDN cache
Content-Disposition	File downloads instead of displaying	Remove header or fix inline setting

Try It Now

Convert WebP to JPG or PNG in your browser, with no software to install and no uploads to a server.

Frequently Asked Questions

Why do my WebP images show as broken in the browser?

The most common causes are: using an old browser that doesn't support WebP (pre-2020), incorrect MIME type on the server (must be 'image/webp'), or the WebP file itself is corrupted. Try opening the image directly in Chrome or Firefox to rule out browser support issues.

How do I check if my server serves WebP with the correct MIME type?

You can check the MIME type using browser developer tools (F12 > Network tab) or an online header checker. The Content-Type header for WebP files should be 'image/webp'. If it shows 'application/octet-stream' or something else, your server needs to be configured to serve the correct MIME type.

Does Safari support WebP?

Yes, Safari 14+ (released September 2020) supports WebP. If you're using an older version of Safari or macOS, WebP images won't display. Update your browser or convert WebP images to JPG or PNG for compatibility.

Should I provide a fallback for WebP images?

For maximum compatibility, yes. Use the HTML `<picture>` element with a WebP source and a JPG fallback: `<picture><source srcset="image.webp" type="image/webp"><img src="image.jpg" alt="description"></picture>`. Modern browsers will use the WebP, and older browsers will fall back to JPG.