A washed-out 4K nature stream is often a signal-path mismatch, not a bitrate problem. Start by confirming that your footage is genuinely HDR, then match its PQ or HLG format through OBS and YouTube’s documented live HDR workflow.
You cannot judge HDR appearance from the Live Control Room preview alone: it does not display HDR colours. Use the preview to check the broadcast, then verify colour and the HDR badge on a supported playback device.
Check whether the source is genuinely HDR
Before changing encoder settings, establish what the camera or file actually outputs. “HDR” on a camera menu or product description is not enough to select a transfer function: look in the camera manual or recording information for support for PQ or HLG, and check the format of the particular clip you intend to stream. A source recorded in SDR does not become HDR because you choose an HDR option downstream.
For a camera, check the recording mode, colour profile and output path, not just the screen’s brightness or a setting called “dynamic range”. Some cameras offer different recording formats, and an external capture route may not preserve every property of the original recording. Confirm that the capture device and software receive the intended output. If you are streaming a prepared video file rather than a camera feed, inspect its colour metadata and confirm how your playback or capture software interprets it.
A useful first test is to open a representative clip in a player that can identify its video properties. Confirm the frame size and frame rate as well as the colour transfer information. If those details are absent or unclear, consult the device or editing software documentation rather than guessing. YouTube’s HDR live-stream requirements and OBS guidance describe the supported standards and signal path.
Keep a short sample that includes bright sky, shaded foliage, water or another reflective surface, and gradual movement. A static landscape can hide exposure and colour problems that become obvious when the camera pans or a cloud crosses the sun. Include the sort of material viewers will see in the actual broadcast; an indoor test pattern does not tell you how your nature footage will behave.
If you still need equipment, search by the capability you need, such as an HDR camera with HLG video, and verify the exact recording or output mode in its manual before buying. The source, capture path and encoder all need to agree. A compatible camera alone cannot ensure the right signal reaches YouTube.
Match PQ or HLG throughout the workflow
PQ and HLG are distinct HDR transfer functions. Choose the one the source actually produces and carry it through capture, encoder configuration and signalling. Do not treat the two as interchangeable menu choices or set one in OBS simply because it appears to look better on a particular preview.
In YouTube’s documented OBS setup, the colour primaries and matrix are BT.2020, with the transfer set to PQ or HLG as appropriate. In practice, check all three parts of the colour description: primaries identify the colour space, transfer describes how signal values map to brightness, and matrix describes how colour components are represented. A mismatch in any of them can lead to a result that looks wrong even if the video still plays.
YouTube recommends HLG in its OBS instructions, but also documents Rec. 2100 PQ. That is not a reason to convert a PQ source to HLG, or the reverse, without a deliberate conversion workflow. If your camera records PQ, use the compatible PQ path; if it records HLG, use the compatible HLG path. When the source format is uncertain, solve that uncertainty first rather than trying both settings on a live broadcast.
Keep a written note of the source standard and intended encoder settings. This is particularly useful when a channel has more than one camera or file type: one clip may be HLG while another is SDR. Do not assume the OBS profile used for one will work for all. If the production changes sources, re-check that source’s properties and the active scene or encoder configuration.
The colour path also depends on how you send the stream to YouTube. YouTube’s HDR help documents OBS routes using RTMPS and HLS, and gives specific requirements for compatible hardware encoders on HLS. Follow the instructions for your selected encoder and route; the presence of an HLS option in one product does not establish that every encoder supports it or that its requirements are identical. If you already plan the channel’s latency and DVR behaviour, this guide to YouTube Live DVR and latency covers those separate viewing choices.
Configure OBS for YouTube HDR
YouTube’s OBS instructions identify OBS version 30.1 or later for this workflow. Select a compatible hardware HEVC encoder, then use the documented HDR settings: Main 10 profile, HDR enabled, P010 (4:2:0) pixel format, and Rec. 2100 PQ or HLG to match the source. The exact control names can vary with the encoder and operating system, so use the OBS and encoder documentation if the option is missing or labelled differently.
The settings are a pathway, not a repair for every source. Main 10 and P010 are part of YouTube’s stated HDR configuration; selecting them does not create detail or correct colour information that was absent or misinterpreted earlier. Likewise, a Rec. 2100 transfer setting cannot make an SDR camera recording genuine HDR. If your hardware encoder does not offer the required profile or pixel format, check its documentation and choose a supported workflow rather than substituting a nearby-looking option.
Set the metadata to match the source: BT.2020 primaries, PQ or HLG transfer as applicable, and BT.2020 non-constant-luminance matrix. Do not invent HDR metadata to compensate for a mismatch. Correct signalling tells the receiving platform how to interpret a signal; inaccurate signalling can make a valid source appear incorrect.
Make one change at a time when testing. Record the starting configuration, confirm the source standard, then change the encoder and colour settings to match. If you change the source, transfer function, pixel format and bitrate together, it becomes harder to identify which change affected the result. Keep a known-good test configuration separate from any experimental profile you may use for a different camera.
For a 24/7 channel built from prepared video rather than a live camera, OBS may not be the only relevant part of the chain: the file and playback path still need to preserve the intended colour interpretation. This overview of looping YouTube stream videos from stored files can help with the file-and-playback side of a continuous channel, but it does not replace checking HDR support end to end.
Choose 4K60 bitrate and bandwidth headroom
YouTube’s live encoder table lists a recommended bitrate of 35 Mbps for H.264 at 4K/2160p and 60 fps. For AV1 or H.265, the listed range is 10–40 Mbps. These are YouTube recommendations, not a guarantee that a particular upload connection, encoder or scene will behave well at every value. Select a bitrate supported by the ingest codec and test it with your actual footage.
| 4K/2160p at 60 fps | YouTube guidance | Practical consideration |
|---|---|---|
| H.264 | 35 Mbps recommended | Use the listed recommendation as a starting point, then test whether your upload and encoder sustain it. |
| AV1 or H.265 | 10–40 Mbps range | Choose within the listed range according to your encoder, connection and image complexity. |
| Keyframe interval | 2 seconds; no more than 4 seconds | Set the encoder to the documented interval and verify the stream configuration. |
| Rate control | CBR | Use constant bitrate as specified in YouTube’s general live settings. |
See YouTube’s live encoder settings and bitrate table for the current guidance. Nature footage can contain fine texture in leaves, moving water and grass, so test with motion rather than assuming that a bitrate which works for a static frame will also suit a moving shot. The source’s colour format and encoder support remain separate requirements from bitrate.
Your upload connection needs headroom beyond the target stream bitrate, because other household or studio use and variation in the connection can affect the available capacity. Run a sustained test over the same connection and at the same time of day you expect to broadcast if possible. Check that the encoder is not reporting dropped frames and YouTube’s stream health is stable. Do not infer a reliable capacity from a brief speed test alone.
At 4K, YouTube does not offer low-latency optimisation; the stream uses normal latency. Account for that in how you respond to viewers and in any interaction that depends on a near-live picture. If upload capacity cannot sustain the selected 4K60 configuration, consider a lower resolution or frame rate rather than repeatedly increasing bitrate beyond what the line can carry. This OBS bitrate guide for an always-on YouTube stream on Indian fibre explains how to think about stable upload capacity for a continuous broadcast.
Avoid SDR/HDR and PQ/HLG mismatches
A common source of confusion is a mixed chain: an SDR file is passed through an HDR-configured encoder, or a PQ source is signalled as HLG. Neither should be “fixed” by changing labels until the preview looks brighter. The signal, pixel format and metadata need to describe the source or a properly converted output. If you do not know whether a conversion occurred, inspect the source and the conversion settings before going live.
Check where the formats may diverge: camera recording mode, HDMI or capture output, operating-system colour handling, OBS colour settings, encoder profile and YouTube ingest route. A setting can be right at one stage and still receive the wrong input from the stage before it. For a file-based stream, include the media player or playout application in that chain.
If a source is SDR, use an SDR workflow unless you intentionally create and validate an HDR conversion. Do not select PQ or HLG merely to make the stream eligible for HDR playback. Conversely, if the source is HDR, an SDR output path can lose the intended HDR presentation. The outcome depends on the full workflow, so the correct next step is to identify the point where the signal changes, not to declare one format universally better.
YouTube’s HDR upload guidance warns that incorrect HDR grading or metadata can produce an incorrect result. Although that page concerns uploads, it reinforces the need to keep colour interpretation accurate; it is not a complete fault tree for live streaming. If you need to convert between standards, use a documented colour-managed conversion and test the resulting file or signal before using it as a live source.
Avoid judging a setting by how it appears on a display with unknown HDR mode, brightness or tone mapping. A viewer’s device may show an SDR version, and two displays can present the same correctly signalled material differently. First establish what format the viewer’s device is receiving, then compare the stream and source on a known HDR-capable setup.
Verify the outgoing image in context
Run a private or unlisted test before the scheduled broadcast. Use the same stream route, OBS profile, camera or sample file, encoder, resolution and frame rate you intend to use live. Include representative movement and audio. Check the Live Control Room for ingest and stream health, but do not use its preview as the final test of HDR colour: YouTube says that preview does not show HDR colours.
Open the test on an HDR-capable device and display that device’s quality menu. YouTube’s guidance says supported HDR playback can show an HDR badge or option; devices that do not support HDR receive SDR. The badge is evidence about the playback format, not a promise that every viewer’s screen will look identical. Check the picture on the target display, and, if possible, compare the same scene against the source on a display configured for HDR.
If the output looks washed out, narrow the question in order. Is the test playback actually HDR, or is the device receiving SDR? Does the source really use PQ or HLG? Does OBS use the same transfer function, and are the primaries and matrix compatible? Is the selected ingest route supported by the encoder? These checks separate a misleading preview or SDR fallback from a genuine configuration problem.
When the HDR badge is absent, check the route, encoder and stream configuration against YouTube’s current instructions before changing colour values at random. When the badge is present but the image still looks wrong, confirm the source’s original appearance and metadata, then examine the capture and processing steps for a mismatch. Repeat the test after one controlled change and note whether the badge, colour and stream health changed.
For a long-running channel, keep a simple test log: date, source clip or camera mode, OBS profile, encoder, bitrate, route, playback device and result. This is not a substitute for official documentation, but it can stop a later scene or software change from silently reintroducing a mismatch. If a camera, encoder or OBS version changes, repeat the test rather than assuming the earlier result still applies.
Once the colour path is verified, make the stream operationally repeatable. Keep the source file and tested configuration together, and avoid changing the stream key or ingest route without checking the encoder instructions. If your goal is a file-based 24/7 broadcast and keeping a computer running is the remaining burden, StreamNeo can take that machine out of the daily loop: upload the video, provide your YouTube stream key, and the broadcast continues with your computer switched off. You still need to validate the source and HDR appearance using the same checks above.
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 I make SDR nature footage look like HDR by selecting PQ in OBS?
No. Selecting PQ or HLG does not turn an SDR source into genuine HDR, and inaccurate signalling may make the image look wrong. Use an SDR workflow unless you deliberately convert and validate the source with a documented colour-managed process.
Should I choose PQ or HLG for YouTube Live?
Choose the standard your source actually produces and that your encoder supports through the documented YouTube path. YouTube recommends HLG in its OBS instructions but also allows Rec. 2100 PQ; neither should be selected without matching the source.
Why does the Live Control Room preview look washed out?
The preview does not display HDR colours, so it cannot by itself establish that the outgoing HDR picture is washed out. Check stream health there, then test playback on an HDR-capable device and look for the HDR badge or option.
What bitrate should I use for 4K60?
YouTube lists 35 Mbps recommended for H.264 at 4K/2160p60 and 10–40 Mbps for AV1 or H.265. Use a value supported by your encoder and stable upload capacity, then test the actual footage and monitor stream health.