Image Tools·4 min read

When to Convert PNG to JPG: A Practical Size Guide

The math on a screenshot archive is brutal. Two hundred full-screen PNG captures at 3 MB apiece is 600 MB of documentation that would occupy well under 60 MB as JPGs, with no reader noticing the difference. Attachment limits make the case even harder to ignore, since a 25 MB email cap fits maybe eight raw captures. This guide covers when to convert png to jpg, when to leave files alone, and precisely what the alpha channel goes through during the trip, because transparency is the one thing this conversion destroys.

Open the tool All insights

Where PNG bloat hides: screenshots, docs, and email attachments

The problem, quantified.

Screen capture tools default to PNG for a good reason: pixel-perfect text. But documentation lives a long life. A how-to guide with thirty embedded captures becomes a 90 MB Word file, a support ticket with three attachments bounces from the mail server, and a wiki grinds under image weight. None of those readers need lossless pixels; they need to see roughly what your screen showed.

That's the honest framing for this conversion. You're trading a quality margin nobody will inspect for an 80 to 95 percent size cut that everybody will feel.

What happens to transparency when PNG meets JPG

The alpha channel, in proper depth.

A PNG pixel carries four values: red, green, blue, and alpha, each typically 8 bits. Alpha runs from 0, fully invisible, to 255, fully solid, and the in-between values are what make anti-aliased logo edges and soft shadows look smooth over any background. JPG stores color in three channels only, so the question of what happens to transparency has a blunt answer: it's discarded entirely.

The converter handles this by compositing every pixel onto a white backdrop before encoding, using the alpha value as the mix ratio. A shadow at 30 percent opacity becomes a light gray smear on white. This looks fine when the image was destined for a white page, and terrible when someone later places the JPG on a dark slide, where the baked-in white box glows around the artwork. If any part of your image is see-through on purpose, this is the wrong conversion.

When to convert PNG to JPG, and when to hold off

A decision list you can skim.

Convert when the image is photographic or screenshot content headed for viewing, not editing:

Convert: screenshot sets for tickets, wikis, and manuals, where size beats pixel perfection.
Convert: photos a design tool exported as PNG by default, which are carrying pointless weight.
Convert: attachment batches bumping against email or upload limits.
Hold off: logos, icons, or anything with transparent regions you intend to keep.
Hold off: images facing more editing rounds, since each JPG save compounds the loss.

Worked example: a 2.9 MB PNG capture as a JPG

Presets compared on one real file.

Input: dashboard.png, a 2560 by 1440 screen capture weighing 2.9 MB. At the High preset, 92 percent, the output dashboard.jpg lands at 310 KB with text edges still clean under close inspection. Medium, 75 percent, produces 148 KB with faint softness around 11-pixel fonts. Low, 50 percent, gets to 89 KB but the interface chrome visibly smudges.

That's a 90 percent saving at High before any real compromise appears, which is why High is the sensible default for anything containing text.

Quality settings for JPG output that keep text readable

Where the artifacts live.

JPG artifacts concentrate around sharp transitions, and nothing is sharper than black text on a light panel. The quality settings for jpg exports in the converter run from 10 to 100 percent via the Advanced fine-tune slider, with the three presets covering the useful range. Above roughly 90, artifacts near text are effectively invisible. Between 70 and 85, photos stay excellent but small fonts pick up a halo. Below 60, block boundaries appear in flat areas.

For mixed batches, screenshots plus photos, run two passes at different presets rather than compromising on one middle number for everything.

Mistakes that ruin a PNG to JPG batch

Learned the hard way by others.

The recurring failures are process errors more than tool errors:

Deleting the PNG originals immediately. The conversion is one-way; keep sources until the JPGs are verified.
Running logos with transparency through the batch and shipping white-boxed artwork to a client.
Choosing Low for a documentation set, then re-capturing every screen when reviewers complain.
Converting the same file repeatedly across edit cycles, stacking generation loss each time.

Tips before you shrink a PNG archive into JPG

Two minutes of prep.

Sort transparent images out of the batch first; searching your set for logos and icons takes a minute and prevents the classic white-background surprise. Then run a three-file test batch at your chosen preset and zoom to 200 percent on the smallest text before committing the full archive. The before and after size readout in the tool tells you the exact savings, so you can judge whether Medium buys enough over High to justify the softness.

PNG to JPG or a different tool entirely?

Match the tool to the goal.

If you want smaller files but must keep transparency, PNG to WEBP delivers compression with the alpha channel intact. If the format needs to stay PNG, the Image Compressor squeezes it without conversion. Oversized dimensions, not format, are sometimes the real weight problem, and the Image Resizer fixes that directly. And when the destination is a document rather than a folder, PNG to PDF or Image to PDF bundles captures into something a reviewer can page through.

Try it now

Open PNG to JPG

The tool is one click away. No sign up, no upload, no payment.

Open PNG to JPG

Write a review