Why this tool is different
PNG is lossless, which is wonderful for logos and terrible for photographs — a phone photo saved as PNG can easily be ten times larger than it needs to be. Converting to JPG usually cuts the file size dramatically. The one thing to decide is what happens to transparency, so we make that an explicit choice instead of a silent default.
How it works
- 1
Add one or more PNG files.
- 2
Pick a background colour for any transparent areas.
- 3
Choose quality, then convert.
- 4
Download the JPGs individually or as a ZIP.
What to watch out for
Transparency has to go somewhere
JPG has no alpha channel, so transparent pixels become a solid colour. White works for most documents; pick a different colour if your image will sit on a coloured background.
Keep PNG for graphics with sharp edges
Screenshots, logos, line art and text render more cleanly as PNG. JPEG compression puts visible fuzz around hard edges. Convert those only if you actually need a JPG.
Photos are where the savings are
For a photograph, JPG at quality 85 is often a fraction of the PNG size with no visible difference. That is the case this conversion is really for.
Frequently asked questions
Will converting PNG to JPG reduce quality?
JPEG is lossy, so technically yes. At quality 85 and above the loss is very hard to see on a photograph. On text and sharp-edged graphics it is much more noticeable.
What happens to the transparent background?
It is filled with the background colour you choose before the JPG is written. White is the default.
How much smaller will the file be?
For photographs, commonly 5 to 15 times smaller. For flat graphics and screenshots the saving is much smaller, and sometimes the JPG is larger.
Are my files uploaded to a server?
No. The conversion runs in JavaScript and WebAssembly inside your own browser. Open your devtools, switch to the Network tab and run a conversion — there is no upload request to see. Closing the tab clears the working session.