Cookies for analytics and advertising
We use cookies for analytics and advertising, both sent to Google. Refusing changes nothing you can see.Read the privacy page
Converting JPG to PNG gives you a copy that loses nothing from this point on. It does not restore detail the JPG already threw away, and it does not create a transparent background; expect the file to grow five to ten times. Drop the JPG above and it converts in your browser, free and without an upload.
Up to 100 files at once. Mixed formats are fine.
They convert one after another and download together as a ZIP.
JPG to PNG






This conversion is worth doing for two reasons and neither is the one people usually have in mind. The first is editing: PNG loses nothing on each save, so an image about to be cropped, adjusted and exported several times will not accumulate damage the way a JPG does. The second is compatibility — some design tools, print workflows and upload forms want PNG specifically, and there is no arguing with a form.
The reason this conversion is often done and should not be is the word lossless. Converting a JPG to a PNG does not repair it. The detail your camera or your last export threw away is gone, and PNG simply stores the damaged picture very faithfully. If a better original exists anywhere — the camera roll, the original export, the file before it went through a messaging app — convert that instead.
PNG supports transparency; your JPG has none; the result is an opaque image in a format that could have held some. Cutting a background out is editing work, and no conversion does it. If that is what you came for, you need a background remover first and then a PNG to keep the result in.
Five to ten times is ordinary for a photograph, because PNG is a poor fit for continuous tone — it compresses by finding repetition, and a photograph has almost none. If size matters and you only need the image to open somewhere, WebP does the same job at a fraction of the space and is read by every current browser.
Almost every reason to convert a JPG to PNG — editing without further loss, needing a format an editor accepts, wanting no more generational damage — is also served by WebP lossless, which Google measured at about a quarter smaller than an optimised PNG of the same picture. If the destination is anything with a modern browser in it, that is the same job in less space, and the PNGs written here are already run through oxipng.
PNG remains the right answer where the destination is old or unknown: a print shop, a corporate template, an upload form that lists the formats it accepts. It has been readable everywhere for thirty years, which is a real property and the reason this conversion exists at all.
A common expectation, and the one worth correcting before it costs anyone a folder of files: converting to a lossless format does not undo lossy compression. PNG stores what it is given with perfect fidelity, and what it is given is the JPG with its artefacts already baked in — the haloing around edges and the blocking in smooth areas are preserved exactly, at five to ten times the size.
Where it does help is everything that happens next. Editing a JPG and saving it again compresses it a second time; doing the same work in PNG does not. The gain is in the future of the file, not in its past.
Convert when the picture is about to be edited, when something downstream demands PNG, or when it is going into a design tool that will re-save it repeatedly. In each case the format change buys you no further generational loss.
Leave it alone when the file is simply being sent or displayed. A JPG that looks fine will look identical as a PNG and take several times the space, which slows a page down and fills an inbox for no benefit anyone can see.
| JPG | PNG | |
|---|---|---|
| Full name | JPEG Image | Portable Network Graphics |
| File extension | .jpg, .jpeg, .jpe | .png |
| Media type | image/jpeg | image/png |
| Compression | Lossy — file size is bought with quality | Lossless — nothing is discarded |
| First published | 1992 | 1996 |
| Published by | Joint Photographic Experts Group | PNG Development Group |
| Specification | ITU-T T.81 | ISO/IEC 15948 |
| Licensing | Open standard | Open standard |
| Standing today | Current | Current |
| Bit depth | 8 | 16 |
| Colour it can describe | RGB, greyscale, YCbCr | RGB, greyscale, indexed palette |
| Largest image | 65,535 px per side | 2,147,483,647 px per side |
| Opens in a browser | Every browser | Every browser |
| Considered instead | WebP, AVIF, HEIC | WebP, SVG, JXL |
PNG has nowhere to put IPTC fields, which hold captions, credits and keywords and the GPS coordinates, so those go no further than the JPG. Worth checking before the original is deleted, and worth knowing if the point was to strip it.
PNG supports transparency and JPG does not. That is room the result has and the original never used — converting does not create a transparent background, it only makes one possible afterwards.
Adobe Photoshop and GIMP read both JPG and PNG, so there is a way to check the result against the original without a second tool.
The result is larger than the original and no better. JPG has already discarded detail, and PNG stores what is left without discarding more — it prevents further loss rather than undoing the first one.
JPG is Joint Photographic Experts Group's format, published in 1992. It records 8 bits per channel.
PNG comes from PNG Development Group and dates from 1996, specified as ISO/IEC 15948. Adobe Photoshop, GIMP and Paint.NET all read it.
No. This conversion runs entirely inside your browser, so the file never leaves your device. You can confirm it yourself: open the network tab of your browser's developer tools and convert something. You will see the page load, plus the analytics and advertising the site is paid for with — and nothing carrying your file. The engine behind this particular pair is jSquash, WebAssembly builds of the reference image codecs; your browser fetches it once and caches it.
No. PNG is lossless from this point on, but the JPG already discarded detail and nothing recovers it. You are preserving what you have, not restoring what was lost.
No. PNG can hold transparency, but a JPG has none to carry over, so you get an opaque image in a format that supports transparency. Removing a background is editing, not converting, and no format change does it.
Because PNG stores photographs inefficiently — it was built for flat colour and sharp edges, not for continuous tone. Five to ten times the size is normal for a photograph and is not a sign that anything went wrong.
When the image is about to be edited and re-saved several times, because PNG loses nothing on each save; and when a specific tool, print workflow or upload form insists on PNG. Outside those two cases you are trading file size for nothing.
This page converts one into the other. If you are choosing rather than converting, JPG vs PNG answers which to use, for what, and what each is bad at.
The claims this page makes about JPG and PNG are checkable, and these are the documents that settle them.