Convert WebP to PNG in your browser
Saved an image off the web and found nothing will open it? Drop it here. The PNG comes back with its transparency intact, and the file never leaves this tab.
or browse your device. Everything is processed on this device
No WEBP to hand?
Then JPG is the better target: a fraction of the size, opened by just as much software, and the quality difference is invisible at normal viewing size. PNG earns its place on transparency and flat artwork.
Convert to JPG insteadHow to convert WebP to PNG
One or a hundred. They are read straight off your disk into this tab and never uploaded.
The defaults keep every colour and every transparent pixel. Only touch the palette if you want the PNG smaller and the image is flat artwork.
The download is a .png that any application will open, including the ones that refused the WebP.
Why will nothing open my WebP?
WebP is a web format, and that is close to literal: browsers read it universally, and a great deal of desktop software still does not. Older Photoshop, most print workflows, a lot of internal tooling and plenty of upload forms will refuse it outright. That is why almost nobody converts a WebP for its own sake; they convert it because something downstream said no.
PNG is the safest possible answer to that. It is lossless, it keeps an alpha channel, and it has been universally supported for twenty-five years. If the image has a transparent background, PNG is the only common format that will carry it: converting to JPG instead flattens that transparency onto white.
Expect the file to get bigger, often several times bigger. A WebP is lossy, so it has already thrown detail away and stored what is left efficiently. A PNG cannot do either of those things: it records every pixel exactly. The size increase is the format keeping its promise, not the conversion going wrong. If you want a lossless file that is also small, the PNG compressor here will take the result and cut it down.
WebP to PNG FAQ
Will transparency survive?
Yes. PNG has a full alpha channel and the conversion keeps it, so a WebP with a transparent background comes out as a PNG with a transparent background. This is the main reason to pick PNG over JPG here: converting to JPG flattens transparency onto white and cannot be undone.
Why is my PNG bigger than the WebP?
Because it is lossless and the WebP was not. A lossy format throws away detail your eye is worst at noticing and then stores the rest compactly; PNG records every pixel exactly. Three to five times larger is normal for a photograph. Nothing has gone wrong, and if size matters, drop the PNG on the PNG compressor afterwards.
Does converting back and forth lose quality?
Going WebP to PNG loses nothing, because PNG stores exactly what it was handed. What was already lost happened when the WebP was made, and no conversion recovers that. Going the other way, PNG to WebP, is where a quality setting starts mattering again.
Can I convert an animated WebP?
You will get the first frame as a still PNG, and the page will say so when it happens. PNG has an animated variant, APNG, but almost nothing writes it and browsers are the only things that reliably read it. To keep an animation, a GIF is the more useful answer.
Are my WebP files uploaded to convert them?
No. The WebP is decoded and the PNG is written by your own browser, in this tab. There is no upload endpoint in the site for a file to go to, which you can check in your network tools: convert something and watch that no request carries it. Disconnect from the network after the page loads and it still works.
Is there a limit on how many I can convert?
No. There is no account, no daily cap and no watermark, because the work happens on your machine and costs us nothing per file. The practical ceiling is your own memory.
Does this remove EXIF, GPS and AI metadata?
Yes, every time, and there is no way to turn it off. The image is decoded to pixels and encoded again from those pixels alone, so EXIF and GPS, the XMP packet, embedded colour profiles, and any Content Credentials or AI-generation tags the file arrived with do not survive. There is no switch for this, because there is no way to keep them. What no compressor can remove is a watermark written into the pixels themselves, such as the invisible marks some image generators add: those survive re-encoding here and everywhere else.
Related
Same format joins the queue. Anything else re-routes to its own tool.