PNG to WebP Converter

What this does

Encodes PNG files as WebP using the encoder built into your browser. WebP was created by Google in 2010 specifically for web delivery: it compresses far tighter than PNG and, unlike JPG, keeps the alpha channel, which makes it the natural replacement for logos, icons, illustrations and screenshots that currently ship as PNG. Up to 20 files per batch, 50 MB each, converted on your device with nothing uploaded.

How much smaller will my WebP be?

For screenshots and UI graphics, typically 60 to 80 percent smaller than the PNG. For PNGs that are really photographs (exports from a design tool or camera app), the reduction is even larger. The exact figure depends on the image and the quality slider; the Download button on each row shows the resulting size so you can compare before you commit. Smaller image bytes translate directly into a faster Largest Contentful Paint, which is why WebP shows up in nearly every page-speed audit recommendation.

Does the quality slider mean the WebP is lossy?

Yes. The canvas API in browsers exposes WebP's lossy mode only, and the slider (10 to 100, starting at 92) controls how much detail is traded for size. There is no lossless-WebP option here. For flat-colour graphics, 80 to 90 usually looks identical to the source; for photos, 75 to 85 is the common web setting. Keep the original PNG as the master and treat the WebP as the copy you publish, then you can re-encode at a different quality any time.

How do I convert PNG to WebP?

1. Drop .png files above or click to select them.
2. Choose a quality; 92 is a safe default, 80 is a good starting point for web assets.
3. Click Convert to WebP and download each file. Output is named after the input, e.g. hero.png becomes hero.webp.

Does transparency survive?

Yes. This is the main reason to choose WebP over JPG for a PNG: the tool draws onto a canvas with an alpha channel and WebP stores it, so soft shadows and anti-aliased edges come through intact rather than being flattened onto a solid background. Output is 8-bit, capped at 8192 pixels per side, and carries no metadata from the PNG, since the WebP is encoded fresh from pixels.

Do I still need a PNG fallback for old browsers?

Rarely. Every major browser has decoded WebP since Safari 14 shipped in 2020, so for a public website WebP alone is fine. The two places to be careful are non-browser consumers — Office documents, email newsletters rendered by Outlook, some CMS thumbnailers and print workflows still want PNG or JPG — and the encoder side: Chrome, Edge and Firefox all ship a WebP encoder, but if a browser lacks one the canvas silently falls back to PNG data even though the file is named .webp, so check the size on the download button looks right. Should you ever need to go back, WebP to PNG reverses this losslessly.