Convert HEIC to PNG
PNG is the right target when the image will be edited again, or when you cannot afford a second generation of compression artifacts.
Options
All processing runs in your browser. No file leaves this device.
The reason to pick PNG over JPG here is generational loss. A HEIC file is already lossily compressed; encoding it to JPG compresses it a second time, with a different transform, and the two sets of artifacts compound. If the image is finished and just needs to be viewable, that is fine and JPG is the smaller file. If it is going into an editor, a compositing step, or any workflow that will re-save it again, PNG stops the loss from accumulating.
PNG also carries an alpha channel, which matters if the source has transparency. Most iPhone camera photos do not, but HEIC files exported from apps sometimes do, and converting those to JPG would silently composite them onto white.
Expect large files. PNG is lossless, so a 12-megapixel photo that was 2 MB as HEIC will typically land somewhere between 15 and 30 MB as PNG. That is not a defect — it is what lossless means for photographic content, where almost every pixel differs from its neighbour and there is very little for the compressor to exploit.
Everything runs on this device. The HEIC decoder is libheif compiled to WebAssembly, executing in a Web Worker on this page; no file is sent to a server at any point.
Common questions
- Is PNG really lossless if the HEIC was already compressed?
- The PNG encoding step is lossless — it stores exactly the pixels the decoder produced. It cannot undo the compression that already happened inside the HEIC. What it does is guarantee that no further loss is added, which is the point when the file will be edited and re-saved.
- Why is the PNG so much bigger than the HEIC?
- Because it is lossless. HEIC discards information the eye is unlikely to miss and gets a very small file as a result; PNG discards nothing. For photographic content the ratio is commonly ten to one or more. If size matters more than fidelity, convert to JPG instead.
- Are the files uploaded?
- No. Decoding and encoding both run in your browser. You can confirm it by watching the Network tab in devtools during a conversion, or by going offline after the page loads — the tool keeps working.
- Can I convert a whole folder at once?
- Yes. Drop in as many files as you like and they are processed in parallel across your CPU cores. Results come back as a ZIP, or, in Chrome and Edge, can be written straight into a folder you choose.
This converter is part of a full editing pipeline — tone, colour, lens correction and batch export all run the same way, without uploading.
Open the full pipeline