Tutorials Motion

HDR Delivery: What Actually Changes

Professional · ~20 min

Overview

HDR delivery is frequently treated as an export setting, and it is closer to a second grade. It changes the brightness range available, the colour space, the way the signal is encoded, and it requires metadata that tells the display what to do, and if any of that is wrong, the result looks worse than the standard version. This guide covers what actually differs, why an automated conversion rarely holds up, and what you need in place before accepting HDR delivery work.

What You Need

A display genuinely capable of HDR, not merely accepting an HDR signal
A grading tool with proper HDR support and scopes in the right units
Source material with the latitude to justify it, log or raw, well exposed
The delivery specification, including which HDR format and what metadata
Time for a separate grading pass, not a conversion
A plan for the standard dynamic range version, which you will still need

Steps

Confirm which HDR format the delivery requires

The formats differ in meaningful ways. Some carry a single static description of the whole programme, others carry per-scene or per-frame metadata, and one uses a transfer function designed for broadcast rather than for graded content. They are not interchangeable and the specification will name one. Establish this before grading, not at delivery.

Check your monitoring can actually show it

A display that accepts an HDR signal is not necessarily a display that can reproduce it. Peak brightness, contrast, and colour volume all determine whether you are seeing your grade or an approximation. Grading HDR on inadequate monitoring produces work that looks wrong everywhere else, and it is the most common failure in early HDR work.

Grade for the extra range rather than stretching into it

HDR gives you headroom for specular highlights (reflections, light sources, sun on water) not permission to make everything brighter. The most common beginner HDR grade raises overall brightness, which is fatiguing to watch and defeats the point. Keep the bulk of the image at a comfortable level and use the range for the things that should be genuinely bright.

Watch the metadata, because it changes what viewers see

HDR relies on metadata describing the mastering display and content characteristics, which consumer displays use to map your grade onto their own capability. Wrong or missing metadata means displays guess, and the result varies unpredictably across devices. Verify it in the delivered file rather than trusting the export dialogue.

Grade the standard dynamic range version separately

An automated downconversion from HDR rarely produces a good standard version, because decisions that work with headroom do not survive compression into a smaller range. Most productions grade both, using the HDR grade as a starting point and then making real decisions about what to sacrifice. Budget for this rather than assuming a checkbox.

Verify the delivered file, not the timeline

Check the actual output: correct transfer function flagged, correct colour primaries, metadata present and sensible, and peak levels within the specification. Play it on a consumer HDR display as well as your reference. Files that look right in the grading suite and wrong on a television are almost always a flagging or metadata problem.

Pro Tips

HDR is headroom for highlights, not an instruction to raise everything. Overly bright HDR is tiring and looks amateur.
A display accepting an HDR signal is not the same as a display reproducing it. Check peak brightness specifications.
Always budget a separate standard-range grade. Automatic conversion is a starting point at best.
Verify metadata in the delivered file. Export dialogues frequently do not do what you assume.
If the source was not shot with latitude to spare, HDR delivery will not add any. Grade what you have.

Knowledge Base

What You'll Learn

HDR changes several things at once, which is why it resists being treated as an export option. Below: what actually differs from standard delivery, and why conversion between them is a creative task.

What Actually Differs From Standard Delivery

Four things change simultaneously, and confusing them is the source of most HDR trouble.

The brightness range. Standard delivery assumes a display of modest peak brightness. HDR allows for considerably brighter highlights while keeping shadows dark, which is the actual point, greater range, not a uniformly brighter image.

The transfer function. How code values map to light output changes. Standard delivery uses a curve derived from historical display behaviour. HDR uses curves designed around human perception across a wider range. This is why an HDR file played as though it were standard looks washed out and wrong.

The colour space. HDR delivery generally pairs with a wider colour gamut, so more saturated colours are representable.

The metadata. Unlike standard delivery, HDR depends on metadata describing what the content was mastered on so that displays with different capabilities can map it sensibly. This has no real equivalent in standard workflows and is where deliverables most often fail.

Why Conversion Between HDR and Standard Is a Creative Task

Converting an HDR grade to standard range sounds like arithmetic and is not, because the two have genuinely different amounts of room.

An HDR grade may place a specular highlight far above the diffuse white level, with detail preserved across that whole range. Standard delivery has nowhere to put it. Something has to give: either the highlight clips, or the entire image is compressed to fit, which flattens contrast everywhere to preserve a highlight most viewers were not looking at.

Automated tone mapping makes that decision globally with no knowledge of what matters in the shot. The results are frequently acceptable and rarely good: faces go dull to protect a window, or a sunset clips to white.

A human doing the conversion decides per scene what to sacrifice, which is a creative judgement about the shot rather than a mathematical operation. That is why productions delivering both grade both, and why "we will just derive the standard version automatically" is a plan that produces complaints.

Where This Fits

This guide covers one specific part of colour and grading. The wider picture, grading in Resolve from a technically correct starting point through building a look that holds up across a sequence, is in Color Grading in DaVinci Resolve, which frames the discipline as a whole and links out to the detailed guides underneath it, including this one. If you are starting from scratch rather than solving a specific problem, read that first and come back here.

FAQ

Q: Is HDR just a brighter picture?
A: No. It is a wider range between the darkest and brightest parts of the image, intended for specular highlights like reflections and light sources while the bulk of the picture stays at a comfortable level. Grading everything brighter is the most common beginner mistake and produces fatiguing, amateurish results.

Q: Can I convert an HDR grade to standard range automatically?
A: You can, and it is a starting point rather than a deliverable. The two have genuinely different amounts of headroom, so something must be sacrificed, and automated tone mapping makes that decision globally without knowing what matters in the shot. Productions delivering both normally grade both.

Q: Do I need a special monitor for HDR grading?
A: Yes, one that genuinely reproduces high dynamic range, not merely one that accepts an HDR signal. Peak brightness, contrast, and colour volume determine whether you are seeing your grade or an approximation of it. Grading HDR on inadequate monitoring reliably produces work that looks wrong on real displays.

Q: Why does my HDR file look washed out on playback?
A: Almost always a flagging or metadata problem. The file is not correctly identified as HDR, so the player interprets it with the wrong transfer function. Verify the delivered file rather than trusting the export dialogue, checking transfer function, colour primaries, and mastering metadata.