For a typical stereo YouTube radio livestream, set the audio bitrate to 128 Kbps and the sample rate to 44.1 kHz. That is YouTube’s recommended setting for stereo live audio.
That figure applies only to the audio track. Your complete livestream also includes video, so the total bitrate depends on the video resolution, frame rate, codec and available upload connection. Leave bandwidth headroom and test the complete stream before relying on it overnight.
What “bitrate” means for a radio livestream
Bitrate is the amount of data encoded and sent each second. It is normally shown in Kbps for audio and Mbps for video. A higher bitrate can preserve more detail, but it also requires more upload capacity and gives a weak connection less room for interruptions.
For a radio channel, the word “bitrate” can mean two different things:
- Audio bitrate: the amount of data used for speech, music and other sound.
- Total stream bitrate: the audio and video data sent together, plus the normal overhead involved in delivering the stream.
This distinction matters because 128 Kbps is the audio setting, not the bitrate of the whole livestream. A radio stream showing a still image still sends a video track. That video track may use several Mbps depending on its settings, even when the picture barely changes.
YouTube’s live encoder settings should be treated as the source of truth for the current combinations of codec, resolution, frame rate and bitrate. Encoder software may present these choices in different places, but the underlying question is the same: how much data will the complete output send every second?
The recommended stereo audio setting
For ordinary stereo radio, use:
| Audio setting | Practical value |
|---|---|
| Audio bitrate | 128 Kbps |
| Sample rate | 44.1 kHz |
| Audio layout | Stereo |
| Audio codec for RTMP or RTMPS | AAC or MP3 |
| Bitrate mode | Constant bitrate, or CBR |
YouTube’s guidance states: “Audio bitrate: 128-Kbps for stereo or 384 Kbps for 5.1 surround sound.” The 384 Kbps value is for a genuine 5.1 surround mix, not a normal two-channel devotional, bhajan, lofi, music or spoken-word radio stream.
If your source files are stereo, selecting 384 Kbps does not turn them into surround sound. It simply uses more data for an output that is still not a 5.1 production. For a standard stereo channel, begin with 128 Kbps at 44.1 kHz and keep the output consistent from the encoder through to YouTube.
The sample rate describes how many times per second the audio signal is sampled. It is separate from bitrate. Changing the sample rate does not make 128 Kbps become a higher-quality bitrate, and increasing the bitrate does not correct a poor source recording. If the music was already clipped, noisy or heavily compressed before it reached the encoder, a larger number will not restore the missing detail.
You should also check the audio level before starting a long broadcast. A bitrate setting controls how the sound is compressed, not whether the signal is too quiet or distorted. Listen to the same file through headphones and through an ordinary phone or small speaker. Music that sounds acceptable on headphones can still have harsh peaks, missing vocals or an uncomfortably loud background when monitored on a smaller device.
Audio bitrate is not total stream bitrate
Suppose your encoder sends stereo AAC at 128 Kbps and H.264 video at 4 Mbps. The audio contributes only a small part of the stream, while the video contributes most of the payload. The connection still needs to carry both, along with protocol and network overhead.
This is why reducing the audio setting is not a complete answer to a stream that keeps disconnecting. Moving from 128 Kbps to a lower audio value may save some bandwidth, but it does not remove the video track. A video setting that is too demanding, or an upload connection that fluctuates, can remain the main problem.
The opposite is also true. A stable audio setting does not make the whole broadcast stable. You could have the correct stereo audio configuration and still see dropped frames, an unhealthy stream warning or a disconnected broadcast if the total output cannot be sustained.
When diagnosing a problem, write down the separate values rather than describing the stream as “128 bitrate”. Record the audio codec, audio bitrate, sample rate, video codec, resolution, frame rate and video bitrate. This makes it easier to identify whether the issue is in the sound, the picture, the encoder or the connection.
For a practical setup checklist, the best OBS settings for a 24/7 YouTube event replay stream covers the wider encoder configuration rather than treating audio as an isolated number.
Video bitrate depends on your visual settings
YouTube’s recommended video bitrate changes with the ingestion codec, resolution and frame rate. A static-image radio stream usually does not need the same visual settings as a fast sports broadcast, but it still needs a properly encoded video signal.
For H.264 at 30 frames per second, YouTube lists these examples:
| H.264 video output | Recommended video bitrate |
|---|---|
| 360p30 | 4 Mbps |
| 480p30 | 4 Mbps |
| 720p30 | 8 Mbps |
These are video figures. Add the audio bitrate separately when considering the complete stream. The 480p30 example is a lower-bandwidth choice than 720p30 in the official table, while 360p30 may be suitable where the visual is simple and the connection is constrained.
Do not select a resolution only because it sounds familiar. Consider what viewers actually see. A single logo, a station name and a background loop place a different demand on the encoder from animated artwork, scrolling text, a music visualiser or a changing news panel. Movement and fine detail make compression more noticeable, even when the resolution stays the same.
Frame rate matters as well. A 30-frame-per-second output sends fewer pictures than a 60-frame-per-second output and is often a sensible starting point for radio. If you choose a different frame rate or codec, check YouTube’s matching recommendation rather than applying the H.264 table automatically.
The YouTube Live Stream Unstable guide is useful when the selected values look reasonable but the broadcast still reports connection trouble. It focuses on the wider failure pattern, including the difference between encoder output and the network carrying it.
For RTMP or RTMPS, YouTube recommends constant bitrate encoding and a keyframe interval of two seconds, with the interval not exceeding four seconds. YouTube recommends RTMPS for encrypted transport. These settings do not replace the bitrate decision, but they help the platform receive a predictable stream.
Choose a complete starting profile
For a radio channel with a static image or simple visual loop, a practical starting profile could be:
- Stereo audio at 128 Kbps.
- Audio sample rate at 44.1 kHz.
- AAC or MP3 audio when using RTMP or RTMPS.
- H.264 video at 480p30 and 4 Mbps, if that matches the connection and the visual content.
- CBR for the encoder output.
- A two-second keyframe interval, without exceeding four seconds.
This is a starting profile, not a promise that every channel should use the same output. A channel with animated backgrounds may need a different visual choice. A channel with a connection that cannot sustain the complete output may need to reduce the video workload or use a different connection before it attempts a continuous broadcast.
If you are deciding between 360p30, 480p30 and 720p30, compare the viewer-facing benefit with the upload requirement. The change from a simple still image to a more detailed visual may be more noticeable than the change in resolution. Conversely, a channel that displays song titles, readable notices or local news text may need enough resolution for those elements to remain legible.
Do not confuse live-ingestion recommendations with settings for uploading a finished video. YouTube uses different guidance for different workflows. Select the live encoder section that matches your protocol and output rather than copying a bitrate table from a video-upload tutorial.
Leave bandwidth headroom
The complete stream bitrate must fit the upload connection, but matching the advertised upload speed exactly is risky. The available rate can change when another person uses the connection, a router switches conditions or the provider’s service becomes busy.
YouTube recommends leaving 20% headroom. In practical terms, do not plan to use every last part of the measured upload capacity for the livestream. Add the audio and video requirements together, allow for overhead, and keep the result below the reliable capacity you observe during testing.
For example, a video setting of 4 Mbps plus 128 Kbps audio is not a “4 Mbps stream” in the sense that the connection only needs to provide exactly 4 Mbps. The audio is additional, and the encoder and transport need room around the encoded payload. The relevant comparison is between the complete stream and the dependable upload rate, not the audio figure by itself.
A speed-test result is only a snapshot. Run tests at the time of day when the channel will normally operate, especially if the broadcast is intended to run overnight. If the connection is shared, repeat the test while the usual phones, televisions or computers are using it. A result that looks adequate when the network is empty may not describe the conditions during a household’s busiest period.
If the upload connection is marginal, changing the video settings is usually more meaningful than cutting the stereo audio below YouTube’s recommended value. You might choose a lower video resolution, simplify the visual output or move the broadcast to a more dependable connection. Make one change at a time so you can see which decision affected the result.
The guide to setting up a 24/7 YouTube radio stream with a playlist also helps separate the media loop from the delivery method. A playlist can be ready while the stream still needs a suitable encoder and connection to run continuously.
Test before you trust the stream
Do not make the first full-night broadcast your test. Start a private or unlisted live stream and let it run long enough to expose the conditions that a short preview will miss. Watch the stream from another device rather than relying only on the encoder’s local preview.
During the test, check four things:
- Audio continuity: Listen for gaps, repeated sections, clipping, sudden changes in loudness or audio that falls behind the picture.
- Picture quality: Confirm that the station image, text and visual loop remain readable and do not become blurry or heavily pixelated.
- Stream health: Watch YouTube’s indicators for dropped frames, connection warnings and changes in the incoming stream.
- Local conditions: Note whether another device, backup process or software update is using upload capacity.
YouTube’s network guidance recommends testing in advance and monitoring stream health and audio/video quality. The official YouTube bitrate and resolution guidance explains the encoder values, while its network and stream-health guidance covers headroom and testing.
A useful test is not merely “the stream went live”. Leave it running while you perform the ordinary tasks that may happen during a 24/7 channel: play the complete loop, change no settings, use the shared network normally and check the result from a separate viewer connection. If the stream fails, note the time and what YouTube reported before changing anything.
Also check what happens after a brief interruption. A local encoder may need manual attention after a lost connection. If your broadcast method requires your computer to stay on, a power cut, operating-system restart or laptop sleep can end the stream even when the bitrate was correctly chosen. For channels that cannot have a computer running continuously, StreamNeo removes that particular burden by letting you upload the video once, add your YouTube stream key and keep the broadcast running with automatic monitoring and restart when it drops.
That does not remove the need to choose sensible settings or verify the channel. It simply separates the continuous delivery task from the computer you use to prepare the file. You should still check the final YouTube output, the rights to your audio and visuals, and the current platform requirements before committing to a long-running broadcast.
A simple decision process
Start with the content, then work towards the connection rather than choosing a bitrate in isolation.
First, identify whether the audio is stereo. For a normal radio stream, set 128 Kbps at 44.1 kHz. Do not use the 5.1 figure unless you are actually producing a surround mix and your whole workflow supports it.
Next, decide what the video needs to show. A still station image may work with a modest resolution, while a visualiser, song information or scrolling local updates may need more room. Select a suitable frame rate and codec, then consult YouTube’s recommendation for that combination.
Then add the audio and video requirements together. Compare that complete output with the reliable upload capacity, not the headline speed on the broadband contract. Keep YouTube’s recommended 20% headroom, especially on a shared or variable connection.
Finally, run a private or unlisted test and monitor it from another device. If the test is unhealthy, do not assume the audio number is at fault. Check the video setting, upload conditions, encoder mode, keyframe interval and the computer or delivery method keeping the broadcast alive.
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
Is 128 Kbps enough for a YouTube radio livestream?
It is YouTube’s recommended audio bitrate for stereo live audio. It is not the total livestream bitrate, because the broadcast also contains video and delivery overhead.
Should I use 384 Kbps for better radio audio?
YouTube lists 384 Kbps for 5.1 surround sound, not ordinary stereo. If your radio output is stereo, use 128 Kbps at 44.1 kHz and focus on the source quality, levels and complete stream configuration.
What video bitrate should a static-image radio stream use?
For H.264 at 30 frames per second, YouTube lists 4 Mbps for both 360p30 and 480p30, and 8 Mbps for 720p30. Choose according to the visual content and your dependable upload capacity, then leave bandwidth headroom and test the complete stream.
Can the correct bitrate prevent a stream from disconnecting?
No single audio setting guarantees a stable broadcast. Stability also depends on the total audio and video output, upload variation, encoder settings, power and the method keeping the channel live.