JPG to PNG
Convert JPG images to PNG in your browser. Explains when this is worth doing, when it is not, and why the file gets bigger.
Runs in your browser
Pick one or more images. They are converted on your device.
This does not improve the image
It is worth being blunt: converting a JPG to PNG cannot recover anything JPG threw away. The compression artefacts — the blocking around edges, the smeared text — are pixels now, and PNG stores them faithfully. What you get is a lossless copy of a lossy image, usually two to five times larger than the JPG it came from.
Nobody should convert a photo library to PNG to “improve quality”. There is none to gain.
When it is the right move
- You are about to edit repeatedly. Every JPG save re-compresses the whole image, so a file edited and saved five times has been through five rounds of loss. Working in PNG between edits avoids that, then export to JPG once at the end.
- The target requires it. Some print workflows, icon pipelines and older software accept PNG and nothing else.
- You need to add transparency. JPG cannot store an alpha channel at all. Converting to PNG first gives you somewhere to erase a background to — the conversion does not create transparency by itself.
If your reason is a smaller file for the web, neither format is the answer; WebP is.
Your files stay here
Conversion happens in your browser, and nothing is uploaded.