For a 24/7 pre-recorded YouTube stream in OBS, select a hardware encoder your computer and OBS installation actually support, then configure the streaming output for CBR and a two-second keyframe interval. Match the video bitrate to YouTube’s recommendation for your chosen codec, resolution and frame rate, but treat that value as platform guidance rather than a promise your connection or computer can sustain it continuously.
A setting that works for a short test is not proof that the same machine, network and feed will run unattended overnight. Set up the stream methodically, test it with representative content, and keep an eye on YouTube’s stream health before relying on it.
Choose a hardware encoder OBS actually offers
Open OBS’s streaming output settings and inspect the encoder choices available on your system. Depending on your hardware, operating system and OBS build, you may see NVIDIA NVENC, AMD AMF, Intel Quick Sync Video (QSV), or Apple VideoToolbox. The list is not universal: a codec or encoder mentioned in a guide may not appear on your particular computer.
OBS generally recommends using NVENC or AMF when your system has a corresponding NVIDIA or AMD GPU, rather than choosing QSV by default. That is a starting point, not a model-by-model ranking. Compare the options you can select by compatibility, the codec they expose, and whether the resulting settings match your target output. OBS explains the role and compatibility of hardware encoding.
A hardware encoder moves video encoding work away from the CPU to a specialised part of the GPU or platform. This can reduce CPU load, which matters when the computer is also reading a video file, composing scenes, and sending a live feed. It does not eliminate every possible limit: the encoder still has to produce the chosen output, while OBS and the rest of the computer continue doing their jobs.
YouTube lists H.264, H.265/HEVC and AV1 for live ingestion, but that does not mean OBS will offer all three on your device. Choose only from the codecs exposed by the installed software and supported hardware. If H.264 is the available choice, use the H.264 row in YouTube’s table instead of selecting an unavailable codec based on a lower listed bitrate.
If your computer has no suitable hardware encoder, or OBS does not expose the codec and output you need, do not force a setting that is absent. You can test the available software encoder, simplify the output, or consider compatible hardware after checking OBS’s requirements. For a broader overview of approaches to pre-recorded continuous broadcasts, see free tools for 24/7 YouTube streaming.
Set the streaming output, not the recording output
In OBS, find the Output settings for the live stream. If you are using Advanced Output Mode, configure the Streaming tab; if you are using Simple Output Mode, check the streaming options it provides and select the available encoder there. The exact labels can vary across OBS versions, so verify that you are editing the live output rather than settings for a local recording.
Choose the supported hardware encoder and codec you intend to send to YouTube. Check that the video dimensions, frame rate and bitrate you plan to use are set for the stream. Your local recording settings can be different: they control a file saved on your computer, not necessarily the encoded feed sent to YouTube.
That distinction prevents a common mistake. OBS’s recording guide gives recording-oriented examples, including constant-QP (CQP) for NVENC recording. YouTube’s ingestion guidance calls for CBR. A setting that makes sense for a high-quality recording is not automatically a suitable live-stream setting. Keep those profiles separate, and consult the OBS advanced recording guide only when configuring a local recording.
Before starting, confirm the stream destination and key in YouTube’s encoder workflow. The stream URL and key direct the encoder feed to the intended live stream. Treat the key like a credential: do not show it on screen or share it in a screenshot, and replace it if you believe it has been exposed. YouTube’s encoder setup instructions explain how to connect the encoder to a broadcast.
Use CBR and a two-second keyframe interval
For a YouTube live stream, set the streaming encoder’s rate control to constant bitrate (CBR). In CBR mode, the encoder aims to send video at the bitrate you specify rather than varying its target in response to each scene. YouTube asks for CBR for RTMP/RTMPS ingestion, so this is the appropriate baseline for the live output.
Set the keyframe interval to two seconds. YouTube says the interval should not exceed four seconds; two seconds follows its recommended baseline and is also used in OBS’s NVENC examples. If the OBS control expects seconds, enter two. If it expects frames, the corresponding value depends on the frame rate: for example, two seconds at 30 frames per second is 60 frames, while at 60 frames per second it is 120 frames.
Use RTMPS for ingestion where your encoder setup offers it. YouTube’s encoder recommendations cover the transport and stream parameters together, so check the current YouTube live encoder settings rather than relying on a remembered profile. Platform guidance can change, and the current official page is the right reference when you configure the stream.
Do not add advanced encoder controls simply because they exist. OBS’s advanced NVENC documentation notes that additional controls arrived in OBS 31.0, and describes options that vary by codec and use case. They are not prerequisites for a continuous broadcast. First establish a valid, testable baseline using the standard controls your OBS build exposes. If you adjust an advanced option later, change one thing at a time and test the actual feed again.
Match bitrate to codec, resolution and frame rate
YouTube’s recommended video bitrate depends on all three choices: codec, resolution and frame rate. Use the row that matches the output you are sending, not the resolution of the original file or a bitrate copied from someone using a different codec. For an SDR stream, YouTube’s published table includes these common examples:
| Output | H.264 video bitrate | AV1 or H.265/HEVC video bitrate |
|---|---|---|
| 720p30 | 8 Mbps | 6 Mbps |
| 1080p30 | 14 Mbps | 10 Mbps |
| 1080p60 | 17 Mbps | 12 Mbps |
These figures are YouTube’s recommendations, not measurements of your system and not guarantees of successful delivery. Check YouTube’s current table when setting up the stream. If OBS does not expose AV1 or H.265/HEVC, the values in those columns do not apply to an H.264 stream.
Think about the picture you are actually sending. A static devotional image, a lofi animation and a local news loop have different amounts of movement, but the table is still organised by codec, resolution and frame rate. The recommendation helps you choose a platform-aligned target; it does not tell you whether a particular network can maintain that rate or whether the source benefits from a higher frame rate.
For audio and picture format, YouTube’s RTMP/RTMPS guidance lists AAC or MP3 audio, 128 Kbps stereo audio, progressive scan, square pixels and Rec. 709 for SDR, with support up to 60 fps. Set the video output to the format you intend to deliver, and confirm OBS’s audio track is active. A quiet or silent source will remain quiet or silent even when the video encoder is configured correctly; if your loop has gaps, this guide to preventing quiet gaps between audio loops covers a separate content issue.
Compare 1080p30 and 1080p60 recommendations
For a common SDR output, 1080p30 is a practical place to begin when the source does not need smoother motion. At 30 frames per second, YouTube lists 14 Mbps for H.264 and 10 Mbps for AV1 or H.265/HEVC. At 1080p60, the listed recommendations are 17 Mbps for H.264 and 12 Mbps for AV1 or H.265/HEVC.
| Question | 1080p30 | 1080p60 |
|---|---|---|
| YouTube’s H.264 recommendation | 14 Mbps | 17 Mbps |
| YouTube’s AV1 or H.265 recommendation | 10 Mbps | 12 Mbps |
| A sensible fit | Slides, still artwork, gentle loops | Content where smoother motion matters |
| Main practical trade-off | Lower frame rate and bitrate target | Higher bitrate target and more frames to encode |
The table is a comparison of YouTube’s guidance, not a statement that 60 fps always looks better. If your video is mostly a still image or slow-moving background, 30 fps may be sufficient for the content and easier to fit within the available upload capacity. If the feed contains fast movement and the source itself has a 60 fps cadence, you may prefer 60 fps, provided the encoder and connection can handle the chosen output.
Do not upscale a lower-resolution source or raise its frame rate just to select a more demanding row. Choose an output that makes sense for the material and the audience, then apply the corresponding codec-specific bitrate recommendation. If your YouTube stream is capped at 1080p rather than 4K, investigate platform and stream configuration separately; changing a hardware encoder preset alone does not resolve every resolution issue.
Check upload capacity and encoder load
The bitrate in OBS is only one part of the delivery path. YouTube recommends enough outbound capacity for the stream and advises keeping 20% headroom. That means your connection should have capacity beyond the stream’s target bitrate, rather than running the broadcast at the edge of a speed-test result. Treat the 20% figure as YouTube’s planning recommendation, not as a promise against interruptions.
For example, if your chosen video bitrate is 14 Mbps, 20% additional capacity works out to 16.8 Mbps for the stream alone. Audio and any other outbound traffic also use capacity, and a shared connection may be serving phones, computers, cameras or cloud backups at the same time. Plan with the actual household or business use in mind, including any backup feed if you run one.
A speed test is a snapshot, not a night-long guarantee. Measure upload performance at the place and time the broadcast will run, and repeat the check when other devices are using the network. Prefer a wired network connection if it is practical, and avoid scheduling large uploads on the same connection during the broadcast. If you see dropped frames or interruptions, compare OBS’s statistics with YouTube’s stream health before deciding whether the cause is bitrate, network use, encoder load or something else. The Tata Play Fiber troubleshooting guide offers a network-focused checklist for one common home broadband setup.
Watch the encoder as well as the network. A GPU encoder can reduce CPU work, but OBS still has to read the media, keep the scene active and maintain the outgoing connection. Check OBS’s statistics while the actual stream is running: look for rendering or encoding lag and network-dropped frames. If the computer struggles, simplify scenes and filters, close unnecessary applications, or test a lower frame rate or resolution. A less demanding configuration that you have tested may be more useful than a higher specification that the machine cannot sustain.
A 24/7 feed also depends on the source and the operating routine. A file that ends, a media player that stalls, a power cut or a router restart can interrupt a stream even when the encoder values are appropriate. OBS settings address encoding; they do not by themselves remove every cause of an unattended broadcast stopping. If keeping a computer on and watching for a dropped process is the pain point, StreamNeo can run an uploaded video as a YouTube live stream without your computer remaining on, so you do not have to maintain the local OBS session yourself.
Test stream health before relying on it
Run a private or unlisted test first, with the same resolution, frame rate, codec, bitrate and scene you intend to use. Include representative movement and audio, rather than testing only a still screen if the live feed will contain animation or music. A test should exercise the real workflow: source file, OBS output, internet connection, stream key and YouTube preview.
Check the preview in YouTube Live Control Room and read the stream health messages. Confirm that video and audio arrive, that the picture is the expected size, and that OBS is not reporting persistent encoding or network problems. YouTube recommends testing and monitoring; neither an apparently clean preview nor a brief successful test establishes that the setup will run uninterrupted for 24 hours.
Let the test run long enough to expose ordinary conditions in your setup, including network activity and computer load. There is no universal test duration that proves continuous reliability. Record what you observe, then adjust one setting at a time. If you reduce bitrate, choose the new value by returning to YouTube’s table for the codec and output you will use, and check that the change still produces an acceptable picture.
Before moving to a regular broadcast, confirm the file is suitable for repeat playback, the audio does not unexpectedly fall silent, the key belongs to the intended stream, and you know where to check stream health. Recheck YouTube’s official requirements when you change the codec, resolution, frame rate or OBS version. A local checklist helps you repeat the setup, but it is not a substitute for monitoring the actual 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
Which hardware encoder should I choose in OBS?
Choose a supported encoder that OBS actually offers on your computer, such as NVENC, AMF, QSV or VideoToolbox, depending on your hardware and operating system. If a codec is not listed, do not assume it is available because YouTube supports it. Test the selected encoder with your actual output and feed.
What bitrate should I use for 1080p30?
YouTube’s published SDR examples recommend 14 Mbps for H.264 at 1080p30 and 10 Mbps for AV1 or H.265/HEVC at that output. Those figures are platform recommendations, not guarantees that your encoder or connection can sustain the stream. Check YouTube’s current guidance and leave upload headroom.
Should I use CQP for a YouTube live stream?
OBS’s recording guide uses CQP in NVENC recording examples, but that concerns a local recording. For YouTube live ingestion, use CBR as specified in YouTube’s encoder guidance. Keep recording and streaming output settings separate.
Do these settings guarantee an uninterrupted 24/7 stream?
No. They provide a practical starting point aligned with YouTube’s published ingestion recommendations, but continuity also depends on the source, computer, power, network and the conditions during the broadcast. Test the real setup and monitor stream health rather than treating any setting as a guarantee.