PNG to WebP Converter

Batch-convert PNG to WebP with transparency, quality and size controls, and ZIP download.

Choose up to 20 PNG images or drop them here

10 MiB per image · 50 MiB per batch · 12 million pixels per image. Files stay in this browser.

Maximum edge

Quality (1–100)

WebP quality follows your browser encoder; some browsers choose lossless at 100. Transparency is retained; a smaller file is not guaranteed. Images are never enlarged. Animated PNG and WebP are rejected; metadata is not retained.

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

Encode PNG graphics as WebP while retaining transparency, with optional proportional downsizing and separate or ZIP downloads.

How to use it

1Choose PNG images, then set the maximum edge and WebP quality.
2Convert and inspect transparency, fine edges and actual file sizes.
3Download successful WebP images individually or package them in a ZIP.

Example

Input: 1,600 × 800 transparent PNG; edge 640
Output: 640 × 320 WebP with alpha

Static, lossy output; the preview checkerboard is not part of the image.

What happens to your data

PNG decoding and alpha-preserving canvas export occur in this open page. The selected graphics are not uploaded, and a downloaded ZIP is assembled from the local WebP results.

Last updated October 2026

Convert PNG graphics into WebP while retaining their transparency. Choose an output quality, keep the original dimensions or reduce the maximum edge, and compare the result before downloading a single file or batch ZIP. The checkerboard behind a preview helps reveal transparent areas; it is not painted into the saved image.

PNG is lossless; WebP encoding here follows the browser and selected quality. That trade can be useful for large illustrated assets, but it deserves a close look on text, icons, diagrams and sharp color boundaries. If exact source pixels matter, keep the PNG. A WebP at quality 100 is not a promise of lossless conversion.

How it works

The converter reads the file signature and dimensions, then asks the browser to decode the image. A JPEG renamed to .png is rejected with a format-specific message. Each PNG is limited to 10 MiB, 12 million pixels and 8,192 pixels per side. Batches allow up to 20 files within 50 MiB. The output budget is 60 MiB, and each failure is named so that a partly successful batch is not presented as complete.

The canvas starts transparent. Because WebP supports an alpha channel, there is no forced white or black background. Transparent and partly transparent areas are kept through drawing and encoding, subject to the browser's decoding and resampling. When reducing dimensions, edge pixels are resampled as well, so inspect fine translucent outlines against both light and dark backgrounds in your destination.

Original dimensions avoids resizing. The maximum-edge control scales down proportionally and never enlarges an already smaller graphic. A 1,600 × 800 PNG becomes a 640 × 320 WebP at a 640-pixel edge. Quality changes compression, not dimensions, and is not an exact byte-size request. Browser encoders can produce different files at the same setting; compare the actual size reported for your image.

Animated PNG and WebP are rejected before browser decoding because a small compressed file can contain many large frames. The converter accepts still images only and does not retain EXIF or profile metadata. Use a dedicated animation workflow if motion is part of the asset. A browser unable to encode WebP produces a visible error; a fallback PNG is never mislabeled as WebP.

Convert processes files sequentially, and Prepare ZIP packages successful results under unique names. Replacing the input, changing settings or choosing Clear removes obsolete outputs. Cancel abandons the current conversion or package result. Everything is kept in the current page until you download it; there is no automatic saved library. File decoding, conversion and archive generation do not upload the image contents.

Worked example: Resize a transparent graphic

Input: 1,600 × 800 transparent PNG; maximum edge 640
Result: 640 × 320 WebP with transparency

The colors use lossy encoding; no background color is added.

Common use cases

Preparing transparent website illustrations for WebP delivery
Reducing the pixel dimensions of oversized PNG assets
Comparing a PNG graphic with a smaller lossy alternative
Packaging a set of transparent WebP assets for a developer

Frequently asked questions

Will PNG to WebP preserve transparency?＋

Yes, the transparent canvas is exported to WebP without adding a background. The checkerboard is only a preview aid. If the destination shows black or white behind the image, check whether that destination supports alpha in WebP.

Is the output lossless WebP?＋

At the default quality 90, expect lossy WebP. Chromium switches to lossless encoding at 100, but that is browser-specific rather than a portable control. Keep the PNG when exact pixel preservation is required, and remember that resizing itself changes pixels.

Does it keep APNG animation?＋

No. Animated PNG is rejected before browser decoding. Export a still PNG first, or use a dedicated animation converter when you need to preserve motion and frame timing.

Why can WebP be larger than PNG?＋

PNG can be very efficient for small flat-color graphics. WebP overhead, the quality setting and the source's content can outweigh compression savings. The tool displays measured sizes so you can keep whichever format is appropriate.

Can I resize without cropping my logo?＋

Yes. Maximum edge keeps the complete image and its aspect ratio, with the shorter side rounded to a whole pixel. It never crops or stretches the canvas and never enlarges smaller inputs.

Why was one file missing from my ZIP?＋

Only successfully converted images enter the archive. A named error appears for a corrupt file, wrong format, source limit or output-budget failure. Reduce the workload or correct that input before converting it again.