JPG to PNG Converter
Turn JPG photos into lossless PNG files instantly.
Free · No watermark · Private — your image never leaves your browser
Every JPEG re-save discards a little more. Converting to PNG freezes the current state so repeated edits and saves cost you nothing further.
PNG has an alpha channel, so once converted you can cut out a background or add soft edges — impossible while the file stays a JPG.
Certain design software, app-store assets and icon pipelines accept PNG only. This is the shortest path to a compliant file.
How it works
This conversion is worth understanding before you rely on it, because it doesn't do what people often hope. Converting JPG to PNG will not restore quality — the detail a JPEG discarded is gone, and PNG simply stores the remaining pixels, artefacts included, perfectly. What it does give you is a lossless working copy: from that point on you can edit and re-save as often as you like without degrading anything further. That, plus compatibility with tools that require PNG, is the real reason to do it.
- 1Drop your JPG in, click to browse, or paste from the clipboard.
- 2Confirm the output is set to PNG.
- 3Download the lossless PNG — expect it to be larger than the JPG.
- 4Edit and re-save it as often as you like without further quality loss.
It won't undo JPEG compression
This is the single most common misunderstanding, so it's worth being blunt. When a JPEG was saved, it permanently discarded frequency data — fine detail, subtle gradients, crispness at edges. Converting to PNG stores whatever pixels remain, exactly as they are. Existing blocking and ringing artefacts are preserved perfectly rather than removed. If the source looks soft or blocky, the PNG will look identically soft or blocky, just in a bigger file.
Why the PNG comes out larger
Expect the file to grow, often by three to five times, and that's correct rather than a fault. JPEG achieved its size by discarding data; PNG has to store every pixel that's left, including the noise and artefacts JPEG introduced. Those artefacts are, ironically, hard for lossless compression to pack efficiently — they're semi-random, which is the worst case for pattern-based algorithms. If size matters more than losslessness, lossless WebP will store the same pixels in a considerably smaller file.
When this is the right move
Before an editing session, so subsequent saves cost nothing. When you need to add transparency. When a tool or platform demands PNG. And when archiving an image you'll work on repeatedly. It's the wrong move if you simply want a better-looking image, or if you're publishing to the web — in that case convert the JPG to WebP instead and get something smaller rather than larger.
Frequently asked questions
Will converting JPG to PNG improve quality?
No. Detail lost during JPEG compression cannot be recovered by any conversion. What PNG gives you is a lossless container, so no further quality is lost from that point on — but it can't add back what was already discarded.
Why is my PNG bigger than the original JPG?
That's expected. JPEG got small by throwing data away; PNG has to store every remaining pixel losslessly, including the artefacts JPEG introduced, which compress poorly. Three to five times larger is a normal outcome for a photograph.
Can I add transparency after converting?
Yes — that's one of the main reasons to convert. PNG supports an alpha channel, so once it's a PNG you can erase a background or add soft edges. Our background remover does that step in the browser too.
Is PNG better than JPG?
Neither is better in general; they're built for different content. PNG wins on graphics, text, screenshots and anything needing transparency. JPG wins decisively on photographs, where it's a fraction of the size at indistinguishable quality.
Should I use WebP instead?
Very likely, if the destination supports it. Lossless WebP stores the same pixels as PNG in a meaningfully smaller file and also supports transparency. Choose PNG when the receiving tool specifically requires it.
Is anything uploaded?
No. The conversion runs entirely on your device inside the browser.