Convert HEIC to PNG online, free

None of this means PNG is a bad format. It is excellent at what it was built for. It just rarely lines up with what an iPhone camera produces, which is the heart of this page.

The file-size cost, in plain numbers

The single most important thing to understand before converting is how much the file grows. HEIC and JPG both compress photographic detail aggressively, while PNG refuses to lose any of it. The gap that creates is dramatic for photos.

A typical 2 MB HEIC snapshot lands somewhere between 10 and 20 MB as a PNG, and a high-resolution shot can go higher still. The same photo saved as JPG would usually sit at 3 to 5 MB. So choosing PNG over JPG for a normal photo can multiply your file size by five or more, with no difference you could spot on any screen.

That matters in practice. A handful of PNG photos can be too large to email. A batch of them downloads slowly and fills storage fast. If you ever plan to put the image on a website, a multi-megabyte PNG photo is the kind of thing that drags page load times down and burns bandwidth.

If your goal is simply to open or share an iPhone photo somewhere that cannot read HEIC, do not convert to PNG. Convert it to JPG instead, which is small, universal, and made for photographs. PNG is the right tool only when one of the specific reasons below applies.

When HEIC to PNG is genuinely the right move

The first solid reason is a system that demands it. Some applications, design tools, and upload forms accept PNG and nothing else, or treat PNG as their preferred import. When a piece of software draws that line, you convert to PNG regardless of size, because compatibility with the destination is the whole point. In that situation the large file is simply the cost of admission.

The second reason is a lossless working copy for editing. If you are going to open an image, edit it, save, reopen, and save again, every JPG re-save nudges the quality down a little because JPG is lossy. PNG does not degrade across repeated saves. Converting your HEIC to PNG once gives you a stable working file you can hammer on without watching it slowly soften, which is valuable for layered edits, compositing, or precise retouching.

The third reason is the most overlooked: the HEIC is not really a photo at all. iPhones can save screenshots, and you may have HEIC files that are diagrams, charts, or exported graphics full of sharp text and hard edges. For that kind of image, PNG is the correct format and JPG is the wrong one, because JPG's lossy compression smears crisp edges and text into blurry halos. PNG keeps every edge razor-clean.

Notice the common thread. PNG earns its place when something specific forces it, not as a default. If none of these three describes your situation, the larger file buys you nothing, and JPG or WebP is the better destination.

Why there is no quality slider here

On the HEIC-to-JPG tool you choose a quality level, because JPG is lossy and that number decides how much detail survives the re-encode. This tool has no such control, and that is deliberate, not a missing feature.

PNG is lossless by definition. The conversion takes every pixel the HEIC decoder produces and writes it into the PNG unchanged. There is no dial that would make the image look better or worse, because the encoder is not allowed to discard anything in the first place.

That has one practical consequence worth stating plainly: you cannot shrink a HEIC-to-PNG file by lowering quality, because there is no quality to lower. The only way to make the output smaller is to choose a different target format. If a small file matters more than losslessness, that tells you PNG is the wrong pick for this image.

So the mental model is simple. Pick PNG when you specifically need every pixel preserved or the destination demands the format. Pick JPG when you want a small, shareable photo. The absence of a slider here is the format being honest about what it is.

How the conversion runs entirely in your browser

The conversion is the same private decode the HEIC-to-JPG tool uses, just pointed at a different output. A HEIC decoder compiled to WebAssembly loads inside your browser tab and turns the HEIC container into raw pixels. There is no server step anywhere in that pipeline.

Those decoded pixels are drawn onto an HTML canvas at the photo's full original resolution, and the canvas then encodes the image as a PNG. Because PNG supports an alpha channel, any transparency present is carried through, though a normal camera photo has none to carry. Dimensions stay identical to the source; nothing is resized or cropped.

Everything happens locally, which means your photos never travel across the internet. The HEIC files you drop, and the PNGs you get back, both stay on your device from start to finish. There is no upload, no queue on someone else's machine, and no copy of your image left behind on a server.

One hardware note. PNG encoding of full-resolution photos is memory-hungry, more so than JPG, because the uncompressed pixel data and the large output both sit in memory at once. For big batches, a desktop browser like Chrome or Firefox handles the load more comfortably than a phone. If a mobile browser stalls on a large run, split it into smaller groups.

Editing workflows where a lossless PNG pays off

Picture a real editing job. You start from an iPhone HEIC, crop it, adjust the colour, paint out a distraction, and save. Then you reopen it the next day, tweak something, and save again. If your working file is a JPG, each of those saves runs the image through lossy compression again, and the small losses stack until edges soften and gradients band.

Converting the HEIC to PNG once at the start removes that decay entirely. PNG re-saves are lossless, so the file on disk after ten edits is pixel-for-pixel as clean as after one. For anyone doing careful retouching, compositing layers, or work that gets revisited over days, that stability is the whole reason to accept the larger file.

The same logic applies when an image is an intermediate handed between tools. If you export from one app and import into another, a lossless PNG guarantees the second app receives exactly what the first produced, with no generational loss in the handoff. That predictability is worth the bytes when the image is still being worked on.

When the editing is finished and the image is ready to ship, the calculus flips. Export the final result to JPG or WebP for sharing and the web, keeping the PNG only as your editable master. The lossless copy is for working, not for delivery.

Screenshots, diagrams, and other HEIC files that are not photos

Not every HEIC on an iPhone is a camera photo. You may have saved screenshots, scanned documents, exported charts, or graphics shared by someone else, all sitting in HEIC. These images are defined by sharp edges and crisp text rather than smooth photographic gradients, and that changes which format is right.

For this kind of content, PNG is the correct destination and JPG is genuinely the wrong one. JPG's lossy compression is tuned for photos and it visibly mangles hard edges, leaving fuzzy halos around text and smeared boundaries on solid-colour shapes. PNG stores those edges exactly, so a converted screenshot stays as readable as the original.

There is a pleasant bonus here too. Graphics and screenshots usually contain large flat areas of a single colour, and PNG compresses those flat regions very efficiently. So a HEIC screenshot converted to PNG is often not the bloated monster a photo would become; it can be perfectly reasonable in size precisely because the content suits the format.

The takeaway is to look at the image before you pick a format. If it is a photograph, lean toward JPG. If it is text, lines, or flat colour, PNG is the right call, and this tool gives you a clean lossless result. If you have a mixed folder of both, the bulk image converter lets you push everything through one format at once, and you can resize the results in pixels afterward if a destination needs specific dimensions.