Drop in as many PNGs as you like. Transparency is preserved, and files typically come out 60–80% smaller.
Or drop images here
PNG is a lossless format. Every pixel is stored exactly as it was, with nothing discarded. That is exactly what you want for a logo or a screenshot with crisp text, and exactly the wrong thing for a photograph.
The problem is that PNG has become the accidental default. Screenshots save as PNG. Design tools export PNG. Plenty of stock photos get handed over as PNG. A photograph saved as PNG can easily be five to ten times larger than the same image as WebP with no visible difference at all.
It depends heavily on what the image contains:
| Image type | Typical reduction |
|---|---|
| Photograph saved as PNG | 70–85% |
| Screenshot with text | 30–50% |
| Illustration with flat colour | 20–40% |
| Logo with transparency | 15–35% |
| Small icon under 100 px | Often no gain |
Photographs give the biggest wins because lossy compression has the most redundant data to throw away. Very small icons sometimes come out slightly larger in WebP, because the format's container overhead outweighs any saving on so few pixels.
This is the question people ask most, and the answer is yes. WebP supports a full 8-bit alpha channel exactly as PNG does. A logo with a transparent background converts to a WebP with a transparent background. Nothing is flattened, nothing gains a white box behind it.
This is the main advantage WebP has over JPEG, which has no transparency support at all and would fill your transparent areas with solid white.
The quality slider trades file size against fidelity. Some starting points that hold up in practice:
Keep the PNG if the image is a small icon, if it contains fine text you cannot afford to soften, or if you are uploading somewhere that rejects WebP. Some older CMS installations, a few marketplaces and most print workflows still expect PNG or JPEG.
Related: JPG to WebP, PNG to AVIF, and our guide to WebP vs AVIF.
No. WebP supports a full alpha channel, so transparent backgrounds are preserved exactly as they were in the PNG.
Yes. Every browser in current use supports WebP, including Chrome, Firefox, Safari and Edge. Support has been universal since 2020.
No. Conversion happens entirely inside your browser using your own device's processing. The files never leave your computer.
There is no limit imposed by us. A few hundred at a time is comfortable on a desktop computer. Phones have tighter memory limits for very large images.
Yes. Add your WebP files and choose PNG as the output format. Note that data discarded during lossy compression cannot be recovered by converting back.
Below roughly 100 pixels, WebP's container overhead can exceed any compression saving. For very small icons, PNG is usually the better choice.
Your browser may ask permission to download multiple files.