Losslessness is the whole reason to choose PNG here
Most people converting an iPhone photo want a JPG, and for sharing or uploading they are right. This page exists for the smaller set of cases where the next thing that happens to the image is not viewing but work: retouching, layering into a design file, running through a batch process, or handing to a system that will re-save it several times before anyone looks at it.
JPEG loses a little on every save. That is not a flaw so much as the deal it offers, and it is invisible once. Six saves later, on a photo that has also been cropped and colour-corrected in between, it is not invisible at all. PNG makes a different offer: store the pixels exactly, take whatever space that needs. Once the HEIC has been decoded, a PNG holds that decode verbatim and every subsequent PNG save holds it verbatim again.
The second reason is duller but at least as common. A great many upload forms, print templates, CMS fields and internal tools simply require a .png file and will not take anything else, and no argument about formats will change their validator’s mind.
Alpha channels, and why a camera HEIC has none
PNG is often chosen for transparency, so it is worth being clear that there is none to preserve here. A photo taken by the iPhone camera app is a fully opaque rectangle; the HEIC container can hold an auxiliary alpha or depth image, but the primary picture that gets decoded has every pixel opaque. The PNG this tool writes is opaque too.
Nothing has been lost in that exchange, because there was never any transparency to lose. If what you actually want is a cut-out with a transparent background, that is a separate operation: convert here, then remove the background with a tool built for it.
Expect a much larger file than the HEIC
Be ready for the size. HEVC, the codec inside a HEIC, is one of the most efficient still-image compressors in wide use, and PNG’s lossless compression cannot compete with it on photographic content, because a photograph contains almost no exactly repeating patterns for a lossless scheme to collapse. The output will typically be several times the size of the input, and on a high-resolution photo it can be dramatically more.
That is the trade you are choosing on purpose. When it turns out to be the wrong trade, HEIC to JPG produces a far smaller file with a quality setting, and the comparison between the two routes is covered in what changes when you convert HEIC to JPG.
Converting a batch of HEIC files to PNG
- Drop your HEIC or HEIF files into the box above, or use Choose files. The batch builds up across drops, with duplicates filtered out by name and size.
- Click Convert HEIC to PNG. There is nothing to configure: PNG has no quality parameter, so every decoded pixel is written out as it is.
- Watch the progress bar, which moves through each photo in turn as libheif decodes it and the browser encodes the PNG.
- Download each result. The name is preserved with a
.pngextension in place of the old one.
When the PNG is a stepping stone
Often this conversion is a middle step rather than a destination, and it helps to plan the whole route. If the PNG is heading somewhere with a size limit, Optimize PNG shrinks it where it can without altering a single pixel, and returns your original bytes when it cannot, and Resize Image will cut the dimensions if the resolution is more than the destination needs. If it is going into a document, PNG to PDF takes it from there.
It is also worth knowing that HEIC is not a format every page here reads. Plenty of the image tools expect an ordinary JPG, PNG or WebP and will refuse a HEIC at the dropzone before any work starts, so a conversion is often the unavoidable first step in a longer pipeline rather than an optional extra. Each tool prints the extensions it takes in its own dropzone line, which is the quickest way to check the route before you commit to it.