Transparent logo for a website header
A 900KB PNG logo with an alpha channel typically converts to a WebP in the tens of kilobytes with the transparency intact. This is the case where PNG to JPG would have forced a white box behind the mark.
Browser-local tool
Use PNG to WebP
Your image is decoded and re-encoded on this device. No upload request is made.
WebP preserves transparent pixels. Maximum quality minimizes further loss, but browser encoders do not guarantee mathematically lossless WebP.
Explore image tools
Find related browser-local tools for nearby tasks without starting another search.
Browse all image toolsAbout PNG to WebP
PNG to WebP is the conversion where the numbers get dramatic, and it is the one that solves a problem PNG to JPG cannot. WebP carries a full alpha channel, so a logo with a transparent background stays transparent instead of being flattened onto white. Meanwhile PNG's lossless deflate compression is poorly suited to anything with gradients or photographic content, and files of several megabytes are routine; the same image through WebP often lands at a fraction of that. The catch is that the saving comes from lossy encoding, and lossy encoding is exactly wrong for some of the material people keep as PNG in the first place. Knowing which of your PNGs is which is the whole skill here, and this page lays out the distinction.
Shape and export choices
- The PNG is decoded with its alpha channel intact. Nothing is composited onto a background colour, which is the step that makes the JPG route destructive for transparent artwork.
- A canvas is created with an alpha-enabled context at the source dimensions, and the decoded bitmap is drawn onto it unmodified.
- Encoding runs through the browser's lossy WebP encoder at a high quality setting. Lossy WebP supports alpha, so partially transparent edge pixels on a rounded logo survive with their transparency values.
- Both the original and resulting byte counts are shown. On graphics with large flat areas the reduction is frequently substantial, and on gradients it can be an order of magnitude.
- The output is a single still image. Ancillary PNG chunks such as embedded text, creation software tags, and colour profile data are not carried across.
Good fits for PNG to WebP
A screenshot you were about to attach
Check what is in it first. A screenshot of a photograph or a design mockup converts well. A screenshot of a terminal, a spreadsheet, or a document is text on flat colour and should stay PNG, or be converted with a lossless tool instead.
Check the image before download
- PNG is lossless and this output is not. Pixel-exact material - UI mockups being compared to a reference, screenshots of code or spreadsheets, pixel art, diagrams with one-pixel lines - will pick up soft edges. Keep the PNG for those.
- Text rendered in an image is the most common failure. Small type against a flat background develops visible fringing at lossy quality settings. If your PNG is essentially a screenshot of words, this is the wrong conversion.
- APNG animation is not preserved. An animated PNG converts to a single still frame; the browser encoder writes one image, not an animated WebP sequence.
- Alpha survives but is itself compressed. Very fine semi-transparent detail, such as a soft drop shadow at low opacity, can band slightly. Inspect the edges against a dark background, where alpha artifacts are easiest to spot.
- Indexed-colour PNGs that are already tiny, such as small flat icons, may convert to a larger WebP. Below a few kilobytes the format overheads matter more than the compression.
Questions about PNG to WebP
Does transparency survive?
Yes. WebP has a real alpha channel, which is the main reason to choose it over JPG for logos, icons, and cut-out product images.
Why is the reduction so much bigger than JPG to WebP?
Because you are switching from lossless to lossy compression at the same time as switching format. A JPG was already lossy, so only the coding efficiency improves; a PNG was storing every pixel exactly.
Is this lossless WebP?
No, it is lossy WebP, which is where the size advantage comes from. If you need lossless, keeping the PNG is usually the simpler answer.
Can I convert back to PNG later?
You can produce a PNG from the WebP, but it will not restore the discarded detail - it will just store the lossy result losslessly, at a larger size. Archive the original PNG.
Does the file leave my computer?
No. This page decodes the PNG and encodes the WebP locally in your browser. It does not send the selected image in a network request.
Related tools
Background Remover
Remove an image background locally and download a transparent PNG. The portrait-matting model runs on your device; your photo is never uploaded.
JPG to WebP
Re-encode a JPG photo as WebP in your browser to cut page weight. Compare the before and after byte counts before you download.
WebP to PNG
Convert a WebP file to PNG in your browser and keep the transparent background that a JPG conversion would destroy.
Compress PNG to 100KB
Get a PNG under 100KB in your browser. PNG has no quality dial, so the size is reached by reducing pixel dimensions - shown plainly, with nothing uploaded.
GIF to WebP
Convert a GIF to WebP in your browser. Keeps transparency and produces a much smaller file for web use.
BMP to WebP
Convert BMP to WebP in your browser for the smallest file of the three options, with transparency preserved.
ICO to WebP
Convert an ICO icon to WebP in your browser. Keeps transparency and produces a smaller file than PNG.