Static WebP input · Decoded alpha retained · Lossless PNG output

WebP to PNG Converter

Convert a supported static WebP to PNG when transparency or a lossless decoded-pixel format matters. Keep alpha, verify the result, and expect photographic PNGs to be larger rather than treating conversion as compression.

Convert WebP to PNGLocal processing · No sign-up
alpha retained
source  WebP · static RGBA
pixels  decode unchanged
result  PNG · lossless RGBA

Lossless does not mean smallMeasure the actual output

Convert one WebP or a local batch of up to 20

Re-encode decoded pixels and alpha as PNG

Select validated static WebPs and review each image's dimensions, transparency-capable preview, and measured PNG size. No quality slider is shown because the browser's Canvas PNG path does not expose lossy quality control.

Loading the WebP to PNG converter…

Enable JavaScript to validate, decode, preview, and download a PNG. Transparency, lossless encoding, animation, and file-size caveats remain readable below.

Alpha has a destination

Static WebP transparency can remain transparent in PNG

WebP and PNG can both represent an alpha channel. The browser decodes the source into color and opacity values, and the PNG encoder writes those decoded pixels without first painting an opaque background. Fully transparent regions remain transparent; soft shadows and anti-aliased edges keep partial opacity.

This is preservation of the decoded appearance, not the source container. The result is a new PNG bitstream with different compression and structure. WebP-specific chunks, original encoding choices, and source metadata are not copied through the Canvas path. Keep the original when provenance or later WebP re-editing matters.

RGBA
Red, green, blue, and alpha values for each decoded pixel.
Alpha preserved
Opacity remains available instead of being flattened onto a matte.
New container
The exported PNG is not a renamed or byte-identical WebP.
Static only
One still image is supported; animation is rejected before export.

Lossless is about reconstruction, not a byte guarantee

The PNG may be several times larger than the WebP

Source contentPNG tendencyDecision
PhotographContinuous tones, fine texture, and sensor noise often produce a much larger lossless PNG.Keep WebP unless PNG compatibility or lossless downstream editing is required.
Logo or iconFlat colors and repeated transparent areas can compress efficiently.PNG is often practical when alpha and broad compatibility matter.
Lossy WebPPNG stores the already-decoded, already-lossy pixels exactly.Do not expect lost detail or original sharpness to return.
Large dimensionsMore pixels generally mean more output data regardless of the small source file.Resize first if the destination does not need every source pixel.

The PNG encoder has no equivalent of a JPEG/WebP lossy quality search. A lower decorative quality value would not provide the promised reduction, so the tool measures the lossless result instead of implying that it can tune it to an exact byte target.

Do not collapse motion silently

Animated WebP is not converted to a single PNG

  1. 1

    Check the WebP container

    The tool verifies RIFF/WebP identity and checks animation-related data before accepting the file as a still image.

  2. 2

    Reject timed sequences

    An animated source stops with an error. Exporting only its first decoded frame could omit important content and ignore frame blending, disposal, loop, and duration rules.

  3. 3

    Select an animation workflow

    Use a frame-aware editor when you need APNG, a frame sheet, or one deliberately chosen composited still. This converter creates only a static PNG.

Strict identity and resource bounds

Supported WebP input and output checks

CheckContractReason
Magic bytesRIFF and WEBP markers must identify the selected file.A file extension or declared MIME type can be wrong.
Static imageAnimated WebP is rejected.A static PNG cannot honestly preserve the source timing and frames.
Input sizeAt most 25 MiB of encoded WebP data.The tool bounds input before allocating decoded image memory.
Pixel countAt most 40 megapixels, measured as width × height.A highly compressed file can expand into a large canvas.
Other formatsPNG, JPEG, HEIC, AVIF, unknown signatures, and undecodable WebP are rejected.This route keeps one input-to-output contract.
PNG encoderThe output blob must report image/png.A silent browser fallback is treated as an error.

Use PNG for a reason

Practical WebP to PNG decisions

Transparent UI asset

Convert a static logo or icon when a downstream design tool accepts PNG more reliably and the alpha channel must remain editable.

Lossless editing handoff

PNG prevents another lossy encoding step for the decoded pixels, but it does not reverse artifacts that already exist in the WebP source.

Photographic delivery

Keep WebP when it is supported. A full-resolution photograph can expand sharply in PNG without gaining visible detail.

Animated source

Stop and use an animation-aware tool. Neither a random nor a first frame is an adequate replacement for a timed sequence.

Local decode and encode

Conversion occurs in the current browser tab

The selected WebP is read through browser APIs, checked, decoded to pixels, encoded as a PNG blob, previewed, and downloaded without intentionally sending its image bytes to a remote conversion endpoint. Decoded images and PNG output can use considerably more local memory than the compressed WebP source.

This does not describe unrelated page requests or third-party software on the device. Extensions, endpoint security, backups, cloud-synced folders, and any platform where you later share the PNG have separate behavior. Canvas conversion is also not a guaranteed metadata sanitizer; inspect consequential output with a dedicated tool.

Need opaque JPEG compatibility?

Choose the background that replaces WebP transparency and review the extra lossy generation.

Convert WebP to JPG →

Alpha, animation, and size answers

WebP to PNG FAQ

Does WebP to PNG preserve transparency?

Yes for a supported static WebP: decoded transparent and partially transparent pixels are written to the PNG alpha channel. The conversion preserves the decoded appearance, not necessarily every original container property or metadata record.

Can this tool convert an animated WebP to PNG?

No. Animated WebP is rejected because this tool creates one static PNG, not an APNG sequence. It does not silently save the first frame; use an animation-aware workflow to choose or export frames deliberately.

Is WebP to PNG conversion lossless?

PNG encoding is lossless for the pixels decoded from the WebP. It cannot recover detail already discarded by a lossy WebP encoder, reproduce the original WebP bitstream, or guarantee preservation of source metadata.

Why can the PNG be much larger than the WebP?

PNG uses lossless compression and has no JPEG-style quality control. Photographs, noise, gradients, and high dimensions often need far more PNG bytes than a lossy WebP representing a similar decoded image.

Which WebP files can this converter accept?

It accepts a validated static WebP up to 25 MiB and 40 megapixels. Animated WebP, JPEG, PNG, HEIC, AVIF, false file extensions, and files the browser cannot decode are rejected.

Is the WebP sent away to become PNG?

The WebP is validated, decoded, encoded, previewed, and downloaded in the current browser tab without intentionally sending its image bytes to a conversion service. Page traffic, extensions, device services, synced folders, and later sharing remain separate boundaries.