EXR to HDR: conversion guide

Drop EXR files here

or choose files from your device

Converter not available yet

OpenEXR needs a dedicated floating-point pipeline that is not implemented yet.

In your browser
No upload
Private by design

What happens when you convert EXR to HDR?

EXR channels & deep data

An EXR may carry named auxiliary channels, multipart images or deep samples, beyond a flat RGB image. A rendered HDR copy is not an equivalent EXR working file. Channel selection, deep compositing and numeric mapping need explicit engine support; no export of every channel or depth sample is implemented.

Multiple source images

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

HDR working data

HDR and EXR can represent values beyond ordinary display white, but use different sample encodings. Conversion needs colour and numeric-range mapping; supported channels and precision may differ. In particular RGBE does not carry EXR alpha, arbitrary auxiliary channels, multipart or deep structures. The future engine defines the mapping.

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.

EXR

Source

EXR

OpenEXR

Compression: Lossy & losslessTransparency: YesMetadata: Typed header attributes, Chromaticities

HDR raster data for rendering and compositing, with named channels and lossless or lossy codecs.

Explore EXR 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 EXR → HDR right for you?

Good choice when

HDR fits your delivery use: Lighting environments & radiometry.
You need a rendered view of selected EXR image data.
You can choose the source image or part needed for delivery.
Your pipeline needs an HDR-capable rendered working image.

Probably not when

You need every auxiliary channel or deep sample for compositing.
You require a complete collection, page set or multipart round trip.
You require identical floating-point values or every source channel.
You need cutouts or translucent edges for compositing.

Conversion considerations

An EXR may carry named auxiliary channels, multipart images or deep samples, beyond a flat RGB image. A rendered HDR copy is not an equivalent EXR working file. Channel selection, deep compositing and numeric mapping need explicit engine support; no export of every channel or depth sample is implemented.
EXR 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.
HDR and EXR can represent values beyond ordinary display white, but use different sample encodings. Conversion needs colour and numeric-range mapping; supported channels and precision may differ. In particular RGBE does not carry EXR alpha, arbitrary auxiliary channels, multipart or deep structures. The future engine defines the mapping.
If EXR 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.

EXR to HDR conversion details

EXR channels & deep data: An EXR may carry named auxiliary channels, multipart images or deep samples, beyond a flat RGB image. A rendered HDR copy is not an equivalent EXR working file. Channel selection, deep compositing and numeric mapping need explicit engine support; no export of every channel or depth sample is implemented.
Multiple source images: EXR 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.
HDR working data: HDR and EXR can represent values beyond ordinary display white, but use different sample encodings. Conversion needs colour and numeric-range mapping; supported channels and precision may differ. In particular RGBE does not carry EXR alpha, arbitrary auxiliary channels, multipart or deep structures. The future engine defines the mapping.
Opaque output: If EXR 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: EXR: Lossy & lossless → HDR: Lossless EXR: EXR supports lossy and lossless codecs. Choose one for the sample types and required precision; .exr alone does not guarantee exact channel preservation. 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: EXR: Yes → HDR: No
Colour depth: EXR: HALF 16 / FLOAT 32 / UINT 32 → HDR: 32-bit RGBE / XYZE pixel
HDR: EXR: Floating-point working values → HDR: Radiometric values
Multiple images: EXR: Multipart
Dimensions: Pixel dimensions, page geometry, rendering resolution, resizing and orientation need explicit converter policies. The future engine has not defined them yet.
Metadata: EXR: Typed header attributes, Chromaticities → 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 all EXR channels and deep samples survive?

Will every source image be exported?

Does HDR-to-HDR mean every channel survives?

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?

EXR: Typed header attributes, Chromaticities → HDR: Radiance header, EXPOSURE, FORMAT. Which fields are copied, rewritten or omitted will depend on the future engine; retention is not implemented yet.