Convert images to PNG
Writes a JPG, a WebP or an iPhone HEIC out as a PNG. This page starts with PNG already chosen, so you can drop the files in and press Convert. Twenty at a time, and the photos stay in this browser tab.
PNG converter
Checking which image formats this browser can save.
What PNG is actually good at
Three jobs, and they are all about edges rather than photographs. A logo or an icon that has to sit on a coloured slide needs its transparent background kept, and PNG keeps it. A screenshot with text, tables or thin lines in it stays crisp, because PNG stores every pixel exactly as it was instead of smoothing the areas around high-contrast edges the way JPG does. And an image you expect to open, edit and re-save several times holds still in PNG — each JPG save shaves a little more off, while a PNG save changes nothing.
The fourth reason is the plainest one: something on the other end only accepts PNG. A slide template, an asset upload, a print spec. In that case what matters is that the bytes really are PNG, which is what this tool produces — the format marker at the start of the file changes along with everything after it.
Expect the file to get bigger
PNG stores the image without discarding anything, so a photo that arrived compressed comes out uncompressed. A JPG is already a picture with detail thrown away; writing it to PNG faithfully preserves what is left, including the compression artefacts, and spends far more bytes doing it. The same 1,200 × 900 photo was saved in three formats and then run through this tool (Chrome 152, 2026-09-04).
| Input | PNG result | Growth |
|---|---|---|
| JPG, 216KB | 1.69MB | 8× |
| WebP, 85KB | 1.54MB | 18× |
| HEIC, 99KB | 1.42MB | 14× |
The smaller the input, the larger the multiplier, because PNG's size follows the colours and patterns in the image rather than how compressed the source was. So converting to PNG to save space runs the wrong way. Shrinking the long edge to 800px at the same time still left the first row at 920KB — four times the untouched 216KB JPG. If an upload is rejecting your file for being too large, PNG is not the answer; a smaller long edge, or JPG at a lower quality, is.
Going to PNG does not undo anything
This is the part that trips people up, so it is worth saying flatly. Detail a JPG already dropped is gone from the file, and a lossless format has nothing to restore it from. If you can see blotchy patches in a sky or across skin, PNG will reproduce those patches exactly. Sharpness does not improve. Banding does not smooth out.
Transparency does not appear either. A JPG has no transparency to carry, so a logo with a white background converts to a PNG with a white background — the white is part of the picture now. Actually removing a background is a different operation, done by a tool that decides which pixels are subject and which are backdrop.
PNG is the high-quality setting
PNG is faithful, not better. It reproduces exactly what you hand it. Hand it a heavily compressed JPG and you get a heavily compressed JPG stored in a large file.
The quality slider is broken
It greys out on purpose. PNG has no quality dial to turn, so there is no value to set. Switch the format to JPG or WebP and the slider comes back.
Re-saving a PNG as PNG compresses it
It comes out about the same size. You are moving between two lossless states. The one thing that does shrink a PNG here is choosing a smaller long edge, which drops the pixel count.
Converted files carry no metadata — no location, no device, no timestamp — because the image is redrawn on a canvas and exported from there. Keep your original if you need any of that.