Why Your EXR Looks Too Dark or Washed Out

Why Does My EXR Look Dark?

This is the most common question from new EXR users — and it comes down to a fundamental difference between how your monitor displays images versus what an EXR file actually stores.

PNG, JPEG, and GIF all store "display-referred" data: pixel values of 0–255 are directly mapped to the brightness levels your screen can show. A value of 128 always means "half bright." Your browser assumes this mapping automatically.

EXR stores "scene-linear" HDR (high-dynamic-range) data instead. Pixel values represent real light intensities — not display brightness. A pixel with a red channel value of 5.0 doesn't mean "dark red"; it means the simulated light at that point was five times brighter than the reference white level. Your monitor can only show up to ~255, so those HDR values need to be mapped down — a process called tone mapping.

Exposure (EV Stops)

In photography and VFX, exposure is measured in EV (exposure value) stops. Each stop doubles or halves the light:

• Exposure = 0 — no adjustment; view HDR values as-is
• Exposure = +1 — doubles brightness (one stop brighter)
• Exposure = −1 — halves brightness (one stop darker)
• Exposure = +3 — eight times brighter

The Online EXR Viewer applies exposure by computing: exposedValue = max(0, pixelValue × 2^exposure). This is the same principle used in camera exposure controls and HDR photo editing software.

If your EXR looks too dark, try increasing the Exposure slider. Most renders need between +1 and +4 EV stops to preview comfortably on a standard monitor.

Gamma Correction

Gamma correction is the second step in converting scene-linear HDR data to display-referred values. It applies a non-linear curve that roughly matches how human vision perceives brightness.

The standard gamma value is 2.2 — which means the displayed output is: output = exposedValue^(1/2.2). This curve preserves more detail in darker tones (where our eyes are more sensitive) while compressing highlights.

In practice:

• Gamma 2.2 — standard sRGB display (most monitors)
• Gamma 1.8 — older CRT displays, some Mac systems
• Gamma 2.4 — dark room compositing environments (DAVINCI Resolve default)

If your EXR looks "flat" or "washed out" at gamma 2.2, try 2.4. If it looks too contrasty, try 1.8.

Scene-Linear vs Display-Gamma in Practice

Understanding the difference between scene-linear and display-gamma is critical for anyone working with EXR files:

• In your render engine: output to EXR in scene-linear (no gamma applied). This preserves the full dynamic range for compositing.
• In your viewer: use exposure and gamma controls to preview. The Online EXR Viewer's default of Exposure 0, Gamma 2.2 is a reasonable starting point.
• In compositing (Nuke, After Effects): work in scene-linear with ACES or sRGB display device transforms for preview.

Blender Renders: Filmic/AgX and View Transforms

If your EXR came out of Blender and looks noticeably different (flatter, darker, or with different contrast) when opened somewhere else, this is the reason: Blender's viewport and render preview apply a view transform — Filmic in older versions, AgX by default since Blender 4.0 — that only affects what you see on screen. It is not baked into the pixel data of the saved EXR.

The EXR file itself still contains the raw scene-linear values straight out of the renderer. Blender applies Filmic/AgX live, on top, purely for display. Open that same file in a different viewer with no view transform (or a plain gamma 2.2 curve), and you're seeing the untouched linear data — which typically looks more washed out in the highlights and less contrasty than what Blender showed you.

Two ways to fix this:

• Adjust in the viewer — use exposure and gamma controls (like the ones in the Online EXR Viewer) to approximate the look, without needing to match Blender's exact curve.
• Apply the transform on save — in Blender's compositor or output settings, bake the view transform into the file before export if you want the "as-seen-in-Blender" look preserved in the delivered file. Note that this trades away the scene-linear data, so only do it for final delivery, not intermediate compositing files.