UtiliKit
Back to blog

PNG to JPG Without Visible Quality Loss: Settings I Use

Published: November 5, 2026 - 6 min read

To convert PNG to JPG without visible quality loss, export at a JPEG quality of 85 to 92% and only do it for photos. At those settings the difference is very hard to see on a phone or laptop screen, and the file is usually several times smaller. For screenshots, text, logos and anything with transparency, JPG is the wrong target, and no quality setting will make it look as clean as the PNG.

That split, photo versus graphic, decides almost everything.

Why PNG to JPG always loses something

PNG is lossless. Every pixel you save comes back exactly the same. JPEG is lossy: it splits the image into 8 by 8 pixel blocks, throws away fine detail the eye is bad at noticing, and usually stores colour at a lower resolution than brightness (chroma subsampling). So a conversion never keeps every pixel. The goal is a result where the loss isn't visible at normal viewing size.

On a photo, that's easy. Photos are full of noise, gradients and soft edges, and JPEG hides its changes inside them.

On a screenshot it's hard. Sharp black text on a flat white background is the worst case for JPEG, because the block artefacts appear right next to the hard edges, as faint grey ringing around letters. Thin red or blue lines are worse still, since colour is stored at lower resolution and those lines go soft first.

Quality settings that work for photos

Here's how I'd think about the quality number for a typical photo, say a 3000 by 2000 pixel shot that someone saved as PNG.

JPEG qualityWhat you'll seeUse it for
95 to 100%no visible change, file much larger than neededarchives you'll edit again
85 to 92%no visible change at normal sizealmost everything
70 to 80%slight softening if you zoom inweb pages, email
below 60%blocky skies, smeared detailtiny previews only

A photo like that as PNG is often somewhere around 8 to 15 MB, because PNG compresses photo noise badly. The same image as a JPG at 90% typically lands around 1 to 3 MB. Those are rough figures, not a promise, since the content of the photo changes everything.

Going from 92% to 100% often doubles the file size for a difference you can't see. That's the setting people pick to be safe, and it's rarely worth it.

Transparency: the white background surprise

JPEG has no alpha channel. A PNG logo with a transparent background has to be flattened onto a solid colour during conversion. In the PNG to JPG converter on UtiliKit that fill is white, which is what you want for most documents and listings.

The catch: if the logo was designed for a dark background (white text, say), it'll be white text on white after conversion. Invisible. Check before you upload it anywhere.

And if you need transparency to survive, don't convert to JPG at all. Keep the PNG, or use WebP, which supports both lossy compression and transparency.

What I'd actually use, depending on the job

For a quick one-off conversion where you don't want to think about settings, the Format Converter saves JPGs at a fixed 92% quality. That sits at the top of the safe range, so the output looks the same as the PNG for photos, and it's still much smaller.

When the file size matters too, I'd use the Image Compressor instead. Set the output to "Convert to JPEG" and move the quality slider, which goes from 5 to 100% in steps of 5. The default is 75%, which is fine for web images, but for "no visible loss" I'd push it to 85 or 90 and compare the before and after at 100% zoom. If you have a hard upload limit like 200 KB, Compress to a File Size picks the quality for you and measures the actual encoded file.

All three run in your browser. The PNG isn't uploaded anywhere, which matters if it's a scan of a document or anything else you wouldn't email to a stranger.

Mistakes that make a JPG look worse than it should

Converting the same image to JPG repeatedly is the big one. Every save at less than 100% throws away a bit more, and the losses stack. If you're going to edit, crop or resize, do it on the PNG, then convert once at the end.

Resizing after conversion is the second. Shrinking a JPG re-encodes it. Resize first with the Image Resizer if you need smaller dimensions, then convert.

Third, judging quality zoomed out. A preview thumbnail hides everything. Open both files at 100% and look at the edges of text, skies and skin, which is where JPEG artefacts show up first.

Fourth, converting screenshots at all. Is the screenshot mostly text and flat colour? Then the PNG is often smaller than you'd expect, sometimes smaller than a high-quality JPG, because PNG compresses flat areas very well. A plain settings page with a white background is the classic case where the PNG can beat a 90% JPG on size and still have sharper text. Not every screenshot behaves like that, but enough do that it's worth checking before you convert.

Metadata, colour and the small print

Because the conversion runs through the browser's canvas, the new JPG is built from the pixels only. Camera data, GPS location and editing history stored in the original file don't come along. For photos you're about to post publicly that's a bonus, since nobody can read where the picture was taken from the file.

Colour is the other quiet one. Most PNGs and almost all web images are sRGB, and they'll look the same after conversion. If a PNG came out of a design tool with a wide-gamut profile attached (Display P3, for example), the colours may shift slightly once that profile is gone. On a product photo for a shop, compare the reds and oranges side by side before you replace the original.

Pixel dimensions don't change at all. A 2400 by 1600 PNG becomes a 2400 by 1600 JPG, so any reduction in file size comes purely from the compression, not from a smaller image.

Keep the PNG.

Seriously: once you've converted, keep the original somewhere until you're sure the JPG works where you need it. Going back from JPG to PNG doesn't restore anything, it just makes a bigger file of the same compressed pixels.

A quick way to decide

Photo with no transparency: convert to JPG at 85 to 92%.

Screenshot, diagram, logo or text: keep it as PNG, or try WebP if you need it smaller.

Anything with transparency you need to keep: PNG or WebP, never JPG.

If it's a photo, drop it into the PNG to JPG converter, open the result at full size next to the original, and you'll know in about ten seconds whether the setting worked.

Frequently asked questions

Does converting PNG to JPG reduce quality?

Technically yes, because JPEG is lossy and PNG is lossless. At 85 to 92% quality the change in a photo is usually invisible at normal viewing size. Screenshots and text show the loss much more clearly.

What happens to a transparent background when I convert PNG to JPG?

JPEG can't store transparency, so the transparent areas are filled with a solid colour. UtiliKit fills them with white. If you need to keep transparency, stay with PNG or use WebP.

What JPG quality should I use for printing?

For print I'd use 92 to 95% and keep the original pixel dimensions. The file is larger, but print shows fine detail more than a screen does, and printers rarely care about a few extra megabytes.

Why is my JPG bigger than the PNG?

That happens with screenshots and graphics that have large flat areas of colour, which PNG compresses very efficiently. For images like that, keeping the PNG or converting to WebP usually gives a smaller and sharper file.

More guides