
An HDR clipping warning in Affinity Photo 2's 32-bit Preview panel is a warning about the configured display range, not by itself proof that the render's floating-point data has been destroyed. Check the display's peak information and Monitor reference white before changing the document to eliminate every warning.
Key Takeaways
- Screen brightness limits and document values are different constraints.
- Reference white should reflect the calibrated display, not a guessed target.
- Clip to Max changes display handling; it is not a repair to the underlying render.
Identify which limit the warning describes
The official 32-bit Preview reference describes HDR clip warnings using average or peak brightness in nits obtained from display metadata. It also describes reference white and Clip to Max. Those controls belong to evaluating the screen presentation.
The 32-bit editing guide explains the wider tonal range available in a float document. A display that cannot show a bright value does not establish that the file no longer contains it. Conversely, the presence of float data does not prove every previous operation preserved an intended highlight.
Establish a trustworthy viewing context
- Preserve the original render and working document.
- Identify whether you are using the HDR or EDR display controls available on your system.
- Check the monitor metadata and use the calibrated reference-white value where applicable.
- Inspect the warning with a fixed, recognizable bright region.
- Record display settings before making an image-level correction.
For a proposed interior render, a luminous window may exceed the display's comfortable range while the nearby wall remains ordinary diffuse content. Do not lower the entire document solely because the window triggers a screen warning. First decide whether the task is scene-linear editing or a finished display-referred rendition.
Compare display handling deliberately
The guide describes Clip to Max as preventing the display's tone mapping above its peak threshold and clipping those displayed values instead. Use that as an inspection choice, not as evidence that the file has been altered to match the monitor.
If the delivered rendition needs tonal compression, make that as a separate documented processing decision. A brighter or darker preview is not a substitute for reviewing the actual export in the intended delivery workflow.
Accept the right evidence
For the proposed render, inspect whether meaningful highlight structure remains available under appropriate viewing conditions, then separately review the final rendition. Keep the float master if later compositing needs its range. This is a proposed evaluation plan; it does not claim a calibrated monitor, measured luminance or successful HDR export. If the warning disagrees with expectations, investigate the display configuration before baking a speculative correction into the only master.
Related tasks
- How to Verify Krita HDR Display and HDR Video Export Separately
- Why Does My HDR Photo Lose Its Bright Highlights After Editing?
- Why Does My Phone's HDR Wedding Video Look Washed Out on Another Screen?
Sources and scope
- 32-bit Preview panel: HDR warning derives average/peak nits from display metadata; reference white should match calibrated value; Clip to Max prevents display tone mapping; preview controls presentation only.
- 32-bit HDR editing: 32-bit float supports tonal values beyond ordinary display range; preview helps inspect range without tonal compression.
Direct official documentation supports technical claims; original proposed examples and checks, no firsthand product test or measured performance claim.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: William Liu / Pexels, Pexels License. This is an illustrative source photograph, not an application screenshot or a generated test result.