How to Convert PNG to JPG (Without Losing Quality)
By Bruce Shang
August 14, 2026· Updated on Sep 6, 2026· 6 min read
A screenshot, a scan, or an exported design arrives as a 15 MB PNG. You need to email it, upload it, or put it on a website, and suddenly the file is in the way. Converting PNG to JPG is the classic fix, but there are two rules you should know first.
When PNG → JPG makes sense
- Photos, JPG shrinks photo files dramatically with no visible loss at sensible quality
- Web uploads, most sites compress anyway; arrive small instead
- Email attachments, stay under the size limits
- Long-term storage of large photo collections
When it doesn't
- Screenshots with text, JPG artifacts make sharp text look fuzzy; keep PNG
- Graphics with transparency, see below
- Design masters, never convert the file you'll edit again
The transparency problem (read this first)
JPG doesn't support transparency. When you convert a PNG that has transparent areas, those areas must become something:
- White background, the safe default for photos and documents
- Solid color, matches your design or webpage background
If the image relies on transparency (logos, icons, cutouts), converting to JPG ruins it. Convert to WebP instead, or keep PNG. See WebP vs PNG for the full comparison.
Step-by-step: convert PNG to JPG with SlimImg
The Image Converter does it in your browser:
- Open the converter
- Upload one or more PNG files
- Choose JPG as the output format
- Set quality to 85–90 for photos
- Download the JPGs
No uploads, no account, no watermarks.
Keeping quality: the settings that matter
- Quality 85–90, invisible difference from the PNG for photos, 60–80% smaller
- Quality 100, rarely worth it; the file grows a lot for detail nobody sees
- Resize first, if the image is larger than you'll display it, resize before converting (see how to resize for email)
Common mistakes
- Converting screenshots, text gets mangled by JPG compression; keep PNG
- Ignoring transparency, logos come out with ugly white boxes
- Converting masters, you lose the editable original; keep the PNG
- Compressing twice, convert once, then compress the JPG once; don't re-save repeatedly
A worked example: what "60–85% smaller" means
Numbers make the decision concrete. Consider a 3000 × 2000 px photo stored as PNG:
| Format | File size | Note |
|---|---|---|
| PNG (lossless) | 9.8 MB | Exact pixels |
| JPG quality 90 | 1.9 MB | Difference from PNG imperceptible in print |
| JPG quality 82 | 1.1 MB | Difference imperceptible on screen |
| WebP quality 75 | 700 KB | Smaller still, needs modern support |
For the same photo you can ship 1.1 MB instead of 9.8 MB, an 89% reduction, and no viewer will spot the difference on a screen. The trade isn't "quality vs size," it's "lossless storage vs file you can actually send."
Choosing what the transparency becomes
When a PNG has transparent areas, the converter has to invent pixels for them. Choose deliberately:
- White, right for photos and documents being emailed or printed. It's what paper looks like.
- Your page's background color, right for web graphics, so a logo blends into the site instead of carrying a white box.
- Black, right for screenshots that will be viewed on dark UIs.
Rule: pick the color the image will usually sit on. If you're not sure, white is the safest default, but if the image is a logo on a dark website, a white box is the classic "why did this get rejected" mistake.
Screenshots: the exception you'll hit constantly
The most common PNG→JPG request is a screenshot, and it's usually the wrong one:
| Image type | PNG → JPG? | Why |
|---|---|---|
| Photo | Yes | Big savings, invisible loss |
| Screenshot of text/UI | No | JPG artifacts blur glyph edges and antialiasing |
| Graph/chart with thin lines | No | Lines get mottled and unclear |
| Scan of a document | Borderline | Readable, but text edges soften, judge it yourself |
| Photo embedded in a document | Yes | Photos compress fine inside JPG |
The quick test: if the image is mostly words, lines, or flat color, keep it PNG. If it's mostly gradients and scene detail, convert.
Batch workflow with sane settings
For a folder of photos, convert the whole batch in one pass rather than file by file:
- Drop all the PNGs into the Image Converter
- Set output to JPG, quality 85
- Check two or three representative files, a bright one and a dark one, not just the first in the list
- Download all; keep the PNG originals as masters
One pass, consistent settings, and your photo collection drops to a fraction of its size. When the goal is email, follow up with the email resizing guide to bring the long side under 1600 px, resizing before converting saves even more.
The same batch logic applies to cloud storage: a folder of family photos or client deliverables that sat at 250 MB as PNGs usually drops to 30–50 MB as quality-85 JPGs, which is the difference between paying for extra drive space and not.
Why the colors sometimes shift a little
Converting PNG to JPG occasionally makes colors look marginally different, not because quality dropped, but because of color profiles. PNG and JPG both carry color-space information (sRGB, Adobe RGB, Display P3), and some editors apply a different profile at each end. The practical effect is tiny on most screens and usually invisible, but two habits remove surprises:
- Convert from the original PNG rather than a re-saved copy, so the color profile stays intact
- If a conversion looks washed out, check whether the source file carried an Adobe RGB or P3 profile, converting through sRGB can mute those colors
If colors matter (brand assets, product photos), compare the JPG against the PNG side by side on the same screen before shipping it.
Conversion questions people ask first
Does converting PNG to JPG lose quality?
JPG is lossy, but at quality 85–90 the difference is imperceptible in photos. Keep the original PNG if you'll edit the file again.
How much smaller will the JPG be?
Typically 60–85% smaller for photos. For flat graphics the savings are smaller, which is a sign you shouldn't convert those anyway.
My PNG has a transparent background, what happens?
Transparent pixels become the background color you choose (white by default). If you need transparency in the output, use PNG or WebP instead.
Should I convert screenshots?
No. Screenshots have sharp text, which JPG artifacts mangle. Keep them as PNG.
What if I need transparency AND a smaller file?
Convert to WebP lossless instead, it keeps transparency and is smaller than PNG. The Image Converter outputs WebP too.
Need to convert in the other direction? The JPG to PNG guide explains when that actually makes sense.
When to press the button
Convert PNG to JPG for photos that need to travel light, and leave screenshots and transparent graphics alone. At quality 85 to 90 the size saving is dramatic and the visual difference is hard to spot, which is exactly the trade most people want.
Try the Image Converter
Free, private, and no account needed — your files never leave your browser.
Open Image Converter →