WebP supports Chrome 32+, Edge 18+, Firefox 65+, Opera 19+, Samsung Internet, and Safari 14+ on iOS, 16+ on macOS. Learn WebP browser support and limitations.

Prince Dewani
May 1, 2026
WebP is a royalty-free image format from Google, specified as IETF RFC 9649, that supports lossy and lossless compression, alpha transparency, and animation. It works in Chrome 32+, Edge 18+, Firefox 65+, Opera 19+, Samsung Internet 4+, Safari 14+ on iOS, and Safari 16+ on macOS, while Internet Explorer never supported it.
This guide covers what WebP is, the browsers that support it, its features, how to detect support, how it compares to JPEG, PNG, and AVIF, and known issues.
WebP is a raster image format that Google built on top of the VP8 video codec, and the IETF formally specified it as RFC 9649. WebP supports lossy compression, lossless compression, alpha transparency, and animation, ships with the .webp file extension, and uses the image/webp MIME type.
WebP plays in every major desktop and mobile browser today. Internet Explorer is the only modern-era browser that never added support.
Chrome supports WebP from Chrome 32 on Windows, macOS, Linux, ChromeOS, and Android. Chrome 17 to 22 played lossy WebP, Chrome 23 to 31 added lossless and alpha but not animation, and Chrome 4 to 16 had no WebP support. Chrome for Android has shipped WebP since Chrome Android 25.
Microsoft Edge supports WebP from Edge 18, the first Chromium-based release on Windows 10. Edge 12 to 17, the legacy EdgeHTML build, did not support WebP, so users still on the original Edge fall back to JPEG or PNG. Edge for Android and macOS support WebP from launch.
Firefox supports WebP from Firefox 65 on Windows, macOS, Linux, and Android. Firefox 2 to 64 did not support WebP. Mozilla shipped lossy, lossless, alpha, and animated WebP in the same Firefox 65 release, so feature detection in Firefox is binary.
Safari supports WebP from Safari 14 on macOS Big Sur and iOS 14 on iPhone and iPad. Safari 14 to 15.6 plays most lossy WebP images, but lossless and animated WebP need Safari 16 on macOS Ventura, since older builds drop frames or render the animation as a static keyframe. Safari 3.1 to 13 had no WebP support.
Opera supports WebP from Opera 19 on desktop, with full lossy, lossless, alpha, and animation support. Opera 11.1 to 18 supported only lossy WebP, and Opera 9 to 11 had no support. Opera Mobile plays WebP from Opera Mobile 11.5 on Android, and Opera Mini renders WebP through its server-side rendering pipeline.
Samsung Internet supports WebP across every shipping version, starting with Samsung Internet 4 on Galaxy phones and tablets. WebP is the default image format the Samsung Internet decoder negotiates over the Accept header, alongside JPEG and PNG, so Galaxy users get WebP automatically when sites send the correct content negotiation.
The legacy stock Android Browser supports WebP from Android 4.2 (Jelly Bean), with Android 4 to 4.1 limited to lossy WebP only. Android 2.1 to 3 had no WebP support. The Android Browser was retired in Android 4.4 in favor of Chrome for Android, which has shipped WebP since the very first Play Store build.
Internet Explorer never added WebP support. IE 5.5 through IE 11 cannot decode WebP in the img tag, in CSS background-image, or inside the picture element. Microsoft has retired Internet Explorer 11, so use Edge, Chrome, or Firefox for WebP work, and ship a JPEG or PNG fallback for any remaining IE traffic.
Note: WebP playback breaks across older Safari, legacy Edge, and Internet Explorer. Test it on real browsers and OS with TestMu AI. Try TestMu AI free!
WebP packs lossy, lossless, animation, and alpha transparency into a single format, with file sizes smaller than JPEG, PNG, and GIF at matching picture quality.
WebP support varies across older browser builds, so production sites need a runtime check before serving a WebP source. The cleanest detection probes the browser's image decoder rather than parsing the user agent string.
function supportsWebP(callback) {
const img = new Image();
img.onload = () => callback(img.width === 2 && img.height === 1);
img.onerror = () => callback(false);
img.src =
"data:image/webp;base64,UklGRhoAAABXRUJQVlA4TA0AAAAvAAAAEAcQERGIiP4HAA==";
}
supportsWebP((isSupported) => {
console.log("WebP supported:", isSupported);
});If the snippet logs false on a browser you expect to support WebP, check that the data URL was not blocked by a Content Security Policy directive that restricts img-src to https only.
WebP, JPEG, PNG, and AVIF all serve images on the web, but they differ on compression, transparency, animation, and browser reach. The table below lays out the trade-offs that drive format selection.
| Dimension | WebP | JPEG | PNG | AVIF |
|---|---|---|---|---|
| Standards body | Google, IETF RFC 9649 | Joint Photographic Experts Group, ISO/IEC | W3C, ISO/IEC 15948 | Alliance for Open Media |
| File extension | .webp | .jpg, .jpeg | .png | .avif |
| Lossy compression | 25 to 34 percent smaller than JPEG | Baseline | Not applicable | About 50 percent smaller than JPEG |
| Lossless compression | About 26 percent smaller than PNG | Not supported | Baseline lossless | Smaller than PNG and WebP lossless |
| Alpha transparency | Lossy and lossless | Not supported | Lossless only | Lossy and lossless |
| Animation | Yes, replaces GIF and APNG | Not supported | APNG variant only | Yes |
| Browser reach | Chrome, Edge, Firefox, Opera, Samsung Internet, Safari 14+ | Every browser ever shipped | Every browser since Internet Explorer 7 | Chrome 85+, Firefox 93+, Safari 16.4+ |
| Best fit | Photos and graphics with transparency, animated assets, default modern web | Universal photo fallback, legacy device coverage | UI graphics, screenshots, lossless transparency | Top-tier compression on Chromium and Firefox, Safari 16.4 and later |
WebP is supported in every major browser, but real-world delivery still has rough edges around legacy browsers, animated playback, and editor tooling.
In my experience, the most common production failure is shipping animated WebP without a poster fallback to Safari 14 and 15 users, who see a frozen first frame instead of the loop. Always pair animated WebP with a JPEG or PNG poster and a sensible HTML fallback inside picture, then probe canPlayType-style detection at runtime.
All WebP version numbers and platform notes in this guide come from these primary sources:
Did you find this page helpful?
More Related Hubs
TestMu AI forEnterprise
Get access to solutions built on Enterprise
grade security, privacy, & compliance