HEIC to JPEG or PNG: choose compatibility without pretending nothing changes

Choose an output for the destination

JPEG is usually the practical choice for photographs because it is widely supported and compact. Its compression is lossy, so repeated conversion or aggressive quality settings can soften edges and introduce artifacts.

PNG stores pixels losslessly and can preserve transparency when present, but a photographic PNG may be much larger. Choosing PNG does not recover detail that was not decoded from the HEIC source.

HEIC can contain more than one flat image

HEIC containers can include sequences, auxiliary images, depth information, thumbnails, and metadata. A browser converter may expose only the primary decoded image.

Treat the result as a compatibility copy. Preserve the original when motion, depth effects, editing history, wide color, or device-specific information matters.

Color and orientation need visual comparison

Color profiles and high-dynamic-range information do not always map identically to JPEG or PNG in every browser and viewer. Compare skin tones, gradients, shadows, and saturated colors in a color-managed application.

Check dimensions and orientation as well. Metadata transfer is not guaranteed, and some viewers rely on orientation information differently.

Manage memory deliberately

Decoding large photographs creates substantial pixel buffers. Batch conversion adds output Blobs and ZIP assembly, so memory use can exceed the compressed file sizes by a wide margin.

On a constrained device, convert individually, close other heavy tabs, and download before starting the next file. A failure on one HEIC does not prove that all files from the device are unsupported.

Treat conversion as delivery preparation, not archiving

Keep the original HEIC when it is the camera’s primary copy. A JPEG or PNG export is useful for delivery to a service that cannot open HEIC, but it may not retain every frame, depth map, edit instruction, profile, or metadata block from the source container. Compare representative colors, highlights, shadows, orientation, transparency, and dimensions in the destination application rather than only in the browser preview. Name the converted copy so its format and purpose are obvious. If future editing, printing, or evidence preservation matters, archive the untouched original beside the reviewed compatibility copy.

What the browser does

heic2any receives the browser Blob and decodes it locally. The tool converts the returned Blob or first Blob from a multi-result response into a downloadable object URL.

The conversion file is not sent to a LocalUtils conversion server. Object URLs are revoked as results are replaced or the component is cleared to avoid retaining unnecessary browser memory.

Inputs and outputs

• Input: HEIC or HEIF files that heic2any can decode in the current browser.
• Output: JPEG or PNG, with batch results packaged as ZIP when available.
• JPEG uses lossy compression; PNG is lossless but can be much larger for photographs.

Verification checklist

• Compare pixel dimensions and orientation with the original.
• Zoom into detailed and high-contrast areas to judge JPEG artifacts.
• Open the result in the exact website or application that required conversion.

Troubleshooting

• If conversion fails, test a different HEIC from the same device to distinguish file damage from format support.
• If colors differ, compare in color-managed applications and keep the original.
• If the browser becomes memory constrained, convert files individually and close other large tabs.