What PNG to WebP actually saves you
PNG was designed for sharp edges and flat colour, and it is the only one of the two old formats that carries transparency. WebP carries transparency too, which is what makes this particular swap work: logos, icons and UI captures keep their empty space instead of being flattened onto a background, and the file gets smaller at the same time.
The saving depends on what is inside the picture. Flat areas compress well in both formats, so the gap is modest on a plain icon; the same screenshot with a photograph embedded in it can drop by a third or more, because WebP handles continuous tone far better than PNG does.
The conversion happens inside your browser. The PNG is decoded, painted on a canvas and re-encoded as WebP on your own device — nothing is uploaded, so there is no queue and no waiting for a round trip.
Which format for which job
How to convert PNG to WebP
- 1
Add the PNG files
Up to 20 at a time, each up to 50 MB. Everything is decoded and re-encoded on your own device — there is no upload step.
- 2
Watch the transparency, not the slider
The alpha channel is carried across automatically, so a logo keeps its empty space. The slider only affects how much detail the encoder keeps.
- 3
Download the WebP files
Each one is written at the original pixel dimensions with transparency intact, and the new file size is shown before you save.
Screenshots, logos and photos behave differently
The saving depends almost entirely on what is inside the file. A PNG icon with two or three colours is already close to optimal, so switching it to WebP might save only 10–15%, and pushing the quality down will damage it faster than it damages a photograph. A photograph saved as PNG is the opposite case: that is what WebP is built for, and savings of 40% and upwards are common, because PNG stores continuous tone very inefficiently.
Small text is the other thing to watch. Type in a screenshot sits on high-contrast edges, which is exactly where lossy compression shows first, so captures of interfaces and documents deserve a higher quality setting than photographs do. The slider is the control that matters here, and its default is tuned for pictures rather than for glyphs.
What you keep and what you lose
You keep the pixel dimensions, the transparency and the colour space: the WebP is the same 1200 × 630 picture, with the same empty areas, in the same 8-bit sRGB colour. Nothing is cropped, stretched or recoloured on the way through.
What changes is that the pixels themselves are approximated. That is the whole trade — a smaller file in exchange for detail the encoder judged you would not miss. It is usually right, and when it is not, raising the quality slider is the answer rather than switching tools.
Frequently asked questions
Does converting PNG to WebP keep transparency?
Yes. WebP has an alpha channel, exactly like PNG, so anything transparent in the original stays transparent in the result — no white box appears behind a logo. The tool never flattens a PNG onto a background colour.
How much smaller do the files get?
Typically 25–40%, and often more. Flat-colour artwork such as an icon or a UI screenshot saves the least, because PNG already handles flat colour well; a photographic PNG saves the most, sometimes more than half.
Doesn’t WebP lose quality?
WebP can be encoded lossy or lossless, and this tool writes lossy WebP so the size saving is real. At the default 90% the difference is hard to see on photographs. For screenshots with small text, raise the quality slider — the encoder still re-encodes the pixels, so keep the original if you need byte-exact output.
Is the resolution preserved?
Yes. The pixel dimensions never change — a 1200×630 PNG comes back as a 1200×630 WebP. Only the encoding changes, so nothing is lost to resizing.
Can I convert several PNG files at once?
Yes — up to 20 files per run, each up to 50 MB. They are processed one at a time on your own device, so a large batch does not stack up in memory.
Are my images uploaded anywhere?
No. Your browser decodes the PNG and re-encodes it as WebP using the Canvas API and a Web Worker. The file never leaves your device, and there is no upload time to wait for.
Can I turn the WebP back into a PNG later?
Yes — every current browser can decode WebP, so the file can be opened and re-exported as PNG at any time. What cannot be undone is the compression: PNG to WebP here is a lossy step, so the PNG you get back will be larger than the WebP but not identical to the PNG you started from. Keep the original if you may need the exact pixels again.
Does a transparent WebP open everywhere?
In current browsers, yes: transparency in WebP is supported by Chrome, Edge, Firefox, Safari and Opera. Desktop software is the weak spot — some older photo editors cannot open WebP at all, and some versions of Word and PowerPoint reject it too. If the file has to be placed into a document, keeping the PNG is the safer choice.
What is the difference between lossy and lossless WebP?
Lossless WebP keeps every pixel and still compresses somewhat better than PNG, but the saving is modest — typically 10–25%. Lossy WebP discards detail the eye is unlikely to notice and reaches 25–40% or more. This tool writes lossy WebP so that the saving is real; raise the quality slider when the image contains small text or fine line art.