Choose PNG when the decoded pixels are the useful result
HEIC to PNG creates a local PNG copy from a supported primary still image in a HEIC or HEIF container. It is useful when a receiving application needs PNG, when supported transparency matters or when you want to avoid a new lossy JPEG encoding after decoding. Keep the original HEIC if you need its original samples, capture metadata or container features.
The phrase “lossless PNG” applies to encoding the resulting decoded pixel grid. It does not mean that the entire HEIC file has been preserved without change. Decoding, orientation, color handling and the browser's working representation happen before PNG encoding. Those steps can differ from a specialized high-depth photographic workflow.
Begin with a supported still container
Choose a HEIC or HEIF file and read the preflight. The container's actual structure matters more than its name. HEIF can hold multiple images and other related data, while this conversion has a narrower primary-still-image scope. It is not an export of every frame, depth map or auxiliary item that the format might permit.
The tool first tries native decoding and can load its reviewed local libheif fallback when needed. That processing stays in the browser. Codec code is downloaded from the site as an application resource, so a first use can need a network connection even though the photograph is not uploaded for conversion.
A source that is outside decoder or resource support may be refused. Do not turn a refusal into an assumed success by saving a displayed preview under a different extension. A supported still conversion should report and verify the actual output format and dimensions of the generated bytes.
PNG does not have a photographic quality slider
PNG stores the new pixel grid without a lossy quality setting in this workflow. There is therefore no JPEG-style percentage to adjust on this page. If the output is large, that can be a normal consequence of storing a detailed photograph with a different compression model rather than evidence that something went wrong.
For a photographic email attachment, JPEG may be more convenient if transparency and another lossy generation are acceptable. For a web destination accepting WebP, that format may offer another tradeoff. Choose HEIC to JPG or HEIC to WebP according to the recipient's actual requirements rather than treating PNG as automatically preferable.
A PNG also cannot repair details lost before the HEIC reached you. It preserves the decoded representation it receives, including any existing artifacts. If a source is blurred, noisy or previously compressed, its new extension does not establish a better photograph. Keep that distinction clear when sharing a converted file as part of an editing handoff.
Transparency and color are separate properties
PNG can carry alpha from a supported decoded image. Inspect the output against a contrasting background if that property matters. A transparent-capable format does not automatically remove an opaque background, and a checkerboard in a viewer is only a way of displaying transparent pixels.
Color requires its own caution. The source ICC profile is not preserved, and the supported browser/codec workflow produces an SDR canvas representation. A PNG file can support richer sample representations elsewhere without this tool promising universal high-depth, HDR or wide-gamut retention. Lossless encoding at the final stage does not undo earlier representation changes.
For a professional master, retain the original and use the color-managed application required by the receiving workflow. A PNG compatibility copy can sit alongside that master. Avoid describing the copy as a complete preservation of the original capture, especially when the source carries HDR presentation information or camera-specific metadata.
Orientation should match the intended photograph
The conversion uses decoded visual orientation rather than copying the source orientation field as an independent instruction. Check a recognizable feature in the generated image: readable text, a horizon or the top of a person. Width and height can change with orientation, so compare them with the displayed result rather than an assumption based on the filename.
An image that is upright in one preview can still need checking in the recipient's application. The purpose of a compatibility copy is that it works where it is needed. Open the actual downloaded PNG there when possible, rather than relying on the browser preview as universal proof.
If a converted photograph needs cropping or a specific output size, save the accepted PNG first and use the corresponding image tool deliberately. Tools do not transfer the selected source automatically. A later resize creates another pixel grid, so it is another transformation to review rather than a metadata-only action.
Respect the memory boundary
Configured input admission is 20 MiB, 16 megapixels and 8,000 pixels per edge. These checks apply together with finite decoder and working-memory budgets. HEIC's efficient storage can disguise how large its decoded image is, and PNG output may require substantially more disk space than the source.
These ceilings do not establish that every maximum workload works on every device. A supporting browser and enough available resources are still required. The quality of the source photograph and its compatibility are separate from whether the current memory plan can admit it safely.
Keep the delivered copy easy to verify
Read the actual format, dimensions and byte count, then download and reopen the result. Confirm visual orientation, transparency where relevant and the detail the recipient needs. A browser beginning a download does not prove that the file finished saving to disk.
Source identifying metadata is not copied, but visible private information remains in the image. Use Image Inspector for supported output metadata and review the frame yourself before sharing. Keep the original HEIC and label the PNG as a converted copy when provenance matters; a useful delivery format should not be mistaken for an unchanged source.