PNG or WebP for screenshots?
Both formats are lossless-capable, both support transparency, and both are supported by every browser that matters. The choice comes down to three things: text edges, file size, and what the receiving platform accepts.
The short answer
| Situation | Use |
|---|---|
| UI screenshot with small text, published on your own site | WebP at quality 90+ |
| Image that will be re-edited or re-compressed by someone else | PNG |
| Image going to a store listing, press kit or print | PNG (or TIFF in print workflows) |
| Top of a page where the first paint matters | WebP, with width and height set |
| Transparent background with a soft shadow | WebP or PNG — test the gradient banding |
| Photograph, not a screenshot | WebP or JPEG |
How each one actually compresses
PNG is lossless by definition and compresses by predicting pixel values from their neighbours — excellent for flat colour and hard edges, which is exactly what a UI is. A clean 1600×900 dashboard PNG typically lands between 250KB and 900KB depending on how much detail and how many subtle gradients it contains.
WebP in lossless mode uses a different prediction scheme and usually lands 20–30% smaller than PNG on interface imagery. In lossy mode at quality 90–95 it typically lands 60–80% smaller than PNG with no difference visible at 100% zoom. The quality setting is where the whole argument lives: at 80, fine text starts to smear; at 92, it does not.
JPEG is the one format to avoid for screenshots. Its compression works on 8×8 blocks, which is the worst possible model for thin, high-contrast text: you get ringing around every glyph, and it gets worse every time the file is re-saved.
Text edges are the real test
Take a screenshot with 12px UI text, export it as PNG, WebP at 92 and JPEG at 90, then zoom to 200% and compare. PNG is exact. WebP at 92 shows a faint softening that disappears at normal viewing size. JPEG at 90 shows coloured fringes around every letter.
If the screenshot is the product — a documentation page someone will read closely — keep the pixels honest. If it is a hero image someone will scroll past, take the 70% saving.
Delivering 2x without breaking layout
Export at twice the display size, then tell the browser how large it actually is:
<img src="dashboard@2x.webp" width="800" height="500" alt="…">
Without the width and height attributes the page reflows as the image loads — that is the layout shift search engines measure. Without a 2x source, the image is upscaled on every retina display, which is the softness people complain about.
A sensible budget
- Hero image: under 200KB.
- In-article screenshot: under 120KB.
- Open Graph card: under 300KB (some scrapers give up beyond that).
- Store listing: follow the store's own limit; usually 1–5MB per image, so PNG is safe.
If a PNG of a screenshot is over 1MB, the image probably contains a photographic background or a very noisy gradient. Exporting that same composition as WebP at 92 will normally bring it under 250KB with no visible change in the interface itself.
Transparency and shadows
Both formats carry an alpha channel, but soft shadows in a wide-radius gradient are where lossy WebP can band. If your export has a 150px blurred shadow on a transparent background, check the result at 100% before publishing; if you see rings, raise the quality or export PNG.
Note that many social platforms flatten transparency onto white or black. If the image is destined for a link preview, a solid background is the safer choice.
What the studio does
Every export is rendered on a canvas at 2x (or 3x with Pro) and encoded by the browser itself — PNG lossless, or WebP with a quality slider defaulting to 92. Nothing is re-encoded twice, nothing is uploaded, and the file you download is exactly what you see in the preview.
Try it on your own screenshot
Free, no sign-up, and the image never leaves your browser.
Open the studio