HEIC

No — convert for long-term storage. The core risks are patent/licensing fragility around HEVC (multiple competing patent pools) and near-total lack of non-Apple browser support, so most DAM ingest pipelines auto-convert HEIC to TIFF or high-quality JPEG on upload.

No — Chrome, Firefox, and Edge do not render HEIC inline in any version, because HEIC's pixel data is HEVC-encoded and HEVC's patent licensing has been fragmented across multiple competing pools, which has kept browser vendors from shipping native decode support for roughly a decade. Safari and Apple's own apps remain the only major browser-level renderer; everywhere else, a DAM must serve a converted preview instead of the original file.

EXIF is embedded inside the ISOBMFF container (structurally different from JPEG's APP1 header but data-compatible with standard EXIF readers), and XMP is stored as an item with MIME type application/rdf+xml; IPTC data typically travels via XMP.

HEIC has been the default photo-capture format on any iPhone with an A9 chip or later since iOS 11 shipped in autumn 2017, and it remains the default today unless a user manually switches Camera settings to 'Most Compatible' (JPEG). Because most people never change that setting, any DAM ingesting phone-shot photography — client deliverables, field photos, user-generated content — will see a steady stream of HEIC files arrive without anyone choosing the format deliberately.

Some third-party HEIC-to-JPEG converters silently drop EXIF or XMP during transcoding, so a DAM's ingest pipeline needs to verify metadata survives the conversion rather than assume it does. Because HEIC supports a wider color gamut and higher bit depth than JPEG's 8-bit/sRGB ceiling, a naive conversion can also clip color or introduce visible banding in wide-gamut source images. Ingest pipelines should log conversion failures and metadata mismatches rather than fail silently, so gaps surface before assets reach production.

Roughly 40–50% smaller files at comparable visual quality, plus higher bit depth — up to 16-bit per channel versus JPEG's 8-bit — and wider color gamuts such as Display P3, versus JPEG's 8-bit/sRGB ceiling. HEIC also supports alpha-channel transparency and can hold multiple images plus thumbnails in a single container. For a DAM, these gains only matter where HEIC is actually decoded and displayed; converted JPEG derivatives lose the bit-depth and gamut advantage.

Yes — HEIF, the ISO/IEC 23008-12 container HEIC is built on, is based on the same ISO Base Media File Format that underlies MP4, and it can store both single images and sequences: individual frames as items, and time-based sequences such as bursts as tracks. In Apple's implementation, a Live Photo is technically a still image paired with a short linked video clip rather than frames inside one file, but burst shots can live together in a single HEIC container.

Server-side thumbnail and preview generation requires an HEVC-capable decoder, typically via libheif (the open-source reference library for HEIF), which not every imaging stack ships with by default — ImageMagick and similar tools often need it compiled in as a separate dependency rather than bundled out of the box. Without that decoder present, ingest either fails outright or falls back to a generic file-type icon, so DAM administrators should confirm HEIF/HEVC decode support explicitly before relying on automatic preview generation.