Picture Batch WebP to PNG
WebP to PNG
This is the conversion to use when the image has transparency, or contains text or flat colour, or is going to be edited further. PNG keeps the alpha channel exactly, adds no further loss, and opens in everything.
Drop WebP images here
WebP files — or any of PNG, JPEG, AVIF, BMP, ICO, TIFF, GIF or camera raw (CR2, CR3, NEF, ARW, DNG, RAF, ORF, RW2). Everything runs on this device.
Your images never leave this device. They are decoded and re-encoded by your own browser, and the security policy on every page blocks this site from sending them anywhere.
Lossless, keeps transparency, universally supported, larger than modern formats.
PNG is lossless — it stores every pixel exactly, so there is nothing to trade away.
Images keep their original dimensions.
Kept. PNG stores a full alpha channel, so cut-outs and soft edges come through exactly.
Exif is carried across where both formats can hold it. Nothing currently in the queue has any.
Exif metadata can be carried from WEBP to PNG. Colour profiles are not, because decoding converts the image to sRGB.
What happens to your image
Expect the file to get larger, often several times larger. PNG is lossless, so it has to store the JPEG or WebP compression artefacts as though they were real detail — which, to a lossless encoder, they are.
| Property | Outcome |
|---|---|
| Transparency | Preserved: Kept. PNG stores a full alpha channel, so soft edges and cut-outs survive exactly. |
| Image quality | Preserved: Nothing further is lost. PNG is lossless, so it stores exactly what the WebP decoded to — including the compression artefacts the WebP already had. |
| Colour | Partly preserved: Converted to sRGB. Decoding an image colour-manages it into the browser's own space, so the output is sRGB and is left untagged, which every viewer reads as sRGB. A wide-gamut source is reported before conversion. |
| Exif metadata | Preserved: Carried across if you leave metadata switched on, or removed completely if you switch it off. Camera, date and any location tag travel together. |
| Orientation | Preserved: Applied to the pixels, and the tag is reset to upright afterwards so nothing rotates the image a second time. |
| Animation | Not preserved: Only the first frame is converted. Animation is not carried across. |
Transparency is the reason to choose this over JPEG
WebP is the format logos and interface assets are most often saved as now, and those are precisely the images with cut-out backgrounds. JPEG would destroy that; PNG stores the same eight-bit alpha channel WebP does, so soft edges and partial transparency come through unchanged.
After conversion the result is decoded again and the transparency is checked in both directions — that it did not disappear, and that it did not appear where it should not have.
Lossless in, lossless out — but only from here on
If the WebP was lossless, this conversion is exact: the same pixels in a different container. If it was lossy, PNG stores the decompressed result faithfully, including the compression artefacts. It cannot undo them, and the file will usually be several times larger than the WebP was.
The queue shows which kind of WebP it found before converting, so this is not a surprise afterwards.
Why a WebP will not open in the program you need
WebP was published in 2010 but only became universal in browsers around 2020, and desktop software follows years behind browsers. Anything whose image importer was written before then — older versions of Photoshop and Illustrator, most office suites, a great deal of print and publishing software, plenty of content management systems, and almost every embedded or industrial application — simply does not recognise the format.
That is the real reason this conversion is wanted, and it is worth knowing that it is a support problem rather than a quality one. The WebP is not worse; it is just newer than the thing trying to open it.
PNG is the safe answer because it has been universal since the late nineteen-nineties and, unlike JPEG, keeps transparency and adds no compression loss of its own. If the destination does accept JPEG and the image has no transparency, JPEG will be substantially smaller.
What the conversion does to the file
The image is decoded by the browser's own WebP decoder, which is the same code that displays WebP on any page you visit, then re-encoded as PNG. Nothing is resampled, nothing is re-compressed lossily, and the dimensions are unchanged unless you ask for a resize.
Afterwards the PNG is decoded again and compared against the pixels that went into the encoder. For a lossless pair like this one the comparison has to come back essentially exact, and anything else is reported as a failure rather than offered as a download.
If something goes wrong
The PNG is several times larger than the WebP.
Lossless storage of a lossy image, which costs space by nature.
What to do: If you do not need transparency or further editing, JPEG will be far smaller.
An animated WebP became a single image.
PNG has no animation. Only the first frame is converted, and the queue warns about it.
What to do: Animated conversion needs a different kind of tool; this one is for still images.
Questions
Does converting WebP to PNG keep transparency?
Yes, exactly — both formats store a full eight-bit alpha channel, and the result is checked after conversion to confirm the transparency survived.
Does it improve quality?
No. Nothing recovers detail a lossy format discarded. PNG stores what is left without adding any further loss, which is a different and more modest promise.