A bright-looking Krita canvas does not prove that an HDR video export is valid. Treat the task as two separate acceptances: first verify the operating system, display, cable, graphics hardware, drivers, and Krita canvas configuration; then verify FFmpeg, H.265, the main10 (HDR) profile, HDR mode, and metadata in the animation renderer. Krita's HDR Display documentation supports these as related but distinct workflows.
Specific judgment and steps
Use the display check only to answer whether Krita can present HDR on the current workstation. Use the export check to answer whether the rendered file carries the intended HDR video configuration.
- Confirm the display chain before opening Krita. The monitor must support HDR, the graphics card and driver must support it, and the connection must be suitable. On Windows, enable HDR in the system display settings and confirm that the system recognizes the setup. A cable or driver that falls back to SDR can make the visible result misleading.
- On Windows, open
Settings > Configure Krita... > Display, choose the preferred surface closest to the display format, and restart Krita. The restart is part of this platform's documented procedure. - On Linux, apply the documented route only when using Wayland: open
Settings > Configure Krita... > Color Management > Displayand selectRec 2020 PQas the canvas surface color space. Krita should enable HDR immediately, without a restart. Do not treat this Wayland instruction as a generic Linux recipe. - Record the display result separately. For HDR painting, Krita documents a Rec. 2020 gamut and linear-transfer working profile; this is a canvas and editing choice, not evidence that a rendered animation has correct delivery metadata.
- For animation, obtain an FFmpeg build with H.265 support. In
File > Render Animation, chooseVideo, selectMPEG-4 videoorMatroska, open its format configuration, chooseH.265, MPEG-H Part 2 (HEVC), selectmain10 (HDR), and enableHDR Mode. - Open
HDR Metadataand record the selected Master Display and the values used for MaxCLL and MaxFALL. Save the render settings as the export acceptance record, then inspect the resulting file in the intended playback route. That playback check is an author-recommended comparison, not a claim that Krita alone validates every player or cable.
One acceptance worksheet
The following is a hypothetical worksheet, designed to expose a split result rather than repeat the setup steps. The observations are example data, not a software or hardware test.
| Acceptance item | Hypothetical observation | Decision | Next action |
|---|---|---|---|
| System HDR recognition | Windows reports HDR enabled; monitor menu reports HDR input | Display prerequisite appears satisfied | Continue with Krita display configuration |
| Krita surface | Preferred display surface selected; Krita restarted | Windows display path recorded | Keep this separate from export approval |
| Canvas working profile | Rec. 2020 gamut with linear transfer profile | Suitable documented editing direction | Do not infer video metadata from this field |
| FFmpeg and codec | H.265 option is absent | Export path is not ready | Install or select an FFmpeg build with H.265 support |
| Video profile and mode | H.265 is present, but profile is main10 without HDR mode | Not accepted as the documented HDR route | Select main10 (HDR) and enable HDR Mode |
| Metadata record | Master Display entered; MaxCLL 1,000 nits; MaxFALL 240 nits | Metadata is documented for review | Confirm these values describe the intended display and animation |
| Playback observation | Test player reports an HDR video but another route shows SDR | Encoding result and playback capability are unresolved separately | Inspect the player, system, cable, and display path |
MaxCLL means the brightest pixel value of the animation, while MaxFALL describes the average brightest level of the whole animation. These are metadata responsibilities: do not invent them from the canvas appearance or assume that a monitor's peak brightness automatically supplies the animation values. The Master Display describes the display characteristics for which the image was made, including primaries, white point, and luminance limits.
Limits and next steps after failure
If the operating system does not recognize HDR, stop the Krita display acceptance and check the monitor mode, cable, graphics hardware, and driver. If Windows configuration was changed but Krita was not restarted, repeat that documented step. On Linux, first confirm that the session is Wayland before applying the Rec 2020 PQ instruction.
If main10 (HDR) or HDR Mode is unavailable, the export cannot be accepted through the documented route yet; check FFmpeg's H.265 capability and Krita's format configuration. If the file is encoded but playback differs, do not revise the artwork solely from that appearance. Compare the file's actual media fields and the intended player/display chain. Krita's documentation does not establish universal support for every monitor, cable, FFmpeg build, or player, and this guide reports no device or playback test.
Three short questions
Does a bright canvas prove HDR export?
No. It only supplies a visual clue about the current display path. Export approval requires the separate codec, profile, HDR mode, and metadata record.
Must Windows and Wayland use the same Krita setting?
No. Windows uses the Display page, preferred surface selection, and restart. Wayland uses the Color Management display setting with Rec 2020 PQ and no documented restart.
What should I record for metadata?
Record the chosen Master Display and the documented display characteristics, plus the MaxCLL and MaxFALL values used for the animation. Treat them as delivery data, not as an automatic measurement supplied by the canvas.
Sources and next step
This guide interprets public documentation and uses explicitly hypothetical acceptance examples, not application tests. Controls and availability can change; verify the cited manual against your installed version.
For work created in Imagild, carry the input requirements and acceptance checklist into the photo editor. The external software controls discussed above belong to their respective products.