WebP to PNG Converter

Pixel for pixel, yes. PNG stores whatever the WebP decoder produced without touching it, so nothing is lost in this step. What the conversion cannot do is undo compression that already happened: a soft, blocky WebP becomes a soft, blocky PNG that happens to be several times larger.

Because PNG has to record every pixel exactly. In a test of 30 photographs converted through this page, PNGs came out a median of 12 times the size of the lossy WebP they came from (7× at best, 18× at worst). Flat artwork such as screenshots and diagrams grows far less — around 3× — because PNG compresses runs of identical pixels very well.

Yes. The alpha channel is carried through the canvas and written into the PNG as 32-bit RGBA, including partially transparent pixels such as anti-aliased edges, soft shadows and faded gradients. This is the main reason to choose PNG over JPG as your target.

You get one still image: the first frame. The converter paints the decoded file onto a canvas once, and PNG has no animation in its base specification to write the other frames into. If you need all the frames, use a frame extractor instead of a format converter.

No. Canvas re-encoding writes pixels, not metadata, so EXIF, XMP and any embedded ICC profile are left behind and the PNG is plain sRGB. If keeping a camera's shooting data matters more than the format, do not convert the file at all.

Nothing is uploaded. Open DevTools, switch to the Network tab and convert a file: no request carries your image. The practical limits are 10 files at a time and 50 MB per file, and once the page has loaded the conversion itself needs no network connection.