HDR can make a YouTube live picture retain more detail in bright skies, lamps and other high-contrast scenes, but only when the source, encoder, colour settings and YouTube ingest path agree. The safest approach is to treat HDR as a complete signal chain rather than as a single OBS checkbox.
YouTube's current HDR guidance should be your final reference because encoder support and software menus change. The settings below separate the requirements that apply to the whole chain from the steps that apply specifically to OBS, and they avoid treating one encoder's menu as universal.
Check the source before changing OBS
An SDR source does not become HDR because you select an HDR colour format. HDR needs to be present in the captured or rendered source, and the camera, screen capture path, video file or production software must preserve that information until it reaches the encoder.
Start by identifying what you are actually streaming. A camera may record HDR in a particular picture profile. A game or desktop may output HDR only when the operating system, display connection and application are configured for it. A pre-recorded file may contain HDR metadata and a compatible colour transfer function, while another file may simply be SDR at a high resolution.
Check the source documentation rather than inferring HDR from a label such as 4K, 10-bit or wide colour. Resolution and bit depth can support an HDR workflow, but neither one proves that the picture is HDR. If the source is SDR, keep the stream SDR or create a properly converted HDR master before streaming. Do not use an HDR-looking setting to disguise a conversion that has not happened.
The same check applies to capture hardware. A capture card, HDMI path, display driver or virtual camera can alter the signal before OBS receives it. Confirm that the device can accept and pass the source's HDR signal, then check what OBS reports for the captured input. If the source appears washed out, clipped or unusually dark in a local preview, stop there and resolve the signal path before configuring YouTube.
Keep a short record of the source properties: resolution, frame rate, HDR format, bit depth and whether the signal is PQ or HLG. That record gives you something concrete to compare with the encoder and Live Control Room later.
Understand YouTube Live HDR as a chain of requirements
YouTube Live HDR is not just a more colourful SDR stream. The encoder must produce a supported HDR video stream, with the appropriate codec, bit depth and colour signalling. YouTube must then receive it through a supported live workflow and identify it correctly.
YouTube's official live encoder settings are the controlling reference for supported codecs, HDR formats, resolutions, frame rates and recommended settings. Use that page when you prepare a new channel or revisit an older setup, because software menus and platform guidance can change.
The shared requirements are straightforward in principle:
- The source must genuinely contain HDR information.
- The encoder must support an HDR-capable codec and the required bit depth.
- The pixel format must preserve the required precision and colour information.
- The transfer function and colour primaries must match the source and the encoder output.
- The YouTube live event must be configured to receive the chosen video format.
- Your connection must sustain the selected output without repeated congestion or dropped frames.
These are shared requirements, not a promise that every encoder exposes them with the same names. One application may show P010; another may describe a 10-bit 4:2:0 format in a different way. One hardware encoder may expose HEVC controls that another does not. Match the setting's meaning to your encoder's documentation, not just to a screenshot from another setup.
YouTube's HDR help also explains the expected colour combinations and delivery requirements in more detail. Read the YouTube HDR live streaming guidance alongside your encoder's own documentation before choosing between PQ and HLG.
Do not select a codec merely because it appears in an OBS drop-down. A codec can be available for recording but unsuitable for the live path you are using, or it may be accepted by your local hardware while not matching YouTube's current live guidance. If the official YouTube page and your encoder documentation do not agree, pause and verify the exact workflow rather than improvising.
Configure a supported OBS release and hardware HEVC encoder
OBS-specific instructions begin only after the source and YouTube requirements are understood. Install a current OBS release from the official OBS Studio site, and read its release notes if you are moving from an older version. HDR controls, available encoders and colour-format options can change between releases, operating systems and hardware vendors.
Use a hardware HEVC encoder only when your graphics hardware and installed driver expose one that OBS can use for live output. In OBS, the encoder may appear under a vendor-specific name rather than simply as HEVC. The name alone is not enough: confirm that it is an HEVC video encoder, supports the required bit depth, and can produce the colour format YouTube expects.
Do not assume that an encoder available for local recording is also available for streaming. OBS may list different capabilities depending on whether you select a recording output or a streaming output. If the HEVC encoder disappears after you choose a particular output mode, treat that as a capability or configuration issue rather than forcing a different codec without checking the current YouTube requirements.
In OBS, begin with the video settings that describe your source and intended output, then open the output settings for streaming. Set the codec to the supported HEVC option exposed by your hardware and software combination. Avoid copying an NVENC, AMD or Intel setting from a guide written for another encoder. Names for rate control, keyframe interval, tuning and profile can differ, and not every encoder offers the same choices.
For a live channel, stability matters more than a theoretically optimal setting. Watch the encoder's load, rendering lag and network statistics during a sustained test. If the computer cannot encode the selected output without missed frames or overload, reduce the workload or use a different supported workflow. A nominally correct HDR configuration is not useful if the machine cannot maintain it.
If you are streaming a prepared file rather than producing a live OBS programme, a different workflow may be more suitable. StreamNeo removes the need to keep the production computer running by taking an uploaded video and running it to YouTube from the cloud, with automatic monitoring and restart when the broadcast drops. It is still your responsibility to verify that the uploaded file is a valid HDR source and that YouTube accepts the resulting format.
Set Main 10, HDR and P010 deliberately
The terms Main 10, HDR and P010 refer to different parts of the chain, so do not treat them as interchangeable labels.
Main 10 is an HEVC profile intended for 10-bit video. It is relevant because HDR normally needs more precision than an 8-bit pipeline can preserve. Selecting a 10-bit profile does not, by itself, establish the correct transfer function or colour primaries.
P010 is a 10-bit pixel format commonly used for 4:2:0 video. In an OBS workflow, it may appear as the colour format required for HDR output. The exact menu location and availability depend on the OBS version, operating system and encoder. If P010 is not available, do not substitute an arbitrary 8-bit format and still describe the result as HDR. Check the current YouTube requirements and the encoder documentation first.
In OBS, inspect the advanced colour settings and output encoder settings together. Your aim is for the source, OBS colour pipeline and HEVC encoder to agree on 10-bit HDR output. Confirm that:
- the encoder is HEVC rather than an SDR-oriented H.264 path
- the profile is the supported 10-bit HEVC profile, where the encoder exposes it
- the colour format is the required 10-bit format, commonly shown as P010
- the colour space and transfer function match the source
- no later stage changes the signal back to 8-bit SDR
Some controls may be labelled differently, unavailable, or locked by the selected encoder. That is why these are not universal OBS instructions. If your hardware encoder offers a different 10-bit format, look up its documentation and compare the result with YouTube's current HDR specification. Do not select a setting because it sounds more advanced.
HDR can also be lost before the encoder. A scene source may be converted by a capture device, a browser source may be rendered in SDR, or a filter may process the image in a way that changes its range or transfer function. Test the actual programme output, not only the original camera or file.
For ordinary troubleshooting, keep the signal path simple. Remove unnecessary filters, scaling stages and colour conversions during the first test. Once the basic stream is recognised correctly, add production elements one at a time and check whether the result changes.
Choose Rec. 2100 PQ or HLG
PQ and HLG are different HDR transfer functions. Choose the one used by your source and supported by the complete delivery path. Do not select PQ because it is listed first, or HLG because it is easier to pronounce in a menu.
PQ is commonly associated with a mastered HDR signal that follows a defined brightness relationship. HLG is designed for a different production and display approach and may be used by cameras or live workflows that are built around it. The important decision is not which label sounds preferable. It is whether the source, OBS pipeline, encoder and YouTube output all describe the same signal.
In the colour settings, the colour space is generally represented by Rec. 2100, with PQ or HLG selected as the transfer function. Set the option that matches your source documentation. If your camera records HLG, converting it to PQ inside an unrelated menu is not a substitute for a controlled colour-management workflow. If your file is mastered as PQ, selecting HLG can produce an incorrect image even though the stream remains technically flagged as HDR.
Check the result on a display that can show HDR, but do not rely on appearance alone. A display may tone-map HDR, apply its own picture mode or fall back to SDR. The signal metadata and the encoder output logs are useful evidence alongside the picture. Compare a known bright highlight, a neutral grey object and a shadow area between the source and the local programme output.
If you are unsure which transfer function the source uses, find that answer before going live. Look at the camera or editing application's export settings, the media file's technical information, or the documentation for the production device. Guessing between PQ and HLG is more likely to create a confusing result than to improve it.
Check resolution, event settings and ingestion protocol
After configuring OBS, open YouTube Live Control Room and check the event settings before starting the broadcast. Confirm the selected resolution and frame rate match what OBS will send. An HDR source can still be delivered at the wrong output size or frame rate if OBS's base and output video settings differ from the event you prepared.
YouTube's Live Control Room help explains how to create and manage live events. Use the current interface there as your reference for stream keys, scheduled events, latency choices and the information YouTube shows after it receives the signal.
The ingestion protocol must also match your encoder. RTMP-based workflows are common, but YouTube may document more than one supported protocol or endpoint option. Choose the protocol supported by your exact OBS build, encoder and YouTube event rather than changing it to solve an unrelated colour problem. Protocol selection does not turn an SDR source into HDR.
Once OBS is connected, look at the Live Control Room preview and health indicators. Confirm that YouTube identifies the incoming stream as HDR where the current interface exposes that information. Check the preview on more than one display type if possible, because an SDR display may not show the intended result.
Network stability remains relevant even though HDR configuration is primarily a colour and codec problem. Higher-quality output can place more demand on the connection, and a stream that begins correctly may still suffer when household traffic, mobile broadband conditions or a router change affects the upload. The guidance in this YouTube current-bitrate troubleshooting guide helps you distinguish an ingest-rate problem from an encoder problem.
For a long-running channel, also plan what happens after a brief interruption. Your guide to recovering a YouTube stream after an internet outage in India covers operational checks that sit outside the HDR settings themselves.
Test the complete stream before going live
Do not make the first HDR test a public overnight broadcast. Create a private or unlisted event, use a short known-good source, and allow enough time to observe the local encoder and YouTube's received signal. The purpose is to test the complete path, not merely to prove that OBS starts sending data.
Begin with a short checklist:
- Confirm the source is genuinely HDR and record whether it uses PQ or HLG.
- Confirm OBS sees the intended source without an unexpected conversion.
- Confirm the selected HEVC hardware encoder supports the required 10-bit path.
- Confirm the profile, pixel format and colour settings agree.
- Confirm the output resolution and frame rate match the YouTube event.
- Confirm YouTube receives and labels the stream as expected.
- Watch for dropped frames, rendering lag, encoder overload and network warnings.
- Review the recording or local capture if you made one, checking highlights, shadows, skin tones and neutral colours.
Use a test clip containing both bright and dark areas. A flat scene may conceal clipping, crushed shadows or a mistaken transfer function. Include motion as well, because a setting that looks correct on a still frame may overload the encoder when the image becomes complex.
Change one setting at a time. If you change the codec, pixel format, transfer function and resolution together, a successful or failed result will not tell you which choice caused it. Keep a note of the working combination, including the OBS version, operating system, graphics hardware, driver and YouTube event settings. This is particularly useful after an OBS or graphics-driver update.
If YouTube reports a problem, first compare its current official requirements with your actual encoder output. Then check the least complicated parts of the chain: source format, HEVC availability, 10-bit pixel format, PQ or HLG selection and event resolution. Do not respond to an HDR error by raising bitrate or changing unrelated network settings.
For a practical 24/7 operation, test the recovery path as well as the picture. Review the advice on automatic restart after a YouTube stream disconnects, then decide whether your chosen workflow can reconnect without losing the intended event configuration. Automatic recovery is useful only if the restarted stream still uses the correct source and encoder settings.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
Can an SDR video be made HDR by changing OBS settings?
No. OBS settings can signal and encode an HDR source, but they cannot create the missing HDR information in an SDR file or camera feed. Keep an SDR source in an SDR workflow, or produce a properly managed HDR version before streaming.
Is P010 enough to make a YouTube stream HDR?
No. P010 is a 10-bit pixel format, not a complete HDR configuration. The source, HEVC profile, transfer function, colour primaries, encoder and YouTube ingest settings must agree as well.
Should I choose PQ or HLG?
Choose the transfer function used by the source and supported by your encoder and YouTube workflow. If the source documentation does not make that clear, test and verify it before going live rather than guessing from the OBS menu.
Why does my OBS HDR setting not match a guide online?
OBS menus depend on the version, operating system, graphics hardware, driver and selected output mode. Treat the guide as version-sensitive, check the current OBS and encoder documentation, and follow YouTube's current HDR requirements for the final decision.