For stereo AAC sent to YouTube Live, set the encoder to 128 Kbps and 44.1 kHz. YouTube does not publish a separate AAC bitrate for prerecorded video played out as a live stream; this is the general live encoder recommendation.
The main distinction is channel layout, not whether the pictures were recorded earlier. YouTube’s guidance gives a separate 5.1 surround target: 384 Kbps and 48 kHz. Choose the setting that matches the audio your encoder actually sends.
YouTube Live’s stereo AAC recommendation
YouTube’s live encoder settings recommend AAC at 128 Kbps for stereo audio. This is the useful starting point for a prerecorded programme going to YouTube Live, whether it is a devotional playlist, a lofi station, a lesson loop or a local news programme.
The number describes the audio bitrate in the incoming live feed. It is not a quality rating for the video file, and it is not a guarantee that each viewer will receive an identical encoded stream. YouTube processes live streams into multiple output formats, so the encoder setting is one part of the path from your playout source to viewers.
That distinction also means there is no reason to raise the audio bitrate just because the source file is prerecorded, or to lower it because the stream will run continuously. Use the published stereo live setting unless your actual channel layout or ingest method calls for a different configuration. If you are building a playlist to run for longer periods, the practical work is making sure the audio remains consistent across files, rather than inventing a new bitrate rule for pre-recorded playback.
For a 24/7 channel, check the whole outgoing programme rather than trusting one short sample. A playlist may contain clips produced at different levels or with different audio layouts. The bitrate setting cannot repair a quiet source, clipped recording, uneven loudness, or a gap in the playlist. It controls how the encoder represents the audio it sends; it does not normalise the programme for you.
Set stereo AAC to 128 Kbps and 44.1 kHz
When the channel is stereo, set both the codec and sample rate deliberately: AAC, 128 Kbps, 44.1 kHz. In your encoder or playout software, the labels may appear in separate audio output controls. Check the output profile rather than assuming that a source file’s own properties dictate the live feed settings.
Stereo means two channel positions, usually left and right. A video can contain stereo audio even if it was recorded in a room with several microphones, because the editing or export process may have mixed those tracks down to two channels. Conversely, a file with multiple tracks does not necessarily mean the stream is sending 5.1. What matters is the layout delivered by the encoder to YouTube.
If a programme is already encoded in a file, its audio properties still matter operationally. Your player may decode that audio and the live encoder may encode it again for transmission. In that case, the setting to verify is the encoder’s outgoing audio configuration. Do not confuse the file’s source bitrate with the bitrate configured for the live feed.
A simple setup note can prevent a later mismatch: write down the chosen layout, codec, bitrate and sample rate alongside the channel’s video settings. If someone else prepares the playlist or restarts the encoder, that record makes it easier to reproduce the working configuration. For video-side checks, the vMix playlist guide provides related context on sending a prepared sequence to YouTube Live; the audio output still needs to be checked in your own profile.
Keep the source files and the outgoing stream conceptually separate. If you export a new stereo master, you can use a higher-quality source file for editing and storage without changing YouTube’s recommended live-feed value. The recommendation is for the encoder’s incoming signal, not a direction to degrade your archive or to encode every file at one particular setting before you build a playlist.
Use the separate 5.1 AAC recommendation
A 5.1 mix is a different delivery choice, not a higher-quality version of stereo that every channel should select. For RTMP or RTMPS ingest, YouTube specifies AAC at 384 Kbps and 48 kHz for 5.1 surround. The platform’s guidance says that 5.1 surround over those protocols is supported only with AAC.
Use this configuration only if the audio is genuinely arranged and delivered as 5.1, and your entire path supports it. Selecting a 5.1 preset for a stereo programme does not add surround information. It can instead create a channel mapping problem, with sound in the wrong positions or missing from the expected mix. A two-channel source should ordinarily remain a two-channel feed.
Check the channel layout at the point where the encoder sends the signal, especially if your editing software, playlist player and encoder each have their own audio settings. A project might contain surround tracks but be configured to downmix them to stereo for playout. In that situation the 5.1 recommendation is not applicable to the outgoing feed.
The same distinction is useful when taking over an existing channel. Do not infer the format from the genre, the number of speakers in the room, or the video file extension. Inspect the playout output and confirm with a test. For most simple devotional, ambience, study and small-business channels, stereo is the relevant case; choose 5.1 only when you have a real surround mix and a reason to deliver it.
A 5.1 configuration also raises more opportunities for an unnoticed mismatch. Verify that the channel order and mapping are correct in the encoder and that the preview includes the expected channels. If you cannot check those details confidently, a correctly configured stereo downmix is usually a more straightforward target than selecting surround merely because the original production used several microphones.
Live encoder guidance is not upload guidance
Uploading a video and sending a live feed are different workflows. YouTube’s upload advice concerns the file you submit to be processed as a video. Live encoder guidance concerns the stream your software sends to the live ingest service. A prerecorded file played through a live encoder belongs to the latter workflow at the point of transmission.
This is why upload guidance that lists a range such as AAC-LC at 128–256 Kbps should not be read as permission or instruction to set a live stereo feed above YouTube’s explicit recommendation. The settings apply to different stages and purposes. For the live feed, follow the live encoder page rather than borrowing a higher figure from an upload troubleshooting page.
That does not make upload settings irrelevant to your workflow. If you are preparing the source video for its own upload as well as for live playout, follow the current official upload recommendations for that file. But once the video is decoded and sent as a live broadcast, configure the live output according to live guidance. If the channel contains both uploaded on-demand videos and continuous live playback, keep a note of which setting belongs to each path.
YouTube can also transcode the incoming feed before delivering it to viewers. Therefore, the configured bitrate tells you about the source feed you are sending, not the exact bitrate each viewer will hear. Network conditions, device support and YouTube’s processing all sit downstream. Avoid using a viewer’s playback status or an uploaded file’s properties as the sole proof that the encoder is configured correctly.
Apply the recommendation to prerecorded playback
For prerecorded playback, identify the signal leaving the player or playout software, then configure the live encoder for that signal. A stereo playlist should go out as stereo AAC at 128 Kbps and 44.1 kHz. There is no special “pre-recorded live” bitrate in YouTube’s published guidance, and the fact that content was created earlier does not change the stereo recommendation.
Consider a channel that loops a set of relaxation videos overnight. One clip may have music mixed into the left and right channels; another may have quiet nature sounds; a third may include a spoken introduction. The live AAC setting remains the same for stereo. What needs attention is whether each clip plays at a sensible level and whether transitions introduce silence, abrupt changes or an unintended extra audio track.
That is why a representative test matters more than tuning by guesswork. Test a section with speech if the channel has speech, a section with sustained music if music is the main content, and the transitions where one file hands over to the next. Look and listen in the Live Control Room preview. For a playlist-focused workflow, the continuous relaxation video guide can help with the programming side, while this article addresses the outgoing audio configuration.
A continuous stream also needs an operating plan for interruptions. Even correct audio settings will not help if the source stops playing, the encoder loses its connection or the outgoing feed becomes silent. If an always-on channel depends on a single machine, consider how you will notice and recover from a failure; the 3AM stream failure checklist is relevant to that separate reliability problem.
When long unattended runs are the goal, the source computer itself can become another thing to monitor. StreamNeo addresses that specific operational burden by letting you upload a video and run it as a YouTube live stream without leaving your own computer on; it does not change YouTube’s audio recommendation, so set and verify the stereo output as described here.
Check the selected ingest protocol’s requirements
The audio targets do not replace the rest of the ingest specification. YouTube documents RTMP/RTMPS and HLS requirements separately, so first establish which protocol your encoder or playout service is using. For RTMP or RTMPS, YouTube lists AAC or MP3 for audio; its separate 5.1 support is for AAC. The recommended audio targets remain stereo at 128 Kbps and 44.1 kHz, or 5.1 at 384 Kbps and 48 kHz.
For HLS, YouTube’s HLS ingest guidance permits AAC, AC3 and EAC3 and gives the same bitrate and sample-rate targets for stereo and 5.1. HLS also comes with packaging requirements that do not apply to every creator’s workflow. The guidance specifies transport-stream segments, segment durations in the 1–4 second range, and a rolling playlist with no more than five outstanding segments.
If you are not deliberately using HLS, you do not need to reconfigure a normal RTMP workflow around those packaging rules. If you are using HLS, however, checking only the AAC bitrate is insufficient: confirm that the segment format, duration and playlist behaviour meet YouTube’s current requirements. The codec and packaging choices are related parts of the same ingest path.
For RTMPS, YouTube recommends encrypted transport. Confirm the selected protocol in the encoder and the matching server or ingest details in the Live Control Room rather than assuming the software’s default is what you intended. A correctly chosen AAC rate cannot compensate for a protocol mismatch or malformed HLS packaging.
Protocol-specific advice is also one reason to avoid copying a full preset from another channel. A setup that works for a different creator may use another protocol, channel layout or software version. Start from YouTube’s official page for the ingest method you actually use, then test your own playout chain end to end.
Verify audio before you start
YouTube recommends testing before going live, with audio and movement in the video similar to the real stream. Take that literally: a static test card with no sound does not exercise the same path as a music-led playlist or a programme with speech and scene changes. Use a short private or otherwise appropriate test in the same encoder configuration you plan to keep.
In the preview, check that sound is present, balanced between left and right for stereo, and free of clipping, unexpected silence or distortion. Listen at a sensible volume on headphones or speakers, and check a second playback device if practical. These are practical checks, not a replacement for the platform’s signal and stream-health information.
Also check stream health while the test is running. YouTube recommends leaving 20% upload bandwidth headroom for the outgoing stream. That is a network planning recommendation, not an audio bitrate multiplier: do not add 20% to AAC or treat it as extra audio quality. It means the connection should have capacity beyond the stream’s total outbound demand, which includes video as well as audio.
For an overnight or recurring channel, make the test representative of the conditions when the stream will run. If your internet connection is shared with other activity, test when that activity is present. If the playlist changes from quiet ambience to spoken announcements, listen across those changes. Keep a brief record of what worked, including the protocol and audio layout, so that a later restart does not depend on memory.
Finally, verify again after changing an encoder preset, audio device, playlist player or ingest protocol. Such changes can reset an output to a default sample rate or channel layout without making the live preview obviously fail. A deliberate check of the outgoing feed is quicker than diagnosing a night of silent or misrouted audio afterwards.
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 is the best AAC bitrate for stereo YouTube Live?
Use 128 Kbps AAC at 44.1 kHz for stereo, following YouTube’s live encoder guidance. This recommendation concerns the incoming live feed, not the bitrate of every source file in your playlist.
Should prerecorded video use a different live AAC bitrate?
No separate bitrate is specified for prerecorded material played as a live stream. Configure the encoder according to the live feed’s channel layout: the general stereo recommendation is 128 Kbps, not a special value based on when the video was recorded.
When should I use 384 Kbps AAC?
Use YouTube’s 384 Kbps recommendation with 48 kHz for a genuine 5.1 surround feed over RTMP or RTMPS. It is not a setting to use for ordinary stereo audio, and it does not turn a stereo mix into surround sound.
Do HLS streams use a different stereo bitrate?
YouTube’s HLS guidance gives the same stereo target of 128 Kbps and 44.1 kHz, while also specifying HLS-specific codecs and packaging. Check the current HLS requirements if that is your ingest protocol; they do not automatically apply to RTMP or RTMPS.