Logo

PNG to WebP Converter

Photographic PNGs typically lose more than 90% of their weight as WebP, transparency included. You pick the quality; your browser does the encoding.

Your PNGs are read, re-encoded and handed back by this tab alone — no server sees them.

Upload Images

Upload or Select File

Conversion Settings

85%
LowHigh
100%
10%100%200%

How much you actually save

The saving depends entirely on what the PNG holds. Across 30 photographic images at 1600 px, quality-85 WebP files came out at a median of 8% of the PNG — a twelvefold reduction — with the best case at 2% and the worst at 15%. The same encoder applied to a flat 1280×800 interface mock-up produced 55% of the PNG: still a saving, but a modest one, because PNG is already efficient at long runs of identical pixels and gains nothing from a codec designed for photographs.

That gap is the rule of thumb worth remembering. Screenshots of code, charts, line art and icons are the cases where PNG competes honestly and where you should compare the two files before switching. Photographs, gradients, textures, scans and anything with grain are where WebP wins by an order of magnitude and the decision makes itself.

What the quality slider actually does

The slider is passed to the browser unchanged: the conversion is canvas.toBlob("image/webp", quality / 100), so 85 on screen means 0.85 in the call and the browser's own WebP encoder decides everything after that. Anywhere from 1 to 99 you get lossy WebP. At exactly 100, Chrome and Edge switch encoders and write lossless WebP instead — in a 256×256 test image the file jumped from 30 KB at 99 to 74 KB at 100, and the internal chunk changed from VP8 to VP8L. Other browsers do not necessarily make that switch.

For photographs the useful range is 80 to 90; below about 75 the encoder starts smearing fine texture and ringing around high-contrast edges. For screenshots that contain text you have two honest options: set the slider to 100 and get an exact copy, or leave the picture as a PNG.

Transparency, animation and metadata

Alpha is preserved. WebP carries a full 8-bit alpha channel in both its lossy and its lossless mode, so cut-outs, rounded corners and drop shadows keep their soft edges — this, rather than raw compression, is why WebP replaced PNG for interface assets instead of JPEG replacing it.

Animation does not cross over: an animated PNG is read as one still frame, and what this page writes is always a single image. Text metadata does not cross over either. Canvas encoding keeps pixels rather than chunks, so tEXt comments disappear, and any ICC profile in the source is replaced by the sRGB profile the browser embeds itself.

Where the WebP will and will not be accepted

Every browser released in recent years displays WebP, which is why it has become the default export of most image pipelines and why converting is usually safe for anything web-facing. Outside the browser it is patchier: e-mail clients, older office suites, some upload validators and a number of print workflows still reject a .webp on sight. Convert a copy, keep the PNG, and hand over whichever file the destination accepts.

One thing not to do is convert a PNG that was itself exported from a JPEG or from a lossy WebP. Each lossy stage compounds the previous one, and the artefacts you cannot see in the PNG will be amplified rather than cleaned up. Start from the largest, cleanest PNG you have.

PNG and WebP side by side

One picture, two very different storage strategies.

 PNGWebP
CompressionLossless only: row filters plus DEFLATELossy VP8 from quality 1–99, lossless VP8L at 100 in Chrome
Transparency8-bit alpha channel8-bit alpha in both lossy and lossless mode
AnimationOnly through APNG, read here as one frameNative multi-frame support, not written by this page
MetadatatEXt comments, ICC profiles, gamma chunksRe-encoded: pixels only, with the browser's own sRGB profile
Typical sizeThe reference point for the numbers on this pageA median of 8% of the PNG for photos, about 55% for flat art
SupportUniversal, including print and office softwareAll current browsers; still refused by some mail and print tools

How to convert PNG to WebP

Pick the files, pick a quality, compare the sizes

  1. Drop in your PNGs

    Up to 10 files of up to 50 MB each. Large exports are fine — they are decoded by this tab, not sent across the network.

  2. Choose a quality

    85 suits photographs, 100 asks Chrome for lossless WebP, and the scale slider can shrink the dimensions during the same pass.

  3. Download and compare

    Each result card prints the original size next to the new one, so you can see what the conversion bought before you keep the file.

FAQ

PNG to WebP questions

Sizes, lossless mode and what happens to transparency

For photographs, dramatically smaller: a median of 8% of the original across 30 test images at quality 85, with a worst case of 15%. For flat artwork the gain is far more modest — a test interface mock-up only dropped to 55% — because PNG already compresses large areas of identical colour extremely well.
Set the quality slider to 100. Chrome and Edge respond to a quality of exactly 1.0 by switching to the lossless VP8L encoder; in a test image the output grew from 30 KB at 99 to 74 KB at 100 and the internal chunk changed accordingly. Below 100 you always get lossy WebP, and other browsers may behave differently.
Yes, in both modes. WebP stores a full 8-bit alpha channel whether it is compressing lossily or losslessly, so logos, cut-outs and drop shadows keep their soft edges instead of picking up a white box the way a JPEG would.
In a browser, effectively yes — every current release displays WebP. Off the web it is less certain: some e-mail clients, older office suites, a few upload validators and parts of the print world still reject the extension. Keep the PNG as your master and send whichever version the recipient accepts.
It is converted as a single still frame. This page always writes one image per file, so an APNG loses its animation even though the WebP format itself is perfectly capable of storing frames.
It works on any modern phone browser and nothing is uploaded — the encoding is a canvas call inside the page. The real limit on mobile is memory: a handful of 40-megapixel PNGs at once can exhaust a phone tab, so convert those in smaller batches.

Related conversions

Go the other way, or reach for a tool built for a different job.

Looking for a new version of the image rather than a smaller one? AI image editor

Pricing · Choose Yours

Flexible AI Pricing

Pay-as-you-go credits or subscription plans. No hidden fees, cancel anytime.

One Time supports crypto payment (BTC, USDT, ETH, 350+)

Monthly billing

Free

Try before you buy

0
One Time
USD
Free
32points
Up to 3 videos
Up to 32 images
Multi-Model Support
Text to Video
Image to Video
Video to Video
Consistent Character
AI Animation Generator
Templates & Effects
AI Video Enhancers
Interactive Community
Faster Generation Speed
No-watermark Outputs
More Camera Movement
Private Video Visibility
Copy Protection
Priority Support
Popular

Pro

Elevate your AI experience

29.99
1 Month
USD
800
800points1 Month
Up to 80 videos1 Month
Up to 800 images1 Month
3 tasks(Parallel Tasks)
Multi-Model Support
Text to Video
Image to Video
Video to Video
Consistent Character
AI Animation Generator
Templates & Effects
AI Video Enhancers
Interactive Community
Faster Generation Speed
No-watermark Outputs
More Camera Movement
Private Video Visibility
Copy Protection
Priority Support

Lite

Start your AI journey

19.99
1 Month
USD
300points1 Month
Up to 30 videos1 Month
Up to 300 images1 Month
3 tasks(Parallel Tasks)
Multi-Model Support
Text to Video
Image to Video
Video to Video
Consistent Character
AI Animation Generator
Templates & Effects
AI Video Enhancers
Interactive Community
Faster Generation Speed
No-watermark Outputs
More Camera Movement
Private Video Visibility
Copy Protection
Priority Support