Is HEIC to HEIF only a filename change?+
HEIF is a container framework; HEIC identifies a commonly used HEVC-coded image convention. Moving between these names does not inherently require changing decoded pixels, but is not guaranteed by renaming a file. The future engine must inspect image items, brands, codec configuration and dependencies before deciding whether to repackage or transcode.
Will every source image be exported?+
HEIC can contain multiple image representations with different roles. These are not automatically a timed animation. Selecting an image, preserving a collection or creating several outputs needs explicit engine support; neither a first-image choice nor an all-images export is implemented.
Can the animation be transferred between formats?+
HEIC and HEIF can represent image animation, but their frame structures are not interchangeable. Retaining motion requires sequence decoding, compositing, timing and loop mapping plus an animation-aware encoder. No such transfer is implemented; a still-only pipeline would lose the sequence.
Are bit depth and colour values guaranteed to match?+
Source and target sample models can differ in precision, channel layout, colour space and transfer function. Lossless compression only preserves the samples actually encoded; a precision reduction or colour conversion can already change them. The future engine defines numeric mapping, orientation and colour conversion; canonical depth facts are listed below where available.
Will metadata and colour profiles be retained?+
HEIC: Exif, XMP, ICC, NCLX → HEIF: Exif, XMP, ICC, NCLX. Which fields are copied, rewritten or omitted will depend on the future engine; retention is not implemented yet.