PNG vs JPG: The Core Trade-Off
PNG = lossless quality + transparency support + larger file size JPG = lossy compression + no transparency + much smaller file size
For photographs, a PNG can be 5-10× larger than an equivalent JPG with no visible quality difference at 85% compression. For UI graphics and logos, PNG preserves quality that JPG would visibly degrade.
When Converting PNG to JPG Makes Sense
✅ Good reasons to convert:
- Photographs stored as PNG — a photo has no hard edges where JPEG artifacts are visible. You can save 60-80% file size.
- Web performance — a JPG product photo loads faster than the same PNG.
- Email attachments — a PNG photo might be 5 MB; the JPG version, 500 KB.
- Platforms with file size limits — many social platforms recommend JPG for photos.
- Reducing storage costs — a large photo library in PNG occupies 5-10× more than JPG.
❌ When you should NOT convert PNG to JPG:
- The image has transparency — JPG doesn't support alpha. Transparent pixels become solid white (or the specified background color).
- It's a logo, icon, or graphic with text — JPG compression creates visible artifacts around sharp edges and text.
- Screenshots — especially those containing UI, code, or text. JPG blurs them.
- The PNG will be edited multiple times — convert to JPG only for the final version.
Method 1: KaijuConverter (Online, Free)
- Go to Convert PNG to JPG.
- Upload your PNG file (up to 25 MB free).
- Download the JPG.
Transparent pixels are filled with white by default.
Method 2: Windows Paint (Built-in)
- Open the PNG in Paint.
- File → Save as → JPEG picture.
- Save.
Paint uses a fixed quality setting (~85%). Fine for most use cases.
Method 3: macOS Preview
- Open the PNG in Preview.
- File → Export.
- Format: JPEG.
- Adjust quality with the slider.
- Save.
Method 4: ImageMagick (Command Line, Batch Processing)
# Single file
convert image.png -quality 85 image.jpg
# Batch convert all PNGs in directory
mogrify -format jpg -quality 85 *.png
# With white background for transparent PNGs
convert image.png -background white -alpha remove -alpha off -quality 85 image.jpg
Method 5: FFmpeg (Alternative Command Line)
ffmpeg -i image.png -q:v 3 image.jpg
# -q:v controls quality: 1 (best) to 31 (worst). 2-5 is the practical range.
Handling Transparency When Converting
PNG supports full alpha transparency. JPG doesn't. When converting, you must decide what color replaces transparent areas:
White background (most common):
convert logo.png -background white -alpha remove output.jpg
Custom background color:
convert logo.png -background "#FF0000" -alpha remove output.jpg
In CSS after conversion — if you control the placement:
img.logo { background-color: #f0f0f0; }
Choosing the Right JPG Quality
| Quality | File size vs PNG | Visual quality | Use case |
|---|---|---|---|
| 100% | ~120% | Identical | Not useful (PNG is better) |
| 90-95% | 25-40% | Excellent | Print delivery |
| 80-85% | 10-20% | Very good | Web and general use |
| 70-75% | 7-12% | Good | Thumbnails |
| 60% and below | <10% | Noticeable artifacts | Avoid for photos |
85% is the sweet spot for most web images.
What Happens to Quality After Converting
Converting PNG to JPG always involves some quality loss — that's the point of JPG compression. Key facts:
- The loss happens once at conversion time.
- Saving the same JPG again doesn't add more loss.
- Re-converting the JPG back to PNG "freezes" the quality at the JPG level — the PNG will be lossless, but starting from already-compressed data.
- Always keep your original PNG if you might need it again.
Batch Conversion Tips
For large collections:
- Use ImageMagick's
mogrify— processes hundreds of files in seconds. - Keep the originals — never overwrite the source PNGs.
- Use a consistent quality setting across the batch.
- Consider WebP instead of JPG for web images — same compatibility, 25% smaller.
Related Conversions
- PNG to JPG
- PNG to WebP — modern alternative for web
- JPG to PNG — restore lossless quality
- PNG to PDF