Images TOOL

PNG to WebP

Move PNG images into WebP without leaving your browser. PNG is excellent for screenshots and graphics but heavy on disk; WebP keeps transparency and usually lands at a fraction of the size, which matters when a page carries a dozen of them.

Processed locally in your browser — your file is never uploaded

IMAGEPNG to WebP
Processed locally
Drop your JPG files hereor choose files from your device.jpg · .jpeg · .png · .webp · .avif · .gif · .bmp · .svg · .ico · .heic · .heif · up to 100 MB per file · up to 20 filesGenerated in your browser. Nothing is downloaded.
%

Set higher than for photographs. Flat areas compress well in WebP, and a higher quality keeps small text and thin lines crisp.

Add 1 more file to continue.Files stay on this device. Nothing is uploaded.

How png to webp works

  1. Add your PNG filesDrop in your screenshots, diagrams or cut-outs. Furtu checks the PNG file signature so a renamed file is caught early.
  2. Set the qualityStart at 90%. WebP handles flat graphics well, so a higher quality costs little in file size compared with a photograph.
  3. Download the WebP filesEach image is re-encoded in your browser with transparency preserved, and the size saving is shown for every file.

What you get

Convert PNG screenshots, diagrams and cut-outs to a much lighter WebP. Everything happens inside this page: the file is read by your browser, transformed in memory and handed straight back to you as a download. There is no upload queue, no waiting for a server, and nothing left behind when you close the tab.

Supported formats

Furtu accepts .jpg, .jpeg, .png, .webp, .avif, .gif, .bmp, .svg, .ico, .heic, .heif files up to 100 MB each, and processes up to 20 files in one run.

  • Every file is checked against its real file signature, not just its name, so a renamed or corrupt file is rejected with an explanation instead of failing halfway through.
  • Files over the limit are refused up front rather than after a long wait.

Limitations, stated up front

  • The conversion is lossy. The browser does not expose a lossless WebP encoder, so the pixels are recompressed at your chosen quality.
  • Text in a screenshot can soften slightly at low quality. If the text must stay razor sharp, use 90–100% or keep the PNG.
  • Animated GIFs and SVGs are rejected, because a canvas cannot preserve animation or re-encode vector art without rasterising it.
  • Furtu does not resize in this step. If the file is also too large in pixels, run “Resize Image” first.

Frequently asked questions

Does PNG to WebP keep transparency?

Yes. WebP supports an alpha channel, so a logo or cut-out with a transparent background converts cleanly. Converting to JPG would flatten that transparency onto white, which is why it is not the right target here.

Are PNG files uploaded?

No. Everything happens in your browser, using the image codecs already present in it. Nothing is sent to a server, so a screenshot of an unreleased design or a private document is not exposed to anyone else.

How much smaller will a PNG become?

A lot, usually. Flat areas and repeated colours — exactly what a screenshot or a diagram is made of — are handled far more efficiently by WebP. Screenshots commonly drop by 60–90%. A photographic PNG, which is already a poor fit for its own format, may save less.

Is the converted WebP lossless?

No. Browsers do not expose a lossless WebP encoder, so the conversion applies the quality setting you choose. At 90% or above, artefacts on flat graphics are very hard to see; the pixels are nevertheless recompressed rather than copied.

Should I keep the PNG instead?

If the image is a logo, a diagram or an illustration you will edit again, keeping the PNG is reasonable. For anything served to a page — screenshots, thumbnails, decorative graphics — WebP at the same quality is the better file.