For a typical SDR stream, start in OBS with H.264, CBR, a 2-second keyframe interval, AAC stereo audio at 44.1 kHz and 128 kbps, and Rec. 709 colour. Then choose the resolution and frame rate your computer and upload connection can sustain, and use the matching H.264 bitrate recommendation from YouTube.
Those settings are a practical baseline, not a universal best preset or a guarantee of quality. A static devotional image, a lofi visual loop and a fast-moving local news feed do not place the same demands on the encoder or network. YouTube’s encoder settings and bitrate table is the authority for the ingest combination you select; check it again when you configure a stream.
Start with a compatible SDR baseline
In OBS, set the output video encoder to H.264 if your computer offers it, then set rate control to CBR and the keyframe interval to 2 seconds. For an ordinary stereo stream, use AAC at 44.1 kHz and 128 kbps. Set the video colour space to Rec. 709 and the colour range and depth to a supported SDR configuration; YouTube’s guidance specifies Rec. 709 and 8-bit for SDR.
Encoder labels and available controls depend on your operating system, graphics hardware, drivers and OBS version. You may see a hardware H.264 encoder or a software option. Pick one your system supports and test it with the actual scene and content; the name of an encoder alone does not tell you whether your machine can keep up while doing other work.
This baseline aims for broad compatibility. YouTube also accepts H.265/HEVC and AV1, but their bitrate recommendations differ from H.264’s. If you change codecs, consult the corresponding row on YouTube’s page rather than carrying over the H.264 number. H.264 is a straightforward starting point where you want to configure a typical SDR setup without relying on a specialised workflow.
The appropriate choice also depends on what the channel is for. A still image behind a bhajan recording may not benefit much from a high frame rate, whereas a camera feed or fast-moving graphics may need smoother motion. Neither case changes the need to keep the encoder, resolution, bitrate and connection within what your setup can actually sustain.
Set H.264, CBR and a two-second keyframe interval
YouTube specifies CBR for these encoder settings and recommends a 2-second keyframe frequency, with a maximum interval of 4 seconds. In OBS, select CBR rather than a variable-rate mode, then enter 2 seconds for the keyframe interval. These are ingest requirements and recommendations from YouTube, rather than conclusions from a universal OBS preset.
A keyframe is a complete reference picture from which later frames can be decoded. A regular interval helps the platform ingest and process the stream. Setting a shorter or longer interval simply because an OBS tutorial recommends it can put your configuration out of step with YouTube’s guidance, so begin with two seconds.
CBR means the encoder aims to send video at a steady bitrate. That steady target makes it easier to plan the network capacity the stream needs, but it does not make an unreliable connection reliable. If the target video rate is more than the available upload can carry, the stream can lose frames or disconnect even though the OBS controls are set correctly.
Some versions of OBS expose advanced encoder controls, and YouTube gives additional guidance for advanced settings, including progressive scan, square pixels, two B-frames, one reference frame and CABAC entropy coding. Do not assume every control is available for every encoder or required in every workflow. Start with the controls relevant to the baseline, then use YouTube’s current documentation and the encoder’s supported options if you need to configure advanced details.
If you use OBS for a computer-based broadcast, keep configuration advice separate from continuity advice. The OBS Studio cost and streaming overview is relevant when deciding whether a local OBS workflow fits a long-running channel; it does not replace this encoder configuration or solve a computer that is switched off overnight.
Choose resolution and frame rate for your setup
Resolution describes the size of the video frame; frame rate describes how many frames are sent each second. Increasing either can add detail or smoother motion, but it also raises the data and processing demands. Choose based on your source material, audience, computer and upload link rather than treating 1080p60 as the default.
For example, a stationary illustration or album-cover visual paired with music may not need 60 frames per second. A presenter moving in front of a camera or a news loop with motion may make a higher frame rate more useful. If the content does not supply extra visual detail, raising the output resolution cannot create it; it can still increase the bitrate and encoder work needed to deliver the stream.
A sensible comparison is to consider 1080p30, 1080p60 and 720p at either 30 or 60 fps, then choose the combination you can test reliably. For a modest computer, 720p30 may be more practical than a higher setting that overloads the encoder. For a capable system with enough upload capacity and content that benefits from smoother motion, 1080p60 may make sense. These are examples for choosing, not promises about how a particular setup will perform.
The source matters too. If you are broadcasting a pre-produced file or a playlist, inspect its actual resolution and frame rate before setting OBS to upscale or convert it. A 24/7 ambient study music channel workflow may use a largely static visual, while a camera-based stream has ongoing movement that can reveal motion judder or encoding strain more readily.
Do not make the resolution choice in isolation from audio, overlays and other applications. A browser, scene transition, animated ticker or camera source can add work that a simple still scene does not. Test the intended scene, not an empty OBS preview, and watch the OBS status indicators for rendering or encoding lag. If the computer cannot encode the selected mode consistently, reduce the workload or choose a lower resolution or frame rate before considering more bitrate.
Match video bitrate to YouTube’s ingest recommendation
Once you have chosen H.264 and a resolution/frame-rate combination, look up its recommended video bitrate in YouTube’s table. The figures below are recommended ingest video bitrates, not total connection speeds and not guarantees of visual quality. The current page accessed for this guidance does not display a publication year, so these values are attributed to YouTube’s page rather than assigned an invented publication date.
| H.264 ingest setting | Minimum video bitrate | Recommended video bitrate |
|---|---|---|
| 1080p at 60 fps | 6 Mbps | 17 Mbps |
| 1080p at 30 fps | 5 Mbps | 14 Mbps |
| 720p at 60 fps | 3 Mbps | 8 Mbps |
| 720p at 30 fps | 3 Mbps | 8 Mbps |
Use the recommended column as the starting target when your connection can carry it reliably. If it cannot, choosing a lower resolution or frame rate and using the corresponding row is generally a more useful adjustment than selecting a high-resolution setting and hoping the network will manage. The minimum column is not a promise that the picture will look good at that rate; it is YouTube’s listed minimum for the selected ingest mode.
Do not mistake video bitrate for total upload demand. Audio adds to the stream, and network overhead and other use on the connection also matter. YouTube’s streaming tips say to ensure total stream bitrate does not exceed available upload bandwidth and recommend leaving 20% headroom. The actual capacity available to OBS can change when other people or devices share the connection.
Run an upload speed test under conditions similar to the planned stream, and account for other use in the home or workplace. A speed test is a snapshot, not a guarantee that the connection will stay at that rate through the night. If the connection varies, choose a less demanding setting that leaves room for those changes. A wired Ethernet connection may remove some Wi-Fi variability, but it cannot remedy a limited ISP upload rate, congestion upstream or an overloaded encoder.
If OBS reports dropped frames, investigate the network path; if it reports encoding lag, investigate the encoder and computer load. They are different causes and reducing bitrate alone will not repair every encoder problem. For an overnight broadcast where restarts and power continuity matter as well as encoding, the power-backup planning guide covers another failure point that a bitrate adjustment cannot address.
Set AAC stereo audio
For ordinary stereo output, choose AAC, 44.1 kHz and 128 kbps as a practical starting point. YouTube also lists MP3 for stereo, but AAC is the baseline used here. Confirm that OBS is sending stereo if the material is mixed for left and right channels; a stereo bitrate setting does not create stereo separation from a mono source.
Listen to a local recording or a private test stream before relying on the channel. Check that the source is not clipping, that the music or microphone is audible at a consistent level, and that no unintended desktop sounds are being captured. A bitrate value cannot correct a noisy recording, an unbalanced mix or an audio source routed to the wrong OBS track.
If a music loop runs for many hours, verify that the audio remains in sync with the picture and that transitions do not create silence or clicks. For a software-generated stream, the guide to diagnosing long-running audio drift explains a separate issue that can emerge over time. That is not an OBS setting recommendation, but it is a useful distinction: correct encoding parameters do not guarantee that source audio and video remain aligned indefinitely.
YouTube’s guidance for 5.1 audio is different: it specifies AAC, 48 kHz and 384 kbps for 5.1 over RTMP/RTMPS. Use that only when your content, OBS configuration and end-to-end setup genuinely support surround sound. For a typical devotional, ambience or talk stream intended for ordinary stereo listening, keep the simpler stereo baseline.
Use RTMPS and Rec. 709 for SDR
YouTube lists RTMP and RTMPS as streaming protocols and recommends RTMPS, which it describes as a secure extension of RTMP. If your OBS configuration and YouTube stream setup offer RTMPS, use it. Check the current instructions in YouTube Studio and OBS rather than copying an old server address from a tutorial; the ingest endpoint and stream key must match the destination shown for your broadcast.
Treat the stream key as a credential. Paste it only into the encoder configuration for the intended channel, do not include it in screenshots or recordings, and replace it if it is exposed. A correct protocol does not by itself confirm that the selected YouTube event is available or that the stream is healthy. If you encounter a connection error, follow the current message in Studio and OBS rather than repeatedly changing unrelated picture settings. The OBS RTMP error 400 troubleshooting guide can help separate a connection or configuration problem from an encoding choice.
For SDR output, set Rec. 709 and 8-bit colour as YouTube recommends. Keep the colour workflow consistent from the source through OBS: a mismatched colour space can make levels or colour appearance differ from what you saw while preparing the file. Do not enable HDR merely as a checkbox. YouTube’s guidance for HDR calls for a compatible workflow, including HEVC and 10-bit depth, and says AV1 is not supported for HDR. If you have not prepared and tested HDR end to end, SDR is the more straightforward choice.
Test the complete stream before relying on it
A configuration is only useful if it works with your real content and connection. YouTube’s preparation guidance says, “Make sure to test before you start your live stream.” Set up a test with movement and audio representative of the planned broadcast, then inspect the Live Control Room preview. Check the picture, sound, stream health and messages rather than assuming a successful connection means every setting is right.
A useful test is specific: play the same kind of video or scene, run the same overlays, and keep the other devices that normally share the connection in their usual state. Watch for dropped frames, encoding lag, disconnections, audio clipping and changes in synchronisation. If the problem appears, change one category at a time: reduce resolution or frame rate for processing limits, lower the selected mode when upload capacity is insufficient, or correct the source and audio routing when the picture is fine but sound is not.
For a scheduled broadcast, YouTube’s preparation checklist advises arranging the stream ahead of time and starting the encoder at least 15 minutes before the scheduled event. Use that time to verify the preview and stream health, check that the intended watch page is available, and confirm any local archive recording. A preflight is not a guarantee against later network or power failures, but it gives you a chance to catch a wrong key, silent audio or unsuitable bitrate before viewers arrive.
If your 24/7 channel depends on a local OBS machine running continuously, remember that these settings address encoding and ingest, not the burden of keeping that computer powered and connected. StreamNeo is relevant when the specific pain is needing to keep your own computer running simply to repeat an uploaded video as a YouTube live stream: it takes the uploaded file and stream key, then runs the broadcast with the computer off and restarts it if it drops. The encoding choices in this guide still need to be appropriate for the file and YouTube destination.
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 1080p60 for every YouTube Live stream?
No. Use 1080p60 only if the content benefits from it and both your encoder and upload connection can sustain the setting. A 1080p30 or 720p stream can be the more dependable choice for a static visual, a less capable computer or a variable connection.
What bitrate should I enter for OBS?
Choose the H.264 recommended bitrate for the resolution and frame rate you selected in YouTube’s current encoder table. The cited examples are 17 Mbps for 1080p60, 14 Mbps for 1080p30 and 8 Mbps for either 720p30 or 720p60. Those are video rates, not total upload requirements.
Do these settings guarantee a stable stream?
No. CBR and the recommended keyframe interval align with YouTube’s ingest guidance, but stability also depends on available upload bandwidth, shared network use, computer load and the source. Test the complete setup, leave bandwidth headroom and monitor stream health.
Should I use H.265 or AV1 instead of H.264?
YouTube supports H.265 and AV1 as well as H.264, but encoder support and workflow vary. If you choose another codec, use YouTube’s recommendation for that codec rather than the H.264 bitrate table, and confirm that your OBS version and hardware can sustain it.