For a 720p30 YouTube loop stream, set OBS to output 1280×720 at 30 fps, use CBR and a two-second keyframe interval, then choose the bitrate for the codec YouTube receives. YouTube’s recommendation is 8 Mbps for H.264 or 6 Mbps for AV1 or H.265; neither number guarantees that your internet connection will sustain a stable stream.
Those figures are encoder-ingest guidance, not a special allowance for loops, devotional music, or static scenes. Treat them as a starting point, test the actual stream and inspect YouTube’s health messages before relying on a long broadcast.
Set OBS to 1280×720 at 30 fps
Open Settings → Video in OBS. Set Output (Scaled) Resolution to 1280×720, then set Common FPS Values to 30. These fields specify the dimensions and frame rate OBS sends, which may differ from the canvas or the media file’s original properties. OBS’s overview guide explains the distinction between base canvas and scaled output resolution.
For a loop, check the output rather than assuming that a 720p source file automatically produces a 720p live feed. If your source is larger, OBS can scale it down; if it is smaller, scaling up does not restore detail that was never present. Keeping the output at the intended 720p can make the stream settings and YouTube’s corresponding bitrate guidance easier to match.
A 30 fps output is a useful fixed target for ordinary recorded-video loops. If the file itself uses a different frame rate, OBS still needs to produce the stream at the chosen output rate. Preview the result for judder or repeated frames, especially where the footage has pans, moving text, or other regular motion. A static artwork background with a slowly changing visualiser will behave differently from a live-action loop, but the official bitrate table does not provide a separate rate for either.
YouTube may transcode an ingested stream into other viewing formats. That gives viewers playback choices, but it does not remove the need to send a correctly configured source feed. OBS describes this in its transcoding guidance. A clean 720p source is still the starting point for the output you intend to provide.
Choose the streaming codec
In OBS, the available streaming encoders depend on your system and OBS installation. The relevant question is which video codec YouTube receives: H.264, H.265/HEVC, or AV1. YouTube lists all three in its live encoder settings and bitrate table, with different recommended rates for 720p30. Do not pick a bitrate first and then assume it applies to every codec.
An encoder name in OBS can refer to the implementation or hardware path as well as the codec. Check the selected encoder’s details and the stream workflow you are using rather than inferring its format from a label such as “hardware”. If you are unsure, use the OBS encoder information and YouTube’s current guidance to confirm which codec is being sent.
The practical trade-off is that a codec recommendation only addresses the platform’s ingest settings. Your computer or chosen encoder must also be able to produce that codec consistently, while your connection must carry the outgoing stream. The research guidance here does not establish that one codec is faster or better on every machine. Test the combination you will actually use, including the same OBS profile and content, instead of choosing AV1 or H.265 solely because its listed bitrate is lower.
YouTube lists RTMP and RTMPS for ingest and recommends RTMPS for encrypted transport. Use the ingest option supported by your workflow and consult YouTube’s encoder setup instructions when configuring the stream. A secure protocol does not change the codec-specific bitrate target.
Set CBR and a two-second keyframe interval
In Settings → Output → Streaming, set Rate Control to CBR. Set the keyframe interval to 2 seconds. YouTube recommends a two-second interval and says not to exceed four seconds. At 30 fps, two seconds corresponds to 60 frames, though OBS commonly asks for the interval in seconds rather than frames.
CBR means the encoder aims to keep the stream’s bitrate consistent rather than allowing it to vary widely with each moment of picture complexity. This makes it easier to plan the outgoing bandwidth requirement. It does not mean the network connection itself is constant, nor does it guarantee that every frame arrives on time. Congestion, Wi-Fi interference, competing uploads, or a weak upstream connection can still interrupt delivery.
A regular keyframe interval gives YouTube a predictable structure in the stream. It also supports smooth changes between viewer quality options, as OBS notes in its transcoding material. Avoid using a longer interval to compensate for a difficult connection: that is not a substitute for choosing a rate your connection can carry reliably.
Check the setting again if you change encoder presets or switch between OBS profiles. Profiles can preserve different output settings, and an old profile may quietly retain a different rate-control mode or keyframe interval. Before an unattended run, verify the values in the active profile rather than relying on what you remember from a prior test.
Match the bitrate to the codec
YouTube’s 720p30 recommendations differ by codec. Its table lists both minimums and recommended values. The minimum is not the target to use when you are trying to meet the recommendation, and the recommended value is not a connection guarantee.
| Codec received by YouTube | Listed minimum for 720p30 | Recommended bitrate for 720p30 |
|---|---|---|
| H.264 | 3 Mbps | 8 Mbps |
| AV1 | 2 Mbps | 6 Mbps |
| H.265 / HEVC | 2 Mbps | 6 Mbps |
The values above are from YouTube Help’s encoder settings page, checked in October 2026. Use the row for the codec your OBS workflow actually sends. In particular, do not copy the H.264 recommendation of 8 Mbps onto AV1 or H.265 and call it YouTube’s recommendation for those codecs; the listed recommended figure there is 6 Mbps.
The minimum figures are useful context, not a promise of acceptable picture quality or uninterrupted delivery. A stream configured at a listed minimum may leave less room for motion detail than the recommended setting. Conversely, setting the recommended bitrate cannot make an inadequate upload connection reliable. These are separate questions: the platform’s ingest recommendation and your own connection’s sustained capacity.
Loops do not have a separate line in YouTube’s bitrate table. A low-motion scene might be easier for an encoder to represent than rapid movement, but the cited guidance does not quantify a loop-specific adjustment. Start with the ordinary 720p30 recommendation for the selected codec, then use a representative test to see whether your full setup is stable. Do not treat static artwork as grounds for inventing a YouTube-approved lower bitrate.
Audio contributes to the total stream traffic as well. YouTube’s table lists audio guidance separately, including 128 Kbps for stereo and 384 Kbps for 5.1 audio. Remember that a 8 Mbps video bitrate is not the whole outgoing stream budget: audio and protocol overhead add to what must travel over the connection. For a typical stereo music or ambience channel, the separate audio value is small beside the video rate, but it still belongs in your planning.
Test upload capacity and stream health
A speed test gives you a snapshot, not proof that an upload rate will remain available overnight. YouTube Help explicitly recommends running a speed test to check upload bitrate. Test from the same connection and location you plan to stream from, preferably at a time when other people or devices are also using the connection. If the test is made on a quiet network but the real broadcast competes with cloud backups or video calls, the result may be misleading.
Run a private or otherwise controlled test using the codec, bitrate, resolution, frame rate, audio, and OBS profile intended for the public loop. Include a representative piece of the actual video: a quiet holding image alone does not test the harder moments in a music video, a moving fireplace, a news ticker, or a study timer with changing text. Let the test run long enough to encounter ordinary variation in your connection, then review YouTube’s preview and stream-health messages.
In YouTube Live Control Room, confirm that the preview appears and that the health panel does not report ongoing problems. Watch for dropped frames in OBS as well. These signals help separate a feed that is configured as expected from one that is struggling to reach YouTube. If the preview looks wrong, check output dimensions and the selected encoder before changing bitrate at random.
A practical test is repeated when something material changes: a different connection, a new encoder, a new router location, a bitrate change, or a new source with much more motion. You do not need to invent a laboratory procedure. Use the real chain from OBS to YouTube and observe the stream in the place where YouTube reports incoming health.
For channels built around recorded programming, the broadcast settings are only one part of the operating routine. The workflow in streaming Hindi bhajans from recorded videos is relevant when planning the content side of a continuous channel; it does not replace checking the live ingest settings for your own encoder.
Adjust when the connection is unstable
If OBS reports dropped frames caused by network conditions or YouTube reports an unstable incoming stream, first confirm that the problem is network-related rather than a rendering or encoding overload. OBS can drop frames because the computer cannot render or encode in time, while a connection problem prevents encoded data from reaching the service consistently. The symptom matters: lowering bitrate may help an upload bottleneck, but it will not fix a computer that is overloaded by a scene or encoder setting.
For an upload bottleneck, reduce the video bitrate in a measured step and run the same representative test again. Do not assume that the minimum in YouTube’s table is a safe target for your connection or that it will look good for your material. It is a listed floor, not a recommendation for all situations. If you must go below the codec’s recommended value, evaluate the resulting picture quality and stability yourself rather than describing it as guaranteed.
Also look for traffic you can schedule elsewhere. A cloud backup, large file upload, or another stream can compete for upstream capacity. Prefer a wired connection if it is available and practical, and avoid placing the streaming computer at the edge of weak Wi-Fi coverage. These steps do not create more capacity from your provider, but can remove avoidable variability inside your home or venue.
If the encoder is overloaded, reduce unnecessary scene complexity or choose an encoder setting the machine handles consistently. A long loop can expose problems that a short setup test misses, but the bitrate table does not specify what hardware is sufficient. Check OBS’s own status indicators and test the exact scene. Do not choose a codec based on an assumed hardware advantage without verifying that your system can encode it smoothly.
If an always-on channel depends on a single computer and connection, decide what you will do if either becomes unavailable. Some operators want the flexibility of OBS and their own equipment; others want their personal computer out of the continuous-streaming path. For the specific pain of leaving a computer running just to keep a prepared file live, StreamNeo can take an uploaded video and run the YouTube broadcast while your computer is off. That does not alter YouTube’s bitrate recommendations or remove the need to verify the resulting channel and stream settings.
A persistent stream also needs content planning, not just encoder settings. For a sequence of clips, how to stop a YouTube podcast stream repeating the same episode addresses a different but related failure mode: a loop that is technically live can still repeat content in an unintended way. If your arrangement uses a computer-hosted playlist, consider the distinction between stream health and playlist behaviour before treating a long test as complete.
Plan the loop separately from the bitrate
The official rate table is organised by resolution, frame rate, and codec, not by whether the stream is unattended or repeats a file. There is no special 720p30 bitrate in the cited guidance for a devotional channel, local news loop, fireplace, or study stream. Use the normal codec-matched baseline and test the actual material rather than assuming that “loop” means a different platform requirement.
A loop can make continuity easier to manage because you prepare the media in advance, but it also means a fault may remain unnoticed if nobody is watching the control room. Establish a routine for checking the live preview and stream health before a planned long run, and revisit it after changing the source or output profile. For more context on continuous playback, setting up a 24/7 fireplace stream on YouTube can help with the broader loop use case, while this article’s bitrate settings remain tied to the stream’s codec and output format.
Do not confuse successful ingest with approval of every part of a channel or its content. The encoder documentation addresses transmission settings, not rights to the media, monetisation, or YouTube policy decisions. Check the current official YouTube guidance relevant to your content and channel separately.
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
Should I use 8 Mbps for every 720p30 YouTube stream?
No. YouTube lists 8 Mbps as the recommended 720p30 bitrate for H.264, while its recommendation for AV1 and H.265 is 6 Mbps. Confirm the codec YouTube receives and use the matching row rather than treating one figure as universal.
Is YouTube’s minimum bitrate enough for a stable stream?
The listed minimums are 3 Mbps for H.264 and 2 Mbps for AV1 or H.265 at 720p30. They are not a promise of stable delivery or a guarantee of picture quality. Test your real connection and material, then check stream health.
Does a mostly static loop need a lower bitrate?
YouTube’s published table does not set a special bitrate for loops or static scenes. Low motion may affect how the encoder represents a picture, but the cited guidance does not give a quantified loop adjustment. Begin with the codec-specific recommendation and judge any change with a representative test.
What should I check if OBS is dropping frames?
Look at OBS’s status indicators and YouTube’s stream-health messages to distinguish network drops from rendering or encoding overload. If the connection is the issue, reduce bitrate carefully and test again; if the machine is overloaded, address the scene or encoder load instead. Lowering bitrate alone will not fix every kind of dropped frame.