Will my transparent background survive the conversion?
Yes. WebP supports an alpha channel and the converter keeps it, including semi-transparent pixels such as anti-aliased edges. Test the result over a dark background if the edges are critical.
PNG to WebP
Convert PNG images to WebP format in batches with transparency support and smaller file sizes
Drag and drop your files here
or browse your device
Files are deleted automatically. Downloads expire after 10 minutes.
PNG to WebP, With Transparency Intact
PNG files are dependable but heavy. Screenshots, interface mockups and exported graphics routinely weigh in at several hundred kilobytes each, and WebP can usually cut that down a long way. This converter accepts PNG files and produces lossy WebP with the alpha channel carried over, so a logo or cutout keeps its transparent background.
The Lossy Trade
One honest caveat up front: the output here is lossy WebP, not the lossless variant. PNG stores every pixel exactly; lossy WebP does not. For photos saved as PNG the difference is invisible at reasonable settings and the size win is enormous, often 70 percent or more. For screenshots with small text, look closely at the result before you replace the original. Compression can soften letterforms, and at lower quality values thin lines pick up faint noise around the edges.
What to Set the Slider To
The default is 85. For UI screenshots and graphics with text, try 90 first and only come down if the files are still too big. Flat-color graphics compress so well that the gap between 80 and 90 is often just a few kilobytes, so there is little reason to be aggressive. Photographic content tolerates lower values better than line art does.
Transparency
WebP has full alpha support, and the conversion preserves it, including partial transparency such as soft drop shadows and anti-aliased edges. Place the converted file over a colored background to confirm the edges still look clean; semi-transparent pixels are where lossy compression artifacts show up first.
Batches and Cleanup
A single job accepts up to 30 PNGs provided the combined size stays within 50MB, which covers most icon sets and screenshot folders. Multiple outputs come back zipped together. The server clears uploaded files and results on its own about ten minutes after processing, so download promptly.
When Not to Bother
Skip the conversion if the PNG is going anywhere other than a website. Design handoffs, print work and Office documents either require PNG or handle it better. Also leave alone any PNG that is your only master copy of a graphic, since converting it to lossy WebP and deleting the source means quality you cannot get back. Any metadata in the PNG, such as text chunks or a color profile, is dropped during conversion.
How to Convert PNG to WebP
1
Upload PNG files
Select one PNG or a batch of up to 30; transparency in the files will be preserved.
2
Choose a quality value
The default of 85 suits most graphics, but screenshots with small text often look better at 90.
3
Run the conversion
Click Convert and the tool writes a lossy WebP for every PNG in the batch.
4
Save your WebP files
Download the result directly, or as one ZIP when the job contained several images.
Frequently Asked Questions
Is the output lossless like my PNG?
No, this tool produces lossy WebP. At quality 85 or 90 the difference is hard to see, but it exists, so keep the PNG as your master copy and treat the WebP as a web delivery format.
My PNG is a screenshot with small text. Anything to watch for?
Look at the text at 100 percent zoom after converting. Lossy compression can soften letter edges, and raising the quality to 90 or 95 usually fixes it while still producing a file much smaller than the PNG.
Why is the size saving so different from one PNG to another?
PNGs with flat colors and few details are already efficient, so they shrink modestly. Large screenshots and photos stored as PNG are very inefficient, and those can lose 70 to 90 percent of their size as WebP.
Are there limits on batch jobs?
One conversion run takes up to 30 PNG files with a 50MB ceiling on the combined upload. All files in the run share the same quality value, so split the job if some images need different settings.