HEIC to PNG

When you need transparency or a lossless copy.

Nothing is uploaded

Drop files here, or click to choose

Accepts HEIC, HEIF. No size limit, no sign-up.

    Turn HEIC files from your iPhone into PNG without uploading them. Choose this over HEIC to JPG when the image has a transparent area, or when it is going into an editing chain and you do not want to add another round of lossy compression.

    PNG or JPG — pick deliberately

    For an ordinary photograph, JPG is almost always the better target. PNG stores every pixel exactly, and photographic detail is close to incompressible that way. In our own measurements a 1600×1000 photographic image is 848 KB as an optimised PNG and 72 KB as a quality-75 JPG — more than eleven times larger for no visible gain.

    PNG earns its size in two situations. The first is transparency: HEIC can carry an alpha channel and JPG cannot, so a cut-out or a sticker exported from an iPhone would lose its transparent background on the way to JPG. The second is editing: PNG is lossless, so re-saving it repeatedly during a workflow never degrades the pixels.

    What "lossless" does and does not mean here

    The PNG side of this conversion is lossless — every pixel that comes out of the HEIC decoder is stored exactly. But HEIC itself is a lossy format, so the pixels being preserved already went through compression when your iPhone wrote the file. PNG freezes them perfectly; it cannot recover detail HEVC discarded at capture.

    The practical upshot is that HEIC to PNG is a good "stop the bleeding" move before editing, and a poor choice if your goal is simply a smaller, more compatible file.

    The PNG we produce is optimised, not just written

    Most browser-based converters encode PNG by dumping raw RGBA through a generic encoder. That produces a technically valid file that is often several times larger than it needs to be — on a flat-colour test image we measured a naive encode at 410 KB where the source was 92 KB.

    Breezo runs the encoded PNG through oxipng, a lossless optimiser compiled to WebAssembly, before handing it to you. It picks better filters and strips redundant chunks without altering a single pixel. On that same test image the optimised result was 47 KB — half the size of the original file, with identical pixels.

    Nothing leaves your device

    The HEIC decoder, the PNG encoder and the optimiser are all WebAssembly modules that run inside this browser tab. Your photo is read from disk by the file picker and never travels further.

    That is also why there is no size cap, no hourly quota and no account here. Open DevTools, watch the Network tab, and convert something — no request carries your image.

    Frequently asked questions

    Should I use PNG or JPG for iPhone photos?

    JPG for ordinary photographs — it is dramatically smaller with no visible difference. PNG only when the image has transparency, or when it is about to be edited repeatedly and you want to avoid compounding lossy compression.

    Does converting to PNG improve the photo?

    No. HEIC is already lossy, so the detail discarded when your iPhone saved the file is gone. PNG preserves what remains exactly, but it cannot restore anything.

    Why is the PNG so much bigger than the HEIC?

    HEIC uses HEVC compression, which is extremely efficient on photographs. PNG is lossless and stores every pixel, so photographic content typically expands by an order of magnitude.

    Is the transparency preserved?

    Yes. PNG has a full alpha channel, so any transparent area in the HEIC survives the conversion intact.

    Is my photo uploaded?

    No. Decoding, encoding and optimisation all run in your browser using WebAssembly. You can verify it in the DevTools Network tab.

    Other tools