Convert JPG to PNG
JPG (JPEG) is a lossy compressed format great for photos, while PNG uses lossless compression and supports transparency. Converting from JPG to PNG gives you an editable, pixel-perfect copy that you can layer, mask, or annotate without further quality loss.
To convert JPG to PNG in your browser, drop a JPG file into the tool above and download the result. The JPG is decoded once, re-encoded losslessly as PNG, and never uploaded. The PNG will look pixel-identical to the JPG on screen but will not restore detail the original JPG compression already discarded — it simply stops any further edit from adding new compression artifacts, and gives you a file that supports transparency for future edits. Expect the PNG to be considerably larger — often three to five times the JPG, because PNG stores every pixel exactly while JPG discards detail by design. That is the trade-off in a sentence: you gain an editing-safe master and lose file size. The genuinely useful cases are preparing an image for repeated editing, feeding a design tool that dislikes JPEG artefacts, or adding transparency to a logo. Converting a JPG to PNG purely to "improve quality" does nothing, since the discarded detail cannot be recovered by any format.
Drop a JPG here, or click to upload
Output: PNG
What happens when you convert JPG to PNG?
PNG is a lossless raster format standardised as ISO/IEC 15948. Every pixel in the JPG source is preserved exactly, including chroma-subsampled edges that a second JPG save would soften. PNG uses DEFLATE compression, so photographic content typically produces PNG files 3–8× larger than the JPG source, while flat graphics can end up smaller. PNG supports 8-bit and 24-bit color plus a full 8-bit alpha channel, but a JPG source has no alpha to begin with — the converted PNG will be fully opaque unless you add transparency in an editor afterwards. Every current browser, OS thumbnailer and design tool reads PNG without a codec, which is why it remains the safe interchange format for screenshots, logos and layered work.
Common mistakes and limitations when going from JPG to PNG
Converting JPG to PNG cannot undo JPG blocking, ringing or color bleed — those artifacts are baked into the source pixels. If you can find the original camera RAW or a pre-compression export, always prefer that. PNG is also a poor choice for photos going straight to the web: the file will be several times bigger than the JPG for zero visible gain. If you only need to edit and re-export, TIFF or WebP lossless will usually give you a smaller working file.
Choosing the right settings for JPG to PNG
There is no quality slider on the way out, because PNG is lossless — every pixel the JPG decoded to is stored exactly. That makes the conversion deterministic but also means file size is entirely out of your hands, and photographic content will typically grow between two and ten times. The thing worth checking afterwards is whether you actually needed PNG. The common reason people convert is to edit without further degradation, and that reasoning is sound: each JPG re-save re-quantises the image and compounds artefacts, whereas a PNG can be opened and saved indefinitely with no change. But if the file is going straight to the web with no further editing, converting to PNG makes it larger for no benefit. A related trap is expecting transparency to appear. JPG has no alpha channel, so the converted PNG is fully opaque — the white background behind a logo is real image data, not empty space, and it has to be removed manually in an editor. If you need a transparent logo, the JPG was the wrong source and you want the original vector or a PNG export from the design file. Where JPG artefacts are already visible — blocky 8×8 squares around text, halos along high-contrast edges — converting to PNG freezes them permanently. It stops things getting worse but nothing recovers detail that the original compression discarded.
JPG to PNG conversion FAQ
Will converting JPG to PNG improve quality?
- No. The JPG has already discarded detail during its lossy encode. PNG only prevents any additional loss on later saves; it cannot recover what the JPG threw away.
Does the PNG have transparency?
- Only if the source had transparency, which JPG cannot store. The converted PNG will be opaque; you can add an alpha channel later in an editor if needed.
Why is the PNG so much bigger than the JPG?
- JPG uses lossy DCT compression tuned for photos; PNG uses lossless DEFLATE. On a typical photograph, expect the PNG to be roughly 3–8× larger than the JPG.
Which apps read PNG?
- Every modern browser, macOS Preview, Windows Photos, Word, PowerPoint, Figma, Photoshop and mobile OS thumbnailers read PNG without any plugin.
Should I use PNG or WebP as a lossless replacement?
- For pure editing use PNG. For a web-facing lossless image, WebP lossless is usually 20–30% smaller than PNG at identical visual quality.
Is the conversion truly private?
- Yes. The JPG is decoded on a canvas element in your browser and re-encoded via toBlob(); nothing is uploaded to a server.
Can I convert many JPGs at once?
- This tool handles one file at a time, which is the fastest path for occasional saves. For large batches, drop each file in sequence — nothing leaves your device either way.
Will EXIF metadata carry over?
- No. Canvas re-encoding strips EXIF, GPS and camera tags. If you need the metadata, keep the original JPG alongside the PNG.
JPG vs PNG at a glance
| Property | JPG source | PNG output |
|---|---|---|
| Compression | Lossy DCT | Lossless DEFLATE |
| Transparency | No | Yes (8-bit alpha) |
| Typical photo size | 0.3–2 MB | 2–8 MB |
| Color depth | 24-bit | 24-bit + alpha |
| Best used for | Photos on the web | Editing, screenshots, logos |
Last updated:
References: ISO/IEC 15948 (PNG specification), W3C PNG (Third Edition), libpng documentation on lossless re-encoding.