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 WebP 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.
How will HDR brightness be mapped?+
If HDR source content is exported through an SDR representation, it needs a display rendering. Values outside the output range require tone mapping, scaling or clipping; brightness relationships can change. Tone mapping, exposure and colour handling depend on the future engine. Renaming or lossless compression cannot preserve out-of-range values.
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 → WebP: Exif, XMP, ICC. Which fields are copied, rewritten or omitted will depend on the future engine; retention is not implemented yet.