Convert JPG to PNG in your browser
Lossless from here on, which is not the same as better: whatever the JPG already lost is baked in. Expect a much larger file, and nothing sent anywhere.
or browse your device. Everything is processed on this device
No JPG to hand?
If the PNG was a means to an end, the JPG compressor works on the file you already have and will not multiply its size on the way.
Compress the JPG insteadHow to convert JPG to PNG
JPG or JPEG, one or a hundred. They are read into this tab and never uploaded.
A PNG of a 12 megapixel photo runs to tens of megabytes. Width is the control that changes that; the palette is not, on a photograph.
The download is a .png containing exactly the pixels the JPG decoded to. Nothing further has been discarded.
This will not improve your JPG
It is worth being direct, because it is the single most common misunderstanding about this conversion. PNG is lossless, and people reasonably read that as "better quality". What lossless actually means is that PNG will not throw anything away from here on. The detail your JPG lost was discarded when it was written, by the camera or the app or the website that made it, and it is not recorded anywhere in the file. No format can put it back.
So what you get is a perfect copy of an imperfect image, at three to ten times the size. If the JPG has visible compression artefacts, the PNG will have exactly the same artefacts, stored losslessly and expensively.
There are good reasons to do it anyway. If you are about to edit the image repeatedly, working in PNG stops each save adding a fresh generation of loss. If something downstream demands a PNG, it demands a PNG. And if you need to add transparency, you need a format that has an alpha channel, which JPG does not. Those are real reasons. "It will look better" is not one.
JPG to PNG FAQ
Will converting to PNG improve the quality?
No. PNG is lossless, which means it will not discard anything further, not that it recovers what was already discarded. Your JPG lost detail when it was written and that detail is not in the file. The PNG will look exactly like the JPG, at several times the size.
Why is the PNG so much bigger?
Because JPG is lossy and PNG is not. JPG throws away the detail your eye is worst at noticing and stores the rest compactly; PNG records every pixel exactly, including every compression artefact the JPG already has. Three to ten times larger is normal for a photograph.
Can I add a transparent background now?
PNG can hold one, so yes, in an editor afterwards. The conversion itself cannot invent it: the JPG has no transparency information, so every pixel arrives fully opaque and something has to decide which of them should not be.
When is this actually worth doing?
When something downstream requires a PNG, when you are about to edit the image repeatedly and want no further generational loss, or when you need a format that can carry transparency once you add it. Not for quality, which this cannot change.
Are my JPG files uploaded to convert them?
No. The JPG is decoded and the PNG is written by your own browser, in this tab. There is no upload endpoint in the site for a file to go to, which you can check in your network tools: convert something and watch that no request carries it. Disconnect from the network after the page loads and it still works.
Does this remove EXIF, GPS and AI metadata?
Yes, every time, and there is no way to turn it off. The image is decoded to pixels and encoded again from those pixels alone, so EXIF and GPS, the XMP packet, embedded colour profiles, and any Content Credentials or AI-generation tags the file arrived with do not survive. There is no switch for this, because there is no way to keep them. What no compressor can remove is a watermark written into the pixels themselves, such as the invisible marks some image generators add: those survive re-encoding here and everywhere else.
Related
Same format joins the queue. Anything else re-routes to its own tool.