For a conventional SDR YouTube Live stream, set OBS colour space to Rec. 709. Choose Limited or Full range according to what your source and capture path actually output; Limited is a useful starting point for a video-range workflow, not a universal rule.
Colour space and range are separate settings. Rec. 709 describes the SDR colour space, while range describes the sample levels used for brightness; a mismatch between devices can make dark or bright detail disappear, or leave the picture looking washed out.
First identify whether your signal is SDR
Before changing OBS, establish whether the material reaching it is SDR or HDR. Most camera, desktop, console and prerecorded-video workflows for a conventional YouTube stream are SDR. If that describes your setup, the relevant starting point is YouTube’s live encoder guidance, which specifies Rec. 709 for SDR and 8-bit video.
Do not infer HDR merely because your monitor, camera or game console supports it, or because the source is 4K. Resolution and frame rate describe image size and motion; they do not tell you whether the signal is SDR or HDR. Check the source’s output setting and, for prerecorded material, its format or export settings. If the source is HDR, follow a separate HDR workflow rather than forcing it through SDR settings.
YouTube’s HDR setup instructions call for a compatible HDR source and an appropriate encoder configuration. The directions specify OBS 30.1 or later, hardware HEVC encoding, Main 10, P010, and Rec. 2100 PQ or HLG, with HLG recommended. Those are not settings to apply just because you are streaming at 4K60: if your content is SDR, use the SDR path.
This distinction matters when you are troubleshooting. If an SDR desktop capture looks dull, changing the range may help, but switching the colour space to an HDR mode is not a general fix. Likewise, an HDR signal interpreted as ordinary Rec. 709 can lose the intended appearance. Confirm the signal type first, then configure the stages that receive and encode it.
Set Rec. 709 for conventional SDR
For SDR, use Rec. 709 as OBS’s colour space. It is YouTube’s stated SDR colour-space recommendation, and it is the conventional choice for HD and 4K SDR delivery. Keep this choice distinct from range: selecting Rec. 709 does not itself tell OBS whether your source uses Limited or Full levels.
That separation is useful when diagnosing a picture. If colours seem broadly wrong, confirm the colour-space and source assumptions. If blacks look grey and the image seems washed out, or shadow and highlight detail appear clipped, inspect range through the chain. Adjust one aspect at a time so you can tell which change affected the result.
A common SDR starting configuration in older OBS community guidance is NV12, Rec. 709 and Partial (also called TV or Limited) range. Treat that as a conventional starting point for a video-range source, rather than a required package for every 4K60 stream. The OBS community’s colour settings guide explains the distinctions, but it is not a current official OBS manual; labels can vary by version and source type.
YouTube’s guidance also covers ingest settings beyond colour. For 2160p60, it lists recommended bitrates of 35 Mbps for AV1 or HEVC and 50 Mbps for H.264, with minimums of 10 Mbps and 14 Mbps respectively. Those are YouTube-published recommendations, not guarantees that a particular internet connection can sustain the stream. Select a bitrate your upload path can hold steadily, and test at the actual resolution, frame rate and codec before relying on it overnight.
Choose range to match the source path
Range is a description of how brightness values are represented, not a colour gamut. In an 8-bit signal, the OBS community guide describes Limited luma values as 16–235 and Full values as 0–255. Devices can convert between these representations, so the label chosen in OBS must describe the signal it receives at that point in the chain.
Use Limited when the source and capture path deliver video-range levels and the downstream processing expects them. Use Full when the source is actually outputting full-range levels and the intervening capture or conversion stages preserve that signal. The YouTube HLS specification supports both kinds of sample values; it recommends limited-range samples but also requires the declared range to match the content. In other words, a recommendation to use Limited is not permission to mislabel a Full signal.
The practical question is not “Is this a PC, console or camera?” but “What range is being output here, and what range is the next stage interpreting?” A computer monitor may display full-range output, while a capture card may convert incoming levels before passing them to OBS. Conversely, a camera or console may be configured for video levels. Do not choose Full simply because a computer monitor uses a full-range display.
A mismatch can be visible in either direction. If a Full signal is interpreted as Limited, the ends of the range can be clipped and detail may be lost. If a Limited signal is interpreted as Full, the picture can look washed out, with blacks lifted and contrast reduced. These descriptions help you identify a likely mismatch, but they are not proof of which device caused it; check the source and each conversion stage.
| Signal arriving at OBS | OBS range to try | What to verify |
|---|---|---|
| Video-range signal, with no conversion to Full | Limited / Partial / TV | Confirm the source and capture path are still outputting video levels. |
| Full-range signal preserved through capture | Full | Check that the capture device has not converted or expanded the levels. |
| Range is unclear or the image looks wrong | Do not guess from the monitor alone | Inspect source, capture-device controls and OBS; compare a test capture. |
The table is a decision aid, not a device compatibility list. A capture card can change the signal, and two systems with the same camera or console may have different output settings. For a complex path, record the setting at each stage: source output, any capture-device conversion, then OBS interpretation. That makes it easier to reverse a change if the picture gets worse.
Find the video controls in OBS
In OBS, open Settings, then Advanced, and look under Video for the colour-space and colour-range controls. The exact layout or wording may differ between OBS versions. Check that the setting you are changing applies to the processed output, and confirm the selected SDR colour space is Rec. 709.
Set the range only after deciding what the input path supplies. If your setup offers Partial and Full rather than Limited and Full, Partial is commonly used for Limited video range. The terms are often used interchangeably in video workflows, but rely on the actual source and device behaviour rather than the name alone. Keep a note of the original setting before changing it.
Do not assume that the 4K60 part of the setup changes this logic. Resolution and frame rate affect encoding load and bandwidth, while colour space and range identify how the image is represented. A stable 2160p60 stream still needs a sustainable upload connection and a correctly configured encoder. YouTube recommends testing with representative motion and audio and watching stream health; its encoder page also lists CBR and a two-second keyframe interval as recommended, with intervals not to exceed four seconds.
If you are building a looped channel rather than capturing a live camera, first make sure the media itself is suitable for continuous playback. This guide to preparing long MP4 files for OBS addresses playback reliability, which is a separate problem from colour interpretation. A file that loops reliably can still have a range or colour-space mismatch when OBS processes it.
Inspect capture-card settings as well
When a capture card is involved, OBS is only one part of the path. Check the source device’s output setting, the capture card’s input and processing controls, and the OBS source properties or advanced video controls. Some capture devices convert levels or expose their own colour settings, so the OBS choice must match what the card passes onwards, not merely what the console or camera originally produced.
If you are capturing a PC or console, look for output options related to RGB range, video range or black level at the source. Then inspect the card’s current driver or utility for any range or colour conversion option. Finally check the OBS source properties and global video settings. Avoid changing several controls at once; if the result shifts, you will not know which stage caused it.
An OBS community resource about the Elgato 4K60 Pro provides examples of separate full- and limited-range cases. Its instructions date from 2018, so treat them as an illustration of why matching matters, not as current menu directions for every card or driver. Check the device maker’s current documentation and the menus available in your own version.
A capture card is not required simply to set OBS’s colour space or range. If you are using a webcam, media source or direct desktop capture, focus on the settings that exist in that path. Where no explicit source range control is available, use a representative test and check for a consistent image from source to OBS preview and output, rather than inventing a setting that the device does not expose.
Test with the image you will actually stream
A single still image can hide a mismatch that becomes obvious in motion or in another scene. Test with a representative part of your content: a bright frame, dark detail, skin tones if present, and the sort of movement your channel normally shows. Compare the source view with OBS preview and, if practical, a private or unlisted test stream. Do not make the test depend on a promise that YouTube will preserve every pixel exactly; YouTube transcodes live streams into multiple output formats.
A colour or range test chart can help expose clipping and lifted blacks, but it is only useful when you know how the chart was generated and displayed. The OBS community guide includes test charts; do not mistake them for an automatic calibration system. Look for near-black and near-white detail rather than judging the image by brightness alone, and keep other display adjustments constant during comparison.
If the result looks washed out, check whether a limited source is being interpreted as Full. If shadow or highlight detail disappears, check whether a Full source is being interpreted as Limited or clipped earlier in the chain. Revert the last change if it makes the image worse, then trace the signal from source to capture device to OBS again. It is safer to verify each stage than to try combinations at random.
For 4K60, also test whether the stream remains stable at your intended encoder settings. YouTube’s published bitrate recommendations vary by codec, and a bitrate figure does not account for every network fluctuation. Leave enough headroom for a reliable upload and monitor the test’s stream health. If you are troubleshooting dropped delivery rather than a washed-out picture, this upload-speed guide for a 24/7 church stream covers the separate question of connection capacity.
Colour accuracy and continuity are different tasks. A correct Rec. 709 and range setup will not stop an encoder or computer from disconnecting during a long broadcast. If the aim is a channel that runs when your local computer is off, compare cloud PC and VPS workflows for prerecorded live streams separately from this image-quality setup. Keep the colour test focused on the signal path, and the reliability test focused on whether the broadcast continues.
HDR is a different configuration
If the source is genuinely HDR, do not apply the SDR advice as though it were a universal 4K setting. YouTube’s HDR instructions describe a 10-bit workflow using BT.2020 primaries and matching transfer and matrix characteristics. For OBS, the guidance specifies a compatible hardware HEVC encoder, Main 10, P010, and Rec. 2100 PQ or HLG; YouTube recommends HLG. Confirm that the source and encoding hardware support the chosen path before enabling it.
Range still needs to describe the samples produced by the source. YouTube’s HDR guidance says to enable Full only if the source produces full-range video. That is consistent with the SDR principle: the range setting describes what is actually being sent, not what seems preferable in the abstract. If you do not have an HDR source and do not intend an HDR broadcast, remain with the conventional SDR Rec. 709 path.
The HDR controls are not a shortcut for a brighter or more vivid SDR image. Converting SDR material into an HDR-labelled stream does not create the missing highlight detail or colour information. If a channel consists of ordinary SDR video, configure it as SDR and investigate any washed-out appearance by checking range and conversions instead.
Make a repeatable pre-stream check
For a channel that runs for hours, write down the working configuration once it has passed a representative test. Note whether the source is SDR or HDR, the OBS colour space and range, any capture-card conversion, and the encoder settings used for the test. If a driver update or OBS upgrade changes the image, this record gives you a known starting point rather than a memory-based guess.
Check the result after the full path is active, not only in a camera’s settings panel. A source can be configured one way, converted by a device, and then interpreted differently by OBS. If your channel changes sources—for example, from a camera to a desktop scene—verify the new source path separately; one global range assumption may not describe every input equally well.
Keep the test modest and practical. Confirm that the image’s dark and bright detail remains visible, that the stream is using the intended SDR or HDR configuration, and that the broadcast remains stable at the chosen 4K60 encoding load. YouTube’s recommendations are useful starting points for ingest, but your own upload connection and equipment decide whether those settings remain workable in practice.
When a file-based channel is already prepared and you want to avoid leaving a local machine running, StreamNeo removes that specific operational burden by running an uploaded video as a YouTube live stream while your computer is off. It does not change the need to confirm your file’s colour characteristics or choose a matching workflow before you broadcast.
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
Should I use Rec. 709 for every 4K60 YouTube stream?
Use Rec. 709 for conventional SDR; 4K60 does not automatically mean HDR. If your source is HDR and you intend to stream HDR, follow YouTube’s separate HDR requirements and confirm the source and encoder support them.
Is Limited range always right for YouTube Live?
No. YouTube recommends limited-range samples in its HLS guidance, but the selected range must match the actual content. Use Limited when the source path supplies video-range levels, and Full when full-range samples are preserved through the path.
Where do I change OBS colour space and range?
The controls are under Settings > Advanced > Video in OBS. Also inspect the properties or control panel for your capture device, if you use one, because it may convert the incoming signal before OBS receives it.
What should I change if my stream looks washed out?
Check whether a Limited signal is being interpreted as Full, then trace source output, capture-device processing and OBS settings in order. Change one stage at a time and verify with a representative test; the symptom points to a possible mismatch but does not identify the device by itself.