For a 1080p pre-recorded loop in OBS, set the stream bitrate to match the frame rate and ingest codec YouTube receives. YouTube’s live recommendations differ between H.264 and AV1 or H.265, so “1080p” by itself is not enough to choose a target.
For H.264, the recommended live rates are 14 Mbps at 30 fps and 17 Mbps at 60 fps. For AV1 or H.265/HEVC, they are 10 Mbps at 30 fps and 12 Mbps at 60 fps. These are starting targets, not guarantees of sharp video or uninterrupted streaming: your encoder, source and stable upload capacity still matter.
Choose the OBS output frame rate and codec first
The bitrate table is meaningful only after you know what OBS is sending to YouTube. A video file may have been exported at one frame rate and codec, but OBS output settings and the chosen encoder determine the live stream sent to the platform. Start by deciding whether the broadcast should be 30 or 60 frames per second, then confirm the stream encoder’s codec.
For a loop of devotional songs, a study session or a mostly static ambience scene, 30 fps may be a reasonable choice if it matches the source and the movement on screen. A 60 fps output can preserve smoother motion where the video genuinely contains it, but it calls for a higher recommended bitrate in both codec groups. Do not choose 60 fps simply because the source file or a preset offers it; weigh the visible benefit against the greater upload demand.
In OBS, check the output resolution and common FPS under Settings → Video. The stream bitrate is configured under Settings → Output. OBS offers Simple and Advanced output modes, and Advanced mode gives you separate stream and recording controls. Make changes to the live stream output, not the local recording bitrate: those settings serve different outputs.
The codec is also a practical constraint. YouTube’s table gives one pair of recommendations for H.264 and another for AV1 or H.265. Make sure the codec selected by OBS is actually supported by your setup and accepted by the ingest route you are using. If you are unsure, H.264 is a clear baseline to test; do not assume an encoder option in a menu means YouTube is receiving that codec. Check the live control room or stream diagnostics when available.
OBS’s overview guide covers its output and video settings. If your stream encoder choices depend on whether encoding runs in software or on supported hardware, OBS’s hardware encoding guide describes the trade-off: hardware encoding can offload work, while older hardware encoders may produce lower image quality at the same bitrate than software encoding with the default veryfast preset. That is a reason to test the actual result, not to buy a particular graphics card.
YouTube bitrate recommendations for 1080p30 and 1080p60
Use the row that matches the codec and frame rate OBS sends. The figures below are YouTube’s live-ingest recommendations, not upload-file targets and not a promise that any connection can sustain them.
| OBS output sent to YouTube | Recommended live video bitrate |
|---|---|
| 1080p30, H.264 | 14 Mbps |
| 1080p60, H.264 | 17 Mbps |
| 1080p30, AV1 or H.265/HEVC | 10 Mbps |
| 1080p60, AV1 or H.265/HEVC | 12 Mbps |
YouTube publishes these figures in its live encoder settings guidance. Within either codec group, its 60 fps recommendation is higher than its 30 fps recommendation. The codec group changes the target as well: for example, 1080p30 H.264 is listed at 14 Mbps, while 1080p30 AV1 or H.265 is listed at 10 Mbps. There is no single bitrate that applies to every 1080p stream.
A pre-recorded loop does not get a separate lower live bitrate in YouTube’s guidance. Even when the source changes little, OBS is still encoding and sending a live stream. The live-ingest table does not publish a distinct target for static images or looping footage, so use the row for the actual output codec and frame rate rather than inventing a low-motion discount.
Keep this separate from YouTube’s recommendations for files uploaded as videos. Its upload-encoding guidance lists 10 Mbps for standard-frame-rate 1080p and 15 Mbps for high-frame-rate 1080p. Those are upload-file recommendations, not the live ingest figures in the table above. A finished video uploaded to a channel and a file played through OBS into a live broadcast travel through different workflows.
Compare recommended rates with listed minimums
YouTube lists minimum live bitrates as well as recommended rates. A minimum is not the target to aim for when configuring a normal stream: it marks a lower listed threshold, while the recommendation is the more appropriate starting point for the matching mode.
| Output and ingest codec | Listed minimum | Recommended target |
|---|---|---|
| 1080p30, H.264 | 5 Mbps | 14 Mbps |
| 1080p60, H.264 | 6 Mbps | 17 Mbps |
| 1080p30, AV1 or H.265/HEVC | 4 Mbps | 10 Mbps |
| 1080p60, AV1 or H.265/HEVC | 4 Mbps | 12 Mbps |
The minimums come from the same YouTube live encoder settings page. They should not be read as a preferred compromise that automatically gives acceptable detail, nor as a bitrate at which a stream is guaranteed to work. If your upload route cannot sustain the recommended target, dropping to a listed minimum may reduce the amount of data OBS attempts to send, but it does not make the connection stable or establish what picture quality your viewers will see.
This distinction matters for an always-on channel. A test that stays connected for a brief opening does not show whether an upload route will remain stable through a long broadcast. If you must operate below the recommendation, make that a deliberate trial based on the actual content and stream health, and be prepared to reduce output resolution or frame rate instead of treating the minimum as a universal fix.
Set CBR, a two-second keyframe interval, and RTMPS
After selecting the video target, configure the encoder settings YouTube recommends for live ingest. Use constant bitrate (CBR), set the keyframe interval to two seconds, and use RTMPS as the transport where your setup offers it. YouTube says not to exceed a four-second keyframe interval; the recommended two-second interval is the direct setting to use, rather than a range to optimise by guesswork.
CBR keeps the encoder’s output bitrate comparatively consistent over time. It does not mean every frame contains the same visual detail: a busy scene can be harder to encode cleanly than a still frame at the same rate. A constant output is useful for predictable ingest, but it cannot compensate for an underpowered computer, poor source quality or unstable upload capacity.
The keyframe interval governs how often the encoder sends a full reference frame. Other frames can refer back to that information, which reduces the work needed to represent changing frames. The two-second setting follows YouTube’s guidance; it is not a sharpening control. If the keyframe field uses seconds, enter two. If the encoder presents a frame-count field instead, check that the resulting interval corresponds to two seconds at the output frame rate.
RTMPS is YouTube’s recommended secure transport for a live encoder connection. Confirm the destination and connection method in OBS rather than assuming a bitrate adjustment will address a connection problem. If you are configuring a dedicated always-on setup, the 24/7 YouTube encoder settings guide provides related channel-level considerations, while the PC-on or always-on stream discussion is relevant when deciding where the broadcast should run.
These are linked but distinct controls: bitrate sets the approximate amount of video data sent, CBR controls rate behaviour, keyframes establish reference points, and RTMPS is the transport. Changing one does not remove the need to set the others appropriately.
Check stable upload capacity before going live
The configured video bitrate is not the only traffic on the connection. Audio also uses capacity, and the computer may have other network activity. The total stream bitrate must fit within the upload capacity that remains stable during the broadcast. A speed-test result is a snapshot, not proof that the same rate will hold overnight or while other devices are active.
Test with the intended scene, audio and encoder, and allow the stream to run long enough to observe whether it remains healthy. YouTube’s streaming tips recommend monitoring stream health. Watch for encoder overload, dropped frames or warnings in OBS and the YouTube live control room. If the stream reports a problem, note whether it is an encoding issue, a network issue or a source problem before changing several settings at once.
For example, if the intended mode is H.264 1080p60 at 17 Mbps but the route repeatedly drops frames, first check what OBS reports and whether other devices or applications are using upload capacity. A stable test may require a lower output frame rate or resolution, or a different connection, rather than persisting with a target the route cannot sustain. If the goal is an always-on channel, an option that removes the need to keep your own computer transmitting can address that specific operational burden: StreamNeo takes an uploaded file and YouTube stream key so the broadcast can continue with your computer switched off, monitored and restarted if it drops.
Whichever route you use, do not infer reliability from the bitrate setting alone. A recommendation describes YouTube’s preferred ingest configuration for a mode; actual capacity depends on the upload path and its conditions. Test near the time and place where the channel will run, and check stream health after making a change.
Loop a file or playlist in OBS
For one local file, add a Media Source to the scene, select the file and enable Loop in its properties. OBS then starts playback again after the file completes. The OBS Media Sources documentation describes the file source and its playback controls. The property to restart playback when the source becomes active is on by default, and “Show nothing when playback ends” is also on by default; check these options if the source behaves differently than expected when you change scenes or the file ends.
For an ordered playlist, add a VLC Video source and enable Loop Playlist. This source requires VLC to be installed; OBS’s documentation notes that 64-bit OBS requires 64-bit VLC. A playlist is useful when you want several videos to play in sequence rather than repeating one long file. Check the order, file paths and loop behaviour before starting the public stream, especially if media is stored on a removable drive or in a location that may not remain available.
| Content arrangement | OBS source | What to check |
|---|---|---|
| One local video | Media Source | Enable Loop; confirm playback restarts as intended |
| Ordered group of videos | VLC Video | Install the matching VLC version; enable Loop Playlist and check order |
Looping is separate from bitrate selection. The source does not set YouTube’s ingest recommendation, and a static segment does not justify using an invented lower live target. Ensure the source is 1080p if 1080p is the intended output, and check that OBS scales or crops it as expected. A low-resolution source enlarged to 1080p remains limited by the source; a higher bitrate cannot recreate detail that is not there.
The practical sequence is to add the source, verify its playback, set output frame rate and encoder, apply the matching live bitrate, then test the stream with representative material. If you are preparing a regional-language playlist, the Gujarati video export settings guide is relevant to the source-file side of the workflow, though it does not replace the live-ingest settings described here.
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 YouTube streaming in OBS?
Use the YouTube live recommendation that matches the codec and frame rate OBS sends: H.264 is 14 Mbps at 30 fps or 17 Mbps at 60 fps; AV1 or H.265 is 10 Mbps at 30 fps or 12 Mbps at 60 fps. Treat these as starting targets and check that your upload route can sustain the total stream bitrate.
Can I use the listed minimum bitrate instead?
YouTube lists minimums, but they are not the recommended targets. If capacity forces you below the recommendation, test the actual output and monitor stream health; a minimum does not guarantee stable delivery or a particular picture quality.
Does a pre-recorded loop need a lower bitrate than live footage?
YouTube’s live encoder guidance does not publish a separate bitrate for pre-recorded, static or low-motion content. OBS still sends an encoded live stream, so choose the live recommendation for the output codec and frame rate.
How do I loop one video or a playlist in OBS?
Add a Media Source and enable Loop for one local file. For a sequence, use VLC Video and enable Loop Playlist; VLC must be installed, with a version matching whether OBS is 64-bit.