For a stereo music playlist on YouTube Live, set your encoder to 128 Kbps audio bitrate and 44.1 kHz sample rate. YouTube publishes these as encoder recommendations; they are not a promise that every viewer will hear the same playback encoding.
For RTMP or RTMPS ingest, YouTube lists AAC or MP3 audio. If you are sending 5.1 surround over RTMP/RTMPS, use AAC and the separate 5.1 settings; do not carry the stereo recommendation across to that format. HLS has its own codec guidance.
Recommended settings for stereo music
A playlist stream using two-channel audio should start with YouTube’s published stereo values: 128 Kbps and 44.1 kHz. Those figures apply to stereo live audio generally. YouTube does not publish a special, higher bitrate recommendation for music playlists, or a separate setting for a static picture paired with music.
That distinction is useful when you are tempted to raise the encoder bitrate because the stream contains music rather than speech. YouTube recommends 128 Kbps for stereo. Its guidance does not establish that setting a higher ingest bitrate will improve the sound delivered to every viewer, particularly because live streams are transcoded into different output formats. Start with the recommendation, then verify the actual programme and the stream health rather than treating a larger number as a quality guarantee.
| Use case | Audio bitrate | Sample rate | Protocol and codec note |
|---|---|---|---|
| Stereo playlist | 128 Kbps | 44.1 kHz | RTMP/RTMPS lists AAC or MP3; HLS has separate codec guidance |
| 5.1 surround | 384 Kbps | 48 kHz | RTMP/RTMPS requires AAC for 5.1; HLS lists AAC, AC3 and EAC3 |
The 5.1 row is only relevant if your source and intended broadcast genuinely use surround channels. A stereo file does not become a 5.1 programme by choosing a surround setting in an encoder. If you are sending a conventional playlist mixed for left and right speakers, keep the channel format stereo and use the first row.
The recommendations are encoder ingest settings, not a statement about all audience devices. A viewer may receive an output chosen by YouTube for their device or connection. For that reason, consider the bitrate as a sound starting point for the signal you send, not a control over every listener’s playback.
Set 128 Kbps and 44.1 kHz
In your encoder, locate the audio controls and set the bitrate to 128 Kbps, the sample rate to 44.1 kHz, and the channel layout to stereo. The labels vary between applications: bitrate may appear as audio bitrate or AAC bitrate, while the channel field may be called channels or layout. Check that the values are applied to the live output profile, not only to an unrelated recording preset.
If the encoder offers a choice between constant and variable audio bitrate, follow the encoder’s normal stable live-stream preset unless you have a specific reason to change it. YouTube’s cited recommendation gives a bitrate value; it does not prescribe every encoder’s menu choices or claim that a particular rate-control mode is superior. Avoid changing several audio parameters at once during a live channel’s routine operation, since it makes faults harder to isolate.
Sample rate is not the same setting as bitrate. Kbps describes the amount of encoded audio data sent each second; kHz describes the number of audio samples represented each second. For this stereo recommendation, set both explicitly rather than assuming that the source file’s properties will be carried through unchanged by the encoder.
A music file may be mastered at a different sample rate or have a different loudness from the next item in a playlist. Conversion to the stream’s output rate is normal, but listen for clicks, abrupt level changes, or silence at transitions in a local test. A continuous broadcast can reveal these problems only after the playlist has moved between tracks, so the test should include representative transitions rather than a short listen to the first few seconds.
For a practical encoder walkthrough that covers related video-side values, use the YouTube RTMP bitrate and keyframe settings guide. Keep its video recommendations separate from the audio figures here: changing video bitrate does not replace setting the stereo audio bitrate and sample rate.
RTMP/RTMPS audio codec options
For RTMP and RTMPS ingest, YouTube lists AAC and MP3 as audio codec options. Choose a codec supported by both your encoder and the ingest workflow, then keep the bitrate and sample rate aligned with the intended channel format. YouTube’s listing identifies supported choices; it is not a comparison declaring that AAC or MP3 will sound better at matching settings.
If you are configuring a common software encoder, AAC is a straightforward choice where it is available and works with the rest of your profile. MP3 is also listed for RTMP/RTMPS, but do not infer from that listing that every protocol or channel configuration has identical codec support. The protocol matters, especially if you are considering HLS or surround sound.
A useful way to select a configuration is to decide in this order: protocol, channel format, codec, then bitrate and sample rate. If you first pick a codec without knowing whether you are sending stereo or 5.1, you can create an output profile that is inconsistent with the format you want. For a stereo music stream over RTMP/RTMPS, either listed codec can be considered, with 128 Kbps and 44.1 kHz as the stereo targets.
HLS is not just another spelling for RTMP. YouTube’s HLS-specific documentation lists AAC, AC3 and EAC3, and gives stereo and 5.1 audio recommendations separately. HLS also sends video in segments and has higher latency than RTMP, so protocol choice can affect how live the channel feels as well as which encoder settings apply. Consult YouTube’s HLS ingest guidance before building an HLS profile; do not copy an RTMP codec list into it by assumption.
YouTube’s live encoder settings guidance is the primary reference for the RTMP/RTMPS options and general encoder recommendations. Check the current page when setting up or revising a profile, because published platform guidance is the authority for its supported ingest configuration.
When 5.1 settings apply
Use the 5.1 recommendation only when the programme is genuinely encoded as 5.1 surround. YouTube lists 384 Kbps and 48 kHz for 5.1. For RTMP/RTMPS ingest, AAC is required for 5.1. Do not use MP3 for an RTMP/RTMPS 5.1 configuration, and do not confuse its support with the separate stereo options.
Many devotional, lofi, ambience, study, and local radio playlists are prepared as stereo. If your source is stereo and listeners are meant to hear a left-right mix, the 5.1 row adds unnecessary configuration complexity. It may also leave you wondering why channel mapping does not behave as expected. Select stereo end to end unless your content production and encoder output really carry six surround channels.
HLS has its own 5.1 codec list: AAC, AC3 and EAC3. The codec list does not mean that every codec is valid for every protocol. YouTube’s HLS audio guidance should be checked for an HLS workflow, while the RTMP/RTMPS 5.1 condition remains AAC. Keep protocol and channel format together when documenting a saved profile.
If you do not have a surround production chain, there is no reason to buy equipment or rebuild a playlist merely to select 5.1. The YouTube recommendation is a target for the signal being ingested, not an instruction to upmix ordinary stereo material. A clean stereo mix is a more appropriate choice than a surround setting that your source cannot meaningfully supply.
How YouTube transcodes live audio
The bitrate in your encoder describes the audio sent to YouTube at ingest. YouTube processes live streams into multiple output formats for viewers using different devices and network conditions. The signal you send therefore does not directly dictate one identical audio encoding for every person watching or listening.
This is why 128 Kbps should be understood as YouTube’s recommended stereo encoder setting, rather than a guarantee about the bitrate or codec a viewer receives. It is also why simply increasing the ingest setting is not proof that audience playback will improve. Use the published recommendation as the stable baseline, then test the quality of the source mix, the encoder output and the viewer experience on the devices that matter to your audience.
For an audio-only playlist accompanied by a still image, the cited guidance does not provide a different audio bitrate from other stereo streams. The picture may be static, but the audio is still a stereo live signal. Set its audio stream appropriately and make sure the video portion also meets YouTube’s ingest requirements.
Transcoding has a practical implication for troubleshooting. If one listener reports a problem, first check whether it is reproducible across devices and connections before concluding that the encoder ingest value is wrong. Conversely, if the test stream itself is clipping, muted, out of sync, or breaking between tracks, resolve that at the source or encoder; a viewer-side rendition cannot repair a defective incoming programme.
Keep ingest settings distinct from viewer playback
Keep three stages separate in your notes: the media source, the encoder’s outgoing signal, and YouTube’s playback rendition. A track may have its own file format and sample rate; the encoder produces the configured live feed; then YouTube transcodes for delivery. These are related stages, but the settings at one stage should not be described as if they control every later stage.
This separation prevents a common misdiagnosis. If the encoder profile says 128 Kbps, that confirms what you intended to send for stereo ingest; it does not verify every viewer’s playback codec. If a viewer hears a difference, compare a controlled test on a known device and connection, and check YouTube’s stream health information before changing the profile without evidence.
The same separation helps with bandwidth planning. Audio is only part of a live stream’s upload demand; video and protocol overhead also use capacity. YouTube recommends leaving 20% upload-bandwidth headroom in its encoder guidance. Treat that as a planning margin, not as a guarantee that a particular internet connection will remain stable overnight.
If the stream runs from a local computer or mini PC, the quality of the broadband upload and the continuity of the machine both matter. The ACT Broadband upload speed check for an India gaming rerun stream explains how to examine upload capacity in one practical setting. For a broader local-machine trade-off, the always-on mini PC guide considers the computer-side approach. Neither changes YouTube’s stereo audio recommendation; they address whether your chosen setup can keep sending the programme.
Validate the audio in a test stream
Do a private or otherwise appropriate test before putting the playlist into its regular schedule. YouTube recommends testing in advance with audio and movement similar to the planned stream, monitoring stream health during the event, and leaving upload headroom. For a playlist channel, the audio test should include the kind of music, level changes, silence, and transitions the audience will actually encounter.
Listen on the encoder output if possible, and also review the received stream on a separate device. Check that both stereo channels are present, the level is not clipping, and the beginning and end of tracks do not create unwanted gaps or abrupt jumps. If the channel combines music with a static image, confirm that the video feed remains valid even while the picture does not change; the audio should not be treated as a substitute for verifying the entire broadcast.
Watch the stream health indicators while the test runs. If you see interruptions, distinguish an audio configuration issue from network instability, a device sleeping, or a playlist source that has ended. Do not respond to every dropped-frame or reconnect message by raising audio bitrate. A larger bitrate can consume more of the available upload capacity without solving a fault elsewhere.
For a local encoder, test the exact saved profile and the same network path you expect to use. Leave YouTube’s recommended 20% upload headroom rather than planning to occupy all measured capacity. Broadband can vary, and a speed test at one moment is not a promise about sustained performance later. A night-long run is a different test from a quick preview: you need to see whether the source, machine, network and encoder continue behaving after the initial setup.
If you do not want your own computer to stay on for a continuous file-based broadcast, StreamNeo removes that particular operational burden by letting you upload the video and have the YouTube broadcast run without your computer switched on. That does not change the need to prepare the right file, configure the channel and check music rights; it addresses the risk of depending on a local machine to keep a playlist running.
Music rights and continuity
Audio settings do not settle whether you may use the music in a live stream. YouTube says live streams are scanned for matches to third-party content. If a match is identified, the stream may show a placeholder or the streamer may receive a warning; continued use can interrupt or terminate the broadcast. A rights holder may also need to add a channel to a Content ID allowlist for a licensed use to proceed without that interruption.
Review the official copyright guidance for live streams and the relevant terms for the music you plan to use. YouTube’s live-stream terms say providers represent that they hold necessary rights for live content, including applicable music rights. Creator Music usage details also state that tracks under those terms cannot be used in live streams. These platform documents do not determine your position for a specific track, territory or licence, so check the current official material and your own rights documentation.
For a channel intended to run continuously, continuity has two separate meanings: technical continuity and permission to use the programme. A stable bitrate and a reliable source can help with the first, but neither prevents a rights match from affecting the stream. Do not assume that a track is suitable for a live playlist merely because it can be included in a normal video or is available in a music library for some other kind of use.
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 audio bitrate should I use for a YouTube Live music playlist?
For a stereo playlist, set 128 Kbps audio bitrate and 44.1 kHz sample rate. YouTube publishes these as encoder recommendations, not as a promise that all viewers receive identical playback encoding. There is no separate playlist-specific bitrate in the cited guidance.
Is 128 Kbps enough for stereo streaming?
It is YouTube’s recommended stereo ingest bitrate. Use it as your encoder baseline, then test the actual mix and stream health. The recommendation does not establish that a higher setting will improve what every viewer hears after YouTube transcodes the stream.
Should I use AAC or MP3?
For RTMP/RTMPS, YouTube lists AAC and MP3 for audio. For 5.1 surround over RTMP/RTMPS, AAC is required; HLS has a different list that includes AAC, AC3 and EAC3. Choose based on the protocol and channel format you are actually sending.
Do I need a separate bitrate for a static-image playlist?
The cited YouTube guidance does not specify a different audio bitrate for a playlist with a static image. If the audio is stereo, use the 128 Kbps and 44.1 kHz recommendation and check the video feed separately. Confirm that your source and rights are suitable for the planned live use.