JPG to PNG Converter
A PNG cannot undo what JPEG already threw away, but it can stop the next save from taking more. Everything runs in this tab.
JPEG has no transparency, so transparent areas are filled with this color.
Everything runs locally in your browser. Nothing is uploaded to any server — close the tab and your files are gone.
How to convert JPG to PNG
Drop in the JPEGs
PNG is already selected as the output format here, so there is nothing to configure first. Files ending .jpg and .jpeg are both read by the same decoder, and there is no cap on how many go in at once.
Walk straight past the settings
With PNG selected the quality slider is not shown at all, because a lossless encoder has nothing to trade away. What does run is oxipng at level 2, which repacks the file to save bytes without changing a single pixel.
Set the dimensions now, not later
Every resize done in another program is another save. Doing it here happens once, on the way into the PNG: the longest edge fits to 1024, 2048 or 4096 px, and an image already smaller than the target is passed through as it is.
Download the PNGs and keep the JPGs
Rows download one at a time, and a ZIP button appears once more than one is finished. The original JPG is still the far lighter file for anything that only needs to be sent or posted, so there is no reason to throw it away.
What a PNG can and cannot fix
It stops the losses from stacking
JPEG re-compresses every time it is written. Open a JPG, crop it, save it, hand it on to someone who adjusts the levels and saves again, and each round quietly takes a little more — that is generation loss, and none of it comes back. Converting to PNG once puts an end to it: from that point every save writes the same pixels out unchanged, and the picture stays wherever it is now.
It does not undo the first pass
Whatever the original JPEG discarded was gone before the file ever reached this page. The PNG is an exact copy of the pixels as they stand: blocking in flat areas, faint outlines around type, gradients already smoothed over. A lossless format preserves what it is handed — it does not reconstruct what is missing.
And it does not add a transparent background
This is the most common misunderstanding about the conversion. A JPEG is opaque by definition — there is no alpha information in the file to recover — so the PNG comes out opaque too, white background and all. Removing a background is editing work done in an editor; PNG is only the format that can hold the result once that work exists.
And the file grows, often steeply
PNG compresses by finding repetition, and JPEG leaves fine noise spread across the image that offers very little of it. A photograph converted here routinely lands at several times the size of the JPG it came from, and the row prints the real figure for each file. oxipng shaves off what it can without touching the image, but no amount of that closes the gap between a lossy source and a lossless container. If a lighter file was the actual goal, our format guide covers which container to reach for instead.
The destinations that take nothing else
Plenty of them, once you start noticing: app icon and favicon fields, game engines and texture pipelines, print templates that expect a lossless placement, e-signature and stamp assets, documentation tools, and upload forms whose allow-list happens to name PNG and nothing else. In those cases the size increase is not a trade-off you are choosing — it is simply the toll.
JPG to PNG — frequently asked questions
Does converting to PNG make my JPG look sharper?
No. The PNG holds exactly the pixels the JPEG decoded to, so it looks identical at every zoom level. Sharpening, upscaling and artifact cleanup are separate jobs, and none of them happen on this page.
Will the PNG have a transparent background?
No. A JPEG has no transparency to carry over — every pixel in it is opaque — so the PNG comes out opaque as well. Cutting a subject away from its background is editing work, not a conversion; the PNG only becomes useful once that work has been done somewhere else.
Then why convert a JPG to PNG at all?
Two reasons come up constantly. Something in the chain accepts only PNG — an icon field, a print template, a game engine, an upload form with a fixed extension list. Or the image is about to be edited and re-saved several times, and saving as JPEG each round is what you are trying to avoid.
Why did the file size go up so much?
Because the two formats pull in opposite directions. JPEG got small by discarding detail; PNG stores every pixel it receives, artifacts of that discarding included, and those artifacts are exactly the kind of fine noise PNG compresses worst. Landing at a multiple of the original size is ordinary here.
Is a PNG made from a JPG good enough for print?
It is no better than the JPG was. The conversion creates no new resolution and removes no compression artifacts, so a print shop still sees the same pixel dimensions and the same blocking in the flat areas. What PNG does give you is a placement file that will not lose anything further as the layout is saved and re-saved.
Should I convert to PNG or to WebP if I am going to keep editing?
PNG. The WebP written on this site comes out of the lossy encoder, so it would add a round of compression before your editing even starts, while the PNG path is lossless from the moment the JPEG is decoded. WebP is the better choice for the finished file you publish, not the working one.
Does the PNG keep the shooting date and other camera fields?
No. The file is decoded to raw pixels and a new PNG is written from them, so no EXIF block travels across. If the capture date, the lens or a copyright field matters, keep the JPG next to the PNG.
If I resize, does that happen before or after the PNG is written?
Before. The pipeline decodes the JPEG, resamples once at the size you asked for, and encodes the PNG from that — so there is no intermediate file and no second save. Doing the same thing in two steps elsewhere would put another encode between them.
Does the photo leave my computer while it converts?
No — there is no upload step in the first place. The JPEG decoder and the PNG encoder are WebAssembly running inside this tab, so the only copy of the file stays on your own disk.