PNG to WebP Converter - Convert PNG to WebP Free Online

Convert PNG to WebP in your browser with an adjustable quality setting. Transparency is preserved, batches download as a ZIP, and nothing is uploaded to a server.

What PNG to WebP Does

This tool decodes your PNG onto an in-browser canvas and re-encodes the pixel data with the browser's own WebP encoder. WebP is unusual among common web formats in that it supports an alpha channel and a quality-driven lossy encoder in the same file, which is exactly why it suits PNG source material better than JPG does. Transparency survives the conversion intact: a transparent background stays transparent, and soft anti-aliased edges keep their partial alpha instead of picking up a white fringe. What does not survive untouched is the pixel data itself. This page uses WebP's lossy path, and the Quality slider — 1 to 100, defaulting to 92 — sets how much detail the encoder is allowed to throw away. Higher values keep more texture at a larger file size; lower values shrink the file and eventually leave visible smearing and blotching around sharp edges, text, and hard color boundaries. The point of the conversion is size. PNG stores photographic noise and smooth gradients very inefficiently, so photos, screenshots with gradients, and rendered artwork usually drop a long way. Flat graphics are the exception: solid-color icons, simple line art, and diagrams already compress well under PNG's lossless scheme, and the WebP version may save very little or occasionally come out larger. The conversion adds nothing either. It does not sharpen, upscale, or change the pixel dimensions — output width and height match the input exactly — and in practical terms it runs one way. Once the lossy encoder has discarded detail, converting the WebP back to PNG produces a lossless file that faithfully preserves the artifacts rather than the original.

Why You'd Convert PNG to WebP

PNG is a lossless format, and on photographic or gradient-heavy images that honesty costs a lot of bytes. WebP keeps the transparency PNG gave you while encoding the rest far more compactly.

Cut page weight on image-heavy sites without giving up transparent backgrounds or soft edges
Shrink PNG screenshots, UI mockups, and 3D renders that gradients make disproportionately large
Serve one WebP file instead of a PNG-plus-JPG pair, since WebP covers both alpha and lossy
Batch-convert an asset folder to WebP in one pass and download it as a single ZIP

How to Convert PNG to WebP

Four steps, all of them local — the file is decoded, re-encoded, and handed back without ever touching a server.

1

Drop in one PNG or a whole batch — every file in the run shares the same settings

2

Set the Quality slider; 92 is the default, and 75-85 gives noticeably smaller files on photos

3

Apply the conversion — the button reads "Converting..." while the encoder works through your files

4

Download each WebP on its own, or grab the whole batch as a single ZIP

Frequently Asked Questions

Yes, completely. WebP carries a full alpha channel, so transparent backgrounds stay transparent and semi-transparent pixels keep their exact opacity. This is the main reason to pick WebP over JPG for PNG sources — JPG has no alpha at all and has to flatten transparency onto a solid color. Anti-aliased edges on logos and icons come through without the white fringe a JPG conversion would leave behind.
It depends entirely on what the image contains. Photographs, screenshots with gradients, and rendered artwork commonly drop 60-85% at the default quality, because PNG's lossless scheme stores that kind of noisy, continuous-tone data very inefficiently. Flat graphics behave differently: a solid-color icon or a simple line drawing is already near-optimal as a PNG, so the saving may be a few percent, none at all, or in rare cases the WebP ends up slightly larger.
Start at the default of 92. It is generous enough that artifacts stay invisible in normal viewing while still cutting most photographic PNGs down hard. Drop to 75-85 when page weight matters more than pixel-level fidelity. Below roughly 65 you will start seeing smearing in smooth gradients and mushy halos around text and sharp edges. There is no universally correct number — check one representative image at your chosen setting before committing a large batch to it.
In browsers, effectively yes — Chrome, Firefox, Safari, and Edge have all supported WebP for years, including the alpha channel. Outside browsers it is patchier. Some older desktop image viewers, certain print and prepress workflows, a few legacy content management systems, and older versions of Office or design software still reject WebP or ignore its transparency. If you are handing a file to a system you do not control, PNG remains the safer choice.
Yes, some. This page uses WebP's lossy encoder, which is how it reaches those file sizes — it discards detail the encoder judges least noticeable. At the default quality of 92 the loss is very hard to spot on photos. Flat graphics, screenshots with small text, and hard-edged illustrations show it sooner, since those patterns are exactly what lossy compression handles worst. Lower the quality and the degradation becomes visible as smearing near edges.
You can, and the result will be a valid lossless PNG from that point on, but it will not undo anything. Detail the WebP encoder discarded is gone permanently, so the new PNG simply stores the compressed version's artifacts losslessly — often at a larger file size than the WebP it came from. Converting back is worth doing when you need a lossless base for further editing and want to stop new artifacts accumulating. Keep your original PNGs if you may need them.
No. Decoding and re-encoding both happen inside your browser through the canvas API, so the image data never leaves your device. That has two practical consequences: private screenshots, documents, and personal photos stay on your machine with no trust required, and the ceiling on batch size is your device's memory and CPU rather than an upload limit. Once the page has loaded, the tool keeps working offline.
Yes. Add as many PNG files as you like and they run through the same Quality setting in one pass, then download individually or as a single ZIP. Because one quality value applies across the whole batch, mixed content can come out uneven — a detailed photo and a flat diagram respond very differently to the same number. Spot-check the busiest image and the flattest one before trusting the rest of the set.

Más herramientas de imagen

Explora otras herramientas poderosas para tus necesidades de edición