PNG to WebP Converter

WebP often achieves 25–35% smaller files than PNG on UI graphics while keeping transparency, which improves Largest Contentful Paint and saves mobile data. It is now baseline in every evergreen browser for `<img>` and `<picture>`, so dual formats are less mandatory than five years ago.

Yes: WebP supports lossy and lossless modes with alpha. This tool uses lossy WebP controlled by the quality slider; very flat graphics may show tiny alpha fringing at aggressive qualities—bump quality up if halos appear.

Encoding WebP requires `canvas.toBlob("image/webp")` support, which lagged in Safari for years. Decoding WebP in `<img>` came earlier than reliable encoding. If export throws, use Chrome or Firefox once; your CDN can still serve the file everywhere readers accept WebP.

Same general idea (raster → WebP), but each encoder implementation differs slightly in psychovisual tuning. For mission-critical assets, compare visually at your chosen quality. This path is optimized for convenience inside it3, not pixel-identical parity with every CLI version.

No. The canvas sees one static frame—the first decoded bitmap from your PNG. True animation or multi-page PNG workflows need specialized encoders beyond a single-canvas export.

Color is whatever the browser decodes into sRGB-ish canvas pixels; embedded ICC from PNG is honored during decode but the WebP carries no parallel ICC in this simple export. For brand-critical color proofs, verify in your target environment.