For YouTube Live at 1080p and 30 fps using H.264, set OBS to send 1920×1080 at 30 fps, use constant bitrate (CBR), and set a two-second keyframe interval. YouTube’s current live-ingest guidance recommends 14,000 Kbps for this format and lists 5,000 Kbps as its minimum; the recommendation is a starting point, not a promise that your connection can sustain it.
The important distinction is that OBS’s output resolution is what it sends, while the base canvas is the space in which you compose the scene. Labels and available encoder controls vary by OBS version, operating system and hardware, so check the actual output and YouTube’s stream-health messages rather than assuming a setting name proves the stream is correct.
Set OBS video output to 1080p30
Open Settings → Video in OBS. Set Output (Scaled) Resolution to 1920×1080 and Common FPS Value to 30. Those are the settings that define the resolution and frame cadence of the stream output. Some versions or workflows may present slightly different labels, but look for the output resolution and frame-rate controls in the Video settings.
Do not change the base canvas merely because the output should be 1080p. The canvas is the working area used to arrange sources: a camera, graphics, browser panels, images or a video loop. If you design a scene at 1280×720 but set output to 1920×1080, OBS scales the composed image up. If your sources are composed at 1920×1080 and the output is also 1920×1080, there is no resolution conversion at that stage.
For a simple full-screen video or still-image loop, matching canvas and output dimensions can make the setup easier to reason about. For a scene assembled from sources with different shapes, keep a canvas that suits the composition and inspect how it maps to the output. Scaling can soften fine text or add processing work. Check the actual preview and a private test rather than assuming that an output label describes every source’s original size.
The stream can still be 1080p if an individual source is smaller, but the smaller source will be enlarged and may look soft. Conversely, a source larger than the output is reduced. Decide what matters in your picture—small captions, devotional lyrics, a map, or a static background—and inspect those details at the size viewers are likely to see. OBS’s overview guide explains the distinction between the canvas and output in its interface.
If OBS offers a downscale filter, it matters when the canvas and output differ. Choose a filter available in your build and compare the result with the content you are sending. Fine line art and text may reveal scaling artefacts more readily than a soft ambience background. Do not add scaling just to use a particular filter; it is a conversion choice, not a separate quality guarantee.
Choose an available H.264 encoder
In Settings → Output, select the Streaming tab or its equivalent, then locate the video encoder. Choose an encoder that outputs H.264 and is actually available on your computer. Depending on operating system, OBS build and installed hardware, the list may include a software encoder and one or more hardware encoders. The names and controls are not universal, and no single choice can be prescribed for every machine.
For this recipe, codec matters more than whether the encoder is labelled hardware or software: the requested ingest format is H.264. A hardware encoder can reduce some work done by the CPU, while a software encoder uses the processor; either can be constrained by the computer, settings or concurrent workload. Check OBS’s output statistics and test the selected encoder while the scene is active. If the encoder overloads, the remedy may be a different available encoder, lighter scene composition or less demanding settings—not an assumption that a particular brand or computer will work.
Once you choose an encoder, review which controls it exposes. You may see rate control, bitrate, keyframe interval, preset, profile or other advanced options. These can differ between encoders even in the same OBS installation. Use the controls that exist for the selected encoder; do not translate a guide’s preset label mechanically if your interface uses another name or omits it.
A preset changes the encoder’s workload and may change the trade-off between image quality and processing demand. The YouTube live-ingest values below describe the stream target; they do not establish that a particular preset is suitable for your CPU or GPU. Start with a sensible available preset, run a representative test and watch for encoder overload as well as network drops.
Configure rate control and bitrate
Set rate control to CBR, or constant bitrate, for this H.264 live-ingest configuration. CBR aims to keep the encoded video rate around the target you select, which makes the outgoing feed more predictable than a variable-rate choice. The actual rate can still fluctuate with audio and protocol overhead, and a bitrate field does not make a weak connection stable.
For YouTube Live H.264 at 1080p and 30 fps, YouTube’s live encoder settings table lists a 5 Mbps minimum and 14 Mbps recommended. In OBS this is typically expressed in Kbps: enter 14,000 Kbps as the recommended starting value if your upload connection can sustain it. These are live-ingest figures for H.264, not values taken from YouTube’s separate guidance for encoding prerecorded uploads.
| Setting or choice | YouTube Live H.264 1080p30 guidance | Practical use |
|---|---|---|
| Video bitrate | 14 Mbps recommended; 5 Mbps minimum | Start at 14,000 Kbps only if tests show a stable connection; lower it if drops persist. |
| Rate control | CBR | Use constant bitrate for the requested recipe. |
| Keyframe interval | 2 seconds recommended; do not exceed 4 seconds | Enter two seconds if the encoder exposes the field. |
| Audio | AAC or MP3; stereo 128 Kbps recommended; 44.1 kHz listed | Check the selected audio output and test it with the picture. |
The table’s minimum is platform guidance, not a guarantee of acceptable image quality in every scene. A mostly static image with a small ticker may tolerate a lower rate better than rapid camera movement, falling particles or scrolling text. Lower bitrate can make the connection easier to sustain but leaves less data for detail and motion. Choose based on both a stable test and how the picture looks, rather than treating the recommended figure as mandatory for every network.
Upload capacity needs headroom beyond the stream’s nominal bitrate because other devices and traffic can use the connection, and network conditions change. A speed test is useful, but it is only a snapshot of available upload performance. If your OBS connection drops frames or YouTube reports an unstable stream, reduce the bitrate and retest. OBS’s stream connection troubleshooting guide describes dropped frames as a connection issue that can occur when the connection cannot sustain the configured rate. For related diagnosis, see our guide to encoder overload at 1080p, which distinguishes reducing output detail from reducing bitrate.
Do not borrow figures from another codec or from the upload table. YouTube lists different 1080p30 ingest rates for AV1 or H.265 than it does for H.264. The chosen codec and the matching live-ingest table determine which guidance applies. Here the scope is deliberately H.264, so use the H.264 line and no other table’s numbers.
Set keyframes and audio
Set Keyframe Interval to 2 seconds where the chosen encoder exposes the control. YouTube recommends two seconds and says not to exceed four seconds for the live encoder settings. OBS may ask for a duration in seconds, or present a field whose interpretation depends on the encoder; verify that you are entering an interval rather than a frequency expressed in a different unit.
Keyframes provide periodic complete reference frames in the encoded video. A two-second interval gives the ingest feed the cadence YouTube specifies. It does not itself determine resolution or bitrate, and setting it correctly does not cure dropped frames caused by an encoder or connection problem. If the control is unavailable, note the selected encoder and check its documentation or the output information before assuming the setting is in force.
For stereo audio, use AAC or MP3. YouTube recommends 128 Kbps stereo and lists a 44.1 kHz stereo sampling rate in its encoder guidance. These audio settings are separate from the video bitrate. If you send speech, music or a mix, listen to a test recording or private stream for clipping, missing channels and a mismatch between sound and picture. A silent test cannot confirm that the audio path works.
Be careful with the OBS audio track selection as well as the encoder setting. Sources may be routed to different tracks, and the stream can use a different track from a local recording. Check the track selected for streaming and verify that meters move when the planned audio is playing. Then listen on YouTube, not only in the OBS preview, because the delivered stream is the result you need to validate.
Check scaling, colour and ingest settings
For SDR output, YouTube’s advanced recommendations specify Rec. 709 colour, 8-bit, square pixels and progressive scan. OBS controls for colour format, colour space and range may be under Settings → Advanced or elsewhere depending on version. Use settings that match the source and SDR workflow, and avoid changing several colour controls at once without checking the result. The aim is consistent colour and a correctly shaped picture, not a particular label regardless of what your encoder supports.
Square pixels mean the image is displayed without a non-square pixel aspect ratio; progressive means frames are drawn as complete images rather than interlaced fields. For a typical 1920×1080 OBS scene these are the expected assumptions. If the image appears stretched, cropped or washed out in YouTube playback, compare the source, OBS preview and delivered test. Do not infer correct colour solely from seeing “1080p” in the interface.
For ingest, select YouTube in OBS’s service list when that option is available, or use the stream URL and key YouTube provides. YouTube lists RTMP and RTMPS ingest and recommends RTMPS. Treat the stream key as a credential: do not place it in screenshots, public notes or shared documents. If it is exposed, replace it through the channel’s live-stream controls.
YouTube automatically detects resolution and frame rate by default. Manual resolution selection is an optional Live Control Room setting associated with a custom stream key and manual settings. Most users configuring OBS do not need to force a matching manual selection merely because they set output to 1920×1080 and 30 fps. If you do enable manual selection, verify that the stream key and the manual resolution choices correspond to the feed you are actually sending.
The output dimensions, frame rate and codec are properties of the feed arriving at YouTube; viewer playback is a separate stage. YouTube transcodes the incoming stream into viewer formats, so the quality option a viewer sees need not match a single exact OBS profile. Our article on testing a YouTube loop privately before going public covers a useful way to inspect the delivered result without making the first check in front of viewers.
Test the stream and monitor health
Before a public broadcast, run a private or unlisted test through YouTube and include the same sort of sound and movement you expect in the real stream. YouTube’s encoder settings guidance explicitly advises testing before going live with audio and movement similar to the planned programme. A still image test will not expose the same bitrate demands as a moving scene, and a muted test cannot prove the audio setup.
Check three things during the test: OBS’s output statistics, YouTube’s stream-health messages, and the stream as played back from YouTube. Look for dropped frames, encoder overload, interrupted connection, unexpected resolution or frame rate, missing audio and visible scaling problems. A connection can be stable while the encoder struggles, or the encoder can keep up while the network drops packets; these point to different adjustments.
If OBS reports network drops, reduce the video bitrate, then repeat a test long enough to observe the stream under ordinary household or business network use. If the encoder overloads, try an encoder that is available and better suited to your computer, or reduce the scene’s processing demands. If the picture is the issue but health indicators are stable, inspect scaling, source quality and colour settings before changing the connection target.
In OBS, the statistics view offers evidence about what is happening locally, but it does not replace YouTube’s view of received signal. On YouTube, confirm the incoming stream’s health and whether the detected resolution and frame rate match the intended output. If you need to change a setting, change one category at a time and test again; otherwise it becomes difficult to know whether the improvement came from bitrate, encoder workload or scaling.
Keep a note of the tested OBS profile and the date you last verified it. OBS profiles can preserve stream settings separately, which is useful when you operate more than one channel or switch between a short live show and a continuous loop. Do not assume an old profile remains appropriate after an OBS, operating system or encoder update. Our live-stream pre-flight checklist is a useful reminder to check the actual broadcast path before an audience depends on it.
For an always-on channel, a successful short test is necessary but not evidence that a desktop will remain healthy unattended through the night. Sleep settings, power cuts, updates, heat and network interruptions are outside the bitrate field. If the specific pain is leaving your own computer switched on to keep a video broadcast running, StreamNeo turns an uploaded file into a YouTube live stream without relying on that computer to stay on; you still need to check the channel and content before broadcasting.
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 YouTube Live 1080p30 H.264?
YouTube’s current live-ingest table recommends 14 Mbps and lists 5 Mbps as the minimum for H.264 at 1080p30. In OBS, 14 Mbps is entered as 14,000 Kbps. Start there only if your connection sustains it in a representative test; lower it and retest if you see dropped frames.
Should the OBS canvas and output both be 1920×1080?
They can match, but they serve different purposes. The canvas is where you compose the scene; Output (Scaled) Resolution determines the dimensions OBS sends. If they differ, OBS scales the composition, so inspect text and fine detail in the delivered stream.
Which H.264 encoder should I select in OBS?
Select an H.264 encoder that is available and stable on your computer. Software and hardware options expose different controls and have different workloads, and labels vary by platform and OBS version. Test the chosen encoder with your real scene and watch for encoder overload.
How can I confirm YouTube is receiving 1080p30?
Run a private test, check OBS output statistics and YouTube’s stream-health information, then inspect playback on YouTube. Confirm the detected resolution and frame rate, along with audio and visual quality. Do not rely on a setting label alone: it describes your intended configuration, while the received stream is what viewers will get.