JPG to PNG: When It Helps, When It Is Pointless, and How to Convert
Converting JPG to PNG does not restore quality that was already lost. Here is what the conversion genuinely buys you, when it is a waste, and how to do it.
Updated August 11, 20265 min read
This conversion is requested constantly and misunderstood almost as often. The belief is that PNG is the higher-quality format, so moving a JPG to PNG upgrades it. It does not. JPG discards detail when it is first saved, and that detail is gone; wrapping the result in a lossless format preserves the damage perfectly rather than repairing it. There are good reasons to convert — they are just not the reason most people have in mind.
What the conversion actually does
JPG is lossy: at save time it analyses the image, throws away detail the eye is unlikely to miss, and stores an approximation. PNG is lossless: it stores every pixel exactly as given. Convert a JPG to PNG and PNG faithfully records the approximation, including every compression artefact the JPG already contains.
The file usually gets larger — often three to five times — because PNG is inefficient at photographic content and because it now has to encode the JPG's blocking artefacts as if they were real detail. You end up with a bigger file that looks identical at best.
When converting is the right call
- 1You are about to add transparency. JPG has no alpha channel. If you are cutting out a background with the background remover, the output must be PNG or WebP — this is the most common legitimate reason.
- 2You are going to edit and re-save repeatedly. Every JPG save re-compresses and loses a little more. Converting to PNG once, then editing in PNG, stops the decay. Convert back to JPG only for the final export.
- 3Something downstream demands PNG. Plenty of app stores, print templates, CMS uploaders and design tools accept only PNG. Compatibility is a perfectly good reason on its own.
- 4The image is a screenshot, logo or diagram that was wrongly saved as JPG. You cannot undo the artefacts, but converting stops further damage and PNG will handle the sharp edges from here on.
- 5You need an exact-pixel copy for comparison. Difference testing and automated visual checks need a format that will not re-approximate the image between runs.
When it is a waste of space
- "To improve quality." There is no quality to improve. The information left the file at the original save.
- For web delivery of photographs. A photo as PNG is several times the bandwidth for no visible gain. Use JPG, or WebP for a third less again.
- To make it print better. Print shops want maximum-quality originals, not a lossless copy of a lossy file. Send the best original you have.
- Because a form said "image file". If it accepts JPG, send JPG — the file will be smaller and upload faster.
If your actual goal is a smaller file rather than a different one, that is a different job entirely: see image file size vs dimensions, which covers which lever actually controls the number.
JPG in, PNG out, in one step — the reverse has its own PNG to JPG page. Conversion happens on your device — nothing is uploaded.
Convert an imageConverting the other way
PNG to JPG is the more frequently useful direction, and it comes with one trap. Transparency does not survive: JPG has no alpha channel, so every transparent pixel is filled — usually with white, sometimes with black. A cut-out logo converted to JPG arrives with a solid box around it.
When transparency is not involved, PNG to JPG is often a large win. A PNG photograph converted to JPG at 85–90% quality is typically a fifth of the size with no visible difference. If you have inherited a folder of PNG photos, that conversion is usually the single biggest storage saving available, and the PNG to JPG converter does it in one step.
If you need transparency *and* a small file, convert to WebP instead. It keeps the alpha channel and lands roughly a quarter below PNG for the same content.
Making PNGs smaller without changing format
Sometimes PNG is genuinely required and the file is simply too big. PNG has more headroom than people expect, because most PNGs are written with settings nobody chose deliberately.
- Reduce the colour palette. A logo with eight colours does not need 24-bit colour. Palette reduction is lossless for flat graphics and can cut the file by 70% or more.
- Strip metadata. Colour profiles, editing history and thumbnails ride along inside PNGs and are often larger than the image data on small icons.
- Cut the dimensions. The same rule as every other format: pixels are what you are paying for.
The PNG compressor reduces the palette to hit a size target — lossless on flat graphics with few colours, but expect banding on photos — and drops metadata along the way. And before you convert anything, it is worth confirming what you actually have — a file named .png is not necessarily a PNG, and the image analyzer reads the real format from the file's own header rather than its name.
Frequently asked questions
Does converting JPG to PNG improve quality?
No. JPG discards detail permanently when it is first saved, and PNG simply stores that already-degraded image losslessly. The result looks identical to the JPG and is usually three to five times larger.
Why is my PNG so much bigger than the JPG?
PNG is lossless and was designed for flat graphics rather than photographs. It has to encode every pixel exactly, including the JPG's compression artefacts. On photographic content that routinely means three to five times the file size.
Can I make a JPG transparent by converting it to PNG?
Converting gives the file an alpha channel, but it does not decide what should be transparent — the image still has its original background. Remove the background first, then save as PNG; the conversion alone changes nothing visually.
Which is better for a website, JPG or PNG?
JPG for photographs, PNG for logos, screenshots and anything with sharp edges or flat colour. WebP beats both for web delivery — roughly a third smaller than JPG on photos and a quarter smaller than PNG on graphics, with transparency support.