it3 — URL shortener & tools

PNG to WebP Converter

WebP often beats PNG on file size while keeping good visual quality—great for performance-minded sites.

Open tool

Your browser may not support WebP export. Try the latest Chrome or Firefox.

Drop a PNG, paste, or browse.

Works in modern desktop and mobile browsers. Focus this area (tap or Tab) before pasting.

About this tool

This tool draws your PNG onto a canvas and exports WebP if your browser supports encoding WebP (most Chromium-based and Firefox builds do). Safari support improves over time; if export fails, try another browser.

Benefits

  • Smaller assets than PNG for many graphics
  • Widely supported in modern browsers
  • One-click download

Features

  • Drag & drop, paste, or browse
  • Quality control
  • Same dimensions as source
  • Private local processing

How it works

  1. Add a PNG.
  2. Adjust quality if needed.
  3. Download the WebP.

FAQ

Why pick WebP over PNG for the web?

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.

Will my alpha channel survive?

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.

Safari or older browsers fail to export—why?

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.

Is this identical to Squoosh or cwebp?

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.

Animated PNG to animated WebP?

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.

Does the PNG filename or ICC profile matter?

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.

Buy Me a Coffee at ko-fi.com