WebP to PNG

Drop in your WebP files and get PNGs back, with transparency carried across untouched.

  • Free forever
  • No signup
  • Files never uploaded
  • No watermark
  • Unlimited files

WebP to PNG converter

WebP files are accepted. Paste from clipboard with Ctrl+V (Cmd+V on a Mac).

Compression mode

PNG output is always lossless. Every pixel and every alpha value from the decoded WebP is preserved exactly.

Lossless mode discards nothing, so there is no quality control here — no quality decision is being made.

Output on this page is always PNG. Every other setting is yours, and the compressors elsewhere on the site let you pick any format.

  • Removes timestamps and embedded comments from the output.

  • Convert without changing the pixel size of the image.

Ready. Add a file to begin.

Results

Lossless mode · PNG output · 0 files

No files yet. Results will appear in this table as soon as you add one.

Your files are processed by your own browser. Nothing is uploaded to a server, so nothing can be stored, read or shared.

More tools

Other tools on this site

Each one runs in the browser the same way, with no upload and no account.

  • Compress JPEG

    Shrink JPG and JPEG photos with a quality slider or an exact target size in kilobytes.

    Compress JPEG
  • Compress PNG

    Reduce PNG screenshots and graphics while keeping transparency and hard edges intact.

    Compress PNG
  • Compress WebP

    Re-encode WebP images at a lower quality, or convert JPEG and PNG into WebP.

    Compress WebP
  • Resize Image

    Change pixel dimensions by width, height or percentage, with the aspect ratio locked.

    Resize an image
  • JPG to PDF

    Combine several photos into one PDF, reorder the pages and choose paper size and margin.

    Build a PDF
  • Document Editor

    Write a formatted document in the browser and export it to PDF, DOCX or HTML.

    Open the editor

Specification

Technical specification

Every capability written out as text, including the ones where the answer is no. A specification that only listed the wins would not be worth reading.

Technical specification — what this tool supports, attribute by attribute.
AttributeThis tool
Supported input formatsJPG and JPEG
Output formatsJPEG, PNG, WebP
Compression typeLossyJPEG discards detail permanently by design. PNG output is lossless but far larger for photographs.
Quality controlAdjustable, 10 to 100Maps directly to the encoder's quality setting. Moving it genuinely changes the output.
Exact output file sizeYes — target in KBThe encoder searches for the highest quality that fits under your limit, then reports the size it actually reached.
Resize / image dimensionsYes — max width and heightAspect ratio preserved. The resizer page adds exact pixel and percentage modes.
Batch / bulk processingUnlimitedFiles are encoded in parallel across a Web Worker pool and can be downloaded as one ZIP.
Maximum file sizeNo limit set by this siteBounded in practice by your device's memory, since each image is held uncompressed while it is processed.
EXIF and metadataStripped by defaultCamera model, timestamps and GPS coordinates are removed. You can switch it off.
Transparency / alpha channelNot applicable to JPEGJPEG has no alpha channel. Choose PNG or WebP output if you need transparency.
Chroma subsampling controlNot availableThe browser's encoder chooses it and exposes no setting. We will not add a control that cannot affect the output.
Progressive JPEG controlNot availablecanvas.toBlob gives no control over progressive encoding. Use MozJPEG or ImageMagick if you need it.
Color profile handlingConverted to sRGBA browser canvas works in sRGB, so wide-gamut images are converted. Correct for the web, wrong for print masters.
Bit depth8 bits per channelThe maximum a browser canvas provides. HDR and 10-bit output need AVIF, which browsers cannot write.
Animation supportNot supportedA canvas decodes only the first frame of an animated file, so animation is out of scope rather than half-supported.
Where processing happensIn your browserNo upload endpoint exists in the compression path. Disconnect from the network after the page loads and it still works.
File retentionNone — nothing is receivedThere is no copy to retain or delete, because no file is ever transmitted.
WatermarkNeverThe output contains your image and nothing else.
Account, quota or costNoneNo sign-up, no daily cap, no paid tier withholding a feature.
Browser supportChrome, Edge, Firefox, SafariDesktop and mobile. Requires Canvas and Web Workers, which every current browser provides.

How it works

How to webp to png converter

  1. Step 1: Add your files

    Drag them onto the drop zone, click to browse, or paste from the clipboard. Batches are fine.

  2. Step 2: Set the quality

    The default suits most images. Move it if you want a smaller file or a more faithful one.

  3. Step 3: Download the converted files

    Each row shows the size before and after. Save them one at a time or as a single ZIP.

Features

What this tool does

  • Batch processing

    Queue as many image files as you like. A Web Worker pool runs them in parallel, so a large batch never freezes the page.

  • Real quality control

    The slider maps straight to the encoder setting. Move it and the output genuinely changes — nothing here is cosmetic.

  • Exact target size

    Ask for 200 KB and the encoder finds the highest quality that fits, then reports the size it achieved.

  • EXIF and metadata stripping

    Camera model, timestamps and GPS coordinates are removed on the way out — worth doing before publishing a phone photo.

  • Format conversion

    Write the result as JPEG, PNG or WebP whatever you put in, so you can test which is smallest.

  • Nothing is uploaded

    The whole pipeline runs in your browser through the Canvas API. Disconnect your network after the page loads and it still works.

  • No watermark, no sign-up

    The output is your image and nothing else. There is no account, no daily quota and no paid tier holding back a feature.

  • Works on mobile

    The layout, the drop zone and the results table are all usable on a phone, and mobile browsers run the same encoder as the desktop ones.

In depth

About this conversion

Expect the file to get bigger

This conversion almost always produces a larger file, and that is not a fault — it is the point. WebP is a compressed format built for the web; PNG is lossless and stores every pixel exactly. Going from one to the other means giving up the compression that made the WebP small.

A 200 KB WebP photograph commonly becomes a 1.5 MB PNG. If your goal was a smaller file, this is the wrong conversion; if your goal is compatibility with something that refuses WebP, it is exactly right.

Why people need this

The usual reason is software that has not caught up. Plenty of content management systems, older desktop applications, print workflows and internal tools still reject a WebP upload outright, even though every browser has displayed the format for years.

Converting to PNG is the safe answer because PNG is universally understood and lossless, so nothing degrades on the way. If file size matters more than universality, converting to JPEG instead will produce something far smaller — at the cost of transparency.

Lossy and lossless compression are not the same thing

Lossless compression rewrites the file so every pixel survives exactly — decode it and you get the original back, byte for byte. PNG, GIF, lossless WebP and ZIP all work this way.

Lossy compression discards detail on purpose. JPEG converts the image to a frequency representation and throws away the high-frequency detail your eye is least likely to miss. That is irreversible, and it is how lossy reaches sizes lossless cannot: a photograph saved as PNG is routinely five to ten times larger than the same photograph as JPEG.

Neither is better. Photographs suit lossy encoding; screenshots, logos and line art suit lossless, because lossy encoders leave haloes around hard edges.

Transparency and color JPEG cannot carry

JPEG has no alpha channel and cannot store transparency. Converting a transparent PNG forces those pixels to become something, and most tools fill them with black — which is why a logo exported to JPEG arrives in an unwanted dark box. Keep it as PNG, use WebP (alpha support, typically 25–35% smaller than PNG), or flatten onto a chosen background deliberately.

Color is the other gap. Screens mix additively in RGB; printing presses mix subtractively in CMYK, and converting between them always approximates. A CMYK JPEG is converted to RGB before a browser can display it, and saturated cyans and deep blues can shift noticeably. Compress and resize in RGB for screens, and keep a separate CMYK master for print.

Questions

Frequently asked questions

Every answer below is present in the page source, expanded, so it can be read without opening anything.

Is transparency preserved?

Yes. Both WebP and PNG carry a full 8-bit alpha channel, and it is copied across untouched. This is the main reason to choose PNG rather than JPEG as the destination.

Why is my PNG so much larger than the WebP?

Because PNG is lossless. It records every pixel exactly, with no ability to discard detail your eye would not miss. The WebP was small precisely because it did discard some. Converting cannot recover that detail, but it does have to spend bytes storing what remains, exactly.

Does converting back improve the quality?

No, and it is worth being clear about that. Detail discarded by the original WebP encode is gone permanently. The PNG is a faithful, larger copy of the compressed image — not a restored original.

Can I convert animated WebP files?

No. This tool works on still images, and an animated WebP would be reduced to its first frame. There is no animation support here and none is advertised.

Should I convert to JPG instead?

If the image is photographic and has no transparency, yes — the JPEG will be a fraction of the PNG's size and will be accepted by the same software. Use PNG when transparency or exact pixel fidelity matters.

Are my files uploaded?

No. Decoding and re-encoding both happen in this browser tab on your own device.

From the blog

Related reading

Longer explanations from the blog.

  • Image Formats

    WebP vs JPEG: Which Should You Use, and When JPEG Still Wins

    WebP produced a 27.0 KB file against MozJPEG's 41.1 KB on the same photograph at slightly higher measured fidelity — 34% smaller. It also produced a larger file than JPEG on random noise. The advantage is real and content-dependent.

    9 min read

  • Image Formats

    PNG vs JPEG: When to Use Each, With the File Sizes to Prove It

    PNG stored the same photograph in 1274.1 KB where JPEG needed 67.5 KB — nineteen times larger. On a flat graphic PNG won. On a smooth gradient PNG lost to JPEG by a factor of two, which surprises most people.

    9 min read

  • Practical Guides

    How to Compress Images for a Website Without Wrecking Them

    Resize before you compress. Measured on one photograph: half the width at quality 80 produced a 16.4 KB file, while full width at quality 40 produced 20.6 KB and looked far worse. The order of operations matters more than the settings.

    8 min read