Screenshots: should you save PNG or JPG?

What a screenshot is made of

Most screenshots are not photographs. They are made of solid backgrounds, straight edges, small text, icons, and thin one-pixel borders. That structure is very different from the smooth, continuous detail found in a photo, and the two kinds of content behave in opposite ways when compressed.

This is the single most useful idea for choosing a screenshot format: the format that is best for photographs is the worst for interface graphics, and the other way around.

Why PNG suits most screenshots

Screenshots are full of text, buttons, and flat color — exactly the content JPG compression handles worst. PNG stores these areas losslessly, so text stays crisp and edges stay clean, with no fuzzy halo around letters.

PNG also supports full transparency, which matters when you capture a window with rounded corners or a region selection that should sit on a colored background. JPG would force a solid fill and leave visible corners.

That is why PNG is the default choice for documentation, tutorials, bug reports, and UI work, where clarity of text is the whole point.

How JPG hurts text

JPG divides an image into small blocks and adjusts them to save space. On a photograph this is invisible. On text, it produces ringing — faint ripples and gray speckles around letters — and on sharp edges it produces soft, slightly colored halos.

The damage is subtle at high quality, but even a mild quality setting can make small text tiring to read and can blur fine lines on charts and tables. If legibility matters, this is the wrong trade.

When JPG is the better trade

A screenshot of a photograph, a video frame, a gradient-heavy illustration, or a photo editing workspace compresses well as JPG. The smooth areas hide the artifacts, and the file shrinks considerably compared to PNG.

In practice, the decision follows the content: if the screenshot is mostly smooth image data, JPG wins on size; if it is mostly text and flat interface, PNG wins on quality.

High-density and retina screenshots

Screenshots taken on modern high-density displays often have twice or three times the pixel dimensions they need. A window captured at 2560 pixels wide but displayed at 1280 is carrying four times the necessary pixels.

Resizing a high-density screenshot down to its intended display size is the most effective way to shrink it, and it often makes text slightly crisper after downscaling. Do the resize before choosing a format, then compare the result.

Meeting attachment size limits

If a support form or email system limits attachment size, converting a large screenshot to JPG can bring it under the limit quickly. Start by resizing rather than by lowering quality, because a smaller dimension reduces size far more aggressively than compression alone.

When a screenshot must stay perfectly legible but is too large, splitting it into two or three images is often better than compressing it into a blur.

A practical workflow

Save UI and text screenshots as PNG. If the file is still too large, resize it to the width it will actually be displayed at rather than compressing harder. For screenshots that need to be small and still contain text, a high-quality WEBP is usually the best compromise.

Convert photo-like screen captures to JPG when the source makes it worthwhile, and compare both outputs at 100 percent zoom before choosing. For anything that will be edited later — annotations, redactions, crops — keep the PNG master as well.

Choosing a screenshot format in one line

Text and interface: PNG, or high-quality WEBP if size is critical. Photographs and video frames: JPG. Screenshots that need transparency: PNG or WEBP, never JPG. When in doubt, compare the two at 100 percent zoom and let the visible result decide.