For an ordinary SDR loop, use Rec. 709 colour space and 8-bit SDR output. Use HDR settings only when the video itself is genuine HDR and your encoder path can preserve its intended signal.
The key is agreement: the source grade, its colour interpretation and the encoder settings need to describe the same image. Changing an SDR loop to HDR settings does not make it genuine HDR, and may make the result look wrong.
Start by identifying the source
Before changing an encoder menu, find out how the loop was created and exported. A phone video, an edited MP4, an animation and a professionally graded master may all be labelled “4K”, but resolution does not tell you whether the image is SDR or HDR. The colour space and transfer characteristics are separate from the pixel dimensions and frame rate.
Check the export settings in the editing application, the file properties if they expose colour metadata, or the information supplied with the master. If you commissioned the video, ask the editor whether the delivery is SDR or HDR and which colour space and transfer function it uses. Avoid guessing from how colourful it looks on your monitor: a vivid SDR image is still SDR.
For a typical loop assembled for YouTube from standard video clips, graphics, devotional artwork or a lofi visual, SDR is a reasonable starting assumption unless the source or export explicitly identifies itself as HDR. This is a question about the actual master, not what you hope the stream will look like. YouTube’s general live encoder settings guidance identifies Rec. 709 for SDR and distinguishes SDR from HDR bit depth.
Make a note of the source’s properties before opening the encoder. At minimum, record whether it is SDR or HDR, whether it is progressive video, its frame rate, and any colour information available. That gives you something definite to match, rather than a set of sliders to adjust by eye.
Ordinary SDR: Rec. 709 and 8-bit
For an ordinary SDR loop, set the encoder’s colour space to Rec. 709 and its output to 8-bit SDR. YouTube’s published SDR guidance names Rec. 709 and 8-bit. These are the starting settings for an SDR signal; choosing 10-bit or a PQ/HLG transfer option does not upgrade the source.
The complete live configuration has other parts. YouTube’s encoder table lists H.264, HEVC/H.265 and AV1 as live codecs, supports frame rates up to 60 fps, and specifies CBR, progressive scan, square pixels and a recommended two-second keyframe interval (not exceeding four seconds). For 4K/2160p at 60 fps, its English table gives 35 Mbps recommended for H.264 and a 10–40 Mbps range for AV1 and HEVC. As listed on YouTube Help’s site in October 2026, treat these as guidance for the listed modes, not a promise that every application, connection or ingest configuration should use the same bitrate. Check the current table and Live Control Room when choosing your settings.
Those codec and bitrate choices affect delivery; they do not determine whether your source is HDR. An SDR stream encoded at a high bitrate remains SDR. Conversely, setting Rec. 709 does not fix a file that has already been misinterpreted during export. Keep the colour decision distinct from the resolution, frame rate and bitrate decisions.
If the loop already looks as intended in an SDR player, start by matching its SDR signalling. Do not increase saturation or contrast simply because a setting is available. A change might suit one particular grade, but it is not a universal correction and can clip bright colours, crush shadow detail or make skin, text and artwork less natural. Make adjustments only to solve a visible, specific problem in the source, and check that the edited master remains SDR.
Keep the grade and signal interpretation together
A grade is the creative appearance given to the footage: the balance of colour, contrast and brightness chosen by its editor. Signal interpretation is how software or hardware understands the encoded values. The encoder must transmit a signal that accurately describes the source it is sending. If the source was graded and exported as SDR Rec. 709, label and encode it as SDR Rec. 709 rather than asking the encoder to describe it as PQ or HLG HDR.
A mismatch can show up as washed-out colours, excessive contrast, clipped highlights, dark shadows or a flat-looking image. These symptoms do not prove which setting is wrong, so change one thing at a time. Confirm the source export first, then check the encoder’s colour space, transfer function, bit depth and any range or metadata options your software exposes. Menu labels vary, and an option named “colour range” is not a substitute for selecting the right colour space.
For a loop made from several assets, also check the edited output rather than assuming every ingredient has the same properties. A graphic created in an editor may be combined with footage from a camera or downloaded clips; the timeline and export process determine the final signal. If a particular scene looks inconsistent, inspect it in the exported file and compare it with the project settings before changing the live encoder.
Keep an unmodified export as a reference. Compare representative frames from the actual stream with that file on a display that supports the signal you intend to send. A technically correct setting cannot restore detail or colour information removed earlier in the edit, and a preview on one device may not reveal how every viewer’s display will handle the stream.
For a stream that runs overnight, repeat the check at points across the loop rather than inspecting only its opening frame. A devotional image with deep shadows, a bright lamp, a dark gradient or strongly coloured lettering may expose a different problem than a calm mid-toned scene. YouTube recommends testing before going live, including audio and movement similar to the intended stream, and monitoring stream health during the event. Checking those kinds of frames is practical advice for your content, not a special YouTube test protocol.
Why SDR-to-HDR is not a vividness switch
HDR is a way to represent and display a wider range of brightness and colour, when the source, encoding and playback path support it. It is not a saturation preset. Sending SDR material through an HDR-labelled output does not reconstruct highlight or colour information that the SDR master never contained. It can instead cause the image to be interpreted differently from its intended grade.
The common temptation is understandable: select a more vivid-looking transfer option, see a brighter preview, and assume viewers will get a better picture. But the preview may be showing the wrong interpretation, or a display may be applying its own conversion. The result can vary between screens, and what looks striking in one preview can be too bright, washed out or unnaturally intense elsewhere.
If the SDR image genuinely needs correction, make the correction in the edit and review the resulting SDR export. Adjusting saturation or contrast is a creative decision tied to that footage, not a general YouTube Live colour recommendation. Retain the source, compare the export in a consistent viewing setup, and check the whole loop for new clipping or banding before replacing the file.
The same distinction applies to colour space menus. Rec. 2020 or Rec. 2100 options do not make a source HDR by their presence in an encoder. The labels describe how the outgoing signal is to be interpreted. For ordinary SDR, follow the SDR path; do not select HDR signalling in the hope that YouTube or a viewer’s television will turn it into a better grade.
When HDR settings are appropriate
Use HDR settings only when the loop itself is a genuine HDR master and the source, encoder and YouTube stream configuration support that HDR path. The master should have been produced or deliberately mastered for HDR, rather than converted from SDR just to select an HDR option. Confirm which transfer characteristic it uses: PQ or HLG.
YouTube’s HDR guidance calls for HEVC/H.265 and 10-bit output, and says that colour primaries, matrix and transfer characteristics need to match the content. Its OBS walkthrough describes an HEVC hardware encoder, Main 10 profile and P010 colour format, with Rec. 2100 PQ or HLG; it recommends HLG in that particular workflow. That walkthrough is not a reason to apply HLG to an SDR loop, nor does it establish that every encoder supports the same options.
| Decision | Ordinary SDR loop | Genuine HDR loop |
|---|---|---|
| Source | SDR master or export | HDR-produced source intended for PQ or HLG |
| Colour signalling | Rec. 709 | BT.2020 primaries and matrix, with PQ or HLG matching the source |
| Bit depth | 8-bit SDR | 10-bit output |
| Codec guidance | YouTube lists H.264, HEVC/H.265 and AV1 for live encoding | YouTube’s HDR guidance requires HEVC/H.265; it does not support AV1 for HDR |
| Practical starting point | Standard SDR live configuration | Compatible HDR encoder and appropriate YouTube stream configuration |
The table is a decision aid, not a substitute for your encoder documentation or YouTube’s current help pages. HDR support depends on the full path: the master, its metadata, the encoder’s format and the stream setup. If any part cannot preserve the intended HDR signal, use a suitable SDR deliverable instead of assuming that one HDR checkbox will handle the conversion correctly.
YouTube’s HDR streaming guidance describes its supported HDR workflows and settings. It notes that HDR streams can use RTMP(S) or HLS in the documented workflows, and that the HDR stream-key settings should keep “Turn on manual settings” unchecked. Follow the current instructions for the workflow you actually use; do not change stream-key options based on advice for a different encoder or transport.
HDR also changes what you need to verify. Check that the file really is HDR, that the encoder sends the intended 10-bit format, and that primaries, matrix and transfer characteristics describe that source. Then verify the stream on a supported HDR display, while remembering that viewers using SDR displays may see a conversion. If your workflow cannot confirm those points, a correctly signalled SDR stream is a more dependable choice than mislabelled HDR.
Check the whole 4K60 live path
Colour settings are one part of a stable 4K60 broadcast. Match the encoder’s frame rate to the source and the intended output rather than treating 4K as evidence that every clip is 60 fps. YouTube lists frame rates up to 60 fps; an export at a different frame rate may still be suitable, but unnecessary conversion can create uneven motion or duplicate frames.
For the encoder settings beyond colour, use YouTube’s live table as a reference, then check your actual application and ingest status. Its listed 4K60 bitrate figures differ by codec, and the table’s wording and columns can vary across localised results. As listed on YouTube Help’s site in October 2026, use the current English table and Live Control Room to confirm the appropriate bitrate for your codec and connection rather than treating a single number as universal. YouTube also says low latency is unavailable for 4K/2160 streams, which use normal latency.
Test the stream before relying on it for a long unattended loop. Include representative movement and audio as YouTube advises, and inspect scene changes, dark gradients, saturated colours and bright highlights. Confirm that the stream is stable in Live Control Room and that playback appears as expected on a supported display. These checks help separate a colour mismatch from dropped frames, an ingest problem or a playback-device limitation.
If your workflow uses OBS, a desktop encoder or a dedicated appliance, the relevant controls may be labelled differently. Do not buy a capture card merely to choose Rec. 709: the colour setting is a configuration choice. Additional hardware is worth considering only if your current equipment cannot process the 4K60 source and codec you have selected. For a 24/7 setup, the guide to running an OBS stream on a Jio laptop without sleep mode covers a separate operational risk: keeping a local computer awake.
The signal path also includes the exported file, the encoder and the stream key. If you are looping a yoga class or another pre-recorded programme, the guide to streaming a looping yoga video from an Indian broadband connection is useful for thinking through the broader source-to-live workflow. For a continuous pre-recorded channel, YouTube’s encoder stream creation instructions explain how to create a live stream with an encoder. The colour settings still need to be matched to your own file and encoder.
For an overnight loop, a small configuration error can repeat for hours. Keep a record of the export profile and encoder settings that passed your test, and check them again if you replace the video or update the encoder. If you want the broadcast to continue without leaving your own computer on, StreamNeo can remove that particular overnight computer-running task after you upload the video and configure the YouTube stream; it does not change the need to prepare the file and choose correct colour settings.
A practical preflight for your loop
Use this short preflight before scheduling or starting the stream. It is not a substitute for the current YouTube settings table, but it reduces the chance that a correct source is sent with an incorrect label.
- Identify the exported file as SDR or genuine HDR. Do not infer HDR from resolution, brightness or saturation.
- For SDR, set Rec. 709 and 8-bit SDR output. Leave HDR transfer options off.
- For HDR, confirm PQ or HLG from the source documentation, then use a compatible HEVC/H.265, 10-bit path with matching signal characteristics.
- Check representative frames in the exported file and in a test stream, including difficult dark and bright scenes.
- Confirm the selected codec, frame rate, keyframe interval and bitrate against YouTube’s current guidance and your encoder’s capabilities.
- Monitor stream health during the test and confirm playback on a display suited to the signal.
If the picture looks wrong, work from source to output: inspect the file, verify its interpretation in the encoder, and then inspect the received stream. Avoid changing several colour controls at once, since that makes it harder to identify the cause and to return to a known-good setup. When in doubt, ask whoever exported the video for its colour profile rather than applying HDR settings to an SDR file.
A stream that is visually simple can still contain difficult colour cases. A loop of a temple interior might have both a dim background and a bright flame; a study ambience scene may include a nearly black gradient; a local business display may rely on legible brand colours. Look at those scenes in motion and after encoding. If your workflow includes a logo or scrolling text, the guide to adding a logo and scrolling text to an FFmpeg YouTube stream addresses the overlay side of the output; keep those graphics consistent with the colour treatment of the video underneath.
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
What colour space should I use for 4K60 streaming?
For an ordinary SDR loop, use Rec. 709 with 8-bit SDR output. YouTube’s live encoder guidance specifies Rec. 709 for SDR; 4K resolution and a 60 fps frame rate do not change that colour recommendation. Use HDR signalling only for an HDR source and a compatible path.
Should I choose HDR to make my SDR loop more vivid?
No. An HDR output setting does not add genuine HDR detail to an SDR master, and it may cause the intended grade to be interpreted incorrectly. If the SDR picture needs a change, correct and review the SDR export rather than changing its signal type.
Which HDR settings does YouTube recommend?
YouTube’s HDR guidance calls for HEVC/H.265 and 10-bit output, with primaries, matrix and transfer characteristics matched to the source. Its OBS walkthrough uses Rec. 2100 PQ or HLG and recommends HLG in that workflow. Check the current official instructions and your encoder’s support before using those settings.
How can I tell whether the stream’s colour is wrong?
Compare the exported file with a test stream on a display appropriate for its SDR or HDR signal, then inspect difficult scenes such as shadows, highlights and saturated colours. Check the source profile and encoder interpretation before making grade changes. A preview alone may not reveal how all viewers’ displays will show the result.