What this does
Re-encodes JPG photos as PNG files, locally in your browser. Drop up to 20 JPGs, hit convert, and download PNGs named after the originals.
When do I actually need JPG as PNG?
Usually when something downstream demands it. Typical cases:
- A form, CMS, or design tool that only accepts
.pnguploads. - Asset pipelines (app icons, sprite sheets, document templates) standardized on PNG.
- You're about to edit the image repeatedly and want to stop further generation loss — PNG never degrades on re-save.
Does converting JPG to PNG improve quality?
No — and it's worth being clear about this. JPG compression already discarded fine detail when the photo was saved; converting to PNG preserves exactly what's left, byte-for-byte going forward, but it can't reconstruct what was lost. Think of it as freezing the current quality, not restoring it.
Why is the PNG bigger than my JPG?
Expect 5–10× growth for photographs. PNG's lossless compression is built for flat colors and sharp edges (interfaces, diagrams), not for the smooth gradients of real-world photos. The size increase is the cost of the format's guarantees, not a sign something went wrong.
Can I add transparency to a JPG this way?
The output PNG supports an alpha channel, but conversion alone won't create one — your photo still covers every pixel. To actually remove a background, run the photo through the background remover first, which outputs a transparent PNG directly.
Is my data private?
Yes. Conversion is handled by the canvas API in your own browser; nothing is uploaded. Verify it in DevTools → Network if you like.