For a 4K 60fps YouTube Live loop, set OBS to 3840×2160 at 60 frames per second, use constant bitrate (CBR), and configure a two-second keyframe interval. At 60fps, two seconds is 120 frames; then test the media joins and confirm YouTube is receiving a healthy stream before you rely on it overnight.
OBS can repeat a video or playlist, but that only controls what plays next. It does not make the end of a file match its beginning, nor does a fixed keyframe interval guarantee uninterrupted delivery. Treat repeat behaviour, transition quality and stream health as three separate checks.
Prepare a prerecorded loop in OBS
Start with the actual video files you intend to broadcast. In OBS, create a scene for the stream and add the prerecorded file as a Media Source. Open the source properties and check that the correct local file is selected, that its dimensions and orientation make sense on the canvas, and that its audio is present if the clip is meant to have sound. A source that plays correctly in an editing preview may still be misframed or silent in the OBS scene.
Keep the project simple while you troubleshoot. A single scene with one video source makes it easier to identify whether a problem comes from the media, the scene layout, the encoder or the connection. If you are re-encoding a folder of clips before importing them, the HandBrake queue workflow can help you process files consistently; it is not a substitute for checking the resulting files in OBS.
For 4K at 60fps, the file itself needs to contain the image and motion you want viewers to see. Sending a lower-resolution or lower-frame-rate file through a 4K/60 encoder setting does not create genuine detail or motion that was not in the source. Conversely, a demanding source can make preview performance a useful early warning: play a representative section and watch whether OBS remains responsive before configuring a long broadcast.
Use a source with rights appropriate for repeated public streaming. A video that is available to download is not automatically cleared for an always-on broadcast. If you are using stock clips or music, review the terms for the specific asset and intended use; the discussion of licence traps for 24/7 loops is relevant before you assemble a long playlist.
Enable looping for one Media Source
In the Media Source properties, enable Loop. OBS defines this option as replaying the file after playback completes. This is the repeat control: when the source reaches the end, OBS starts it again. It does not add an edit, crossfade the audio, conceal a black frame or repair an abrupt cut encoded into the file. The OBS Media Sources documentation describes the source options; labels and layout may vary with OBS versions.
Test the repeat in the scene rather than assuming the checkbox is enough. Let the file reach its end and observe the first moments after it restarts. Look for a pause, black image, frozen frame, unexpected reset of a title or abrupt audio change. For a short test, seek close to the end if the controls allow it, but also let it run naturally at least once: seeking can obscure behaviour that occurs during ordinary playback.
If the source does not start or restart as expected, check the selected file path and source properties first. Avoid changing multiple encoder settings to fix a media-source problem. A keyframe interval affects the encoded stream's frame groups; it is not a loop or transition setting inside the media file.
Use a playlist for multiple clips
When the programme consists of several files, OBS's VLC Video source supports a playlist that can be looped. Add the intended files in their planned order, enable playlist looping, and test both a transition from one clip to the next and the eventual return from the last clip to the first. Those are different joins and can fail in different ways. A playlist that advances reliably can still have an awkward black gap or a loudness jump at one boundary.
Choose whether to keep clips separate or assemble them into one continuous file based on how you need to update the programme. Separate sources make it easier to replace one item or adjust the running order, but introduce more boundaries to inspect. One joined file reduces playlist transitions, but a change to one segment may require you to prepare and check the combined file again. Neither approach inherently makes the content seamless.
A playlist also needs an operational fallback. Check what happens if a clip is moved, renamed or unreadable, because a missing item can interrupt the intended sequence. For a broader approach to failures in a video sequence, see keeping a YouTube playlist running when one video fails. That is a separate concern from whether OBS repeats the clips successfully, so test the exact OBS source you plan to use.
Set the canvas and output to 3840×2160 at 60fps
In OBS video settings, set the base canvas and output resolution to 3840×2160 if you want the stream encoded at 4K. Set the common frame rate to 60fps. Check the preview after changing resolution: a source with a different aspect ratio may be scaled, cropped or surrounded by unused canvas depending on your scene layout. Review the complete frame, including text near the edges, rather than relying on a small preview.
A 4K/60 output asks the encoder and upload connection to handle more data than a lower-resolution or lower-frame-rate stream. YouTube's encoder guidance supports frame rates up to 60fps and publishes codec-specific 2160p60 bitrate recommendations. The setting should match what your material and equipment can sustain, not just the highest option shown in a menu. If the computer struggles to encode representative motion or the upload varies, a lower output setting may be a more dependable choice for your viewers.
For SDR material, follow YouTube's recommended SDR colour guidance rather than selecting HDR options by default. The official encoder settings and bitrate guidance distinguishes these workflows and gives the current recommended values. A 4K label alone does not tell you whether the source is HDR, and applying an HDR workflow to SDR content can produce an unintended appearance.
Configure CBR and a two-second keyframe interval
In OBS's streaming output settings, choose a supported encoder and set rate control to CBR. Set the keyframe interval to two seconds. YouTube recommends a two-second keyframe frequency and says not to exceed four seconds. With a 60fps output, the two-second target is 120 frames. If the encoder asks for seconds, enter two; if it asks for frames, use 120 at this frame rate.
The keyframe interval is not the same as the video frame rate. Frame rate describes how many frames are sent each second; keyframes provide reference points within the encoded sequence. A fixed interval is the intended configuration, but do not assume the value shown in OBS proves what YouTube received. Check the stream diagnostics after connecting and look for GOP/keyframe messages. The Live Streams API documentation describes diagnostics that can report keyframe-related issues. An interval over four seconds can be flagged, while an unusually short GOP can reduce image quality.
Select the bitrate according to codec rather than using one 4K/60 figure for every encoder. YouTube's published table gives these 2160p60 recommendations:
| Codec | Minimum bitrate | Recommended bitrate |
|---|---|---|
| AV1 or H.265/HEVC | 10 Mbps | 35 Mbps |
| H.264 | 14 Mbps | 50 Mbps |
These are YouTube's recommended ingestion settings, not a promise of the quality any viewer will receive. In particular, a recommended bitrate is useful only if your encoder supports the codec and your actual upload connection can sustain the selected rate. H.264 may be the practical choice on equipment without suitable AV1 or HEVC encoding support, even though YouTube lists a higher recommended bitrate for it. Compare codec support, the published bitrate for that codec, and whether your source is SDR or HDR before settling on a configuration.
YouTube recommends RTMPS, the encrypted version of RTMP. In Live Control Room, create or select the broadcast and enter the stream URL and stream key in OBS. Treat the key as a password: keep it out of screenshots and public notes, and reset it in Live Control Room if it is exposed. YouTube explains how to set up a live stream with an encoder. For 4K, plan for normal latency rather than expecting YouTube's low-latency option, which is not offered for 4K streams.
Inspect loop joins for audio or visual breaks
A looping checkbox and an encoded keyframe interval address different mechanics. The checkbox tells OBS to replay a file; the keyframe setting shapes the outgoing encode. Neither edits the file's end-to-start boundary. To judge transition quality, watch and listen to the actual restart in the OBS programme output, and, if possible, review a test stream as a viewer. The playlist troubleshooting guide may help when the issue is failure to advance, but a successful advance does not prove the cut sounds or looks right.
Inspect the last seconds and first seconds of each file pair. Watch for a flash to black, a frozen final frame, a jump in camera position, a change in brightness or a title that resets mid-sentence. Listen for silence, a click, an abrupt cut in music, a duplicated phrase or overlapping audio. For devotional or ambience channels, a short discontinuity in a sustained sound can be more noticeable than a visual cut; for news or study loops, a repeated opening sentence can confuse someone who joins part-way through.
If the boundary is poor, edit the content or choose a more suitable point to begin and end. A fade can soften an audio change, but it may not suit a continuous beat or spoken sentence; a crossfade can also briefly combine two sounds. A visual dissolve may hide a cut but can make text or moving subjects appear doubled. Make the change in the source edit, render a new file, and test that file in OBS. Avoid assuming that a transition effect is an automatic property of the loop control.
Test every distinct boundary in a multi-clip playlist, not just the first one. Also watch what happens after the full sequence returns to its first clip. If the file is long, make a shorter test playlist containing representative material and the difficult joins, then test the final arrangement before broadcast. Keep a note of the tested file version so you do not replace it after validation without checking again.
Check stream health before relying on the broadcast
Run a preflight using the same computer, OBS scene, encoder settings and upload connection planned for the broadcast. YouTube explicitly advises testing with audio and movement similar to the live stream. That matters for a loop because a static opening screen may put less pressure on the encoder than a section with camera movement, animated lyrics, particle effects or several layers. Include the busiest representative part and listen through a join.
Once the encoder connects, wait for YouTube to show that it is receiving the stream and review stream health and any messages in Live Control Room. Check that the received resolution and frame rate are what you intended, that audio is present, and that the bitrate is not repeatedly dropping below the selected target. Check keyframe or GOP diagnostics too: the setting in OBS is a configuration, while the incoming diagnostics are evidence of what arrived. YouTube's stream health guidance is the place to interpret current warnings.
An upload test should use the actual connection and the selected codec and bitrate. Leave margin rather than selecting a bitrate that consumes the whole measured upload capacity; other devices and normal network variation can affect what remains available. If the connection cannot sustain the chosen rate, reduce the stream settings and test again. YouTube may transcode a live stream into other formats for viewers, but transcoding does not repair an unstable incoming feed or a bad source join.
Before committing to an all-night setup, let the test run long enough to expose ordinary operational issues: a source that fails to restart, audio that disappears, encoder overload, or a connection warning. Keep the computer awake and the broadcast scene undisturbed if using OBS locally. If first-time live streaming has not been enabled on the channel, YouTube says activation may take up to 24 hours, so check access before the planned start rather than discovering the delay at airtime.
A cloud-based broadcast can remove the need to leave your own computer running for a prerecorded loop: StreamNeo takes the uploaded file and YouTube stream key so the broadcast can continue with your computer switched off, with monitoring and automatic restart if it drops. You still need to check the content, keyframe configuration and YouTube stream health; the delivery method does not make a loop join seamless or guarantee uninterrupted YouTube delivery.
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 keyframe interval should I use for 4K 60fps YouTube Live?
Set a fixed two-second interval. At 60 frames per second, that corresponds to 120 frames; YouTube recommends two seconds and says not to exceed four seconds. Verify the received stream diagnostics rather than relying only on the OBS field.
What bitrate should I use for YouTube 4K 60fps?
YouTube's encoder table lists 35 Mbps recommended for AV1 or H.265/HEVC, and 50 Mbps for H.264, with lower minimum values for each codec. Treat those as ingestion recommendations, not guaranteed viewer quality, and check that your encoder supports the codec and your upload connection can sustain it.
Does enabling Loop in OBS make a seamless transition?
No. It tells OBS to replay the file when playback completes, but the end and beginning may still have a visual or audio break. Inspect the boundary and edit or choose the source material accordingly.
How do I know the stream is ready for an overnight run?
Test the actual scene and connection with representative motion and audio, then confirm YouTube receives the expected resolution, frame rate and a healthy stream. Review warnings and keyframe diagnostics, and watch the joins in the programme output before relying on the loop.