For a 4K 60fps YouTube Live loop, set OBS to 3840×2160 at 60 fps, select an NVIDIA NVENC encoder that your installed OBS build and GPU actually offer, and use YouTube’s ingest settings. Add your prerecorded video as a repeating media source, connect the event’s stream URL and key, then test and monitor the feed before relying on it.
The settings do not guarantee that a particular computer, source file or internet connection can sustain 4K60. Treat the first broadcast as a controlled test: confirm YouTube detects the intended resolution and frame rate, check stream health, and make a lower-resolution fallback plan if the feed is unstable.
Check OBS, GPU and source-file readiness
Start by noting the OBS version shown in its About information and the NVIDIA GPU in the computer. Menu names, encoder options and controls can differ between OBS releases and GPU generations. An NVENC option visible in a guide may not be present in your installation; choose from the options actually offered rather than trying to reproduce a label from a different version.
Check that the existing GPU supports an NVENC option in OBS and that the system can decode the video while encoding a live output. This guide does not require buying a particular card, capture device or paid programme. OBS is listed by YouTube as an encoder available at no charge. If your installed build has no NVIDIA encoder choice, investigate OBS and driver compatibility or use a supported encoder available to you.
Inspect the source file before building the scene. Note its resolution, frame rate, aspect ratio, audio tracks and duration. A 4K output setting cannot restore detail absent from a smaller source, and a 60 fps output setting does not turn lower-frame-rate footage into genuinely captured 60 fps motion. If the file is a different shape from the 16:9 canvas, decide whether to accept bars or crop some picture; avoid stretching faces, text or scenery to fill the frame.
Also consider the material’s rights and the channel’s intended use. A stream key only connects an encoder to a YouTube event; it does not establish permission to broadcast the video or audio. Keep a copy of the original file and, if possible, a shorter representative clip for testing scene transitions and sound before scheduling a long loop.
A loop of one clip has a different operational risk from a folder of clips. A file that ends with a black frame, abrupt silence or a visible editing slate will repeat that defect each time it reaches the end. Review the beginning and end of the source, and consider whether the transition is acceptable before you leave OBS running.
Set the 3840×2160, 60 fps output
In OBS’s video settings, set both the base canvas and the output resolution to 3840×2160 when your source, GPU and connection can sustain that target. Set the common frame rate to 60 fps. The exact placement and wording of these controls may vary by version, so use the installed OBS interface and its documentation rather than assuming a universal click sequence.
For ordinary SDR content, use square pixels, progressive scan, Rec. 709 colour and 8-bit output. These match YouTube’s listed SDR guidance. HDR is a separate workflow: YouTube recommends HEVC/H.265 and 10-bit for HDR and does not support AV1 for HDR in the cited guidance. Unless HDR is an explicit requirement and your source, encoder and workflow support it, keep this setup in SDR.
The output resolution and frame rate are independent of what the source contains. If your source is 1920×1080, OBS can scale it to a 3840×2160 output, but the additional output pixels do not create original 4K detail. Likewise, 60 fps output may repeat or interpolate frames from a lower-rate source depending on the workflow. Match the output to a real delivery need, not merely to a menu option.
A 4K60 feed also asks more of the encoder and upstream connection than a smaller stream. Close unnecessary GPU-heavy applications, avoid changing several demanding settings at once, and watch both OBS statistics and YouTube’s health messages during a test. If performance is marginal, reducing output resolution or frame rate is a practical fallback; a stable lower-resolution broadcast is preferable to repeatedly dropping frames at a nominal 4K60 setting.
YouTube’s live encoder settings say 2160p60 cannot use the low-latency option and is set to normal latency. That matters if your plan depends on rapid viewer interaction: account for the additional delay rather than searching for a low-latency switch that the platform does not make available for this format.
Choose an available NVENC mode
In OBS’s streaming output settings, choose an NVIDIA NVENC video encoder if one is available. Some installations expose more than one codec-specific NVENC choice; others may expose a different set. Select only a mode supported by both your installed OBS build and GPU, and confirm that the codec you choose is accepted by the YouTube workflow you plan to use.
For a broad-compatibility starting point, H.264 is the straightforward choice. YouTube’s current live encoder settings page, accessed in October 2026, recommends 50 Mbps for 4K/2160p at 60 fps with H.264, with 14 Mbps as the minimum. For H.265/HEVC or AV1, the same page recommends 35 Mbps and lists 10 Mbps as the minimum. These are ingest recommendations, not a promise about viewers’ delivered quality or a substitute for testing upload capacity.
| Codec | YouTube’s 4K/2160p60 recommended video bitrate | Listed minimum | Practical consideration |
|---|---|---|---|
| H.264 | 50 Mbps | 14 Mbps | A broad-compatibility starting point if NVENC offers it |
| H.265/HEVC | 35 Mbps | 10 Mbps | Use only if the encoder and your workflow support it |
| AV1 | 35 Mbps | 10 Mbps | Availability depends on the GPU, OBS build and destination workflow |
YouTube’s page lists CBR and recommends a keyframe interval of two seconds, with no more than four seconds. Set those values in the encoder controls when available. Its advanced SDR recommendations also include two B-frames and one reference frame, but controls and supported values can vary; do not force settings that OBS does not expose or that the selected GPU cannot use. For more detail on the interval itself, see this guide to GOP length and keyframe interval for prerecorded YouTube Live.
Do not assume that a named preset, tuning option or rate-control control is universal. OBS documents that some advanced NVENC controls are specific to particular versions and hardware. Its Advanced NVENC Options article describes controls introduced in OBS 31.0; use it as version-specific documentation, not evidence that every control exists in every installation. If the UI offers a standard preset but not a guide’s newer option, use an available conservative configuration and test.
Choose the bitrate with headroom in mind. If the connection’s upload capacity varies, operating close to the line leaves little room for other network use or fluctuations. YouTube’s minimum is not a target that guarantees an acceptable 4K60 result. If the recommended rate cannot be sustained, test a lower resolution or frame rate instead of assuming that a low bitrate will preserve the same picture quality.
For related codec trade-offs, the HEVC guide for YouTube Live playlist streams can help you think through whether an alternative to H.264 suits your encoder and audience. In either case, judge the result by YouTube’s ingest status and actual viewing needs, not by the codec name alone.
Add and repeat the prerecorded video
Create or select the OBS scene for the broadcast, then add the prerecorded file as a media source using the controls in your installed OBS release. Find the source’s repeat or loop option and enable it. Because media-source controls can change, check the current OBS documentation for your version if the option’s label or location differs; the important behaviour is that playback starts again when the file reaches its end.
Fit the source to the canvas while preserving its aspect ratio. If the source is not 16:9, decide whether letterboxing or a deliberate crop is less distracting. A crop may remove information at the edges, so check titles, subtitles and any logos before leaving it in place. Avoid stretching the image simply to fill 3840×2160.
Check the media source’s audio behaviour as well as its picture. Confirm that the intended audio track is audible in OBS, that it does not overlap with another scene source, and that its level is not clipping. If the video has no sound, decide whether the channel should be silent or whether you have a separate, properly licensed audio source. Keep the choice deliberate; an unnoticed desktop audio source can add sounds that were not in the prerecorded file.
Watch through the end of the clip and into the restart. Confirm there is no unwanted pause, flash, black frame or audio cut that would become part of the repeating experience. A short source can still work, but repeated seams may be noticeable; an extended source can make the seam less frequent without removing it. If you are looping multiple videos rather than a single file, OBS source behaviour and transitions need separate checking. This guide to looping multiple videos in OBS without a transition gap covers that different case.
For a long-running broadcast, the local approach means OBS and the computer must keep operating, with the source file available and the connection maintained. If having a computer run continuously is the specific problem, StreamNeo removes that need by taking an uploaded video and running it as a YouTube stream while your computer is off. It is YouTube-only; decide whether that operating model fits before changing the workflow.
Configure YouTube ingest settings
YouTube accepts RTMP/RTMPS and lists H.264, H.265 and AV1 video, with frame rates up to 60 fps, in its encoder settings. Prefer RTMPS when the option is available. In OBS, enter the YouTube-provided stream URL and select the matching encoder configuration; do not copy a URL or key from an unrelated event.
Set the encoder to CBR and a two-second keyframe interval, keeping YouTube’s stated maximum of four seconds in mind. Match the codec-specific bitrate recommendation from the table above where the setup can sustain it. YouTube also accepts AAC or MP3 audio, and its guidance lists 128 Kbps for stereo audio, 44.1 kHz for stereo and 48 kHz for 5.1. Use the channel format you actually intend to send rather than configuring surround sound for a stereo source.
YouTube’s ingest recommendation is not a viewer bitrate guarantee. The platform processes a live feed for playback, and a viewer’s available quality depends on the stream and playback conditions. Check the health messages in Live Control Room to see whether YouTube is receiving the expected format, and separately check playback on a device or connection representative of your audience.
If you already have an OBS bitrate checklist, compare it with the 4K60 YouTube Live bitrate settings for OBS. Use the current YouTube page as the authority when recommendations change. A guide can explain what to check, but it cannot tell whether your own uplink will remain steady through an overnight stream.
Connect Live Control Room URL and stream key
Prepare the event in YouTube Studio’s Live Control Room. Create or schedule a stream and retrieve its stream URL and stream key. If this is the channel’s first live broadcast, enable live streaming in advance: YouTube says initial activation may take up to 24 hours. Consult its guide to creating a live stream with an encoder for the current event workflow.
In OBS, paste the URL into the server or URL field and enter the corresponding stream key in its designated field. The labels depend on the OBS version. Treat the key like a password: YouTube uses it to identify which encoder feed to accept, and anyone who gets it could potentially send a feed to that stream. Do not show it in a screenshot, share it in a public guide or save it somewhere others can access.
Confirm the key belongs to the event you intend to use. YouTube’s live stream settings guidance explains event and key management. If a key has been exposed, use YouTube Studio’s current controls to manage or replace it, then update OBS with the correct value. Avoid testing with a live event that has the wrong title, audience setting or scheduled time.
Once OBS connects, wait for the event preview or incoming signal in Live Control Room before starting a public broadcast. Whether you schedule, keep the event unlisted for testing or go live directly depends on the channel’s plan. Verify the current visibility and audience settings in Studio; do not assume that entering a key alone sets them correctly.
Test output and troubleshoot issues
Run a test using representative video movement and audio before a scheduled broadcast. YouTube specifically recommends testing and monitoring the stream’s health and messages. If practical, use an unlisted event or another controlled setup and check that the incoming stream is identified as 2160p60. Test the file’s repeat point as well as its opening, since a clean start does not prove a clean loop.
Use OBS’s statistics and YouTube’s Live Control Room together. OBS can help distinguish rendering or encoding overload from network drops; YouTube’s health messages indicate what its ingest is receiving. Make a note of the time when a warning appears, what changed immediately beforehand, and whether the issue appears in the local preview, YouTube preview or both. Change one setting at a time so that a successful adjustment has a clear cause.
| What you see | What to check first | A practical next step |
|---|---|---|
| YouTube does not detect 2160p60 | OBS output resolution, frame rate and event ingest status | Recheck the output settings and allow the event to identify the incoming format before making it public |
| Dropped frames or unstable health | Upload connection, competing network traffic and bitrate | Reduce competing traffic; if the feed remains unstable, test a lower bitrate or output format |
| Encoding or rendering overload | OBS statistics, other GPU-heavy tasks and the selected encoder mode | Close unnecessary GPU workloads or test a less demanding output configuration |
| Black frame or pause at the loop point | Source-file ending, repeat behaviour and media-source settings | Preview through a complete repeat and adjust the file or source configuration |
| Audio disappears, clips or drifts | Selected source track, OBS audio meter and the loop restart | Test representative playback and isolate the intended audio source |
| Stream connects to the wrong event | URL and stream-key pairing | Confirm the event in Studio and replace the OBS connection details with that event’s values |
If YouTube shows an ingest warning, do not treat it as proof that the whole broadcast is unusable or as a diagnosis by itself. Read the message, compare it with OBS statistics and test a single change. A bitrate below YouTube’s recommendation can be a sensible fallback when the connection cannot sustain the higher rate, but the image may lose detail; verify the result rather than assuming it is equivalent.
A short test can confirm configuration, not guarantee a 24/7 run. For an always-on loop, periodically check that OBS is still connected, the media source continues and YouTube health has not changed. Decide who will respond if the computer sleeps, the network drops or the application stops. If you do not want to operate a local computer continuously, a managed cloud workflow may suit you better; compare control, operating cost, scheduling and monitoring needs rather than assuming the same trade-offs as local OBS.
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 stream a 1080p video as 4K60?
OBS can scale a smaller source to a 3840×2160 output, but scaling does not add original image detail. A 60 fps output also does not make source footage captured at a lower frame rate genuinely 60 fps. Set the output to 4K60 only when there is a reason to deliver that format and the complete system can sustain it.
Which NVENC encoder should I select?
Select an NVIDIA NVENC option that your installed OBS build and GPU expose, then confirm its codec is suitable for your YouTube workflow. H.264 is a broad-compatibility starting point; YouTube’s current 4K60 recommendations also cover HEVC and AV1. The available controls and supported codecs vary, so test the option you actually have.
Does YouTube 4K60 support low latency?
YouTube’s current live encoder settings page says 2160p60 cannot use its low-latency option and is set to normal latency. Plan for that delay if you expect live interaction. Check YouTube’s official page before broadcasting in case platform guidance changes.
Is a successful test enough for a 24/7 stream?
No. A test helps verify the format, loop point, audio and ingest health at that time, but it cannot prove that the computer and connection will remain stable indefinitely. Monitor the stream during operation and have a response plan for dropped connections, source problems or encoder overload.