PNGToolbox

Workflow

WebP to JPG: when the smaller lossy file is the right answer

If a destination refuses WebP and cannot take PNG either, JPG is the universal fallback. The interesting part is choosing a quality setting that does not spend bytes for nothing.

By PNGToolbox Editorial Published 2026-10-22 Last reviewed 2026-10-22 How we test

At a glance

  • JPG has no alpha channel: converting a transparent WebP to JPG flattens it onto a matte colour, usually white.
  • Quality above roughly 90 buys almost nothing visually and multiplies the file: on our photo test, q90 was 2.94x the bytes of q75 while SSIM moved 0.888 to 0.893.
  • At q95 the measured PSNR fell below q85 (38.0 dB versus 38.9 dB) — the encoder was preserving noise rather than detail.
  • JPG remains the most universally accepted image format, which is often the only reason the conversion is necessary.

Why people convert to JPG at all

Not because it is better — WebP is a more modern codec with better compression at comparable quality, and PNG is lossless. People convert to JPG because something downstream refuses anything else: an upload form with a fixed file-type list, an older desktop application, a print shop's workflow, a piece of hardware that reads memory cards, or an email system that renders attachments inconsistently.

In those situations the question is not "is JPG good" but "what is the least damaging JPG I can produce from this file".

The two costs: transparency and quality

Transparency is lost outright. JPEG stores three channels — luminance and two chroma — and has no place to put an alpha value. A transparent WebP converted to JPG is composited onto a matte colour, which most encoders default to white. Semi-transparent edge pixels become opaque blends of the subject and that matte, which is where the famous pale halo around a converted cutout comes from.

If the destination needs the cutout to stay cut out, JPG is the wrong target; PNG or WebP is required. If the destination wants a white background anyway, the flattening is harmless — provided the matte is what you intended.

Quality is a budget you spend. And it is spent unevenly. Measured on a 1600 x 1200 photo-like test image with libjpeg-turbo:

Quality Size vs q75 PSNR SSIM
q60 76.3 KB 0.54x 38.6 dB 0.883
q75 141.2 KB — 38.7 dB 0.888
q85 270.2 KB 1.91x 38.9 dB 0.892
q90 414.7 KB 2.94x 38.8 dB 0.893
q95 952.8 KB 6.75x 38.0 dB 0.877

The useful band for photographs sits between roughly 75 and 85. Below it, artefacts become visible in smooth areas and around edges; above it, the file grows several times over for differences that are hard to demonstrate at normal viewing sizes. The q95 row is the instructive one: more bytes, and both metrics worse, because the encoder faithfully preserved grain.

Content changes the picture as well. The same sweep on a UI screenshot grew from 170.9 KB to 752 KB between q40 and q95 while PSNR stayed flat at 26.7 dB — for text-heavy images, no quality setting makes JPG the right choice.

Working backwards from a size limit

When a form states a byte limit, compute the budget before choosing settings:

bits per pixel = (target bytes x 8) / (width x height)

A 1200 x 900 image at 200 KB is working with about 1.48 bits per pixel — comfortable. The same 200 KB budget across a 4000 x 3000 image is 0.13 bits per pixel, which no JPEG encoder achieves without visible damage. The fix is to reduce the dimensions first, then set quality.

Things to check before and after converting

Colour profiles. A file carrying an embedded profile can look different when the profile is stripped. Compare the original and the export in the same viewer, and keep the profile if the destination supports it.

Orientation metadata. Some pipelines rotate on EXIF orientation and others do not; if the source came from a phone, confirm the exported image is the right way up everywhere it will be displayed.

Progressive encoding. Progressive JPEGs render gradually and can be smaller at equal quality for larger images; they are widely supported, but a few old tools expect baseline. If the output looks wrong in one specific application, that is the setting to try changing.

Naming and extension. Renaming a .webp to .jpg does not convert it, and some systems will still detect the real format. Convert, then save.

A short workflow

  1. Decide whether the destination truly requires JPG; if it accepts WebP or PNG, keep the better format.
  2. If the image has transparency and the destination needs a white background, accept the flattening — and check the edge pixels afterwards.
  3. Crop to the required aspect ratio.
  4. Resize to the pixel dimensions the destination displays, before touching quality.
  5. Export at quality 75-85 for photographs, then check the file against the byte limit.
  6. Inspect at 100% zoom on the busiest area, especially any text or hard-edged shapes.

The converter on this site exports to JPG or PNG from the same source file in one pass, locally in the browser — so you can compare the two outputs side by side against the original before deciding which one to send.

Sources

  • Joint Photographic Experts Group, JPEG overview — https://jpeg.org/jpeg/
  • Quality and size values measured on 22 October 2026 with Pillow 11.0.0 (libjpeg-turbo); raw CSV published at ./assets/bench/study-b-jpeg-quality.csv

Convert WebP files to PNG or JPG — in your browser

Batch conversion, ZIP download, transparency kept. No upload.

Open the converter