Convert EXR to HDR

Why Convert EXR to HDR?

Converting EXR to HDR (Radiance RGBE) simplifies complex multi-layer EXR files into a widely compatible single-layer HDR format. While EXR is the production standard for VFX, the Radiance HDR format is the most common format for distributing and sharing HDRI environment maps, light probes, and HDR panoramas. Many 3D tools, HDRI libraries, and online marketplaces use HDR as the standard interchange format.

The HDR format's RGBE encoding provides an efficient representation of high dynamic range data. Each pixel is stored as four bytes (RGB mantissa + shared exponent), giving effective floating-point precision while being smaller than EXR's 16-byte-per-pixel 32-bit float format. For single-layer HDR content like environment maps, HDR files are typically 3-4x smaller than equivalent EXR files.

EXR-to-HDR conversion is particularly common when preparing environment maps for 3D lighting. If you render a panoramic HDRI in a production renderer (V-Ray, Arnold, Cycles) and output to EXR with multiple passes, converting the beauty pass to HDR creates a portable file that works in any 3D application for image-based lighting. Blender, Maya, 3ds Max, Cinema 4D, and game engines all import HDR environment maps directly.

Note that HDR does not support alpha channels or multiple layers — only RGB data. Multi-layer EXR files will be flattened to the composited RGB output. If you need transparency or separate passes, keep the EXR format. The conversion preserves the full dynamic range of the RGB data, making HDR ideal for lighting and environment map applications where alpha is not needed.

Key Benefits of Converting EXR to HDR:

• Smaller File Size: RGBE encoding is 3-4x more compact than 32-bit float EXR
• Wide Compatibility: Supported by virtually all 3D and HDR software
• HDR Preserved: Full dynamic range maintained via RGBE encoding
• HDRI Standard: The default format for environment map libraries
• Simple Format: Easy to read, write, and integrate into pipelines
• IBL Ready: Direct use for image-based lighting in 3D scenes
• Fast Loading: Quick decode for real-time 3D viewport preview

Practical Examples

Example 1: Creating HDRI Environment Map for Distribution

Scenario: An HDRI photographer captures a 360-degree panorama, processes it in Photoshop as EXR, and needs to convert to HDR for distribution on an HDRI library website.

Source: studio_panorama.exr (180 MB, 8192×4096, 32-bit float, multi-layer)
Conversion: EXR → HDR (Radiance RGBE)
Result: studio_panorama.hdr (42 MB, 8192×4096, RGBE)

Distribution workflow:
✓ 77% file size reduction for download
✓ Compatible with all 3D applications
✓ Full HDR dynamic range preserved
✓ Standard format for HDRI Haven, Poly Haven, etc.
✓ Loads directly in Blender, Maya, Cinema 4D

Example 2: Preparing IBL Probes for Game Engine

Scenario: A technical artist renders HDR reflection probes in Houdini as EXR and needs to convert to HDR for import into Unity's lighting system.

Source: probe_lobby.exr (24 MB, 2048×1024, 16-bit half-float)
Conversion: EXR → HDR (RGBE)
Result: probe_lobby.hdr (8 MB, 2048×1024)

Game lighting workflow:
✓ Unity imports HDR for reflection probes directly
✓ Dynamic range enables PBR specular reflections
✓ Compact format for multiple probe locations
✓ Fast viewport preview during level design
✓ Works with both Unity and Unreal Engine

Example 3: Converting Rendered Sky Dome for 3D Scene Lighting

Scenario: A lighting artist renders a physically-based sky dome in Terragen as EXR and converts to HDR for use as environment lighting in a Maya character animation scene.

Source: sunset_skydome.exr (65 MB, 4096×2048, 32-bit float)
Conversion: EXR → HDR (RGBE)
Result: sunset_skydome.hdr (16 MB, 4096×2048)

Lighting workflow:
✓ Direct use in Maya/Arnold image-based lighting
✓ Sun and sky luminance preserved for realistic shadows
✓ Smaller file than EXR for scene loading
✓ Easily shareable with other lighting artists
✓ Compatible with all major 3D renderers

Frequently Asked Questions (FAQ)

Q: Does HDR preserve the full dynamic range of EXR?

A: HDR's RGBE encoding provides approximately 76 orders of magnitude of dynamic range, which exceeds what EXR typically stores in practice. However, RGBE uses a shared exponent for RGB channels, meaning it has slightly lower per-channel precision than EXR's independent 32-bit floats. For environment maps and lighting data, the difference is negligible — both formats preserve the dynamic range needed for realistic rendering.

Q: What happens to EXR layers and channels in the conversion?

A: HDR supports only a single RGB layer — no alpha, no custom channels, no named layers. Multi-layer EXR files are flattened to the composited RGB output. Render passes (diffuse, specular, emission, etc.) are merged. If you need separate passes, convert each EXR layer individually or keep the original EXR format.

Q: Is HDR or EXR better for HDRI environment maps?

A: For distribution and sharing, HDR is preferred — smaller files, wider compatibility, and sufficient precision. For production work where you need to edit the panorama, apply color corrections, or work with separate layers, EXR is better. Most HDRI libraries distribute in HDR format with EXR available as an optional high-quality download.

Q: Can I convert HDR back to EXR later?

A: Yes, but with some precision loss. RGBE encoding quantizes floating-point values to 8-bit mantissa plus exponent, so the round-trip EXR→HDR→EXR will not be bit-identical. For critical production work, keep the original EXR. For environment maps and lighting, the precision difference is visually imperceptible.

Q: Why is the HDR file smaller than the EXR?

A: HDR uses 4 bytes per pixel (RGBE encoding: 3 mantissa + 1 shared exponent) with RLE compression, while EXR uses 6-16 bytes per pixel depending on channel count and bit depth. For a single RGB image, HDR is inherently more compact. Additionally, EXR's multi-layer data adds significant overhead that HDR does not carry.

Q: Does HDR support alpha transparency?

A: No. HDR stores only RGB data — there is no alpha channel in the Radiance RGBE format. If your EXR has transparency that must be preserved, use EXR or convert to a format that supports both HDR and alpha (limited options exist). For environment maps and light probes, alpha is typically not needed.

Q: Which 3D software supports HDR environment maps?

A: Virtually all modern 3D software: Blender (native), Maya/Arnold (native), 3ds Max/V-Ray (native), Cinema 4D (native), Houdini (native), Unity (native), Unreal Engine (native), Godot (native), SketchUp, KeyShot, and more. HDR has broader compatibility than EXR for environment map loading specifically.

Q: What resolution should I use for HDR environment maps?

A: For general-purpose IBL, 4096x2048 (4K) provides good quality. For high-end VFX with visible reflections, 8192x4096 (8K) or higher is preferred. For real-time game engines, 2048x1024 is typically sufficient as the engine will generate convolved cubemaps. Larger resolutions produce larger HDR files — an 8K HDR panorama is approximately 40-60 MB.