When compression actually helps
File size grows not from a “bad” format but from extra pixels and metadata. A 3840×2160 PNG interface screenshot can easily take 6–8 MB, while the page displays it in a 1200 px block. Reducing width to 1920 px and re-encoding to WebP usually gives 85–95% savings with no visible difference on screen.
The opposite case is a photo already compressed by a messenger. Re-compressing to JPEG adds artefacts and may increase the file. In that case use quality 85–90 or keep the original.
Practical guidance
| Scenario | Format | Width | Quality |
|---|---|---|---|
| Interface screenshot | WebP | 1920 px | 80–85 |
| Article photo | WebP | 1600 px | 78–82 |
| Card preview | WebP | 800 px | 75–80 |
| Image with transparency | PNG | as needed | — |
| Old software and email | JPEG | 1600 px | 82–88 |
What happens to quality
At 78–82% artefacts are almost invisible on photos but noticeable on sharp text edges. Check the result at 100%: open before and after in two tabs and compare contrast areas. If text looks soft, raise quality by 5–10 points; the file size will barely change.