For 1080p YouTube Live, start with 1920×1080 output, H.264, CBR and a 2-second keyframe interval. YouTube recommends 14 Mbps for 1080p30 and 17 Mbps for 1080p60; treat those as platform settings to work towards, not a promise that your computer or connection can sustain them.
The best OBS settings depend on what is moving in your video, what your encoder can maintain and how dependable your upload is. This is a configuration baseline drawn from YouTube and OBS guidance, not a report of equipment testing. Test a representative stream before an event, then lower frame rate or resolution if the system struggles.
Start with 1080p30 or 1080p60
In OBS, set the output resolution to 1920×1080 when your target is 1080p. Your base canvas and output resolution can differ depending on how your scenes are assembled, but check that the final output has the dimensions you intend. A 1080p canvas does not by itself make a low-resolution source sharper; it gives the stream a 1080p frame in which to place its sources.
Choose the frame rate according to the content and the computer, rather than assuming 60 fps is always better. A devotional playlist, a talking presenter, a lecture slide or a slow ambience scene may be adequately served by 30 fps. Fast gameplay or other quick movement can benefit from 60 fps, if your encoder and upload can sustain the additional work.
| Target | YouTube H.264 video bitrate guidance | Typical reason to choose it |
|---|---|---|
| 1080p30 | 14 Mbps recommended; 5 Mbps minimum | Less demanding motion or limited encoding and upload capacity |
| 1080p60 | 17 Mbps recommended; 6 Mbps minimum | Fast motion, when the computer and connection can sustain it |
These are YouTube’s listed H.264 values, not measured results or upload-speed guarantees. The minimum is not necessarily a sensible target for every scene: fine detail and movement can make compression more visible. If a connection cannot reliably support the recommended rate, choosing 30 fps or a lower resolution is a more useful starting point than hoping a setting will hold overnight. The 4K 60fps always-on streaming guide also illustrates why higher resolution and frame rate raise the demands placed on an entire streaming setup.
Set YouTube’s H.264 recommended bitrate
For H.264 ingest, YouTube’s current live encoder guidance recommends 14 Mbps at 1080p30 and 17 Mbps at 1080p60. In OBS, set the video bitrate in the streaming output settings to match the target you have chosen, then confirm that your selected encoder is actually sending H.264. YouTube also lists separate recommendations for H.265/HEVC and AV1. Do not carry the H.264 figures across to those codecs: check the relevant row in YouTube’s live encoder settings guidance.
The bitrate setting controls how much data the video encoder aims to send. More bitrate can preserve detail in a busy image, but it also requires more upload capacity and does not repair a weak source, overloaded encoder or unstable connection. If your stream shows blockiness during movement, first establish whether the encoder and network are stable; increasing bitrate without checking capacity can create a different failure.
YouTube lists minimum H.264 rates of 5 Mbps for 1080p30 and 6 Mbps for 1080p60, alongside the higher recommended rates. They are platform guidance, not assurances that any upload connection at those figures will work reliably. In particular, a speed test taken once does not establish what your connection will sustain for a long broadcast. If your upload varies, leave room for that variation rather than setting OBS to consume all available capacity.
Use CBR and a keyframe interval
Set rate control to CBR, or constant bitrate. That matches YouTube’s listed mode for live H.264 encoding and avoids having the output rate vary substantially with scene complexity. A static devotional image may require less data to represent than a fast-moving game, but the encoder and stream still need to follow the configured rate-control approach.
Set the keyframe interval to 2 seconds. YouTube recommends that interval and says not to exceed 4 seconds. A keyframe is a complete reference frame from which later frames can be reconstructed; its timing matters to the ingest and playback workflow. OBS notes that a consistent interval helps YouTube’s quality selector move smoothly between playback options. Set a consistent value rather than leaving it to an unpredictable automatic choice.
These settings are not a cure for every stream issue. If YouTube Studio reports an ingest problem or OBS shows dropped frames, check the network and encoder alongside the keyframe and bitrate fields. Keep the stream key private as well: it is the credential that directs an encoder feed to your channel. YouTube explains how to find and protect your stream key; do not paste it into public screenshots, chat messages or an article.
Choose an encoder your computer can sustain
OBS offers software encoding as well as hardware encoders exposed by your system. A software encoder uses the computer’s processor; a supported hardware encoder can shift some encoding work to a dedicated media block. Which choice is appropriate depends on the machine, encoder settings and the other work it must do. There is no universal choice that will run well on every computer.
Use OBS’s Auto-Configuration Wizard as a starting point. OBS says it takes into account what you want to do, your hardware and network conditions. It can guide an initial configuration, but it cannot know every detail of a long event, a busy scene or a home connection that changes at night. After it produces settings, run a test and watch the stream rather than treating the wizard’s result as proof of capacity.
Close or pause work that competes with streaming if you see encoder overload, and avoid raising output resolution and frame rate at the same time while troubleshooting. Change one thing, test again and note whether the issue is encoder overload, dropped frames or a different problem. If the source is a console or another external camera, a capture card can be relevant to bringing that video into OBS, but it is not required for every 1080p stream and it does not determine your bitrate. OBS’s quick start guide describes adding video-capture sources and checking audio devices.
For a channel that depends on a recorded programme running after the operator has switched off their computer, local OBS settings address only part of the operational problem. StreamNeo removes that particular need to keep a personal computer running: you upload a file and provide the YouTube stream key for a 24/7 broadcast, with monitoring and restart if the feed drops. It is YouTube-only, so it does not replace an OBS workflow where you need live scene switching, a camera or other real-time production controls.
Match settings to upload capacity
The bitrate in OBS is the stream’s video target, not the amount of upload capacity your internet plan promises. Your connection has to carry that outgoing stream consistently, and other devices or activity on the same connection can affect what remains available. A speed test is useful as a snapshot, but it does not reproduce the duration or conditions of a real broadcast.
If the connection is inconsistent, start by simplifying the stream: choose 30 fps rather than 60, reduce the output resolution if needed, and test again. A lower setting can be preferable to a nominally sharper feed that repeatedly loses frames. This is a trade-off: you may give up some motion detail or resolution to make the stream easier to encode and transmit. Do not describe a particular bitrate as a guarantee just because one short test worked.
For remote or cloud-based workflows, upload capacity refers to the connection at the system sending the video, not necessarily the computer on your desk. The same question still applies: can that sending point sustain the configured feed under realistic conditions? For a locally operated channel, practical details such as Wi-Fi congestion, a shared connection or a computer downloading large files can change the answer. A CPU and network monitoring walkthrough can help you separate a processing limit from a connection limit when diagnosing an always-on stream.
Avoid changing bitrate alone as your first response to every quality warning. A high bitrate that exceeds available upload capacity can worsen dropped frames; a low bitrate can reduce image detail even when the connection is sound. Use YouTube’s recommendation as the reference point, then decide whether a lower frame rate or resolution better fits the capacity you can actually rely on.
Check audio, colour and protocol
For stereo audio, YouTube recommends AAC or MP3 at 128 Kbps and lists 44.1 kHz. In OBS, confirm the intended input in Settings → Audio and check the Audio Mixer meters while speaking or playing a sample. If the meters are still, OBS may be using the wrong device or no device. A picture that looks correct does not confirm that a microphone or music feed is reaching the stream.
For an SDR stream, YouTube’s guidance specifies Rec. 709, square pixels, progressive scan and 8-bit depth. Keep HDR workflows separate: codec and colour requirements differ, so do not assume an SDR setting is appropriate for HDR output. If you are repurposing HDR footage for a conventional SDR stream, first check how the conversion affects colour and highlights; the guide to converting 10-bit HDR video to SDR covers that related workflow.
YouTube recommends RTMPS for secure delivery. Use the stream destination and key provided in YouTube Studio, and keep the key private. Re-enter or rotate it through the official account workflow if it has been exposed. These protocol and security choices help configure delivery, but they do not promise that the stream will be approved, uninterrupted or suitable for every network.
Test OBS output before going live
Use a short preflight stream or recording with the actual scenes, audio sources and movement your viewers will see. OBS recommends a test before a first stream, and YouTube recommends tests that include representative audio and movement. A still screen with no microphone activity is not a useful test of a music programme, news loop, gameplay session or presenter-led channel.
Check the output settings, then watch the test through YouTube’s preview or an unlisted broadcast. Listen for the right audio source, look for dropped frames or visible breakup during motion, and make sure the stream is reaching the intended channel. A local recording can expose scene and audio problems, but it does not test the upload path to YouTube. Use a stream test when you need to assess that path.
During the broadcast, monitor YouTube Studio’s stream health and any encoder messages. Keep an eye on OBS statistics as well: network drops and rendering or encoding lag point to different parts of the chain. If the stream is stable for a brief test but your real event is much longer, that is useful evidence, not a guarantee that conditions will stay unchanged. Plan a way to check it after launch, especially if nobody will be watching the controls continuously.
Tune for stability before quality
When a test fails, change settings in a deliberate order. First identify what the warning or OBS statistics indicate; then try a less demanding frame rate or output resolution and repeat the same test. If only the audio is wrong, fix the device selection rather than lowering video bitrate. If encoding is overloaded, investigate encoder choice and competing computer work before assuming that the internet connection is at fault.
Keep a simple note of the settings that were tested, the scene used and the behaviour observed. That helps you avoid returning to a configuration that already failed in similar conditions. For a playlist or recorded programme, check the start and end of the file as well as the middle: a loop transition, silent segment or image change can reveal an issue that a short static preview misses. For an OBS-based recorded music stream, this guide to looping lofi tracks with FFmpeg is relevant to the media workflow, though it does not replace testing OBS’s outgoing feed.
Do not chase maximum quality at the expense of a reliable broadcast. If 60 fps or the recommended bitrate is unstable on your system, a tested 30 fps stream can be the more responsible choice for a slow-moving programme. YouTube’s figures give you a grounded starting point; your test determines whether your whole setup can sustain the choice. Revisit the test when you change the encoder, scenes, source material or network conditions.
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 bitrate should I use for 1080p streaming on YouTube?
For H.264, YouTube recommends 14 Mbps for 1080p30 and 17 Mbps for 1080p60, with listed minima of 5 Mbps and 6 Mbps respectively. Treat them as platform recommendations, then check that your encoder and upload can sustain your chosen setting in a representative test.
Is 1080p30 or 1080p60 better for a YouTube live stream?
Choose 30 fps for slower movement or when you need to reduce encoding and upload demand. Choose 60 fps for fast motion only if your computer and connection can maintain it; YouTube’s higher H.264 bitrate recommendation for 60 fps reflects the added load.
Should OBS use CBR and a 2-second keyframe interval?
Yes, those are YouTube’s recommendations for live encoding: CBR and a 2-second keyframe interval, without exceeding 4 seconds. They align your output settings with the platform guidance but do not guarantee stable delivery.
What should I do if the test stream drops frames?
Check OBS statistics and YouTube Studio messages to distinguish network drops from rendering or encoding lag. Reduce the frame rate or output resolution if needed, check the selected encoder and audio devices, and run the same representative test again.