PNG to JPG — When Lossy Compression Makes Sense
PNGs are lossless and great for editing, but they're often overkill for distribution. A photographic PNG can be 5–10x larger than the equivalent JPG. This converter shrinks it down with adjustable quality, runs entirely in your browser, and never touches a server.
Try PNG to JPG Converter free →
The problem
You end up with oversized PNGs in a few common ways: screenshots from a Mac or Windows machine (often exported as PNG by default), graphics exported from design tools, or images converted to PNG for editing that now need to go somewhere. Upload forms with file size limits are one trigger — some platforms cap uploads at 2MB or 5MB and a high-resolution PNG easily blows past that. Another trigger is simply needing to email something and not wanting to send a 4MB attachment.
JPG's lossy compression is specifically tuned for photographic content. For anything that looks like a photo — even a screenshot of a webpage — the quality difference between a PNG and a quality-85 JPG is nearly invisible, while the file size difference can be dramatic.
How it works
- Drop your PNG onto the tool or click to browse for it.
- Adjust the quality slider. Quality 85 is a good starting point — it's where most people can't tell the difference visually, and the file size savings are significant.
- Any transparent areas in the PNG are automatically filled with a white background. JPG doesn't support transparency, so this is a necessary step.
- Check the size comparison — original PNG size versus the output JPG size — before downloading.
- Download the JPG. Nothing was uploaded. The conversion happened locally using the browser's Canvas API.
Why I built it
I regularly share screenshots and design exports with people who don't need lossless files — they just need to see something. Sending a 3MB PNG when an 200KB JPG looks identical is wasteful. I wanted a tool where I could drag in a PNG, pull the quality slider to 85, and have a shareable JPG in under ten seconds. That's what this is.
When to choose PNG vs JPG
| Use case | Better format | Reason |
|---|---|---|
| Screenshots with text | PNG | Text edges stay sharp; no compression artifacts |
| Photographs | JPG | Dramatic size savings, invisible quality difference |
| Graphics with transparency | PNG | JPG doesn't support alpha channel |
| Email attachments | JPG | Much smaller, inbox-friendly |
| Web photos | JPG (or WebP) | Faster page loads, lower bandwidth |
| Diagrams and line art | PNG | Clean edges without ringing artifacts |
If you're converting a PNG screenshot that contains text or fine lines, preview the result carefully — JPG compression can introduce visible artifacts around high-contrast edges. For photographic content without transparency, JPG (or WebP) is almost always the right call.
Built with vanilla HTML/JS. No frameworks, no backend, loads instantly.