Separate HEIF, HEVC, and HEIC
HEIF means High Efficiency Image File Format. ISO/IEC 23008-12 defines a container based on the ISO Base Media File Format. It can store individual image items, image sequences, metadata, thumbnails, and relationships between images. [1] [2] HEIF names the structure around the images, not one universal pixel codec.
HEVC, also called H.265, is a coding format. HEIC is the label users commonly see when a HEIF file carries HEVC-coded image content and uses a .heic extension. Apple describes HEIF as its photo format and HEVC as its video coding format. [3] In practical terms: HEIF is the box, HEVC can compress the picture, and HEIC is a common HEVC-based HEIF flavor.
Read the FileTypeBox before trusting the extension
A HEIF file starts with a FileTypeBox, written as ftyp, that lists a major brand and compatible brands. The structural brands mif1 and msf1 identify HEIF images or sequences. HEVC-specific brands include heic and heix for image items and hevc and hevx for sequences. [2] A filename can be wrong, so a converter should inspect the bytes before decoding.
Brand inspection is a bounded first check, not a full validation. It can show that the container advertises a known HEIF or HEIC profile. It cannot prove that every image item, metadata block, edit, color profile, or sequence will decode correctly. Keep the original until the destination copy has passed a real open or upload test.
Keep the original when the container matters
One HEIF file can contain several images, a primary image, thumbnails, auxiliary images, derived images, image sequences, Exif, XMP, and color information. [2] The libheif reference implementation exposes primary-image selection, multiple images, alpha, depth maps, transformations, Exif, and XMP as separate features. [4] A single flat JPG cannot carry that whole model.
Keep the untouched HEIC when you may need the phone library, original metadata, nondestructive edits, depth information, burst choices, wide-gamut or HDR handling, or paired media later. Store the JPG beside the HEIC and name it as a delivery copy. This preserves a path back to the richer source without asking every recipient to support HEIC.
Create a JPG for an incompatible handoff
Use JPG when a form, support desk, email workflow, or older app explicitly accepts JPEG but rejects HEIC. Apple notes that AirDrop, Messages, or email may send a more compatible format automatically when the receiver lacks support. It also documents manual export to JPEG or PNG and a Most Compatible camera setting for future captures. [3]
A browser conversion should create one normal JPEG still for each input file. It should keep the decoded pixel dimensions, apply the selected JPEG quality, and leave the source untouched. It should also say what it omits: HEIF metadata, extra image items, container relationships, transparency, and any companion Live Photo video.
Verify the JPG instead of assuming it is smaller
Open the imgrove HEIC to JPG Converter with a working copy. Check the reported major and compatible brands, decoded dimensions, selected quality, input bytes, JPG bytes, and percentage change. The converter verifies a JPEG start and end marker before it enables the download.
Compatibility conversion does not guarantee a smaller file. A compact HEIC can produce a larger high-quality JPEG because the codec and encoder changed. Lower quality only after checking faces, text, gradients, and fine texture. Use the Image Size Checker on the downloaded copy, test the real destination, and retain the original HEIC. [4]
Choose whether to keep HEIC or make a JPG copy
| Situation | Use | Verify or retain |
|---|---|---|
| Phone library or long-term original | Keep HEIC | Metadata, edits, extra items, color, paired media |
| Upload form accepts JPG but rejects HEIC | Make a JPG copy | JPEG type, dimensions, byte limit, visible quality |
| Email or support-ticket attachment | Make a JPG copy | Recipient opens it; sensitive metadata is not needed |
| Photo-editing handoff | Keep HEIC or export from the source app | Color, bit depth, metadata, edit requirements |
| Live Photo or paired-media workflow | Keep the original file set | Still image and companion motion remain together |
| Normal website image | Create a delivery copy | Choose JPG, WebP, or AVIF for actual browser support |
Keep the HEIC original when
- The phone library, metadata, edits, or extra image items still matter
- A Live Photo, burst, depth, HDR, or paired-media workflow may continue
- You have not verified that the receiving app accepts the derivative
Create a JPG compatibility copy when
- A form, email path, support desk, or older app explicitly needs JPEG
- The recipient needs one ordinary still and not the HEIF container extras
- You can inspect the output and keep the original beside it
Related phone-photo and delivery format guides
Related imgrove tools
Make and measure a JPG compatibility copy
Convert a working copy locally, inspect its HEIF brands, dimensions, quality, and before-and-after bytes, then test the JPG in the real destination. Keep the HEIC original: this tool exports one still and does not copy metadata, extra image items, transparency, or companion motion.
Try HEIC to JPG ConverterTry the workflow and tell us what worked, what failed, or what needs clearer guidance: hi@imgrove.com.