Convert PNG to WebP

PNG is the format designers export from and WebP is the format websites should serve. Converting cuts file size by two thirds or more while keeping transparency intact, and every current browser can display the result. The conversion runs on your device, so nothing is uploaded.

How to convert PNG to WebP

  1. Drop one or many PNG images into the tool below.
  2. The output format is already set to WebP. Adjust the quality if you like.
  3. Click run to convert.
  4. Download each WebP, or grab them all as a ZIP.

Why PNG files are so large

PNG is lossless. Every pixel is stored exactly, which is what makes it perfect for logos, screenshots and interface graphics, and also why a PNG photograph can be 10 to 20 times bigger than the same picture as a JPG. Design tools default to PNG export because it is safe, not because it is efficient. The result is that a lot of websites are serving multi-megabyte PNGs for images that could be a few hundred kilobytes.

What WebP does differently

WebP was designed by Google specifically for the web. It has two modes. Lossy WebP uses prediction and transform coding similar to video compression and typically produces files 25 to 35% smaller than a JPG at the same visual quality, and far smaller than a PNG. Lossless WebP stores pixels exactly like PNG does but with a smarter compression scheme, usually 20 to 30% smaller than an optimised PNG. Both modes support transparency, which is the main reason PNG to WebP is such a common conversion: it is the first widely supported format that lets you keep an alpha channel without paying the PNG size penalty.

Picking a quality setting

Source PNG containsSuggested WebP qualityResult
Logo, icon, flat illustration90 to 100Crisp edges preserved, still 50%+ smaller than PNG
Screenshot with text85 to 95Text stays readable, typically 60 to 70% smaller
Photo or rendered 3D image75 to 85Visually identical at normal size, 80 to 90% smaller
Transparent product cut-out85 to 90Edges stay clean, alpha channel preserved

Where to use the WebP

Serve WebP anywhere a browser is the viewer: your website, web app, email templates that target modern clients, and image CDNs. WordPress, Shopify, Webflow, Squarespace and Wix all accept WebP uploads today. If you need to support a legacy viewer at the same time, the standard approach is the HTML <picture> element with a WebP source first and a PNG or JPG fallback.

Do not convert to WebP for print handoff, for archiving master artwork, or for sending to a client who will open the file in an older version of Photoshop or Illustrator. Keep the PNG master and treat the WebP as a delivery format.

Batch conversion

An entire folder of exported PNG assets can be dropped in at once. Each is converted with the same quality setting and the results download as a single ZIP with the original file names and a .webp extension, so swapping them into a project is a find-and-replace on the extension.

Frequently asked questions

Does WebP keep the transparent background from my PNG?

Yes. WebP supports a full 8-bit alpha channel, so soft edges, drop shadows and semi-transparent areas come across exactly as they were in the PNG.

Should I use lossless or lossy WebP?

For logos, icons and screenshots with sharp text, use a high quality setting so the result stays crisp. For photos exported as PNG, quality 80 to 85 gives a huge saving with no visible loss.

Which browsers and apps open WebP?

Chrome, Edge, Firefox, Safari (since version 14) and every current mobile browser display WebP. Windows Photos and macOS Preview open it. Some older desktop software and email clients do not, so keep a PNG or JPG for those.

Why is my WebP sometimes bigger than the PNG?

Tiny images with very few colours, such as a 32 pixel icon, can already be near their minimum size as PNG. WebP shines on anything larger than a couple of hundred pixels.

Your files never leave your device

Every tool on Squishly Tools is 100% free and runs entirely inside your browser. Your images and documents are processed on your own computer and are never uploaded to a server. There are no accounts, no watermarks and no catch.