Testing

WebP: Browser Support, Features, Limitations

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.

Author

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.

What is WebP?

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.

Which browsers does WebP support?

WebP plays in every major desktop and mobile browser today. Internet Explorer is the only modern-era browser that never added support.

Loading browser compatibility data...

WebP compatibility in Chrome

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.

WebP compatibility in Edge

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.

WebP compatibility in Firefox

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.

WebP compatibility in Safari

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.

WebP compatibility in Opera

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.

WebP compatibility in Samsung Internet

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.

WebP compatibility in Android Browser

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.

WebP compatibility in Internet Explorer

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

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!

What are the key features of WebP?

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.

  • Lossy compression: WebP files are 25 to 34 percent smaller than JPEG at the same quality, based on Google's reference encoder tests on the Kodak photo set.
  • Lossless compression: WebP lossless files are about 26 percent smaller than equivalent PNG files, with full alpha transparency.
  • Alpha transparency: Both lossy and lossless WebP carry an 8-bit alpha channel, so designers no longer need a separate PNG to keep transparency on photos.
  • Animation: Animated WebP replaces GIF and APNG, with full 24-bit color, alpha, and frame timing inside a single .webp file.
  • ICC, EXIF, and XMP metadata: WebP carries color profile, camera, and copyright metadata, so it slots into existing photo pipelines without a transcode step.
  • Royalty-free license: Google publishes libwebp under a BSD-style license and the WebP bitstream itself carries no patent fees, so encoders and decoders ship without per-unit costs.
  • Maximum dimensions of 16383 x 16383 pixels: WebP supports images up to 16383 by 16383 pixels, which covers all responsive web use cases except print-grade gigapixel scans.

How do you check if a browser supports WebP?

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.

  • Open DevTools: Open the page in the browser you want to test and press F12 (or Cmd+Option+I on macOS). Switch to the Console tab.
  • Paste the feature-detection snippet: Run the JavaScript below. It loads a 2x1 WebP buffer through the Image() API and reports whether the browser decoded it.
  • Read the result: A true value means WebP works in this browser; false means you need to ship a JPEG or PNG fallback.
  • Wire a picture element fallback in HTML: Wrap your image in a picture tag with a WebP source and a JPEG or PNG img child. The browser picks the first format it can decode, with no JavaScript required.
  • Verify on real browsers and OS: Cross-check the result on Chrome, Edge, Firefox, Safari 14, Safari 16, the legacy Android Browser, and any Internet Explorer traffic still in your audience.
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 vs JPEG, PNG, and AVIF

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.

DimensionWebPJPEGPNGAVIF
Standards bodyGoogle, IETF RFC 9649Joint Photographic Experts Group, ISO/IECW3C, ISO/IEC 15948Alliance for Open Media
File extension.webp.jpg, .jpeg.png.avif
Lossy compression25 to 34 percent smaller than JPEGBaselineNot applicableAbout 50 percent smaller than JPEG
Lossless compressionAbout 26 percent smaller than PNGNot supportedBaseline losslessSmaller than PNG and WebP lossless
Alpha transparencyLossy and losslessNot supportedLossless onlyLossy and lossless
AnimationYes, replaces GIF and APNGNot supportedAPNG variant onlyYes
Browser reachChrome, Edge, Firefox, Opera, Samsung Internet, Safari 14+Every browser ever shippedEvery browser since Internet Explorer 7Chrome 85+, Firefox 93+, Safari 16.4+
Best fitPhotos and graphics with transparency, animated assets, default modern webUniversal photo fallback, legacy device coverageUI graphics, screenshots, lossless transparencyTop-tier compression on Chromium and Firefox, Safari 16.4 and later
...

What are the known issues with WebP?

WebP is supported in every major browser, but real-world delivery still has rough edges around legacy browsers, animated playback, and editor tooling.

  • No Internet Explorer support: IE 5.5 through IE 11 cannot decode WebP in any context. Sites that still target enterprise IE fleets need a JPEG, PNG, or GIF fallback inside a picture source list.
  • Safari quirks before macOS Ventura: Safari 14 to 15.6 plays most lossy WebP images, but drops frames on animated WebP and renders some lossless WebP files as a static keyframe. Safari 16 fixed both gaps, so users still on Big Sur or Monterey hit this regularly.
  • Animated WebP is not always smaller: Animated WebP beats GIF on file size, but it can fall behind animated AVIF and even short MP4 clips for loops longer than a few seconds. Profile your clips before swapping formats.
  • Older Android Browser gaps: Android 4 to 4.1 played only lossy WebP, and Android 2.1 to 3 had no support. Use Chrome for Android, Firefox for Android, or Samsung Internet on modern phones to avoid the legacy stock browser.
  • Image editor friction: Adobe Photoshop needs version 23.2 or later for native WebP, and many older Windows editors still require the WebP codec pack. Designer hand-offs often arrive as PNG until the editor is updated.
  • Email client coverage is patchy: Apple Mail, Gmail, and Outlook for Microsoft 365 render WebP, but legacy desktop Outlook builds and several embedded webview clients still need a fallback. Test campaigns with Litmus or Email on Acid before sending.
  • Default download behavior on older Windows builds: Windows 8.1 and the original Windows 10 (build 17763 and earlier) treat WebP as a download instead of opening it in the Photos app. Users on those builds need the WebP Image Extensions package from the Microsoft Store.

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.

...

Citations

All WebP version numbers and platform notes in this guide come from these primary sources:

Author

Prince Dewani is a Community Contributor at TestMu AI, where he manages content strategies around software testing, QA, and test automation. He is certified in Selenium, Cypress, Playwright, Appium, Automation Testing, and KaneAI. Prince has also presented academic research at the international conference PBCON-01. He further specializes in on-page SEO, bridging marketing with core testing technologies. On LinkedIn, he is followed by 4,300+ QA engineers, developers, DevOps experts, tech leaders, and AI-focused practitioners in the global testing community.

Open in ChatGPT Icon

Open in ChatGPT

Open in Claude Icon

Open in Claude

Open in Perplexity Icon

Open in Perplexity

Open in Grok Icon

Open in Grok

Open in Gemini AI Icon

Open in Gemini AI

Copied to Clipboard!
...

3000+ Browsers. One Platform.

See exactly how your site performs everywhere.

Try it free
...

Write Tests in Plain English with KaneAI

Create, debug, and evolve tests using natural language.

Try for free

Frequently asked questions

Did you find this page helpful?

More Related Hubs

TestMu AI forEnterprise

Get access to solutions built on Enterprise
grade security, privacy, & compliance

  • Advanced access controls
  • Advanced data retention rules
  • Advanced Local Testing
  • Premium Support options
  • Early access to beta features
  • Private Slack Channel
  • Unlimited Manual Accessibility DevTools Tests