PNG to WebP

1. Add your PNG files. Drag them in or browse for them. This page accepts files ending in .png only, and a run holds up to 10 of them.
2. Choose Quality before you convert. Output format is already WebP. Quality takes a number from 50 to 100 and starts at 85. The PNG is exact and the WebP will not be, so go higher for screenshots, text and sharp-edged artwork, and lower for photographs.
3. Ignore Background for transparency. WebP keeps see-through areas, so the white or black choice is never applied to this output.
4. Select Convert to WebP. Files upload to private storage, and our servers convert them. The page names the current stage and counts finished images as they complete.
5. Sign in and compare. Pick Google or an emailed code; the account is free and has no password. Each result row shows its type and size, so you can weigh it against your PNG before you download or save it.

A PNG stores every pixel exactly. The WebP that Docubox writes is lossy, so the new file is a close copy, not an exact one. The payoff is often a much smaller file, which matters when a page has to show large images.

• Good candidates: photographs or big illustrations that someone saved as PNG, wide banner images, and product shots with a transparent background for a web page.
• Weaker candidates: screenshots with small text, pixel art and crisp logos in flat colors. A PNG can already be compact for these, and lossy compression may add fuzz around the edges. Try a high Quality and compare, or stay with PNG.
• Keep the PNG as your master. Treat the WebP as a delivery copy. Turning it back into a PNG does not bring the exact pixels back.
• Compare at full size. View the WebP at 100 percent zoom next to the PNG. Differences in small text and thin lines show up there first, long before they are visible when the picture is scaled down.
• Think about the destination. Current browsers show WebP, but design tools, print workflows and older apps may not accept it.

• It is lossy at every setting. Docubox has no lossless WebP option, and Quality 100 still loses some information.
• Very tall or wide images can fail. WebP cannot store an image more than 16,383 pixels on either side. A long full-page screenshot over that size stops the run with a message explaining the limit, even though it is within the 40-megapixel limit. Shrink it first with Resize image, or keep it as a PNG.
• Transparency stays. Fully and partly transparent pixels are kept, so soft shadows and anti-aliased edges survive the trip.
• Small palette PNGs can grow. An icon or simple graphic stored with a limited palette is expanded to full color for WebP, and the result may end up larger than the original. Check the size in the result list.
• 16-bit grayscale is reduced to 8 bits. A grayscale PNG with 16 bits per pixel is saved at 8 bits, and the result page notes it. Grayscale pictures also come out as ordinary color WebP files.
• Animated PNG gives one frame. The first frame becomes the WebP, and a note on the result page says so.
• Extras are not copied. Text chunks and other metadata inside the PNG are left behind, and a color profile that matches the picture is kept. A rotation flag, if there is one, is applied to the pixels.
• Names and runs. banner.png comes out as banner.webp, one file per image and no ZIP. If any one image is invalid or over the pixel limit, the run produces nothing.
• Limits. One run takes up to 10 PNG files totaling no more than 25 MB, and each image may be up to 40 megapixels. Pro, at $9.99 a month, helps people who convert often and keep many files, and does not enlarge these limits.

To send a WebP back the other way, WebP to PNG writes a PNG with transparency intact. If the WebP is still larger than you want, Resize image lowers the pixel dimensions, and the full Convert image tool can write a JPEG instead.