HEIC to PNG Converter - Lossless, No Upload

Convert iPhone HEIC and HEIF photos to PNG without losing a single pixel. Transparency is preserved, and the decoder runs inside your browser so nothing is uploaded.

What HEIC to PNG Conversion Does

A .heic file is an HEIF container — the ISO High Efficiency Image File Format — holding a picture compressed with HEVC, the codec built for 4K video. Converting to PNG means decoding that HEVC bitstream all the way back to raw pixels and then re-compressing those pixels with PNG's DEFLATE, which is lossless. That distinction is the whole reason to pick PNG here. The decoded pixels coming out of the HEIC file are written into the PNG unchanged, so the conversion introduces no generation loss whatsoever: no blocking, no ringing around hard edges, no colour smearing, no quality slider to second-guess. Convert the same file a hundred times and every output is byte-identical. PNG is also the only one of the three common targets that carries an alpha channel the way HEIF does. If your HEIC holds a screenshot with rounded transparent corners, a sticker, an exported logo, or anything else with genuine see-through regions, PNG keeps those pixels transparent. JPG has no alpha at all and would flatten them onto a solid background. The decode happens on your own device using libheif compiled to WebAssembly — the first conversion spends a few seconds downloading and starting that module, and later ones reuse it. Nothing is transmitted anywhere. What PNG will not do is make the file smaller. It is a lossless format applied to photographic data, which is close to a worst case for it, and the honest expectation is an output several times the size of the HEIC input. PNG also does not preserve HEIF's extras: a Live Photo's motion track is dropped and only the still key frame survives, Portrait mode depth maps are discarded, and 10-bit HEIC content is written out at 8 bits per channel. What you get is an exact, universally readable copy of the visible image.

Why Convert HEIC to PNG Instead of JPG

JPG is the right answer when you just need a photo that opens everywhere and you do not mind losing a little. PNG is the right answer when losing anything is unacceptable, or when the picture has transparency to protect.

Keep every pixel exactly as the camera recorded it — nothing is re-compressed away, so the file survives repeated editing and re-saving
Preserve transparency that JPG cannot represent at all, which matters for screenshots, stickers, logos, and exported graphics
Hand a clean, artefact-free source to designers, print shops, and editing software that would otherwise inherit JPG compression damage
Open the result anywhere — PNG has been readable by every browser, operating system, and image editor for over two decades

How to Convert HEIC to PNG

Three steps, all of them on your own device. Your photos are decoded locally and never sent to a server.

1

Add one or more .heic, .heif, or .hif files by dragging them in or using the picker. Each file is verified by its contents, not its extension

2

There is nothing to configure. PNG is lossless, so there is no quality setting to balance and no way to get a worse result by choosing wrong

3

Press convert and watch the per-image counter. The first file is slow while the HEIF decoder loads; the rest are quick

4

Download each PNG on its own, or take the whole batch as a single ZIP. Filenames are kept and only the extension changes

Frequently Asked Questions

Pick PNG when the image has transparency, when it will be edited and re-saved several times, or when it is going to a printer or designer who wants a pristine source. Pick JPG when it is an ordinary photograph headed for email, a web page, or an upload form, and file size matters more than pixel-perfect fidelity. The practical difference is stark: the same HEIC might produce a 900 KB JPG and a 6 MB PNG that most people cannot tell apart on screen. PNG is worth that cost only when losslessness or alpha actually buys you something.
Because PNG is lossless and HEIC is not. HEVC compression achieves its small files by discarding detail your eye is unlikely to miss; PNG's DEFLATE compression is required to reproduce every pixel exactly and so has far less room to work with. Photographic content, full of fine noise and gradients, is close to the hardest case for lossless compression. Five to ten times the original size is normal and larger ratios are not unusual. Nothing has gone wrong and no data has been added — the resolution is identical. If you want a smaller file, convert to WebP instead, which is close to HEIC in efficiency.
Yes. HEIF can store an alpha channel and PNG can too, so transparent regions are carried across intact rather than being flattened onto white or black. This is the main functional reason to choose PNG over JPG, which has no alpha channel whatsoever and would replace every transparent pixel with a solid colour. Most iPhone camera photos are fully opaque and gain nothing from this, but screenshots, stickers, and images exported from design apps often do carry real transparency.
None at the PNG stage. The pixels decoded from the HEIC are written into the PNG unchanged, which is what lossless means, and re-converting the same file always produces identical output. That is why this page has no quality slider — there is nothing to trade off. The one caveat worth stating is that quality already lost when your camera encoded the HEIC cannot be recovered by converting to a lossless format afterwards. PNG preserves exactly what is in the file; it does not improve it.
No. The HEIF decoder is a WebAssembly build of libheif that runs inside your browser tab. Your file is read into memory on your own device, decoded there, and handed straight back to you as a download. Nothing is transmitted, which matters more than usual for camera-roll photos that are personal and often carry location data. It also means the tool keeps working with no network connection once the page has loaded, and the practical batch limit is your device's memory rather than an upload cap.
Decoding HEIF requires libheif, a substantial C library compiled to WebAssembly. It has to be downloaded and instantiated before the first image can be decoded, typically two to five seconds depending on your connection and device. Once loaded it stays in memory for the rest of your visit, so later images convert far faster. Images are processed one at a time on purpose: a decoded photo occupies a lot of wasm memory, and running a whole batch in parallel would multiply peak usage and can crash the tab on a phone.
Yes. Add as many as you like and they are converted one after another, with an on-screen counter showing which image is being decoded. When the run finishes you can download each PNG individually or take the whole batch as a single ZIP. Each output keeps its original filename with only the extension swapped, so IMG_1234.heic becomes IMG_1234.png and your photos stay in the same order in a folder. Be aware that PNG output is large, so a big batch of camera photos can add up to hundreds of megabytes.
Only the still image survives, exactly as with any other target format. A Live Photo's motion is stored as a separate video track and is discarded, leaving the key frame. Portrait mode depth maps, which editing apps use to recalculate background blur, are dropped — you keep the blur already baked into the picture but can no longer adjust it. PNG's losslessness applies to the pixels of the still image, not to the extra tracks the HEIF container can carry alongside them.

更多图片工具

探索其他强大的图片编辑工具