Convert HEIC to PNG
Lossless, local, and honest about the file size that costs you.
Runs in your browser0 bytes uploadedLossless, local, and honest about the file size that costs you.
Runs in your browser0 bytes uploadedDrop your HEIC photos here
or paste Ctrl+V
Nothing is uploaded. The photos are converted to PNG inside this tab — including the GPS coordinates an iPhone writes into every one of them.
For a photo out of a camera, JPG is almost always the right choice: Convert HEIC to JPG.
Browsers without built-in HEIC support decode with libheif, self-hosted here under the LGPL-3.0-only license. Source: github.com/strukturag/libheif.
There is a specific set of reasons to want PNG, and they are worth checking against before you run anything. A design tool or an editing pipeline that refuses lossy input. A system that accepts PNG and nothing else. A screenshot or a graphic that was saved as HEIC and has flat colour or sharp edges, where a lossy re-encode would visibly smear the text. An image with an alpha channel you need to keep.
If none of those describe your file — if it is simply a photograph out of a phone — then JPG is the better answer and the tool says so above the button rather than after the download. Nothing here tries to talk you out of a conversion you have a reason for. It just refuses to pretend the trade does not exist.
PNG stores every pixel exactly as it was decoded. HEIC and JPEG both discard detail your eye is unlikely to notice, which is how twelve megapixels fit into two megabytes. Take that away and the same photo lands somewhere between eight and fifteen megabytes, often more.
The estimate appears before the conversion, not after it. It is given as a range rather than a single number, because the real figure depends on how much detail the photograph contains — a flat sky compresses far better than foliage — and a precise-looking guess would be a confident lie. Once the batch is done you get the actual before and after for every file plus a total, so you can see how close the estimate came.
PNG carries an alpha channel and this conversion keeps it. In practice that matters less often than people expect: photographs taken with a phone camera have no transparency to preserve, so for a normal camera roll the alpha channel is simply unused bytes. HEIC files exported from editing software can carry one, and those are the files where converting to PNG rather than JPG is unambiguously correct.
When there is no transparency in the source, the receipt says so instead of implying that something was preserved. The same goes the other direction on the JPG side: transparent areas there have to be flattened onto white, which is a real loss and gets stated plainly.
Lossless has no quality setting. Every converter that shows you one for PNG is either controlling the compression effort — how long the encoder thinks, not how the image looks — or quietly quantising the colours down to a palette, which is no longer lossless. Rather than offer a control that does nothing, or one that does something other than what it says, there is no slider here at all.
What you do get is a limit on the longest side. Scaling down is honest: it changes the image in a way you asked for and can see. If the file needs to be smaller and the pixels need to stay, the answer is not PNG.
Decoding and encoding both happen on your own machine, in a background worker so the page never freezes. In Safari on a Mac or an iPhone the system's own HEIC support does the decoding and nothing is downloaded at all. In Chrome, Firefox and Edge a decoder is fetched once and cached, with the real byte count on the progress bar.
That is worth more here than the convenience. A HEIC out of an iPhone carries the GPS coordinates of where the picture was taken, and a converter that uploads has already received them by the time it strips anything. PNG output on this page carries no EXIF at all, so the location is gone either way — but the file never left the machine to begin with.
Because PNG never throws anything away. HEIC and JPG both discard detail your eye is unlikely to miss, which is how a 12-megapixel photo fits in two megabytes. PNG stores every pixel exactly, so the same photo lands somewhere between eight and fifteen megabytes. That is not a fault in the conversion — it is what lossless means.
For a photograph, usually not. PNG earns its size on screenshots, logos, diagrams and anything with flat color or a transparent background. For a picture taken with a camera, JPG gives you a file a fraction of the size that nobody can tell apart. Convert to JPG instead unless you have a specific reason — an editing pipeline that demands lossless input, or a system that only accepts PNG.
If the HEIC had an alpha channel, yes. Photos taken with an iPhone camera do not have one, so in practice this matters for HEIC files exported from editing software. When there is no transparency to keep, the tool says so rather than implying it preserved something.
No. The decode and the PNG encode both happen in this tab, which is why there is no queue and no file limit beyond your own device memory. The photo — and the GPS coordinates an iPhone writes into it — never leave your machine.