Version prerequisite: this guide follows Shotcut’s documented HDR workflow, which identifies Preview Window (HDR) as new in v26.6. Use that window only in a version and platform that provides it; verify the actual controls in your installed build. Supported dedicated Blackmagic monitoring hardware is the documented alternative. First decide whether the deliverable should remain HDR or be converted to SDR. For a native HDR deliverable, check the timeline’s HDR format and processing path before changing export codec options. Shotcut’s documentation says the project Video Mode and 10-bit processing settings drive export color metadata; an export setting is not a way to convert PQ footage to HLG, or vice versa.
Check the project and processing path in order
- Identify the clips. Select each relevant source and inspect Properties > Video > Color transfer. The documentation identifies SMPTE ST2084 (PQ), SMPTE ST428, and ARIB B67 (HLG) as HDR transfer types. Record what is actually present; a washed-out-looking image alone does not identify its format.
- Resolve format consistency before grading or export. If the project contains PQ and HLG, or other different HDR formats, stop and choose a consistent route. Shotcut documents that it cannot convert between HDR formats or combine different HDR formats on one timeline. Do not try to solve that mismatch by changing an encoder or metadata field.
- Set the project deliberately. In a custom Video Mode, use BT.2020 colorspace and select the project’s intended dynamic range, HLG HDR or PQ HDR. For an existing timeline, check Timeline Properties. These are project choices, so confirm they match the intended delivery and source format rather than assuming a default is suitable.
- Enable 10-bit processing if the edit uses filters, transitions, or compositing. Under Settings > Processing Mode, choose Native 10-bit CPU or Linear 10-bit GPU/CPU; the latter requires GPU Effects enabled. Without 10-bit processing, the documented route is limited to cuts, trims, and sequencing. In an HDR project, use filters labeled
#gpuor#10bit; node color is only a clue, not a substitute for checking the type label. - Separate preview diagnosis from export diagnosis. In a version and platform that supports the v26.6 HDR preview feature, use Player > External Monitor > Preview Window (HDR), place it on an HDR-capable display with HDR enabled in both display controls and operating-system settings, and ensure the display accepts the project’s PQ or HLG signal. The documented preview may otherwise fall back to SDR or display incorrectly.
Hypothetical HLG/PQ acceptance worksheet
This example is a proposed check, not a test result or a guarantee of Shotcut behavior. Suppose a timeline contains one clip reported as HLG and another as PQ, while the project is set to HLG. Record the observations before making a decision:
| Check | Hypothetical observation | Decision |
|---|---|---|
| Source transfer | Clip A: ARIB B67; Clip B: SMPTE ST2084 | Do not treat the mixed timeline as a valid native HDR combination; resolve the format route first. |
| Project and processing | BT.2020, HLG HDR, Native 10-bit CPU | The project has an explicit HLG mode and 10-bit processing; this does not convert Clip B from PQ. |
| Filter labels | One required filter has neither #gpu nor #10bit | Remove it from the proposed HDR processing path or choose a compatible route; do not infer compatibility from its color. |
| Preview conditions | HDR is off in the operating system, or the monitor is not configured for the project signal | Treat the preview as unverified; correct the display conditions before judging HDR appearance. |
| Export and playback | Export color range differs from the source; target player not yet checked | Match the export range to the source, then inspect the exported file and target playback chain. |
Limits, failures, and next steps
The export panel’s defaults are documented as suitable for HDR according to the current Video Mode and 10-bit processing. If using a preset, Shotcut recommends the ten_bit category. Check Video > Color range against the source; the documentation gives GoPro and iPhone examples with different range choices, so do not apply one range universally. Then inspect the exported file’s color information and play it through the intended display and player. This acceptance check is a workflow recommendation, not a claim that a particular file was tested here.
If preview looks wrong but the export has not been checked, first verify the HDR display conditions. If the preview is unavailable, note that the cited documentation lists Linux as unsupported for this HDR preview window and says it is incompatible with Settings > Player > Use Old Video Output. It also flags preview scaling and some hardware decoders as possible issues. If the source formats conflict, resolve that constraint before further export experiments. If the required destination is SDR, choose an intentional HDR-to-SDR workflow instead; that is a separate conversion decision, not native HDR troubleshooting.
Three quick questions
Can export settings turn PQ into HLG? No. The documented HDR export metadata follows project Video Mode and 10-bit processing; Shotcut says it cannot convert between HDR formats.
Can I judge HDR from the main editing preview? Not reliably under the cited workflow. In a supporting version and platform, use the v26.6 HDR Preview Window on a correctly configured HDR display, or supported dedicated monitoring hardware.
What if I only need cuts? The documentation permits cuts, trims, and sequencing without 10-bit processing. If you add filters, transitions, or compositing, enable 10-bit processing and check filter labels.
Sources and next step
- Editing HDR Source Clips - Documentation - English - Shotcut Forum
- External Monitor and Preview Window (HDR) - Documentation - English - Shotcut Forum
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 film workspace. The external software controls discussed above belong to their respective products.