PNG to WebP Converter
Drop PNG files in and WebP comes out, transparency and all. The encoder runs inside this tab, so nothing is uploaded.
JPEG has no transparency, so transparent areas are filled with this color.
Everything runs locally in your browser. Nothing is uploaded to any server — close the tab and your files are gone.
How to convert PNG to WebP
Drop your PNG files
Add one file or a hundred. The output format on this page is already set to WebP, so you can drop and download without touching a setting — and the picker stays there if you want AVIF, JPEG or PNG instead.
Match the quality to what the PNG actually holds
The slider starts at 75, a sensible landing spot for a PNG that is really a photograph. Screenshots, UI mockups and flat illustrations hold up better at 85–95, where the edges of text stay crisp. The number runs 1 to 100 and applies to every file in the queue at once.
Scale it down if it is headed for the web
A 4000 px export rarely needs to stay 4000 px. Fitting the longest edge to 2048 or 1024 px cuts more weight than any quality setting will. The resize only ever shrinks: hand it an image that is already smaller than the target and it passes through untouched.
Compare, then download
The compare view puts the original and the WebP under one slider so you can inspect the difference at full size. Take files one at a time, or grab the whole batch as a ZIP once more than one has finished.
What changes when a PNG becomes a WebP
Lossless in, lossy out
PNG stores every pixel exactly. The WebP here is written by the lossy encoder, so the result is a re-encode rather than a repack — and that is where the size drop comes from. If the pixels have to stay untouched, switch the output format to PNG instead: that path is lossless and only shaves off file overhead. Which of the three modern formats deserves the job in the first place is a separate question, and WebP vs AVIF vs JPEG works through it on real images.
Transparency survives
WebP carries an alpha channel, so cut-outs, soft shadows and rounded corners come across transparent rather than flattened onto white. That is what makes PNG → WebP a safe swap for logos and UI assets, where PNG → JPEG is not: the JPEG route has to paint a colour behind every transparent pixel before it can encode anything at all.
Flat colour is where the win is biggest
Screenshots, diagrams and UI mockups are broad areas of identical colour plus a few hard edges. PNG has to record every one of those pixels; WebP does not. The exception is a PNG that was already saved with a small indexed palette — a flat icon in 32 colours is close to as small as it is going to get, and re-encoding it buys very little.
The hard edges break first
Push the slider too low and it is never the busy part of the picture that gives way. Thin type picks up a soft halo, one-pixel strokes go grey at the ends and a crisp border between two flat colours starts to smear, all while the photographic areas still look fine. That is the reason to judge a conversion on a corner of the image with text in it rather than on the middle.
There is no lossless WebP switch here
WebP the format has a lossless mode; this page does not expose it. Every WebP written here comes out of the quality-based lossy encoder, even at 100. When a byte-for-byte copy of the PNG pixels is the requirement — a design source file, an asset that will be edited again, anything going into a print workflow — leave the output on PNG and use the resize control for the size.
PNG to WebP — frequently asked questions
Will the transparent background survive the conversion?
Yes. The alpha channel is decoded and written straight back out, so fully transparent and semi-transparent pixels stay that way in the WebP. Nothing is flattened onto a white background, and no background-colour control appears — that one belongs to the JPEG output.
How much smaller will my PNG get?
It depends entirely on the picture, so the tool shows the real number for each file instead of promising one up front. Simple graphic images usually drop a lot, and a photograph that was saved as PNG drops even more — PNG was the wrong container for it to begin with.
What quality setting should I use for a screenshot?
Higher than the 75 the slider starts at. Lossy compression blurs text and UI edges before anything else, so 85–95 is the comfortable range. If a screenshot has to stay pixel-perfect — a bug report, a UI spec, anything someone will zoom into — set the output format to PNG rather than WebP.
Can I convert a folder of PNGs in one go?
Yes. Every file gets its own row with its own before/after size, and they encode across background workers — up to three on a desktop machine, one on a phone. Once more than one is finished, a single ZIP download appears.
Do older browsers still read WebP?
Every browser released in the last several years does, Safari included. Software is the real limit rather than browsers: some desktop apps, some email clients and plenty of print tools still refuse WebP outright, and for those the PNG is worth keeping.
Can I produce a lossless WebP from my PNG?
Not on this page. The WebP encoder here is the lossy one and the slider only moves it between 1 and 100 — there is no lossless-WebP toggle. For an exact copy of the pixels, keep the output on PNG; that encoder is lossless and oxipng then trims the file without changing the image.
Should I delete the PNGs once I have the WebPs?
No. Treat the WebP as the delivery copy and the PNG as the master — it is the lossless one, and a second WebP made from the first would stack another round of compression. There will also be places that still want the PNG: favicons, some email templates, older CMS uploads.
Does the file name change when the format does?
Only the extension. logo.png comes back as logo.webp, and inside a ZIP two files that would end up with the same name get a numbered suffix so neither one overwrites the other.