YouTube does not publish a separate live bitrate recommendation for a static background. Choose the general video bitrate for the codec, resolution and frame rate you send, then set music audio separately.
For an H.264 stream at 1080p30, YouTube Help recommends 14 Mbps for video; at 720p30 it recommends 8 Mbps. For stereo audio it recommends 128 Kbps. These are general encoder recommendations, not a claim about the minimum bitrate an unmoving picture needs.
A static image does not get its own official bitrate
A still image seems as though it ought to need less bandwidth than a busy scene: after the picture has arrived, the encoder has little visual change to describe. That observation may inform an encoder experiment, but it is not a separate setting in YouTube’s published live recommendations. YouTube’s table is organised by video codec, resolution and frame rate, not by whether the picture moves.
That distinction matters when you set up an always-on channel. If you tell a helper or an encoder to use a “special YouTube static-image bitrate”, you may be passing on a rule the official guidance does not state. Use the applicable general recommendation as your starting point. If your encoder offers a lower rate and you want to test it, treat that as your own trial, not as an official YouTube minimum or a guaranteed safe setting.
A static background can still include motion that changes encoding demands: a visualiser, scrolling text, a clock, transitions between images, or occasional video clips. Even when the artwork never changes, the music remains a separate audio stream and the service still receives video at the frame rate you configure. Decide what actually goes into the stream rather than relying only on the label “static”.
YouTube also transcodes an incoming live stream into playback formats for viewers. You are choosing the feed sent to YouTube, not encoding an individual rendition for every viewer’s device. The live encoder settings and bitrate table are the relevant reference for that outgoing feed.
Start with the general video recommendation
First write down the actual video configuration: codec, resolution and frame rate. Then look up the corresponding recommendation. Do not choose a bitrate first and assume it applies equally to every resolution or codec.
For two common H.264 configurations, YouTube Help lists these recommended video rates:
| Incoming video configuration | YouTube Help recommendation for video |
|---|---|
| H.264, 1080p at 30 fps | 14 Mbps |
| H.264, 720p at 30 fps | 8 Mbps |
These figures are video only. They do not include audio or the extra network capacity you should leave available. They are recommendations for the specified incoming H.264 configurations, not measurements of how much data a still picture consumes in practice. If your stream uses another codec or frame rate, consult the current table rather than transferring one of these figures by guesswork.
Resolution is a practical choice as well as a quality choice. A 1080p artwork file does not by itself require you to broadcast at 1080p. If your source is a single illustration and text that is legible at 720p, the 720p configuration may suit the channel and reduce the outgoing video rate compared with the cited 1080p30 recommendation. But check how small text, fine linework and gradients look on an actual phone and television before settling on it.
Frame rate is another part of the recommendation, not a decorative encoder setting. A motionless graphic may tempt you to choose a very low frame rate, but YouTube’s recommendation is still tied to the frame rate you send. Pick a supported configuration that behaves consistently in your encoder and check it against YouTube’s current guidance. For a broader run-through of the decisions that affect a continuous channel, see how to optimise a 24/7 YouTube Live stream.
If you are comparing configurations, include network capacity in the decision. A recommended video rate is of little help if your connection cannot hold it steadily, especially when the stream must run overnight. The guide to upload speed for prerecorded video on YouTube Live explains how to think about the connection alongside the encoder settings.
Keep the music audio rate separate
A stream’s total outbound data includes the video and audio feeds. If you set an encoder to the recommended video rate, that is not the total connection requirement: music audio adds its own bitrate, and protocol overhead and network variation also matter. Keep the fields separate in your encoder and when you estimate bandwidth.
For stereo music, YouTube Help recommends 128 Kbps audio. That value is an audio recommendation, not part of the 14 Mbps or 8 Mbps video figures in the table above. Choose stereo if that is how your programme is mixed. If you plan to send 5.1 audio instead, use the corresponding current recommendation rather than applying the stereo figure to it.
For a bhajan stream, a lofi station or a local radio-style loop, the difference between audio and video settings is easy to miss because the picture may be mostly artwork. The music still has to arrive as audio data, so a seemingly modest visual scene does not make the audio field irrelevant. Listen to representative material on headphones and a phone speaker: a quiet devotional passage, a louder chorus and any transitions can expose clipping or level jumps that a bitrate value cannot fix.
Bitrate does not settle whether you may use a recording. YouTube’s live stream settings guidance tells creators to ensure they have rights to the audio and video they use. Check the current official guidance and your own permissions for the recordings, compositions, artwork and other material in the channel; a technically correct encoder setting is not a rights clearance.
Configure CBR and keyframes deliberately
YouTube recommends constant bitrate (CBR) for the live encoder and a keyframe interval of two seconds, with keyframes no farther apart than four seconds. Set these in the encoder rather than assuming a preset has chosen the right values. YouTube’s guidance covers the incoming live feed generally; it does not create a static-background exception.
CBR aims to keep the encoded rate steady over time. For a long-running stream, that makes the outgoing demand more predictable than allowing the rate to vary widely. It does not mean the connection is immune to congestion, nor does the setting guarantee that a stream will remain healthy. The practical benefit is that you can plan around a more consistent target and observe whether the connection sustains it.
A keyframe is a reference frame from which later frames can be decoded. The interval affects how frequently those reference points appear in the video stream. Set two seconds if the encoder allows it and keep within YouTube’s stated ceiling of four seconds. Do not infer that a still picture can skip keyframes indefinitely; use the published setting and check the encoder’s actual output configuration.
Some encoders offer variable bitrate (VBR) alongside CBR. The choice can be confusing when most of the picture is unchanged, but the static-scene question does not replace YouTube’s CBR recommendation. For the underlying distinction and configuration trade-offs, see CBR versus VBR for YouTube Live streaming. If a workflow requires another mode, verify what it sends and test it rather than presenting the choice as YouTube’s static-image rule.
Check the audio format and sample rate
A bitrate is only one part of audio setup. YouTube’s live encoder guidance lists AAC or MP3 audio over RTMP or RTMPS, and its advanced settings recommend a 44.1 kHz sample rate for stereo. Use a format your encoder and ingest path support, and check the current official settings if you change from stereo to another channel layout.
Sample rate and bitrate describe different things. The sample rate is how often audio is sampled; the bitrate is how much encoded data is sent each second. Changing one does not automatically set the other to the recommended value. Check both fields in the encoder, then listen to the result after it has reached YouTube, rather than relying on a local preview alone.
For a continuous music channel, make sure the audio is actually continuous where you expect it to be. Check the joins between tracks or programme segments, and listen for silence, abrupt level changes, or a persistent hiss. These are content and signal checks, not reasons to change the published video recommendation. If the stream combines a still image with a playlist, the H.264 and AAC settings for a YouTube playlist stream may help you think through how video and audio settings fit together.
Leave headroom and test the complete path
YouTube recommends leaving 20% upload headroom and counting both primary and backup streams when calculating outbound bandwidth. That is not an added video bitrate; it is capacity to keep available above the planned stream demand. If the same connection must carry another stream, include it in the estimate as well as the main one.
For example, when comparing the H.264 recommendations above, do not treat an internet plan’s advertised upload rate as if the entire figure were reserved for the broadcast. Measure the connection at the location and time you intend to stream, then allow for other household or business traffic and the recommended headroom. An upload test is a snapshot, not a promise that the link will remain steady all night. YouTube’s streaming tips discuss upload capacity and headroom.
Test a private or otherwise non-public stream before relying on the setup. Use the real artwork, representative music, selected resolution and frame rate, and the intended network connection. Let it run long enough to see whether the encoder and connection stay consistent; include any backup path in the test if you plan to use one. YouTube recommends testing before going live and reviewing stream-health messages.
During the test, look at the health indicators in YouTube Studio as well as the encoder preview. A smooth local preview can coexist with trouble in the feed received by YouTube. If YouTube reports a problem, check the actual outgoing bitrate, dropped frames, encoder settings and connection before changing several values at once. Change one setting, repeat the test, and note whether the message or playback improves.
The test should resemble the final broadcast. A short clip with an animated visualiser may not represent a channel that displays one image for hours; conversely, a single still image may not represent a schedule that changes artwork or includes video inserts. Include whatever motion and audio transitions viewers will encounter. The goal is to verify the chosen general recommendation and your delivery path, not to prove an unofficial lower static-image rate.
A local computer can be a reasonable fit if you want control over the encoder and can keep the machine and connection running. If the specific pain is having to leave your own computer on to keep an uploaded file broadcasting, StreamNeo removes that task: you upload the video once, provide your YouTube stream key, and the cloud broadcast can run with your computer switched off. It is YouTube-only, so check that this matches your channel and workflow.
For an always-on schedule, document the working configuration somewhere another person can find it: codec, resolution, frame rate, video bitrate, audio format and rate, CBR, keyframe interval, and any relevant YouTube health messages from the test. This avoids rebuilding the setup from memory after a restart or a change of operator. Recheck the official encoder page when you change resolution, codec, or programme format, since recommendations are tied to the incoming settings.
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 a static background with music?
There is no separate official YouTube bitrate for a static background. For H.264 at 1080p30, YouTube Help recommends 14 Mbps video, and for H.264 at 720p30 it recommends 8 Mbps; for stereo audio it recommends 128 Kbps. Match the general video recommendation to your incoming codec, resolution and frame rate, and treat video and audio as separate settings.
Can I lower the video bitrate because the picture does not move?
You can test a different encoder setting if your workflow permits, but do not describe a lower rate as YouTube’s official static-scene recommendation or as an exact minimum. A visualiser, captions, transitions or occasional clips also change what the encoder has to handle. Test the actual programme and check YouTube’s stream-health messages before relying on a configuration.
Does the audio bitrate count towards the video bitrate?
No. The video bitrate and audio bitrate are separate components of the outgoing stream. Include both, plus headroom and any backup stream, when considering the upload capacity needed for the broadcast.
What CBR and keyframe settings should I use?
YouTube recommends CBR and a two-second keyframe interval, with the interval not exceeding four seconds. Set and verify these in your encoder, then test the feed before using it for a continuous broadcast.