For a 1080p gaming stream to YouTube Live, start with H.264, CBR, a two-second keyframe interval and RTMPS. YouTube recommends 17 Mbps for 1080p60 or 14 Mbps for 1080p30; your upload connection must sustain the chosen bitrate with headroom.
Those are platform recommendations, not a guarantee that a particular PC or connection will run all night without interruption. Test with representative gameplay and audio, check YouTube’s stream health, and keep live-feed settings separate from settings used to record a local VOD.
Choose between 1080p30 and 1080p60
The frame rate determines how often the picture updates. At 60 frames per second, fast movement in a game can look smoother; 30 frames per second uses fewer frames to encode and is a reasonable 1080p target when system capacity or upload bandwidth is limited. Choose based on what your setup can sustain over time, rather than the highest number available in a menu.
For H.264, YouTube’s live encoder recommendations list 17 Mbps for 1080p60 and 14 Mbps for 1080p30. The same guidance lists minimum values of 6 Mbps and 5 Mbps respectively. A minimum is not the recommended target: dropping to it may help a constrained connection send a signal, but should not be presented as equivalent to the recommended quality.
For gaming, test a section with the kind of motion your audience will see. A static menu or quiet loading screen is not representative of a busy match, rapid camera turns or particle-heavy scenes. If the PC struggles to render or encode smoothly at 60 fps, or your upload cannot support its recommended bitrate plus headroom, try 30 fps and test again.
In OBS, set the video canvas and output to 1920×1080 if that is the intended stream size, with progressive output. Make sure the game source and OBS output are not accidentally using different aspect ratios or an unexpected scaled resolution. YouTube’s guidance also specifies progressive scan and square pixels among its advanced recommendations.
The VOD in your title might mean the replay YouTube retains after a live broadcast, or a separate recording saved on your PC. The live frame rate applies to the feed YouTube receives. A separate recording can have its own output settings, but recording a second copy is optional and adds its own storage and encoding demands. For a lower-power system, a simpler continuous playlist workflow may be more appropriate; see the practical trade-offs in running a 24/7 kids’ channel at 720p on a low-power PC.
Set H.264 bitrate and CBR for the live feed
In OBS’s streaming output settings, use H.264 and set rate control to CBR, or constant bitrate. CBR aims to send data at a steady configured rate, which suits live ingestion. Set the video bitrate to 17,000 Kbps for 1080p60 or 14,000 Kbps for 1080p30, matching the frame rate you selected. The values are video bitrate, not a combined allowance for every byte used by your connection.
The bitrate field is commonly shown in kilobits per second, so enter the equivalent Kbps value rather than typing “17 Mbps” into a field that expects a number. Confirm OBS is still set to the intended output resolution and frame rate after changing the output tab. The quality target only makes sense as a set of compatible choices: output size, frames per second, codec and rate control.
You may see AV1 or H.265 options. YouTube lists lower recommended figures for those codecs at 1080p, but use them only if your encoder and complete workflow support the chosen codec. This article’s settings are for H.264, which remains the straightforward baseline when following H.264 guidance. Do not switch codecs merely because a number in a table is lower; a successful stream depends on the encoder, OBS configuration and YouTube ingest accepting the workflow.
Audio is part of the transmitted stream and the connection budget. YouTube lists AAC or MP3 support, with 128 Kbps stereo audio at 44.1 kHz among its advanced recommendations. If a game capture includes sound, test that audio is actually routed to the live mix and is not muted or doubled. For commentary, listen to a private or unlisted test rather than relying only on OBS’s mixer meters.
A common confusion is CQP or CRF. These are quality-based controls discussed in OBS’s Advanced Recording Settings Guide, which is specifically about local recording. They are not substitutes for CBR on the YouTube live feed. A recording may vary its bitrate according to scene complexity; the live output still needs its own configured live rate control and bitrate.
If you need a local archive as well as the YouTube replay, set it up as a distinct recording output and account for its disk use and encoder load. OBS’s recording guide describes CQP for NVENC and CRF for x264 as recording approaches, where lower values produce higher quality and larger files. Those controls do not mean “set live bitrate to CQP 20” or any equivalent. Keep the two output paths conceptually separate when troubleshooting.
Use the recommended keyframe interval
Set the keyframe interval to two seconds. YouTube recommends two seconds and says not to exceed four seconds. In OBS this is commonly a field expressed in seconds; use the two-second interval rather than leaving it at a value inherited from a different streaming profile.
A keyframe is a frame encoded without depending on earlier frames in the same way as the intervening frames. Regular keyframes help the live platform and playback pipeline identify points from which a sequence can be decoded. A mismatched interval can create an ingest configuration that differs from YouTube’s guidance even when resolution and bitrate appear correct.
Check the setting in the streaming encoder configuration, not just a recording profile. If you use separate encoders or output profiles for recording and streaming, confirm which one is attached to the live stream. Save the profile with a clear name such as “YouTube 1080p60 H.264” so you can tell it apart from a local recording preset.
Select RTMPS and confirm the stream output
Choose RTMPS as the server connection protocol where the OBS service settings allow it. YouTube recommends RTMPS for live encoder connections. Select the YouTube service or enter the official server information provided in your YouTube Live setup, then use the stream key associated with the intended broadcast. Treat the key as a password: do not show it in a screenshot, recording or public support post.
Before going live to an audience, confirm that the broadcast appears in YouTube Studio and that the preview receives video and audio. Check the title, visibility and scheduled event, too. A technically healthy encoder pointed at the wrong event, or an accidentally public test, is still a failed preparation.
For SDR gaming content, use Rec. 709 and 8-bit SDR where that matches your workflow. Avoid changing colour range or HDR settings by guesswork: a mismatch can make dark scenes look washed out or crush detail. If you are not deliberately producing HDR, a consistent SDR signal is the simpler baseline.
Open OBS’s stats or status area during the test and note whether frames are being dropped because of network conditions or rendering/encoding lag. These indicate different problems. Network drops point towards the connection or ingest path; rendering or encoding lag suggests the PC may not be producing frames in time. Lowering output demand can help isolate the cause, but change one setting at a time and repeat the same test.
Check upload capacity and leave headroom
Test upload capacity, not download speed. A speed test’s headline download figure says little about whether your home connection can continuously send a 14 or 17 Mbps live video feed. YouTube’s streaming tips say the total stream bitrate must fit within available upload bandwidth and recommend leaving 20% room.
As a planning calculation, multiply the chosen video bitrate by 1.2 to allow that recommended 20% headroom, then consider the audio bitrate and other network traffic as well. For a 17 Mbps video feed, that makes the upload capacity target at least 20.4 Mbps before accounting for audio or competing use. For 14 Mbps video, the corresponding figure is 16.8 Mbps before those additions. These are arithmetic planning figures from YouTube’s headroom guidance, not guarantees that a variable home connection will behave consistently.
Use a test at the location and time the stream will run. Upload capacity can be affected by other people using the connection, cloud backups, camera feeds, software updates and Wi-Fi conditions. If several devices share the line overnight, account for their traffic rather than treating the speed test result as dedicated capacity. Check the upload result repeatedly; one favourable reading is not a sustained test.
A wired connection is worth trying if Wi-Fi proves unstable, but do not assume a particular cable will fix an overloaded or inconsistent broadband connection. If reliability differs between locations, compare the actual upload behaviour at each. For an India-specific perspective on a mobile broadband setup and its practical constraints, see making a 24/7 YouTube lofi stream with a Jio connection.
When upload does not have the recommended margin, first reduce avoidable traffic and retest. If the margin remains too small, try 1080p30 at its recommended H.264 bitrate, or reconsider whether 1080p is the right target for that connection. Do not simply raise bitrate to compensate for dropped frames: a higher rate needs more upload capacity and can make network problems worse. The old mini-PC streaming guide also illustrates why the source device and continuous workload matter alongside an encoder preset.
Run a representative test and inspect health
A successful five-minute test is useful, but it does not prove an unattended stream will run all night. YouTube does not provide a universally safe unattended duration or a preset that guarantees uninterrupted broadcasting. Run a test long enough to expose the actual combination of game motion, audio, upload use and PC load that you expect, then inspect the evidence instead of assuming a settings menu guarantees reliability.
Use a representative game scene: movement, camera changes, effects and the normal audio mix. Start the stream as a private or unlisted test if suitable, and watch YouTube Studio’s stream health while OBS is active. YouTube advises testing before an event and monitoring stream health. If health reports a problem, note the time and compare it with OBS’s dropped-frame or lag indicators. The pattern helps distinguish network trouble from an encoder struggling to keep pace.
If you also record locally, watch the file size during the test and open the resulting file afterwards. YouTube’s guidance includes checking local archive file integrity and growth. A file that stops growing may indicate a recording path issue even while the live broadcast continues; a playable opening segment alone does not prove the entire recording is intact. Ensure the destination drive has space for the planned recording, and avoid filling the same disk with unrelated downloads during the session.
For an unattended run, decide in advance what you will do if the stream stops. Keep the stream key accessible privately, know how to check the event from another device, and arrange a way to notice a failure if no one will be watching the PC. Do not rely on an alarm or recovery action you have not tested. StreamNeo can remove the need to leave your own computer running by taking an uploaded video and stream key for a YouTube broadcast, which is useful when the recurring pain is keeping a home PC on overnight.
Latency is a separate choice from bitrate. YouTube describes latency as the delay between capture and playback and notes that lower latency can mean more buffering. For a non-interactive overnight gaming loop, immediate chat response is usually not the goal, so prioritise stable delivery over choosing low latency for its own sake. Review YouTube’s current live stream settings guidance if you are deciding among latency modes.
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 CQP or CRF for a YouTube Live stream?
No. CQP and CRF are quality-based recording controls described in OBS’s local recording guidance. For the H.264 live feed, use CBR and the bitrate appropriate to your selected frame rate.
Is 1080p60 always better than 1080p30?
Not automatically. Sixty frames per second can show fast game motion more smoothly, but YouTube’s H.264 recommendation is higher and the PC must encode that output while the connection sustains it. Choose the highest target that passes a representative test with headroom.
Will these settings guarantee an overnight stream?
No preset guarantees that. The figures are YouTube recommendations, and actual continuity depends on the connection, device, software and monitoring plan. Test the real workload and check stream health before relying on an unattended run.
Do I need to record a local VOD as well?
No. YouTube may retain a replay of the live broadcast, while a local recording creates a separate file on your computer. Record locally only if you need that extra copy, and test its file growth, integrity, storage space and effect on system load.