Skip to main content

WebP to PNG converter

Convert WEBP images to PNG format

No watermarkFree & unlimited
All processing happens in your browser. No data is sent to any server.

Most people arrive at this conversion because something refused a .webp file - an older editor, a marketplace uploader, a document template, a colleague's software. PNG is the universal answer, and it takes everything a still WebP has to offer, including the alpha channel. The two things to know are that the PNG will be substantially larger, since it stores losslessly what WebP compressed, and that an animated WebP contributes only its first frame, because that is all the browser draws onto a canvas.

Key facts about WebP to PNG converter

Key facts about WebP to PNG converter
TransparencyFully preserved. WebP alpha maps directly onto PNG's alpha channel, so cut-outs, rounded corners and soft shadows arrive intact.
Animated sourcesOnly the first frame is converted. Drawing an image element onto a canvas captures a single still, and no timeline reaches the PNG.
QualityNothing more is lost. If the WebP was lossy, its artifacts are reproduced exactly; if it was lossless, the PNG is pixel-identical to it.
Typical size deltaGrowth of two to five times is normal - a 150 KB lossy WebP photo often becomes a 600 KB to 1 MB PNG.
Bit depthEight bits per channel with an alpha channel, written by the browser's own PNG encoder with no quality setting to adjust.
MetadataEXIF and XMP chunks that a WebP may contain are not carried across; the PNG is written from canvas pixels alone.
Colour handlingThe canvas works in sRGB, so a WebP tagged with a wider profile is converted rather than preserved.
Compatibility gainedPNG is accepted by every image editor, office suite, upload form, print workflow and operating system in current use.
BatchTwenty .webp files per run, and multiple outputs download together as converted-png-files.zip.

What happens to your file

Your browser already contains a WebP decoder, and this page uses it: the file becomes an object URL, an image element decodes it, a canvas receives the pixels with their alpha values, and canvas.toBlob with image/png produces the output. There is no decoding service and no temporary storage anywhere - the PNG exists only as a blob in this tab until you save it. Closing the page discards everything, and nothing was sent while it was open.

About this tool

  1. 1

    Add the WebP files

    Up to twenty .webp files per batch. Files saved from a website work exactly like exported ones.

  2. 2

    Optionally set a maximum dimension

    PNG has no quality control, so resizing is the only way to influence the output size before conversion.

  3. 3

    Convert

    The decode and re-encode are fast; the browser's PNG encoder does the compression work.

  4. 4

    Download

    A single file saves as .png with the original name, while a batch arrives in a ZIP.

Specs & compatibility
Input and outputTakes .webp only (image/webp) and returns .png with the image/png type; any other extension is refused before decoding.
Conversion pathWEBP to PNG runs in three steps: an <img> element decodes the WebP and passes frame one to the canvas; the pixels land on a 2D canvas in this tab; then canvas.toBlob with the image/png type returns the finished file.
Browser supportThe WebP side needs Chrome 32, Firefox 65, Edge 18 or Safari 14 to decode, while writing the PNG is just as universal, canvas.toBlob having produced it since canvas existed.
Controls for this pairNo quality slider, PNG not being a lossy target here, so the max-dimension presets from 3840 down to 200 px are the only way to hold the PNG down in size against the WEBP.
Batch, caps and namingTwenty WEBP files per run at 500 MB each; one result downloads as a single PNG, several as converted-png-files.zip, zipped by JSZip 3.10 in page memory.
Device ceilingThe canvas caps it: past roughly 16,384 px a side Chromium refuses the bitmap and iPhone Safari gives up sooner, so an oversized WEBP fails before any PNG bytes exist.
  • Check a transparent result against a dark background - PNG viewers often show a white or chequered backdrop that hides alpha problems.
  • If the file came from a website and looks soft, that softness was already in the WebP; a lossless format cannot sharpen it.
  • When the receiving software accepts JPG as well and transparency is irrelevant, that route produces a far smaller file.
  • For an animated WebP you want to keep animated, this is the wrong tool - a still PNG is all a canvas can produce.
  • Getting a downloaded WebP into an editor, marketplace or document system that only takes PNG or JPG.
  • Turning site assets back into editable, lossless source images for a redesign.
  • Preparing a transparent logo saved as WebP for use in a presentation or a print layout.
Yes, completely. Both formats store an 8-bit alpha channel per pixel, and the canvas carries those values through untouched, so anti-aliased edges and soft shadows survive. This is the safest conversion to choose when the transparency is the reason the image exists.
Because WebP compressed the image far more aggressively than PNG's lossless method can. PNG predicts each pixel from its neighbours and deflates the residual, which is efficient on flat artwork and expensive on photographic detail. A two to five times increase is the usual outcome, and a noisy photograph can grow more.
Not here. The browser draws only the first frame of an animated source onto the canvas, so the result is a single still PNG. Extracting every frame requires a tool that demuxes the animation, and PNG itself would need the APNG extension to store the result.
It will look exactly the same. A lossless format preserves what it is given, including any blur or blocking the WebP encoder introduced. The advantage of converting is compatibility and the ability to edit and re-save without further degradation, not image quality.
The format is newer than much of the software still in daily use, and some vendors never added a decoder. Browsers, Windows 10 and later, and macOS since Big Sur all handle it, but older desktop editors, a number of upload forms and several print workflows still expect PNG or JPG - which is what this conversion provides.

Related tools

View all

Need the opposite? Try PNG to WEBP

Updated

We use anonymous analytics to improve ToolChamp. No personal data is stored or sold. Privacy Policy