Convert WebP to PNG
For logos, screenshots and anything with transparency or text. No second lossy pass.
JPG, PNG, WebP, HEIC, AVIF and BMP. Your file is processed on your device.
How do I convert a WebP file to PNG?
When PNG is the right destination
Converting a WebP is nearly always about compatibility — something will not open the file — but there are two possible destinations and they suit different images.
PNG is the right one when the image has transparency, because JPEG has no way to store it and will fill those areas with solid colour. It is also right when the image has hard edges: a screenshot, a diagram, a chart, a logo, anything with text. JPEG’s compression works by discarding fine detail, and fine detail is exactly what an edge is — the result is a faint shimmer along every boundary that is very hard to unsee once noticed.
For an ordinary photograph, JPG is the better choice: far smaller, and the loss is invisible on continuous-tone content.
Lossless, but not a recovery
PNG is lossless, which means it reproduces exactly the pixels it is given. It does not mean it restores anything the WebP had already thrown away — if the file was saved as a lossy WebP, those artefacts are now part of the picture and the PNG preserves them faithfully.
What the conversion achieves is stopping the bleeding. Every further save as a lossy format would discard a little more; from here on, the file can be opened, edited and re-saved without degrading. That is worth doing before an image goes into a workflow rather than after.
Expect a bigger file
A WebP that is 200 KB can easily become a 1.5 MB PNG. This is normal and it is the trade you are making: exact pixels cost more room than approximate ones. For a logo with a few flat colours the increase is modest, because PNG compresses runs of identical colour very efficiently. For a photograph it is dramatic, because no two adjacent pixels are the same.
If the PNG then has to fit a limit somewhere, be aware that PNG has no quality setting — the only way to make one smaller is fewer pixels. The compressor will do that and will say so, and in most cases the better answer is to accept a lossy format instead. The format tool will encode your specific file three ways and show you the actual numbers.
Nothing is uploaded
The WebP is decoded and the PNG is written by your browser, on your device. This is worth knowing here in particular, because images saved from the web are often saved from places people would rather not hand to a third-party converter.
Common questions
- Why PNG rather than JPG?
- Two reasons. PNG keeps transparency and JPEG destroys it, so a logo or cut-out has to be PNG. And PNG is lossless, so it does not add a second round of compression artefacts on top of the ones the WebP already has — which matters for screenshots and anything containing text, where JPEG leaves faint halos along every edge.
- Will the PNG be much larger?
- Yes, usually several times larger, and that is not a fault. PNG stores every pixel exactly rather than discarding information to save space. For a logo or a screenshot with flat colours the difference is modest; for a photograph it can be five or ten times, which is the case where JPG is the better destination.
- Does this recover quality the WebP lost?
- No, and nothing can. If the WebP was saved lossily, that information is gone — the PNG faithfully preserves the compressed result rather than the original picture. What it does is stop any further loss from happening, which is worth doing before an image gets edited or re-saved several more times.
- What about an animated WebP?
- It is refused rather than converted to a still. Keeping the first frame and discarding an animation without saying so is the kind of silent data loss you would only find out about later, so FileBelow tells you instead.