For YouTube Live, start with YouTube’s recommended CBR settings, a 2-second keyframe interval and a bitrate matched to your codec, resolution and frame rate. For a recording you will upload later, configure a separate local quality target rather than treating the live bitrate as an upload preset.
There is no single best setup for every computer or connection. Use the platform requirements as a starting point, then test the actual scene, audio and sustained upload you plan to use; adjust quality when OBS or the connection cannot keep up.
Start with your YouTube streaming workflow
First decide whether you are sending a live broadcast, recording a video for a later upload, or doing both at once. These workflows use different bitrate guidance. YouTube’s live table describes what to send to its ingest service during a broadcast; its upload guide describes the encoding of a finished file. A number from one table should not be copied into the other without a reason.
In OBS, the main areas to review are Settings → Video and Settings → Output. Video settings define the canvas and output dimensions and frame rate. Output settings control the streaming encoder and, if you record locally, the recording encoder and quality. In Simple Output mode, OBS gives you a less involved configuration. Advanced Output makes it possible to set streaming and recording separately, which is useful when you need a higher-quality local copy while sending a more bandwidth-conscious live feed.
Before adjusting individual controls, sketch the job: what is on screen, whether it moves quickly, how many audio sources are active, and whether you need a local recording. A devotional still image with a slow visualiser has different motion demands from gameplay or a camera shot. A local news loop may need clear text and speech, but not a 60 fps output. This is editorial guidance, not a platform rule: make the output fit the content and the resources you can sustain.
If you are running a continuous channel on a modest connection, plan for the connection to vary rather than assume its best speed is available all night. The walkthrough on setting up a continuous church stream with limited broadband is relevant when the network is the constraint. For a file-based devotional channel, the guide to streaming a devotional video channel on YouTube covers the wider operating workflow.
OBS settings for YouTube Live
Platform requirements and recommendations: YouTube’s current live encoder guidance lists RTMP or RTMPS, H.264, H.265 or AV1 video, up to 60 fps, and CBR. It recommends RTMPS, a 2-second keyframe interval, and says not to exceed 4 seconds. For SDR, it lists Rec. 709. Its audio recommendation is stereo at 128 kbps, using AAC or MP3. Confirm the current details in YouTube Help’s live encoder settings guide.
OBS starting point: In Settings → Output, set Rate Control to CBR for the live encoder and set Keyframe Interval to 2 seconds. Choose a supported encoder and the matching YouTube live bitrate for your chosen codec and output. Set audio to a format and rate consistent with the available OBS options and YouTube’s guidance. The names and availability of encoder controls depend on your operating system and hardware.
Do not confuse the 2-second keyframe interval with the bitrate, or the live recommendation with a recording quality setting. CBR means the stream encoder aims to maintain a set bitrate; it does not make an unstable connection stable. A high bitrate can still fail if the connection cannot sustain it, while lowering the bitrate may reduce visual detail. YouTube advises checking upload capacity, testing before the event, and observing stream health during it.
If you are running a recurring or overnight channel, avoid changing settings in the middle of an important broadcast without a test. Make a small adjustment, verify the preview or an unlisted test, and watch for dropped frames and health warnings. If a long-running OBS broadcast keeps disconnecting, the checks in this OBS YouTube disconnection guide can help separate network problems from settings problems.
Choose resolution, frame rate and bitrate
Platform recommendations: The following are YouTube’s recommended live video bitrates for the listed ingest codec, resolution and frame rate. They are recommendations, not guaranteed results or minimums. Choose the row matching the signal you actually send, rather than selecting a number because it appears higher. YouTube’s live bitrate guidance was checked on 3 October 2026.
| Live output | H.264 recommended bitrate | AV1 or H.265 recommended bitrate |
|---|---|---|
| 720p30 | 8 Mbps | 6 Mbps |
| 720p60 | 8 Mbps | 6 Mbps |
| 1080p30 | 14 Mbps | 10 Mbps |
| 1080p60 | 17 Mbps | 12 Mbps |
| 1440p30 | 21 Mbps | 15 Mbps |
| 1440p60 | 34 Mbps | 24 Mbps |
| 2160p30 | 42 Mbps | 30 Mbps |
| 2160p60 | 50 Mbps | 35 Mbps |
These are for live ingest. If you stream 1080p60 H.264, the relevant YouTube recommendation is 17 Mbps; it is not an instruction that every network should be set to that rate regardless of upload headroom. YouTube’s separate upload encoding recommendations list 1080p SDR at 8 Mbps for standard frame rates and 12 Mbps for high frame rates, and 720p at 5 Mbps or 7.5 Mbps respectively. Those figures apply to an encoded video file being uploaded, not to the live table.
OBS setup: In Settings → Video, Base (Canvas) Resolution is the workspace in which you arrange sources. Output (Scaled) Resolution is the size sent to the stream or saved to a recording. You can keep a canvas that suits the source layout and scale the output down for a constrained connection or system. Frame rate choices such as 30 or 60 fps should match the content: 60 fps can preserve smoother motion, while 30 fps may be sufficient for static artwork, slides or slower scenes.
Editorial advice: A speed test is a useful check, not proof that a connection will hold the same rate continuously. Choose an output whose recommended bitrate leaves headroom for variation and other network use. If 1080p60 causes buffering or dropped frames, try 1080p30 or 720p, then retest. The best compromise is the highest quality that remains steady under the conditions in which the channel will run.
Select an encoder for your system
OBS may offer a software encoder such as x264 and hardware encoders such as NVENC, QuickSync or an AMD option, depending on your computer and operating system. A hardware encoder can reduce CPU work, while software encoding uses CPU capacity. OBS notes that newer hardware encoders can provide very good quality with minimal performance impact, but encoder generation and system load matter. That does not make one encoder universally superior.
Start with an encoder available on your machine and test it with the actual scene. Check OBS’s stats and logs for rendering or encoding lag, not only the apparent quality of the preview. If the encoder cannot keep up, lower the output resolution or frame rate and simplify demanding sources or scene effects before assuming a different bitrate will solve the issue. OBS’s performance guidance discusses ways to reduce load.
A fair comparison keeps the content, output dimensions and target bitrate the same. Try a short recording or unlisted stream, then compare fine detail, motion, audio synchronisation and OBS performance. If one encoder performs better on your specific system, use it; if it does not, choose another available option or reduce the workload. Do not infer a universal quality ranking from a preset name.
For continuous music or spoken-word streams, a quiet scene can be easier to encode than fast movement, but audio still needs a separate check. Listen for clipping, missing desktop audio or an unintended microphone source. If the channel uses an audio visualiser, the article on visualisers for a 24/7 YouTube podcast stream can help you think about how on-screen motion changes the scene.
Set up local recording separately
If you stream and record at the same time, decide whether the local file needs to match the live output or preserve more detail for editing and upload. In Advanced Output, OBS can use separate streaming and recording settings. A separate recording encoder or a recording quality setting different from “Same as stream” uses additional system resources, so test both outputs together rather than assuming the recording is free.
OBS baseline examples for local quality-based recording: OBS’s advanced recording guide gives encoder-specific examples: NVENC CQP 16–23, x264 CRF 16–23, AMD CQP 16–23 and QuickSync ICQ 16–23. These are OBS baselines, not universal prescriptions. Within these examples, a lower control value means higher quality and larger files. Use a short sample to judge whether the file size and image quality suit your editing and storage needs. See OBS’s advanced recording settings guide for the encoder-specific controls.
Do not transfer those quality-control values into the live encoder’s CBR configuration. They describe local recording modes; YouTube Live uses the live ingest settings discussed above. Equally, do not assume that recording at a high quality target will make a later YouTube upload better if your source, editor export or upload encoding changes it.
For recording format, OBS recommends MKV because an unexpected stop is less likely to corrupt the whole file. If your editor or upload workflow requires MP4, use OBS’s remux function to convert the completed MKV rather than risking an unfinished MP4 recording. The recording presets also trade quality against resource use and file size. OBS notes that lossless recording can create extremely large files—about 7 GB per minute in its guide—so that mode is rarely a casual default.
If the local recording is the final video you plan to upload, choose an output profile and export appropriate to that file. YouTube’s upload encoding page is the reference for upload recommendations; it is separate from the Live ingest table. The guide to verifying video files before a YouTube playlist upload is useful when checking a batch before it is put into a channel workflow.
Test stream health before going live
A preflight test should use representative motion, transitions and audio, not just a static starting scene. Run the intended resolution and frame rate, and if you plan to record simultaneously, enable recording too. Confirm that OBS is not reporting rendering or encoding pressure, that the audio is present and in sync, and that YouTube’s stream health is acceptable. A brief test cannot guarantee that a connection will remain stable for the whole event, but it can expose problems before viewers are relying on the broadcast.
If OBS shows rendering or encoding lag, reduce the output resolution or try 30 fps instead of 60. Simplify complex scenes, reduce costly source sizes or effects, and retest. OBS explains that scene composition uses GPU resources. Treat Base (Canvas) Resolution as a layout workspace rather than the first performance knob; reducing it can complicate source placement. Consider changing it only if the system is severely constrained and you have reviewed the layout implications.
If the stream looks healthy in OBS but viewers buffer, investigate sustained upload stability and whether the selected bitrate leaves adequate headroom. YouTube recommends checking upload speed and monitoring stream health. A bitrate increase is not a remedy for an unstable connection. Try a lower output or bitrate, then run another representative test under the same network conditions.
Keep a note of the configuration that passed: output size, fps, codec, live bitrate, encoder and whether local recording was enabled. If you later change a camera, scene, audio source or network, repeat the test. For a channel that is expected to stay on, that small record makes it easier to distinguish a new workload issue from a connection change.
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 are the best OBS settings for YouTube streaming?
Use YouTube’s live recommendations as the baseline: CBR, a 2-second keyframe interval, and the recommended bitrate for the chosen codec, resolution and frame rate. Then test the actual scene and connection, because a published bitrate does not guarantee that your system or upload can sustain it.
What bitrate should I use for 1080p 60fps YouTube?
For live H.264 ingest at 1080p60, YouTube recommends 17 Mbps; its AV1 or H.265 recommendation is 12 Mbps. These figures are for live streaming, and your connection needs enough stable upload capacity to carry the chosen rate.
What are the best OBS settings for recording YouTube videos?
Use a separate local recording quality setting if you need a higher-quality file than the live feed, and test the extra encoder load. OBS’s CQP and CRF ranges are starting examples rather than one-size-fits-all settings; use MKV for safer capture and remux to MP4 if your workflow requires it.
Should I use NVENC or x264 in OBS?
Choose based on the encoders available and the performance of your computer with your actual scene. NVENC is a hardware encoder and x264 is software-based, but neither is best for every system; compare a short test and check OBS stats as well as image quality.