OBS bitrate controls the live feed OBS sends to YouTube, not the bitrate of the pre-recorded file you play. Choose a bitrate for the outgoing stream’s codec, resolution and frame rate, then check that your upload connection can sustain it and test the feed before going live.
For H.264, YouTube’s current recommendations include 14 Mbps at 1080p30 and 17 Mbps at 1080p60. Those are starting points, not guarantees for every connection or encoding setup. In OBS, find the streaming bitrate control, match the output settings to the relevant YouTube row, and confirm the result in a test stream.
Find the streaming bitrate control in OBS
First set the output resolution and frame rate you intend to send. In OBS, open Settings → Video and check Output (Scaled) Resolution and Common FPS Values. Those choices describe the outgoing stream, which is what the YouTube bitrate recommendation must match. The OBS overview of settings explains its video and output controls.
Then open Settings → Output. In Simple output mode, look for the streaming bitrate control. Advanced output mode offers separate streaming and recording controls, which matters if you record a local copy while streaming. Make sure you are changing the streaming value rather than a recording bitrate: the two outputs serve different purposes.
OBS usually expresses bitrate in kilobits per second (Kbps). YouTube’s recommendations are often shown in megabits per second (Mbps); 1 Mbps is 1,000 Kbps. So a 14 Mbps target is entered as 14,000 Kbps. Check the label in the current OBS version, since settings and layout can change.
If you are new to OBS, begin with one source, one output resolution and one frame rate. Changing several settings at once makes it harder to identify why a test stream looks poor or drops frames. Keep a note of the values you test so you can compare them without relying on memory.
File bitrate and live bitrate are separate
A video file has its own encoded bitrate, set when the file was made. OBS decodes that file as a source and encodes the outgoing live feed according to its streaming settings. The file’s bitrate does not determine OBS’s output bitrate. The same file can therefore be sent in an outgoing stream encoded at a different bitrate, resolution or frame rate.
Think of the file as the material being played, and OBS’s streaming encoder as the process that prepares a live signal for YouTube. A high-bitrate source file cannot make a weak upload connection stronger, and a low-bitrate source does not force OBS to use a low outgoing bitrate. It can, however, limit the detail actually present in the picture: encoding a soft or heavily compressed source at a higher bitrate will not restore detail that is already missing.
This distinction is useful when you are looping a devotional programme, ambience video or a recorded lesson. Do not read the file’s properties and copy its number blindly into OBS. Choose the outgoing settings for the feed you want YouTube to receive, then assess whether the source material looks good at that output setting.
For a playlist of clips, check whether the files have consistent dimensions and frame rates before building the stream. If you need to prepare a mixed-resolution playlist, this guide to skipping videos with different resolutions in an FFmpeg playlist covers a related source-preparation issue. It does not change the rule that OBS’s streaming bitrate is set for the outgoing feed.
Match bitrate to output resolution and frame rate
Use the YouTube recommendation for the codec OBS sends, along with the output resolution and frame rate configured in OBS. The table below lists YouTube’s H.264 minimum and recommended bitrates for common and higher-resolution formats. The recommendations are platform guidance, not a promise that every connection or encoder can deliver them reliably. See YouTube’s live encoder settings, bitrates and resolutions and check the current table before a production stream.
| Outgoing H.264 format | YouTube minimum | YouTube recommended |
|---|---|---|
| 360p30 | 0.4 Mbps | 4 Mbps |
| 480p30 | 0.4 Mbps | 4 Mbps |
| 720p30 | 3 Mbps | 8 Mbps |
| 720p60 | 3 Mbps | 8 Mbps |
| 1080p30 | 5 Mbps | 14 Mbps |
| 1080p60 | 6 Mbps | 17 Mbps |
| 1440p30 | 7 Mbps | 21 Mbps |
| 1440p60 | 8 Mbps | 34 Mbps |
| 2160p30 (4K) | 11 Mbps | 42 Mbps |
| 2160p60 (4K) | 14 Mbps | 50 Mbps |
For an ordinary H.264 1080p30 stream, 14,000 Kbps is the YouTube recommended value. For H.264 720p30 or 720p60, the listed recommended value is 8,000 Kbps. If your stream uses another codec, do not select an H.264 row simply because it is familiar: use the matching codec column in YouTube’s live encoder guidance. For example, YouTube lists AV1/H.265 recommendations of 10 Mbps for 1080p30 and 12 Mbps for 1080p60, rather than the H.264 figures above.
Frame rate matters even when the source is pre-recorded. A slow-moving painting or static prayer text may not need the same motion handling as a fast-moving tutorial, but your output still has a configured frame rate. YouTube’s published rows distinguish 30 from 60 fps, and the recommended bitrate can change. Avoid raising frame rate just because a source file supports it: choose a setting that suits the content and that you can test.
Higher resolution and frame rate can require more bitrate, which in turn requires more stable upload capacity. If your connection cannot sustain the recommended value, a lower output resolution or frame rate is often a more useful adjustment than insisting on a high-resolution target with a struggling feed. The right choice depends on the source, the audience’s viewing needs and the connection available at the time the channel runs.
Use CBR and a two-second keyframe interval
For YouTube live encoding, set rate control to CBR and set the keyframe interval to 2 seconds. YouTube recommends constant bitrate and a two-second keyframe frequency, and says not to exceed four seconds. These settings tell the encoder how to maintain a predictable stream and how often to provide keyframes; they do not guarantee that the connection will be stable.
In OBS, the exact location of these controls can depend on whether you use Simple or Advanced output mode and on the selected encoder. Open the streaming output settings and confirm that the rate-control field is set to CBR. If the keyframe interval is set to automatic or zero, change it to two seconds if the chosen encoder exposes that setting. After an OBS update or encoder change, check the values rather than assuming they carried over.
CBR does not mean every frame contains the same visual detail. It means the encoder aims to keep the data rate constant over time. A scene with movement or fine detail can still be harder to encode cleanly than a still frame, which is one reason to test using representative footage rather than a static opening card.
Leave upload headroom
The bitrate you set must fit within the upload bandwidth that is actually available to the streaming computer. YouTube’s streaming tips say the total streaming bitrate cannot exceed available upload bandwidth and recommend leaving 20% headroom. Check upload speed, not download speed: a fast download result does not show how much data your connection can reliably send.
For a simple calculation, if you plan to send 14 Mbps of video and reserve 20% of upload capacity as headroom, you need about 17.5 Mbps of available upload capacity for that video stream. That figure is arithmetic based on the recommendation, not a separate YouTube threshold. Audio and any other outgoing use also consume capacity, so leave room for those rather than treating the video number as the entire load.
A speed test is a snapshot, not a guarantee of overnight performance. Repeat it at the place and time you will use the channel if the connection varies, and check whether other devices or uploads compete for bandwidth. A wired Ethernet connection can be worth trying if Wi-Fi is inconsistent between the computer and router, but it cannot raise the upload capacity supplied by your internet provider.
For a 24/7 channel, the connection needs to carry the feed for long periods, not just pass a brief check. If a full-resolution target leaves little margin, reduce the output resolution or frame rate and test again. A lower, stable feed is usually more useful to viewers than a nominally sharper stream that repeatedly buffers or drops frames.
When a long-running channel depends on a single computer staying on and connected, you may also want to consider how the broadcast is operated, separately from its bitrate. This comparison of ways to keep a 24/7 YouTube stream running covers operational trade-offs; whichever approach you use, it does not remove the need to choose output settings that fit your connection.
Test audio, video and stream health
Before publishing a scheduled or public stream, run a private or unlisted test. Start the same OBS scene and play footage with audio and movement similar to the real programme. YouTube specifically advises testing with representative audio and motion, and its Live Control Room provides a preview and stream health information. A still slate can hide problems that appear when footage moves or music plays.
In the preview, check that the picture is at the intended resolution, motion looks acceptable and audio is present at a sensible level. Listen for clipping, distortion, silence, or audio that drifts out of sync. Confirm that scene changes or transitions do not briefly expose a black screen, desktop or unintended source. A test is also a chance to verify that the right prerecorded file is playing and that it loops or advances as expected.
Watch the stream health indicator and any messages in Live Control Room while the test is running. If YouTube reports dropped frames or another connection issue, record the message and time, then adjust one setting at a time. Do not treat a healthy preview at the start as proof that a channel will remain stable overnight; leave the test running long enough to catch the conditions you are concerned about.
Keep the stream key private. It is the credential OBS uses to send a feed to your YouTube channel, and anyone with access to it may be able to broadcast. For a walkthrough of a different recorded-video workflow, see streaming a 24/7 drawing tutorial from recorded videos; the same test-first habit is useful regardless of subject matter.
Adjust after checking the feed
If the test has dropped frames or YouTube reports a connection-related health issue, first check whether other devices or processes are using upload bandwidth. Compare the tested upload capacity with the total outgoing stream bitrate, remembering YouTube’s headroom guidance. If there is not enough reliable capacity, lower the bitrate and test again rather than continuing to send a rate the connection cannot sustain.
If the connection is stable but detail looks poor, check whether the source file itself is soft or compressed, and confirm that OBS is set to the intended output resolution. The source’s bitrate does not dictate the outgoing setting, but source quality limits what detail the outgoing encode can preserve. Raising OBS bitrate cannot recreate information absent from the original footage.
When a recommended bitrate is out of reach, consider stepping down the output resolution or frame rate and testing again. For example, a channel with limited upload capacity may prefer a 720p output at a bitrate it can sustain over 1080p at a target that produces repeated connection problems. Use YouTube’s table as a reference point, then make the decision from observed stream health and picture quality.
Keep a short record of each test: OBS resolution and FPS, codec and rate control, bitrate, upload result, and the messages shown in Live Control Room. Change only one or two related settings for the next test. That makes it easier to tell whether a bitrate reduction, a lower output resolution or a network change actually helped.
If managing a long stream on a home computer creates a separate problem—such as needing to leave that computer on—StreamNeo can take an uploaded video and run it as a YouTube live stream while your computer is off, with monitoring and restart if the broadcast drops. That addresses the need to keep the playback machine available; you still need to select appropriate stream settings and check the resulting feed.
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
Does the bitrate of my video file set OBS’s live bitrate?
No. OBS uses the file as a source and encodes an outgoing live feed using its streaming settings. Choose the outgoing bitrate for the stream’s codec, resolution and frame rate; the source file can still limit the picture detail available to encode.
What bitrate should I use for YouTube at 1080p30?
For H.264, YouTube’s listed recommendation is 14 Mbps, or 14,000 Kbps in OBS. Treat it as a starting recommendation, check that your upload connection has sufficient headroom, and test the feed. If you use AV1 or H.265, use that codec’s row in YouTube’s current guidance instead.
Should I choose 30 or 60 fps for a pre-recorded stream?
Choose the output frame rate based on the content and the feed you can reliably send, not only on what the file supports. YouTube’s bitrate recommendations differ by frame rate for some resolutions. Test the actual programme at the chosen output setting and compare motion quality and stream health.
What should I do if YouTube reports dropped frames?
Check upload use on the local network and compare available upload capacity with the stream’s total bitrate, including headroom. Reduce bitrate or choose a lower output resolution or frame rate, then test again. Do not assume that a single speed test proves a connection can sustain the stream continuously.