For a YouTube podcast livestream with a still image, start with 720p at 30 frames per second, H.264 video, a constant 8 Mbps video bitrate, AAC stereo at 128 kbps, and a 2-second keyframe interval. This follows YouTube’s 720p30 H.264 recommendation while keeping the visual side proportionate to an audio-led programme.
That is a practical starting point, not a special still-image preset. YouTube’s encoder guidance is organised by codec, resolution and frame rate rather than by whether the picture is moving, so your upload connection still has to sustain the chosen stream reliably.
A still image does not create a separate bitrate category
A still image contains less visual change than a camera feed, a gameplay stream or a video with frequent cuts. That can make the encoded video easier to compress, but it does not mean YouTube publishes a lower bitrate setting specifically for static artwork. The relevant official table is based on the stream you send to YouTube: its resolution, frame rate and encoder codec.
This distinction matters because a still image can tempt you to choose settings by guesswork. You might reason that almost nothing is moving, so a very low bitrate must be enough. The picture may look acceptable in a local preview, yet the stream can still suffer from unstable delivery, poor audio settings, badly timed keyframes or an upload connection that is too close to its limit.
The still image also has to remain readable. A podcast cover with small text, a guest name, a sponsor mark or a schedule may look clear in the original file but become soft after scaling and YouTube’s processing. A sensible resolution gives the encoder room to preserve edges and lettering without asking you to send a needlessly large stream.
YouTube also transcodes a live input into different playback formats for viewers. The bitrate you send is therefore an ingest setting, not necessarily the bitrate every viewer receives. Your job is to provide a clean, sustainable source; YouTube handles the different output versions for supported viewers. The official encoder settings guide explains the broader table, including alternatives for other codecs and frame rates.
Start with 720p30 and H.264
For this type of programme, begin with:
| Setting | Practical starting point |
|---|---|
| Ingestion resolution | 1280 × 720, usually described as 720p |
| Frame rate | 30 fps |
| Video codec | H.264 |
| Video bitrate | 8 Mbps, CBR |
| Audio codec | AAC |
| Audio channels | Stereo |
| Audio bitrate | 128 kbps |
| Audio sample rate | 44.1 kHz stereo |
| Keyframe interval | 2 seconds |
| Transport | RTMP or RTMPS |
YouTube lists 8 Mbps as its recommended H.264 bitrate for 720p30. It also lists 3 Mbps as the minimum for that row. The 8 Mbps figure is not an officially endorsed lower bitrate for still images; it is the recommended H.264 value for 720p at 30 fps, and it is a useful starting point for a podcast whose main content is spoken audio and a mostly static visual.
H.264 is a practical choice because it is widely supported by streaming software and hardware. If your encoder offers AV1 or H.265, do not copy the H.264 number into that codec’s settings. Use the row for the actual codec, resolution and frame rate you have selected. A setting labelled “720p” alone does not tell you enough to choose the bitrate.
Thirty frames per second is also appropriate for a static or lightly animated podcast layout. You do not gain much from sending 60 fps when the visual consists of an artwork panel, a waveform and occasional text changes. A higher frame rate can increase the amount of data and the upload capacity you need, without improving the spoken-word experience.
If you are still waiting for YouTube live access, bitrate configuration is not the only preparation to make. Check the current account requirements and activation process before scheduling a long programme, particularly if you are setting up a channel in India. Our guide to YouTube Live activation in India covers that separate part of the workflow.
Set the video bitrate to 8 Mbps in CBR mode
Set the video encoder to 8 Mbps with constant bitrate, usually shown as CBR. Constant bitrate gives YouTube a more predictable incoming stream and makes it easier to estimate the upload capacity you need. It does not mean every frame contains the same visual complexity; it means the encoder aims to send data at a steady configured rate.
Variable bitrate can be useful in other types of encoding, but a 24/7 or long-running live channel has a practical reason to favour consistency. A quiet still-image segment may need little visual information, while a transition, animated waveform or slide change may need more. CBR avoids relying on short-term spare capacity that may not be available when the picture changes.
Do not confuse the video value with the whole stream. At this starting point, the main video setting is 8 Mbps, and the audio adds another 128 kbps. You also need some room for protocol overhead and normal variation. Following YouTube’s guidance to leave 20% above the total stream bitrate, the arithmetic is approximately 9.8 Mbps for one primary stream: 8 Mbps plus 128 kbps, with the result increased by 20%.
That 9.8 Mbps figure is an estimate derived from the chosen settings and YouTube’s headroom advice, not a separately published upload-speed target. It is also not a promise that any connection advertised at that speed will be suitable. Wi-Fi congestion, other users, cloud backups and evening network conditions can all affect the result.
For comparison, YouTube lists these H.264 values for common 30 fps inputs:
| Input sent to YouTube | H.264 minimum listed by YouTube | H.264 recommended by YouTube |
|---|---|---|
| 1080p30 | 5 Mbps | 14 Mbps |
| 720p30 | 3 Mbps | 8 Mbps |
| 480p30 | 0.4 Mbps | 4 Mbps |
| 360p30 | 0.4 Mbps | 4 Mbps |
These figures describe YouTube’s ingest guidance, not measured results or a quality guarantee. For a still-image podcast, 1080p30 may make sense when your artwork contains small text or you have a strong, consistent upload connection. It also raises the recommended video bitrate to 14 Mbps, so it should not be selected simply because the source image is large.
Use AAC stereo at 128 kbps
Set the audio to AAC stereo at 128 kbps, with a 44.1 kHz stereo sample rate where your encoder exposes that option. YouTube lists AAC or MP3 for RTMP and RTMPS audio, and its advanced settings recommend 128 kbps for stereo. AAC is the straightforward choice for a spoken podcast with music beds, intro audio or two-channel production.
The audio bitrate is small beside the video bitrate, but the listener notices audio faults immediately. A frozen image is inconvenient; clipped speech, a missing microphone, a hum or repeated drop-outs can make the programme unusable. Check that the correct microphone or mixer input is selected before you begin, and listen to the actual encoded stream rather than relying only on the local monitoring feed.
Stereo is suitable when your production deliberately uses two channels, such as a voice on one side and music or a second microphone in a controlled mix. If your source is truly mono, do not create an artificial stereo effect just to fill the setting. The important point here is to match the encoder configuration to the signal you are sending and verify the result in YouTube’s preview.
Keep the audio level conservative enough to avoid clipping. A podcast can sound loud in headphones while the recorded signal is already distorted. Run the microphone, music and any remote guest through the same path you intend to use during the broadcast. YouTube’s streaming tips are useful alongside the encoder table because the real test is the complete programme, not an empty scene.
If the show includes copyrighted music, images or clips, bitrate settings do not change the rights position. Review the permissions for every element before making a long loop public. For a recurring channel, the guide on copyright strikes on a 24/7 loop is a useful check before you treat a technical test as a production broadcast.
Use a 2-second keyframe interval
Set the keyframe interval to 2 seconds. YouTube’s guidance says to use 2-second keyframes and not to exceed 4 seconds. A keyframe is a complete reference image from which later frames can be reconstructed, so the interval affects how the stream is indexed and processed rather than only how much is moving in the picture.
A still image does not remove the need for regular keyframes. Even if the artwork remains unchanged for several minutes, the live encoder and YouTube still need a properly structured stream. When the scene changes, a waveform moves or a lower-third appears, a regular keyframe pattern keeps the stream predictable.
If your streaming software presents the field in frames rather than seconds, check the frame-rate relationship before entering a value. At 30 fps, a 2-second interval corresponds to 60 frames. Some encoders offer an automatic setting; for a live YouTube workflow, an explicit 2-second value is easier to verify than an undocumented automatic choice.
Do not lengthen the interval to try to save bandwidth. The bitrate setting and the keyframe interval solve different problems. If the stream cannot be sustained, reduce the chosen resolution or correct the connection rather than quietly moving outside the recommended keyframe arrangement.
Check upload stability, not only the speed test result
The practical question is not whether your connection once reached a particular download speed. It is whether the upload path can sustain the complete stream for the duration of the programme, with room for ordinary variation. YouTube recommends running a speed test and leaving 20% room above the total stream bitrate. If you use a primary and backup stream, account for both.
For the 720p30 starting point, the working calculation is:
- Video: 8 Mbps
- Stereo audio: 128 kbps
- Combined configured bitrate: about 8.128 Mbps
- With 20% room: about 9.8 Mbps
Treat that as a planning calculation. It does not account for every local condition, and it is not a guarantee of uninterrupted delivery. Test at the place and time where the stream will actually run. A wired connection is often easier to keep consistent than Wi-Fi, but the important evidence is the observed stream health over a realistic test, not the connection type by itself.
Pause other upload-heavy activity. Cloud synchronisation, security-camera backups, large file transfers and another live stream can consume the margin you thought you had. If several people share the connection, test while their ordinary use is taking place. A channel that works at a quiet midday hour may behave differently during a busy evening period.
If your upload is marginal, you have two honest choices. Improve the connection or choose a smaller ingest setting that it can sustain reliably. Moving from 1080p30 to 720p30 is a meaningful reduction in the recommended H.264 video bitrate, while moving from 720p30 to a lower resolution changes the visual clarity of artwork and text. Make that decision based on the channel’s actual purpose, not on a desire to display the largest number.
A stream that repeatedly buffers or drops is usually better served by a stable lower input than by an unstable high-resolution one. Our troubleshooting guide on a YouTube live stream that keeps buffering can help you separate connection problems from encoder and playback issues.
Test the complete programme before going public
Make a private or unlisted test using the same audio path, still image, overlays, transitions and encoder settings as the real show. YouTube specifically advises testing before starting and making the test resemble the intended stream, including its audio and movement. A five-minute blank scene does not tell you whether a guest intro, waveform animation or scheduled image change will behave correctly.
Watch the stream health messages in YouTube Studio during the test. Look for dropped frames, warnings about the incoming bitrate, audio problems and unexpected disconnections. Also watch the preview on another device or connection. The encoder’s local status may report that it is sending data while the YouTube preview reveals silence, delay or a damaged picture.
Check the still image at the size viewers will see. Read the smallest text on a phone and on a normal desktop window. If a title is important, make it larger or simplify the artwork rather than assuming more bitrate will solve every legibility problem. Bitrate cannot restore detail that was never present in the source image.
Test failure and recovery as well. Confirm that your encoder reconnects as expected after a brief interruption, and know where the stream key is stored and how to enter it again if necessary. If you use FFmpeg, our guide to entering a YouTube stream key in FFmpeg explains that part of the setup without changing the bitrate recommendations above.
For a long-running channel, decide who or what will notice a failure overnight. YouTube’s live controls can show stream health, but a person still needs a practical response plan. If you are using a cloud workflow, StreamNeo removes the need to leave your own computer running by taking an uploaded video, your YouTube stream key and the continuous broadcast into one managed workflow, with automatic monitoring and restart when the stream drops.
Choose reliability before resolution
The 720p30 H.264 setup is a sensible first test because it balances a readable visual with a lower upload requirement than the 1080p30 alternative. It is not the right answer for every podcast. A programme built around detailed slides, charts or dense text may benefit from 1080p30, provided the connection and encoder can sustain YouTube’s listed 14 Mbps H.264 recommendation with the required headroom.
A programme built around a face-sized logo, a title, a waveform and clear spoken audio may gain little from that extra resolution. Viewers are more likely to notice a broken audio path or an interrupted stream than the difference between two reasonable artwork sizes. YouTube’s transcoding also means that your input resolution is not a direct promise about every viewer’s playback resolution.
Latency is another separate choice. Lower latency can help when you are responding to live chat, but YouTube notes that it may increase buffering and is less important when you are not interacting with the audience. For a podcast replay or continuous audio station, stability may matter more than the smallest possible delay. Review the current live stream settings guidance before choosing the latency mode for the programme.
Once the test remains healthy, write down the working settings. Record the resolution, frame rate, codec, bitrate, audio format, keyframe interval and the connection conditions during the test. That small record makes it easier to restore the channel after a software update or move the workflow to another machine without re-guessing every field.
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 a still image need a lower bitrate on YouTube?
YouTube’s reviewed encoder guidance does not publish a special still-image bitrate preset. Use the recommendation for the selected codec, resolution and frame rate; for H.264 at 720p30, that is 8 Mbps as a practical starting point.
Is 8 Mbps enough for a 720p podcast livestream?
It is YouTube’s listed recommended H.264 video bitrate for 720p30, but it is not a guarantee of quality or stability. Add the 128 kbps audio setting and leave the recommended 20% room above the total, then test the real stream on the connection you will use.
Should I use 1080p for a podcast with artwork?
Use 1080p30 when the extra resolution is genuinely useful for detailed artwork or text and your upload can sustain the higher requirement. YouTube lists 14 Mbps as its recommended H.264 bitrate for 1080p30, so compare the complete upload requirement rather than resolution alone.
Does the keyframe interval still matter if nothing moves?
Yes. A static image does not remove the need for a correctly structured live stream. Set keyframes to 2 seconds and do not exceed 4 seconds, then confirm the result in a test stream before broadcasting publicly.