PNG is the format everyone exports and the one most websites should stop serving for photographs. It was built for lossless screenshots and sharp edges; it is simply the wrong tool for a 4 MB product photo.
Same job, different trade-offs
| Property | PNG | WebP |
|---|---|---|
| Compression modes | Lossless only | Lossless and lossy |
| Transparency | Yes | Yes |
| Animation | No (APNG is a separate extension) | Yes |
| Photographs | Large files | Much smaller at similar quality |
| Text and hard edges | Crisp | Lossy mode can soften them |
| Browser support | Universal | Current browsers decode it; Safari before 16 cannot encode it |
The table explains the split. PNG never throws away a pixel, which makes it perfect for UI, logos, and screenshots where one wrong pixel is visible. WebP offers a lossy mode for photos, plus a lossless mode that usually beats PNG on size.
What these tools actually produce
- The image format converter writes PNG, JPG, or WebP. It redraws the image on a canvas and encodes at a fixed quality of 0.92 for both JPG and WebP. Transparent areas turn white when the target is JPG.
- PNG to WebP is the same pipeline locked to PNG in, WebP out.
- The image compressor keeps the input format and applies your chosen quality, 1–100 with a default of 80.
Two details worth knowing. The WebP these tools write is a lossy encode at quality 0.92 — the canvas API offers no lossless WebP switch. And on browsers that cannot encode WebP (Safari before 16), the converter removes the WebP option or warns instead of producing a broken file.
The export rule
- Screenshot, logo, icon, chart with thin lines → PNG.
- Photograph, large background, anything with continuous tone → WebP.
- File headed to an inbox where you cannot check the recipient’s browser → PNG or JPG.
Pick by content, not by habit. And do not convert a JPEG to PNG to “improve” it: the lost detail does not come back, the file only gets bigger.