PNG to JPG
Much smaller, as long as it is a photo
← all tools / images
Most people looking for this converter want a sharper photo or a transparent background, and PNG gives neither: it copies the JPG exactly as it stands, compression artefacts included, into a file that is usually 3 to 5 times larger. It is the right move in two narrow cases, when something on the other end accepts PNG only, or when you are about to edit and want no further quality loss.
Gone within the hour.
Files are uploaded over HTTPS, used only to run this tool, and deleted from our server automatically about an hour later. Never sold, never used to train anything.
No, and this is the main thing to understand before you convert. PNG is lossless, so it stores exactly what the JPG holds right now, including the blocky edges and smeared colour that saving as JPG already baked in. Those details were discarded when the JPG was written and no later format change brings them back. A soft JPG becomes a soft PNG that takes up more room.
PNG compresses without discarding anything, and a photograph is millions of slightly different pixels, which is close to the worst case for that kind of compression. A 2 MB JPG photo commonly lands somewhere between 6 and 12 MB as a PNG. Screenshots, logos, and line art fare much better, because PNG is built for large areas of identical colour. The 50 MB limit on this page applies to the JPG you upload, not to the PNG that comes back.
No. JPG has no alpha channel to carry, so the PNG comes back fully opaque, exactly as the photo looked. What you gain is a format that can hold transparency once you cut the subject out yourself in an editor. If getting rid of the background is the actual goal, that is Remove Background, and it is not live on the site yet.
No, this runs the wrong direction: expect the file to grow. Compress Image is the one you want, since it keeps the format you started with, offers three quality levels, and never hands back a file larger than the one you sent. Come here only when a system refuses anything but PNG.
Two situations. First, a PNG-only requirement: some upload forms, print templates, app icon pipelines, and CMS fields reject JPG outright. Second, editing: if you are going to crop, retouch, and re-save the same picture several times, working in PNG stops every save from stacking another round of JPG loss on top. Outside those two, keeping the JPG is the better call.
No. It travels over HTTPS, gets used for this one job, and both your JPG and the PNG are deleted from our server automatically about an hour later. Nothing is sold and nothing is used to train anything. Download the PNG before that hour is up, because there is no account holding it for you.