What is HEIC?

HEIC is a filename extension for images stored in the High Efficiency Image File Format family. In everyday iPhone use, the image data is commonly compressed with HEVC, the same coding family also called H.265. The container can hold a primary image, thumbnails, depth maps, image bursts, and metadata such as orientation and color information.

That container model is the reason a HEIC photo is not just a renamed JPEG. A decoder needs to understand the box structure and the HEVC image payload. If either layer is unsupported, the file may show as an unknown type even though the photo is valid.

Apple switched the default iOS camera setting to High Efficiency in 2017. The practical goal is smaller storage use while keeping the same visible camera output for most photos. HEIC can also carry features that are awkward for plain JPEG, including Live Photo companion data, alpha channels in some workflows, and depth information used by portrait mode.

The alternative setting on iOS is Most Compatible, which saves JPEG for still photos and H.264 for video. That setting is useful when a workflow includes older web forms, Windows desktops without HEVC support, or software that strips unknown image metadata.

Windows can read HEIF containers only when the needed extensions are installed, and HEVC decoding may require Microsoft’s HEVC extension. Enterprise machines often lack it because codecs are managed centrally. Web support is also uneven, so uploading a HEIC file to an older CMS or form can fail even when the same photo opens in Photos on a Mac.

A quick diagnostic is to inspect the file type instead of trusting the extension. On macOS or Linux, file -I photo.heic reports the media type if the magic bytes are recognized. If the file is actually JPEG data with a wrong extension, conversion is not the right first fix; rename or re-export from the source app.

Convert HEIC to JPG when the destination is a web form, a recipient with unknown software, or a photo archive that prizes broad readability over keeping every camera-side asset. Convert to PDF when the photo is evidence, a receipt, or a scan that should travel as a document page. Use PNG only for images with transparency or screenshot-like graphics, because photographic PNG files can be much larger.

Expect metadata differences. A typical HEIC-to-JPG export keeps pixels and may keep EXIF fields, but depth maps, burst members, and some Apple-specific side data may be dropped. If those extras matter, archive the original HEIC beside the converted copy.

Before emailing or uploading, check the recipient’s required format and maximum size. Some systems list JPG and PNG but reject HEIC silently. Others accept HEIC but generate broken thumbnails because their background processor lacks the codec.

If you batch-convert phone photos, keep filenames stable and decide whether to strip location metadata. A public listing photo and a private insurance photo have different metadata needs. A converter can make the file readable, but the privacy decision belongs before export.

For team workflows, write down whether originals are retained. A converted JPG is easier to open, but it is not the same asset as the HEIC captured by the phone. If the original contains depth data, alternate frames, location metadata, or a wider color profile, a downstream JPG-only archive may no longer contain information someone expects later.

For intake forms, give users the accepted extensions instead of saying “photo.” Many people do not know their phone is producing HEIC files. A clear requirement such as JPG, PNG, or PDF prevents a support case after upload fails.