Good for
Common use cases
HEIC is what iPhones save photos as by default — Apple shipped HEIC as the iOS 11 capture format in September 2017 — and it stores roughly the same image quality as JPEG at about half the file size. The trade is portability. HEIC travels cleanly inside Apple's ecosystem and through the iOS Share-sheet's automatic JPEG fallback, but the moment a saved HEIC file leaves that path it lands in front of older Office builds, design tools that pre-date late-2020, marketplace upload flows, and Windows installs where HEIC support depends on Microsoft's HEIF Image Extensions (which is not always present on enterprise or older builds — Microsoft's own OneDrive guidance acknowledges that machines may need additional HEIF/HEVC components or apps before HEIC media renders). The sibling tool HEIC to JPG handles the photographic-content default cleanly. HEIC to PNG is the right target when the destination wants a raster format that does not add another lossy quantisation step on top of the source HEIC — design hand-offs into tools that read PNG more reliably than HEIC, or downstream pipelines where you want to avoid stacking a JPEG re-encode after the HEIC's existing compression. PNG via canvas.toBlob is lossless for the decoded canvas pixels, so no further compression artefacts are introduced; the encoded PNG does not, however, carry the source HEIC's embedded colour profile, EXIF, or container metadata, so if any of those matter to your workflow keep the original HEIC alongside as the archival master. The conversion happens in the browser tab — the HEIC source never leaves the device, the PNG materialises locally, and the only network traffic is the page load itself.
Processing mode
Browser-local
Files are processed by your browser. They never reach our servers.