Convert PNG to WebP

• Writes a lossy WebP at quality 80, which is where the saving on a heavy PNG actually comes from.
• Keeps the alpha channel, so fully clear pixels and the half-clear ones along a soft edge both survive.
• Rebuilds the file from the decoded pixels, so what you download is a real WebP rather than a renamed PNG.

• Nothing is scaled or cropped, so the WebP arrives at the width and height the PNG already had.
• It cannot write a lossless WebP: the encoder in this build takes a quality number and nothing else.
• No EXIF or GPS fields travel with it, because the output is built from raw pixels alone.

1. Choose the PNG on your device. Drop it onto the panel above or press Browse files. The pair is already set, so anything that is not a PNG is refused at the drop.
2. Press Convert to WebP. Your device writes a WebP at quality 80 with the alpha channel carried across, so both fully and partly transparent pixels survive.
3. Download the WebP. The panel prints both sizes. On a photograph saved as a PNG the drop is usually large; on flat artwork it is smaller, and quality 80 is a trade worth looking at.

This is the conversion to use when a PNG is too heavy but the see-through parts have to stay see-through. WebP carries a full alpha channel, so a cut-out product shot keeps its clean edge, a logo keeps its empty corners, and the half-transparent pixels along an anti-aliased curve stay half transparent instead of turning into a fringe.

It is the whole reason this page exists separately from PNG to JPG. JPEG has no alpha channel at all: send the same logo there and every transparent pixel comes back white, or the colour you pick. If the file has transparency in it and you want it smaller, WebP is the only one of the two answers that works.

WebP can be written losslessly or lossily. This converter writes it lossy, at quality 80, which is what makes the saving worth having. For a photograph or a detailed illustration stored as a PNG, that is exactly the right bargain — the file collapses and nothing visible changes.

For crisp vector-style artwork it is a real trade rather than a free win. Lossy compression simplifies detail, and the first place it shows is a one-pixel outline, a small caption baked into the image, or a hard boundary between two flat colours. Look at the result at display size before you commit, and keep the PNG if the artwork has to be pixel-exact.

A photograph that somebody saved as a PNG is the best case by a wide margin. PNG has no good way to compress photographic detail, so those files are enormous, and the WebP can easily be a tenth of the size with nothing visibly different.

A small flat icon is the other extreme: PNG is already efficient on large areas of identical colour, so there may be very little left to take, and a tiny PNG can even come back marginally larger. The panel prints both byte counts, so you can see which case you are in before downloading.

• Favicons and app icons. The tooling around them expects PNG, and the files are small enough that the saving would not matter anyway.
• Email. Mail clients handle WebP inconsistently, and an image that does not render is worse than one that is 20 KB heavier.
• Upload forms and older desktop software that list PNG and JPG and stop there.
• Your working master. Edit in PNG, export WebP for the site, and you never have to re-compress a copy of a copy.

• One PNG per run, up to 20 MB, and no folder mode on this page — bulk work belongs to the resizer panel.
• Quality is fixed at 80 with no slider to raise it, so artwork that needs a gentler setting is better left as the PNG.
• A very large PNG needs room for the decoded picture and the encoder at once, and a device short of memory is refused with the reason rather than risking the tab.