Convert JPG to PNG
Lossless from here on — but no quality comes back. See the new size before you convert.
Runs in your browser0 bytes uploadedLossless from here on — but no quality comes back. See the new size before you convert.
Runs in your browser0 bytes uploadedDrop your JPG files here
or paste Ctrl+V
Nothing is uploaded. The pictures are re-encoded as PNG inside this tab, and the new — usually larger — size is measured before you commit to it.
Came here to make a picture smaller? That is the other direction. Convert PNG to JPG.
This conversion does not improve the picture, and the file will almost certainly get bigger — three to ten times bigger is ordinary for a photograph. Both halves of that sentence are worth taking seriously, because most pages offering this conversion say neither.
Nothing comes back because there is nothing to come back. A JPEG threw detail away at the moment it was first saved, and that detail was not kept anywhere. The soft blocks in a sky, the ringing around text, the smeared edges in a dark corner: those are not a wrapper the PNG can strip off. They are the picture now. Converting to PNG preserves what remains perfectly, which means you end up with a flawless, permanent, considerably larger copy of the flaws.
The estimated new size sits on every file card before you run anything, so the number is never a surprise on the receipt. If nothing here matches what you needed, the honest answer is to keep the JPG.
Something you are uploading to only accepts PNG. Print services, avatar and badge uploaders, government and university portals, older internal systems, app store asset requirements, plenty of e-signature tools. The requirement is often about guaranteeing a lossless pipeline downstream, and sometimes it is a form validator nobody has revisited in a decade. Either way arguing with it is not an option, and the conversion is the whole job.
You are about to edit the image repeatedly. Every save of a JPG re-encodes the entire image, including the parts the previous save already damaged. Open, adjust, save, reopen, adjust again, and the degradation compounds visibly within a handful of rounds. Moving to PNG once does not repair the damage already done, but it stops the counter. From that point every save is identical to the last, however many there are. If a file is about to enter a workflow with several editing passes, converting at the start is the correct move.
You need to add transparency later. Cutting a subject out, removing a background, or dropping a logo onto a colored surface all require a format that can carry an alpha channel. JPEG cannot, at all. So the conversion has to happen before the editing, not after — you cannot cut the background out of a JPEG and then save the transparency into a format with nowhere to put it.
This is the most common misunderstanding people arrive with, and it is worth stating flatly. A JPEG has no transparency to preserve, so every pixel comes out fully opaque. What you get is a PNG that is capable of holding transparency, not one that has any. The white area behind your logo is still white pixels. It looks exactly the same as it did, because it is exactly the same.
Removing that background is a separate operation done in an editor or a background remover, and this conversion is the prerequisite for it rather than a substitute. Any tool promising that a format change alone produces a cutout is describing something the format change does not do.
There is no quality slider here. PNG is lossless — there is no quality to trade, and a slider would be a control that changes nothing while implying it changes something. There is no background color picker and no option to preserve transparency, for the same reason in reverse: the source is a JPEG, so there is no alpha anywhere in the input to fill in or protect.
What remains is a limit on the longest side, which does make a real difference — both to the output size and to whether an upload form accepts the result. The sibling tool atPNG to JPG has a quality slider and a background color picker because in that direction both of them genuinely do something. That asymmetry is why these are two pages rather than one page with a direction switch: half the interface would have to disappear on every flip.
PNG stores every pixel exactly and compresses by finding repetition — runs of identical color, rows that resemble the row above. That works beautifully on screenshots, logos and line art. A photograph is the opposite: millions of values that differ slightly from their neighbors, with sensor noise on top, and almost nothing repeats. There is little for the compressor to work with, so it stores something close to the raw pixels.
A JPEG of the same photo achieved its small size by discarding most of that variation. The gap between the two numbers is the detail JPEG threw away — except you are now paying for the bytes without owning the detail. JPG vs PNG explains which format suits which material, and what PNG actually stands for covers where the format came from and why it works this way.
Most people searching around these two formats want the image to weigh less, and this page is the wrong direction for that. PNG to JPG is the conversion that pays, and if you are trying to land under a specific limit rather than change format at all,compressing to a target size solves that directly by searching for the setting that fits.
The conversion runs entirely in this tab. Your browser already decodes JPEG and already writes PNG, so there is no server involved and no upload endpoint on this site for it. That also means EXIF data, color profiles and copyright fields are not carried across — a canvas writes pixels and nothing else — so keep your originals if the capture data matters.
No, and nothing can. JPEG throws detail away when the file is first saved, and that detail is not stored anywhere — the blockiness and the halos around edges are now part of the picture. Converting to PNG preserves what is left perfectly, which means you get a lossless copy of a lossy image. It will be larger and it will look exactly the same.
Because PNG is lossless and JPEG is not. PNG stores every pixel exactly, and its compression is built for flat color and sharp edges rather than photographs. A photograph is the worst case for it: three to ten times the original is normal, and the tool shows the estimate for each file before you run anything so the number is never a surprise.
Three reasons that are all legitimate. Something you are uploading to only accepts PNG. You are about to edit the image repeatedly and want to stop generation loss from stacking with every save. Or you need to add transparency, which requires a format that can carry an alpha channel — the JPEG cannot, so you have to convert before you can cut anything out.
No. A JPEG has no transparency to preserve, so every pixel arrives fully opaque. What you get is a PNG that is capable of holding transparency, not one that has any — you still have to remove the background yourself in an editor afterward.
No. Your browser already decodes JPG and already writes PNG, so the conversion happens entirely in this tab. There is no upload endpoint on this site for this tool, and you can confirm it with your browser's Network tab open.