Why convert PNG to JPG in the first place?
PNG is a lossless raster format. Every pixel is stored faithfully, which is great for archival, screenshots, and graphics with hard edges — but expensive in file size. A typical 1920×1080 PNG of a photograph weighs 2–4 MB; the same picture as a quality-92 JPG often lands around 300–600 KB without visible loss. For the web, that's a five-to-ten times speed-up on every image load.
JPG (officially JPEG) was invented in 1992 specifically for photographs. Its DCT-based compression discards information the human eye can't easily see — high-frequency detail in smooth color regions — and the result is a much smaller file that looks identical to the eye. The catch is that JPG is lossy: each save degrades quality slightly, so it's a poor intermediate format. Use PNG (or WebP) for editing; convert to JPG at the very end when you ship.
How the converter handles transparency
JPEG has no alpha channel. If your PNG has transparent pixels — say a logo on a transparent background, or a UI element with a soft drop shadow — those pixels can't survive the conversion as-is. This tool flattens them onto a solid white background before encoding, which matches what a Word document, PowerPoint slide, or default Photoshop save would do.
If your image needs a different background color (or any transparency at all), JPG is the wrong target. WebP supports transparency at much smaller sizes than PNG, and AVIF supports it with even better compression on modern browsers. We have converters for both — see the PNG to WebP and PNG to AVIF tools.
How to use this tool
- Drag a
.pngfile onto the drop zone above, or click to open the file picker. - The converter decodes the PNG into a canvas, flattens any transparent pixels onto white, and re-encodes the canvas as a JPG at quality 0.92.
- Click Download to save the JPG. The widget shows the resulting file size and the percentage change versus the source PNG.
Nothing is ever uploaded. The entire pipeline — decode, flatten, re-encode — runs in your browser via the Canvas API. You can verify this by opening DevTools and watching the network tab while converting.
When to keep the original PNG instead
Don't convert to JPG if any of these apply:
- The image has flat colors, sharp text, or thin lines — JPEG compression introduces visible ringing artifacts around hard edges. Screenshots of code, UI mockups, and pixel art should stay PNG (or move to WebP lossless).
- You need transparency for the final use — slot the image into a layout, web background, or print bleed where the surrounding color is unknown.
- You'll edit the file again. Each JPG re-save degrades quality. Keep a PNG master, export JPG copies for distribution.
- The audience is a print shop — most still expect PNG, TIFF, or layered PSD. JPG is a web/distribution format.