Why HEIC to PNG Conversion Exists
HEIC (High Efficiency Image Container) became the default camera format on iPhones with iOS 11. It uses the HEVC (High Efficiency Video Coding) codec to compress photos to roughly half the size of an equivalent JPEG at the same visual quality. That storage saving is valuable on a phone, but HEIC has poor support outside Apple’s ecosystem. Many web platforms, content management systems, desktop applications, and older devices cannot open or display HEIC files. PNG, by contrast, is a universal format supported by every modern browser and image editor.
This page is the only one on the site that specifically converts from HEIC to PNG. A sibling page handles HEIC to JPG, and its interface differs—for example, the JPG version includes a quality slider because JPEG is lossy. Here, because PNG is lossless, there is no quality control; the page shows a short hint that PNG is lossless instead. The conversion is straightforward: decode the HEIC’s compressed pixel data and re-encode it using PNG’s lossless compression. The result is a faithful reproduction of the decoded image, but with a file size that can be dramatically larger for photographs.
What Happens When You Convert HEIC to PNG
PNG uses lossless compression. Every pixel from the HEIC file is copied exactly; no information is discarded. For a typical iPhone photo—about 2–3 MB as HEIC—the PNG output can easily be 15–20 MB. The exact ratio depends on the image’s complexity: smooth areas (sky, walls) compress well, while fine detail (grass, foliage) does not. The tool shows a “Larger” label next to the converted size when it exceeds the original, and a “Saved” label when it shrinks (rare for photos, but common for screenshots and computer-generated graphics with large uniform regions).
For screenshots, line art, and logos, the original HEIC is often already close to the size of a PNG. In those cases the conversion may produce a file that is slightly smaller or nearly identical—no quality loss either way. The table below summarizes typical size behavior:
| Original content | Typical HEIC size | Typical PNG size | Label shown |
|---|---|---|---|
| Photo from iPhone camera | 2–5 MB | 10–25 MB | Larger |
| Screenshot (UI, text) | 200–500 KB | 150–400 KB | Saved or Larger |
| Logo / flat graphic | 50–200 KB | 50–250 KB | Saved or Larger |
In practice there is usually no transparency to preserve: iPhone HEIC photos are opaque. If the HEIC contains a depth map or HDR metadata, that information is not carried into the PNG output—the tool converts only the base color image.
When to Choose PNG Over Other Formats
PNG is the right choice when you need lossless quality and full 8‑bit alpha transparency. No other widely supported format offers both. JPEG drops information every time you save; WebP and AVIF can be lossless but are not as universally supported as PNG, and many older systems still treat PNG as the safe bet.
Common use cases:
- Logos and icons – Transparency is essential for overlaying on different backgrounds. JPEG does not support it, and iPhone HEIC photos never carry it.
- Screenshots of text or UI elements – Lossy compression introduces ringing and blur on sharp edges. PNG keeps every pixel crisp.
- Images that will be edited repeatedly – Each re-save of a JPEG degrades quality. A PNG survives unlimited edits.
- Archival copies – If you remove the original HEIC and keep only a PNG, you have a master that can be copied and converted to any lossy format later without generational loss.
If you do not need transparency and can tolerate some quality loss, the JPG version of this converter will give you a much smaller file. The choice is a direct trade‑off between file size and fidelity.
How This Tool Works: Client‑Side Conversion
All processing happens entirely in your browser: the browser decodes the HEIC file into pixels and re-encodes them as a PNG right on your device. No data is uploaded to the BroBroGo server—your files never leave your device. This is critical for privacy: HEIC photos from iPhones often contain location metadata and faces. A server‑side converter would have to receive those bytes; this tool does not.
You can convert up to 20 images at once. Selecting more produces the message: “Choose up to ‹max› images at a time.” With no image added, the convert button simply stays disabled. Dropping a file type that is not supported triggers: “This file type isn’t supported.”
Because conversion depends on browser capability, very old browsers may fail to decode HEIC. In that case the error reads: “This file could not be opened as an image. It may be corrupted, empty, or not actually an image.” If the file is genuinely corrupted or empty, the same message appears. If decoding succeeds but the PNG encoding fails, the tool shows: “Conversion failed. Try a different image or format.”
Batch Conversion and Download Options
After conversion, each image is displayed with its output filename, dimensions, original file size, converted file size, and a “Saved” or “Larger” label. A total line sums the change: “Total: ‹original› -> ‹converted›”.
- When only one file is converted, you see a single Download button.
- When two or more files are converted, a Download all (.zip) button appears. Clicking it downloads a single ZIP archive — named
brobrogo-converted.zip— containing every converted PNG at the top level of the archive, preserving the original filenames (with the extension changed to.png).
The ZIP archive makes it practical to convert a burst of photos from a trip or a set of screenshots without clicking each one individually. The entire batch is processed sequentially; if some files fail, the tool reports: “‹count› file(s) could not be processed.” The successful ones are still available for download.
Troubleshooting Common Issues
| Error message | Likely cause |
|---|---|
| “This file could not be opened as an image…” | File is corrupted, empty, or not an image. Also occurs if the browser cannot decode HEIC (e.g., Safari on older macOS). |
| “Conversion failed. Try a different image or format.” | The HEIC decoded correctly, but encoding to PNG failed (rare – usually memory-related). |
| “Choose up to ‹max› images at a time.” | You selected more than 20 images. Reduce the number of files. |
| “This file type isn’t supported.” | You dropped a file that is not a HEIC/HEIF image (e.g., a .pdf or .txt). |
| “‹count› file(s) could not be processed.” | Some files in a batch failed. Check each individually. |
If your browser cannot decode HEIC at all, you can try a different browser (Chrome on desktop, Edge, or the latest Safari on macOS 13+). The tool does not fall back to a server-side decoder—privacy demands local processing.
Frequently Asked Questions
Q: Why is my PNG so much larger than the original HEIC?
A: HEIC uses a modern lossy codec (HEVC) that achieves high compression with little visible quality loss. PNG uses lossless Deflate compression, which cannot exploit the same perceptual tricks. A photo that is 3 MB as HEIC will commonly become 15–20 MB as PNG. This is expected and not a bug.
Q: Can I convert a PNG back to HEIC on this page?
A: No. This page reads HEIC and writes PNG only; a sibling page converts HEIC to JPG. Nothing here encodes HEIC. To create HEIC, you would need a different tool—usually found on iOS or macOS.
Q: Does this tool upload my images to any server?
A: No. Everything runs inside your browser. The page never sends your files to BroBroGo or any third party. You can verify this by watching the network tab in developer tools.
Q: Why is there no quality slider?
A: Because PNG is a lossless format. There is no “quality” parameter—every pixel is retained exactly. Quality sliders appear on the sibling pages that output JPG or WebP, because those formats can discard detail to reduce file size.
Q: Can I convert more than 20 images at once?
A: The limit is 20 images per batch. You can run multiple batches back to back.
Q: What happens to EXIF data like GPS location?
A: The converter does not preserve EXIF metadata. The PNG output contains only the raw pixel data. If you need to retain EXIF, you must strip it from a copy of the HEIC first or use a dedicated metadata tool afterward.