PNG to JPG: When & How to Convert

PNG→JPG is the most common image conversion on the web, and the most commonly botched. Done right, it shrinks a 9 MB PNG photo to 1 MB with no visible difference. Done wrong, it turns your transparent logo into a white-boxed mess with fuzzy edges. Here’s how to tell the difference.

When PNG→JPG makes sense

Photographic PNGs. This is the big one. Screenshots of photos, exported camera images saved as PNG “for quality,” WhatsApp images someone re-saved — any PNG whose content is photographic. A 12 MP photo as PNG (~9 MB) becomes ~1.2 MB as JPG quality 85, visually identical. If the PNG contains no transparency and no sharp text, converting is pure win.

Upload forms that reject PNG. Some portals, printers, and older systems accept only JPG. Conversion is mandatory, not optional.

Email attachments. Nobody wants a 15 MB PNG in their inbox. Convert first.

When it DOESN’T make sense

Anything with transparency. JPG has no alpha channel — transparent pixels become a solid color (usually white or black, depending on the converter). A logo with a transparent background becomes a logo in a white box. If transparency matters, do not convert — or flatten onto the intended background color deliberately.

Screenshots of UI and text. JPG’s lossy compression creates fuzzy halos around sharp edges — exactly what text and interface elements are made of. A settings screenshot as JPG looks noticeably worse than the PNG, and often isn’t even much smaller (flat UI compresses well as PNG).

Logos and line art. Same edge-fuzz problem, plus no transparency. Keep PNG (or better: SVG for vector logos, WebP for raster).

Images you’ll edit further. Each JPG save degrades. If this PNG is a working file, keep it PNG until the final export.

The transparency trap (and how to handle it)

The #1 PNG→JPG disaster: converting a transparent PNG without thinking about the background. What happens to transparent pixels:

• Most converters fill with white — fine on white web pages, terrible on dark backgrounds
• Some fill with black — the reverse problem
• Good converters let you choose the matte color

Before converting a transparent PNG, ask: where will this image live? Match the matte to that background. A logo destined for a dark hero section should be flattened on dark, not white. (Or reconsider: if the background might change, keep the PNG.)

Quality settings that work

For photographic content, quality 85 is the honest default — below 80, artifacts creep into skies and gradients; above 90, you’re paying bytes for invisible gains.

The “PNG is higher quality” myth

People save photos as PNG believing it’s “higher quality” than JPG. Technically PNG is lossless — but at quality 85+, JPG’s losses are below the threshold of human perception for photographic content. You’re not preserving visible quality with that 9 MB PNG; you’re preserving invisible data at 7× the bytes. The exception is graphics and text, where PNG’s losslessness is genuinely visible.

Batch workflow

PNG→JPG conversions usually come in batches — a folder of exports, a screenshot archive. Before running the batch:

1. Sort out the transparent ones. Move any transparency-dependent images aside first — they need individual decisions.
2. Spot-check 3–5 conversions at 100% zoom, especially any containing text.
3. Convert into a new folder, keep the PNG originals.
4. Use consistent quality across the batch.

A better alternative for the web

If the destination is a website, consider skipping JPG entirely: WebP beats JPG at photographic content (~30% smaller) and handles transparency properly. Converting PNG→WebP instead of PNG→JPG gets you the small files without the transparency trap. Our optimizer does this with fallback markup included.

Practical next steps

• Convert PNG to JPG in your browser — batch supported, matte color control, files never uploaded.
• Going to the web instead? Optimize to WebP and keep transparency.
• Still unsure which format? Read JPG vs PNG for the full decision framework.