Browser display and browser encoding differ
A browser may decode and display WebP without exposing a WebP encoder through canvas. These are separate capabilities. A local conversion tool should check the MIME type returned by `canvas.toBlob()` rather than assuming the requested format was produced.
Browser and operating-system versions change over time. For broad public-facing support, consult current compatibility data and test the actual browsers you support instead of relying on a static claim from an old article.
Provide a sensible fallback
Modern sites can serve WebP directly to current browsers. Where an older client still matters, use a fallback source or keep a JPEG/PNG asset for that client. A picture element can let the browser select a supported source.
Image format support does not guarantee that every editing app, CMS preview, email client or social platform handles the file identically. Validate the full publishing path, not just browser display.
Frequently asked questions
Can GZ detect a missing WebP encoder?
Yes. The tool verifies the output Blob type and reports when the browser does not return WebP.