PNG to WebP Converter

Convert PNG images to WebP for much smaller files that still support transparency.

This tool runs entirely in your browser. Your data is never uploaded, never stored, and never leaves your device.

Re-encodes a PNG as WebP at a quality you choose, keeping the pixel dimensions and the alpha channel exactly as they were. WebP beats PNG on size while still carrying transparency, and every current browser displays it, which is why it is the usual destination for logos and screenshots headed for a web page.

How to use it

1Choose a PNG — its name, byte size and pixel dimensions appear so you can confirm you picked the right file.
2Set the quality; 90 is the default, and lower values trade detail for size.
3Press Convert to WEBP, read the before-and-after sizes, then download.

Example

Input: A 1200 × 800 photographic PNG, 1.99 MB, at quality 90
Output: 180.8 KB — 91% smaller, still 1200 × 800 pixels

Not every PNG shrinks. A 1000 × 700 interface screenshot came back 57% smaller, but a 400 × 400 logo of flat colour on a transparent background went from 5.9 KB to 6.0 KB — PNG is already close to ideal for large areas of a single colour, so there is nothing left for WebP to win. Quality 100 behaves differently again: the screenshot came back pixel-for-pixel identical to the PNG and 6% larger than it, while the photo above came back identical and still 45% smaller. Transparency survives at every quality — a fully transparent corner stayed fully transparent. Nothing is resized, and one file is converted per run.

What happens to your data

This tool runs entirely in your browser. Your input is never uploaded to a server, never stored, and never logged. The PNG is decoded into an image element, drawn once to a canvas and re-encoded by your browser's own WebP encoder, so the exact bytes depend on which browser you are using — and if that browser cannot write WebP at all, the tool says so rather than handing you a PNG with a .webp name on it.

Last updated August 2026

You have exported a PNG for a website and something downstream has objected: a page-speed report pointing at the header image, a CMS that refuses anything over a couple of megabytes, a page that takes a visible moment to paint. WebP is the usual answer, and for an image headed into a browser it is generally the right one.

Which kind of PNG you are holding decides most of what follows. Photographs, screenshots with gradients, anything with soft shading or grain — WebP has a great deal to take out of those, because it predicts in blocks and approximates in a way PNG never does. Flat colour is the other case: a logo, an icon, a two-tone diagram. PNG is already close to ideal for large areas of one colour, so there is little left to win.

Changing the format is also not a substitute for changing the dimensions, and the dimensions are usually the bigger problem. An image 3,000 pixels across that a layout displays at 800 carries nearly four times the width it needs, and re-encoding does nothing about that — resize before the file reaches a converter, not instead of it.

The mistake worth avoiding is treating the WebP as your master. It is a delivery copy: once a lossy pass has thrown detail away, converting back to PNG returns the format and not the detail. Keep the original, and check what has to accept the result — a web page takes it happily where an email client, an older desktop application or a print supplier may not.

How it works

Toolvore hands the encoding to the browser rather than shipping one of its own. The PNG is read into an image element, a canvas is created at the image's natural width and height, the image is drawn onto it once, and the canvas is asked for a WebP blob at the quality you set — the slider value is divided by a hundred on the way through, so 90 on screen is 0.9 at the encoder. Everything that is not a pixel is lost at that first step, because a canvas holds colour values and nothing else: capture dates, authorship and comment fields, an embedded colour profile, and any animation, since a canvas holds one frame. The tool also declines to trust the format it asked for — a browser that cannot write WebP quietly returns a PNG instead, so the blob's own type is checked before anything is offered for download. Very large images are the practical ceiling: the whole bitmap has to fit in the tab's memory, and when it does not, the failure is caught and reported.

Common use cases

Getting a hero screenshot under a page-speed budget
Cutting the weight of a logo with a transparent background
Meeting a CMS or forum upload cap without cropping
Preparing product photography for a site that already serves WebP
Shrinking a documentation screenshot that must stay legible
Checking that a template accepts .webp before converting the rest

Frequently asked questions

Is WebP actually smaller than PNG?＋

Usually, and how much depends on what is in the picture rather than on the size of the PNG. PNG compresses losslessly by predicting each row of pixels from the one above it, which works beautifully on flat colour and poorly on detail. WebP's lossy mode predicts in blocks and discards what it judges you will not notice, so photographs, gradients and anything grainy give it plenty to remove. Artwork made of a few solid colours can come back the same size or larger, because there was nothing much left to take.

Do all browsers and apps support WebP files?＋

Browsers are the settled part of the answer, and the software around them is not. Major content management systems and social platforms accept a WebP on upload, so anything destined for a web page is low risk. Email is the weak spot, and an inline WebP in a newsletter is still a gamble; older desktop editors may open one only with a plugin; print suppliers generally want PNG, TIFF or a PDF and will hand a WebP back. The test worth doing is the one that matters to you — convert one image and try it where it has to work.

What quality setting should I use for WebP?＋

The slider runs from 1 to 100 and starts at 90, a sensible place to leave it for anything with hard edges: text, interface chrome, line art, a logo. Small text is where a low setting shows first, because lossy encoding throws away exactly the high-frequency detail a sharp letterform is made of. Photographs tolerate far more, and the high seventies or low eighties often take another large bite with nothing visible at normal viewing size. Work downwards rather than upwards, stopping where you can start to see the difference. The preview after a conversion is scaled to fit a small panel, so it will not reveal fine artefacts — open the downloaded file at full size before committing.

Does WebP keep a transparent background?＋

Yes, and the useful comparison is with JPEG, which has no transparency channel at all: that is where the white or black box behind a converted logo comes from, and it is the reason WebP rather than JPEG is the sensible destination for a cut-out. What can suffer at aggressive settings is the soft edge — anti-aliased pixels around lettering or a curve are partly transparent, and heavy lossy encoding can leave a faint halo there. If the image has to sit on a colour you do not control, check the result against black as well as white.

Is my image uploaded to a server when it is converted?＋

It is not uploaded. The file is read into an image element from a local object URL, drawn to a canvas and re-encoded by the browser's own encoder, and there is no network request anywhere in that path — no upload to disable, no copy on a server to delete afterwards. The finished WebP exists as a blob inside the tab, which is why leaving the page discards it and you would have to convert again. Usage is counted, but what gets recorded is the tool's name and the before-and-after byte counts, not the filename and not the pixels.

Can I convert a whole folder of PNGs at once?＋

One file per run, and choosing a second replaces the first rather than adding it to a queue, so a folder of images means a folder of repetitions. For a handful that is fine. For a hundred it is the wrong instrument: a command-line encoder, or a build step that generates WebP alongside the original, is what you want, and most static site generators and image CDNs do it as part of publishing. Working through a set by hand, each download keeps the original name with the new extension, so the files stay matched to their sources.

How do I open a .webp file, and can I convert it back to PNG?＋

Current versions of Windows Photos and macOS Preview open WebP directly, and dragging the file onto any browser window works everywhere. Older image editors may need a plugin. Converting back is possible — there is a WebP to PNG page here for it — but be clear about what it buys you: a PNG made from a lossy WebP holds exactly the detail the WebP held, stored losslessly and usually in a larger file. Nothing discarded comes back, which is the argument for keeping the original rather than letting the converted copy become your only version.

Should I use WebP or AVIF?＋

AVIF generally reaches a smaller file than WebP at a similar visual quality, particularly on photographs, and it carries wide colour and high dynamic range that WebP does not. The trade-offs are encoding time, which is considerably longer, and a support story that is younger — solid in current browsers, thinner in the software around them. WebP stays the low-risk default for a general audience, and a page that wants both can offer AVIF first with a WebP fallback in a picture element. This converter writes WebP only, so AVIF has to come from elsewhere.