HEIF to HDR: conversion guide

Source · HEIF
Target · HDR

Drop HEIF files here

or choose files from your device

Converter not available yet

This conversion needs a HEIF/HEVC codec that is not available in this browser engine yet.

  • In your browser
  • No upload
  • Private by design

What happens when you convert HEIF to HDR?

Multiple source images

HEIF 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.

Animation becomes a still

An animated HEIF has a timed sequence; HDR is a still-image destination in this workflow. A still export loses motion and timing. Frame choice, blending and disposal must be defined by the future engine; a first-frame export is not promised.

HDR display encoding

The source can carry HDR information and HDR has HDR-capable variants. Working radiometric values and display-referred HDR are different representations. Range, primaries, transfer function and signalling must be mapped explicitly; the future engine may instead produce SDR. HDR preservation is not promised by format support.

Lossless sample storage

RLE preserves stored RGBE bytes; RGBE quantization is not exact storage of arbitrary float RGB. The .hdr format is distinct from the general concept of HDR photography. HDR can store its supported image samples without lossy compression. This applies after rendering and sample conversion: it does not guarantee preservation of source precision, colour space or document structure, and cannot undo earlier losses.

HEIF

Source

HEIF

High Efficiency Image File Format

Compression: Depends on variantTransparency: YesMetadata: Exif, XMP, ICC, NCLX

An image container for individual pictures, collections and sequences. The codec inside determines compression.

Explore HEIF format →
HDR

Target

HDR

Radiance HDR / RGBE

Compression: LosslessTransparency: NoMetadata: Radiance header, EXPOSURE, FORMAT

Radiance pictures with a shared exponent for high-dynamic-range lighting values.

Explore HDR format →

Is HEIF → HDR right for you?

Good choice when

  • HDR fits your delivery use: Lighting environments & radiometry.
  • You can choose the source image or part needed for delivery.
  • You want a still illustration from an animated source.
  • You need HDR-capable delivery and can validate its encoding and colour signalling.

Probably not when

  • You require a complete collection, page set or multipart round trip.
  • Motion, frame timing or loop behaviour must survive.
  • You require guaranteed scene-linear values or HDR appearance.
  • You need cutouts or translucent edges for compositing.

HEIF to HDR conversion details

Multiple source images
HEIF 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.
Animation becomes a still
An animated HEIF has a timed sequence; HDR is a still-image destination in this workflow. A still export loses motion and timing. Frame choice, blending and disposal must be defined by the future engine; a first-frame export is not promised.
HDR display encoding
The source can carry HDR information and HDR has HDR-capable variants. Working radiometric values and display-referred HDR are different representations. Range, primaries, transfer function and signalling must be mapped explicitly; the future engine may instead produce SDR. HDR preservation is not promised by format support.
Opaque output
If HEIF contains transparency, HDR cannot retain it as transparent output areas. Those pixels need compositing against an opaque background. Matte colour, alpha interpretation and edge treatment are future engine decisions; no background colour is selected yet.
Lossless sample storage
RLE preserves stored RGBE bytes; RGBE quantization is not exact storage of arbitrary float RGB. The .hdr format is distinct from the general concept of HDR photography. HDR can store its supported image samples without lossy compression. This applies after rendering and sample conversion: it does not guarantee preservation of source precision, colour space or document structure, and cannot undo earlier losses.
Sample precision & colour
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.
Metadata & colour
Format support does not guarantee that an export preserves metadata or colour profiles. Retention and colour handling depend on the future converter; its engine is not implemented yet.
Compression
HEIF: Depends on variant → HDR: Lossless HEIF: HEIF defines the container. Compression may be lossy, lossless or uncompressed depending on its codec binding; one global quality or bit-depth value would be misleading. HDR: RLE preserves stored RGBE bytes; RGBE quantization is not exact storage of arbitrary float RGB. The .hdr format is distinct from the general concept of HDR photography.
Transparency
HEIF: Yes → HDR: No
Animation
HEIF: Yes → HDR: No
Colour depth
HEIF: Codec/profile dependent → HDR: 32-bit RGBE / XYZE pixel
HDR
HEIF: Codec/profile dependent → HDR: Radiometric values
Multiple images
HEIF: Collections & sequences
Dimensions
Pixel dimensions, page geometry, rendering resolution, resizing and orientation need explicit converter policies. The future engine has not defined them yet.
Metadata
HEIF: Exif, XMP, ICC, NCLX → HDR: Radiance header, EXPOSURE, FORMAT. Which fields are copied, rewritten or omitted will depend on the future engine; retention is not implemented yet.

Common questions

Will every source image be exported?

HEIF 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.

Will the output keep animation?

An animated HEIF has a timed sequence; HDR is a still-image destination in this workflow. A still export loses motion and timing. Frame choice, blending and disposal must be defined by the future engine; a first-frame export is not promised.

Will HDR automatically survive in HDR?

The source can carry HDR information and HDR has HDR-capable variants. Working radiometric values and display-referred HDR are different representations. Range, primaries, transfer function and signalling must be mapped explicitly; the future engine may instead produce SDR. HDR preservation is not promised by format support.

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?

HEIF: Exif, XMP, ICC, NCLX → HDR: Radiance header, EXPOSURE, FORMAT. Which fields are copied, rewritten or omitted will depend on the future engine; retention is not implemented yet.