HEIC compatibility

Handle HEIC and HEIF photos without losing the source

HEIC and HEIF containers may hold more than one image plus metadata. A compatibility export usually targets the primary still; it is not a complete migration of every item in the container.

Workflow

  1. Preserve the original container

    Duplicate or back up the HEIC file before conversion, especially when it may include edits, bursts, depth information, or a paired Live Photo video.

  2. Choose the needed destination

    Use JPG for broad photo compatibility or PNG when a lossless pixel export is worth the larger file, then let the dedicated local decoder process a bounded batch.

  3. Compare in the target environment

    Open the output beside the source on a color-managed device and confirm orientation, crop, dynamic range, dimensions, and the chosen still frame.

Limits to understand

A still-image conversion may omit auxiliary images, Live Photo video, depth maps, edit history, HDR gain maps, location data, and some wide-gamut color information. Browser memory can limit large batches.

Privacy mode

The dedicated decoder is loaded into the browser only when needed, and selected files remain local for the supported conversion. The separate module's license is disclosed in third-party notices.

Verify the result

Check output dimensions and orientation, inspect highlights and skin tones, confirm the intended frame was exported, and keep the HEIC original whenever its container features could matter later.

Frequently asked questions

Will a converted JPG keep my Live Photo?

No. JPG stores one still image. Preserve the original HEIC and its paired video if motion or capture context matters.

Why can two viewers show different colors?

HEIC may use wide-gamut or HDR information that a destination format, browser, display, or viewer handles differently. Compare in the final destination.

Editorial review