Image tools · convert
Some doors only open for a PNG. This door converts one JPG to a PNG, here in your browser, and it is honest about the trade before you run: the PNG holds every pixel of your JPG exactly, the picture does not get better, and the file gets bigger. What you gain is a picture that stops degrading every time it is saved. A whole folder at once is the batch convert page; the reverse trip is PNG to JPG.
For one JPG that has to arrive as a PNG: a portal or editor that requires PNG, or a picture you are about to edit and re-save.
Pick a JPG
Convert to PNG
Download the PNG
Drop a JPG on the tray, or click to pick one
JPG in · PNG out · it stays on this device
The wrapper changes, and the picture does not. Every pixel of your JPG is written into the PNG exactly as it decoded: nothing added, nothing sharpened. Expect the file to grow, often a lot; the result line prints both sizes.
PNG is lossless, so there is no quality setting on this door: the decoded picture is written exactly, pixel for pixel.
Pick a JPG to begin.
The JPG is decoded by the open-source jSquash codecs and the decoded picture is written as a PNG, losslessly, the same engine the batch convert page runs. The first run loads the image program (about 2 MB, one time only). The download is how we protect your privacy: the program comes to your device and does the work there, so your file never leaves it.
PNG cannot put back what JPG already threw away: soft edges, blocky patches and lost detail in your JPG are stored faithfully, not repaired, and no tool here claims to restore them. If the file size is your problem, this door makes it worse; the exact-KB tool is the one that lands a JPG on a size a door sets.
No, and this page will not pretend otherwise. A JPG has already thrown detail away; writing its pixels into a PNG stores exactly what is there, nothing more. The picture does not improve; the file gets bigger, often much bigger. What improves is what happens next: the pixels stop changing.
Two honest reasons. Some portals, editors and print queues accept PNG and not JPG, and the door is the door. And every time a JPG is opened and saved again as a JPG, it loses a little more; a PNG freezes the picture as it is now, so further editing starts from a file that no longer degrades.
Photos commonly land several times their JPG size as a PNG; the result line prints both sizes, so the trade is never silent. If the size is the problem, this is the wrong door: compress image lands a JPG on an exact KB target.
Nowhere. It is decoded, re-encoded and offered back to you inside this page. Nothing is uploaded.