Happy Time

Why your PNG turns blurry after converting to JPG (and it is rarely the format)

3 min read

Blurry edges, fuzzy text and white boxes where transparency used to be are three different problems. A practical breakdown of resampling, chroma subsampling and quality settings for screenshots, photos and images with alpha.

Three different symptoms people call the same thing

People say "it got blurry" about three unrelated things: soft edges (the image was resampled to a different pixel size), dirty detail (lossy compression threw away colour resolution), and solid white or black blocks where the background used to be transparent (the alpha channel was dropped). Each has a different fix, so identify the symptom before touching any setting.

The test is to compare at 100% zoom, side by side. If the whole frame looks slightly smeared, the dimensions changed. If only text and line art grow a halo of coloured speckles, that is compression. If the background colour is simply gone, that is alpha.

Why JPEG damages detail: chroma subsampling

Human vision resolves brightness far better than colour, so JPEG splits an image into luma (Y) and two chroma channels, then allows chroma to be stored at lower resolution. The common 4:2:0 setting keeps colour at a quarter of the luma resolution. Photos hide this well because they have few sharp coloured edges. Screenshots, tables and UI mockups are nothing but sharp artificial edges, so subsampling shows up immediately as coloured fringing.

That is why the same conversion looks fine on a photo but makes black text on white look fuzzy: the glyph edge is the steepest transition the chroma channel has to carry.

Where the transparent background went

JPEG has no alpha channel: a pixel is three numbers and nothing else. The converter has to paint transparent pixels some colour, and almost every implementation picks white (a few pick black). Nothing is broken; information that the format cannot represent was dropped.

If transparency matters, do not convert to JPG. Use WebP, which typically lands 25 to 35 percent smaller than JPG at the same visual quality and keeps the alpha channel. That is also why the recommended output in our image tool is WebP, not JPG.

Pick settings by material, not by feel

These three rules cover almost every case and can be applied as-is:

  • Photos (people, landscapes, product shots): JPG at quality 80 to 85. Higher settings cost multiples of the file size for detail the eye cannot resolve.
  • Screenshots, tables, UI mockups, posters with text: skip JPG entirely. Use lossless PNG or WebP, or WebP at quality 90 or above. Text edges are what JPEG is worst at.
  • Anything with a transparent background (logos, cut-out product images): WebP or PNG, never JPG.

Never re-compress a JPEG

Lossy damage accumulates. JPG to JPG to JPG cuts into data that was already damaged, and by the third generation the blocking is impossible to ignore. If a JPEG is all you have, resize it once and write the result directly; do not "convert to PNG first, then back to JPG".

The same applies to images saved from chat apps or social platforms: they have usually been through at least one round of compression already. Re-encoding one does not restore detail, it just makes the existing artefacts more visible.

Common questions

Why did the JPG end up larger than the PNG?
Two reasons. Quality set too high (above about 95, JPEG can bloat on noisy images), or the source is low-entropy — large flat areas, simple shapes, UI panels — where PNG run-length coding is extremely efficient and JPEG loses. Those images should not be converted at all.
Can I get the transparency back after converting to JPG?
No. The alpha data was discarded during encoding, and no algorithm can recover which pixels were transparent. Re-export from the original file if you still have it; otherwise the cut-out has to be redone by hand.
Is quality 100 lossless?
No. The quality knob only scales the quantisation step. Chroma subsampling and the DCT transform still discard information. Quality 100 just makes the error tiny, at several times the file size of quality 85. For genuinely lossless output, use PNG or lossless WebP.

Read next

Why your PNG turns blurry after converting to JPG (and it is rarely the format) · Happy Time