For a conventional prerecorded stereo video, export the file at 48 kHz and use AAC-LC as a practical audio codec. That is YouTube’s recommended upload-file guidance; live ingest settings are separate, and the appropriate sample rate depends on the protocol and channel layout.
The distinction matters when a file is played out as a Live event. Do not assume that a 48 kHz file means the live encoder must use 48 kHz stereo, or that an ingest recommendation changes how you should prepare the uploaded file. Check the setting for each stage.
Separate the file export from live ingestion
A prerecorded live channel has at least two audio decisions. First, you prepare and export the media file. Later, an encoder sends the programme to YouTube using an ingest protocol such as RTMP/RTMPS or HLS. Those stages have related but distinct recommendations.
YouTube’s recommended upload encoding settings list AAC-LC, Opus, or Eclipsa Audio and specify a 48 kHz sample rate. The page recommends an MP4 container. This is useful guidance for preparing the media file, not a bespoke rule for every way of playing a prerecorded file into a Live event.
For ingestion, YouTube documents protocol-specific choices on its live encoder settings page and its HLS ingestion guidance. The listed codecs and settings differ by protocol, and the sample-rate guidance changes with the channel layout. Follow the instructions for the method your encoder actually uses.
A useful way to avoid conflating the two is to write down the signal path before exporting. For example: “stereo programme mix → MP4 file at 48 kHz → software encoder → RTMP/RTMPS stereo ingest at the documented setting.” If you later switch the encoder to HLS, review the HLS guidance rather than carrying over the RTMP settings by habit.
The reviewed official pages do not publish a separate sample-rate rule specifically for a prerecorded file played out as a YouTube Live event. The practical approach is to apply the documented upload recommendations to the file, then apply the live-ingest recommendations to the outgoing stream. Neither stage overrides the other.
Recommended audio for a prerecorded file
For a standard stereo programme, a sensible starting point is a 48 kHz export using AAC-LC. That aligns with YouTube’s recommended upload encoding table. Keep the audio channels stereo if the mix is stereo; do not manufacture extra channels simply because another setting mentions surround sound.
The sample rate describes how frequently the audio signal is sampled, not how many channels it contains. A stereo file can be 44.1 or 48 kHz; those values do not turn stereo into surround. The upload guidance’s 48 kHz recommendation is a clear target for a new export, but an existing clean master at 44.1 kHz is not automatically defective. Avoid unnecessary conversions if your editing or mastering workflow would introduce additional processing or errors.
YouTube’s upload troubleshooting reference also lists AAC-LC at 128–256 kbps and sample rates of 44.1 or 48 kHz. Those are troubleshooting-context figures, not a universal rule for every live encoder or source file. Likewise, a bitrate recommendation for an upload should not be copied into a different protocol’s ingest configuration without checking that protocol’s table.
When exporting, preserve the mix balance and avoid clipping. If your source contains devotional music, ambience, speech, or a local news voice-over, listen to the export itself, not only to the editing timeline. Check the beginning and end, a quiet passage, and the loudest section. A nominally correct codec cannot fix distorted source audio, an uneven mix, or music that has been cut off at a loop point.
If the file will run repeatedly, inspect the edit where the end meets the beginning. A small silence, an abrupt fade, or a mismatched room tone can become conspicuous when viewers hear it again. This is an editorial check rather than a YouTube encoding requirement. The pre-flight checks for a 24/7 stream are useful for putting that listening check alongside the rest of the launch routine.
Choose AAC-LC for conventional stereo
AAC-LC is a practical choice for a conventional stereo programme because it appears in YouTube’s recommended upload codecs and is supported for both RTMP/RTMPS and HLS ingestion. It is familiar in common export and encoder workflows, so you can often keep a straightforward path from the file to the outgoing stream. That convenience is not a claim that AAC-LC is the only valid choice at every stage.
For an uploaded media file, YouTube also lists Opus and Eclipsa Audio in its recommended encoding guidance. For live ingest, however, consult the relevant protocol’s list: RTMP/RTMPS lists AAC or MP3, while HLS lists AAC, AC3, and EAC3. Codec support at one stage should not be mistaken for support in another stage or in every channel arrangement.
For a typical stereo loop, keep the decision simple: use an AAC-LC export at the recommended upload sample rate, then configure the encoder to match the selected ingest protocol. If the encoder re-encodes the file, make sure its output codec is one allowed by that protocol. If the workflow passes audio through without re-encoding, confirm that the file’s codec and channel layout are compatible with the receiving configuration.
Avoid selecting 5.1 just to obtain a different sample-rate option. A stereo mix encoded as six channels may create silent or duplicated channels, confusing downmixes, or unexpected playback. If you genuinely have a surround master and the encoder supports it, treat that as a separate production path and check the documented constraints before the event.
This is especially useful for a small always-on channel where the file is prepared once and then left to play. The guide to starting an always-on channel with prerecorded videos in India covers the broader workflow; here, the narrower task is to make sure the audio file and the outgoing stream settings agree.
RTMP/RTMPS audio settings
For RTMP/RTMPS live ingestion, YouTube lists AAC or MP3 as audio choices. Its advanced live settings specify 44.1 kHz for stereo and 48 kHz for 5.1. The page lists 128 kbps for stereo and 384 kbps for 5.1; treat these as the live advanced-setting guidance, not as upload-file rules or a guarantee that a particular programme will sound good.
There is an important codec constraint for surround: YouTube’s RTMP/RTMPS guidance says 5.1 is supported only with AAC. If your programme is stereo, use a stereo configuration and the corresponding stereo sample-rate guidance. Do not change the channel layout simply to match the 5.1 line in the table.
| Stage or ingest path | Listed audio codecs | Sample-rate guidance | Context for the other figures |
|---|---|---|---|
| Recommended upload encoding | AAC-LC, Opus, Eclipsa Audio | 48 kHz | MP4 container recommended |
| RTMP/RTMPS live ingest | AAC or MP3 | 44.1 kHz stereo; 48 kHz 5.1 | 128 kbps stereo; 384 kbps 5.1; 5.1 only with AAC |
| HLS live ingest | AAC, AC3, EAC3 | 44.1 kHz stereo; 48 kHz 5.1 | 128 kbps stereo; 384 kbps 5.1 |
| Upload troubleshooting reference | AAC-LC | 44.1 or 48 kHz | 128–256 kbps in that troubleshooting context |
The table compares separate contexts rather than giving one master preset. In practice, set the file export according to upload guidance, then check the encoder’s RTMP/RTMPS output settings. If the encoder reports an audio format or sample rate that differs from the target, correct it in the encoder or revise the source workflow; do not assume the receiving platform will silently make every conversion you intended.
If you use a local computer to play a loop and encode it, plan for the whole route: the playback application, operating-system audio device, encoder, and stream preview. A setting can look correct in one menu and still be altered by a resampler or channel mapping later in the chain. The FFmpeg guide to continuing a YouTube stream after a video ends is relevant if your workflow uses FFmpeg, but its continuity problem is distinct from choosing the audio setting itself.
HLS audio settings
For HLS ingestion, YouTube lists AAC, AC3, and EAC3 as audio choices. Its live guidance gives the same channel-layout-dependent sample rates as RTMP/RTMPS: 44.1 kHz for stereo and 48 kHz for 5.1. The listed bitrates are 128 kbps stereo and 384 kbps for 5.1. Use these in the context of the HLS ingest path, not as a reason to change your upload export recommendation.
HLS is not just RTMP with a different name in an encoder menu. YouTube’s HLS live streaming requirements describe transport details including TS segments, segment duration, playlist behaviour, and HTTPS requests. The page also notes that HLS has higher latency than RTMP because it sends segments. Those transport choices may matter to your production, but they do not alter the upload-file sample rate.
A small channel that only needs a straightforward prerecorded loop may not need to choose HLS unless its production workflow calls for it. If HLS is already part of your encoder setup, verify the codec and channel layout in that configuration rather than reusing an RTMP profile. The benefit of keeping a protocol-specific checklist is that you can identify which values belong to the encoder’s outgoing stream and which belong to the media file stored on your computer.
When comparing configurations, write down the protocol first, then the channel layout, then codec and sample rate. This sequence helps prevent a common mistake: seeing “48 kHz” in the upload settings and assuming it is also the correct stereo live-ingest value. For documented HLS stereo ingest, the guidance is 44.1 kHz; for 5.1, it is 48 kHz.
Stereo and 5.1 do not share one sample-rate rule
The relevant sample rate depends on the stage and channel layout. For the recommended upload encoding, YouTube specifies 48 kHz. For live ingest, its advanced guidance specifies 44.1 kHz stereo and 48 kHz 5.1. That is why “use 48 kHz everywhere” is not an accurate summary of the official guidance.
Channel layout should reflect the programme you actually have. A bhajan recording mixed in stereo, a lofi station, or a spoken local-news loop should normally remain stereo unless it was deliberately produced and checked as surround sound. A 5.1 configuration is intended for a real 5.1 programme and a compatible encode path, not as a quality upgrade for two-channel audio.
If you have a 5.1 master, verify the channel order and listen to each channel as well as the downmixed playback. A file can contain six channels yet still be wrong if dialogue is assigned unexpectedly or the encoder interprets the layout differently. For RTMP/RTMPS, remember the documented restriction that 5.1 is supported only with AAC. HLS lists AAC, AC3, and EAC3, but the channel layout and encoder still need to match the actual programme.
If you only have a stereo master, there is usually no benefit in converting it to 5.1 for a live channel. Keep the export simple, use the file-stage recommendation, and configure the live stereo ingest setting for the chosen protocol. This avoids adding channel-mapping variables while leaving the original mix intact.
Check playback before going live
Before a long broadcast, test the entire path with the actual prerecorded file and the intended encoder and protocol. YouTube recommends testing with audio and video similar to the planned stream, checking the preview, and monitoring stream health. These checks are more informative than relying on a preset name or assuming an export setting guarantees a clean live result.
Listen to the preview with headphones or speakers that let you hear the programme clearly. Check that both stereo channels are present, the voice or lead instrument is centred as intended, loud sections do not clip, quiet passages are audible, and the audio stays in sync with the picture. Listen across a loop boundary if the file will repeat. These are practical checks on the path, not a claim that YouTube prescribes this exact listening checklist.
Also check for unintentional silence at the start, an audio track that ends before the video, and a sudden level change between consecutive files. If you use a playlist, compare the end of one item with the beginning of the next. A stable codec and sample rate cannot make two differently mastered files sound consistent by themselves.
Use YouTube’s stream preview and health indicators during the test, and keep the event configuration unchanged after a successful rehearsal unless you test the change again. If a problem appears, isolate the stage: listen to the exported file locally, inspect the encoder output settings, and then check the stream preview. This is more useful than changing several audio settings at once, because it tells you whether the fault is in the source media or the ingest path.
For an always-on stream run from your own computer, a long playback session can also expose interruptions that a short sample misses. If the recurring burden is keeping the computer awake and restarting a dropped broadcast, StreamNeo turns an uploaded video into a YouTube Live stream that can keep running with your computer switched off and is monitored and restarted if it drops. It does not remove the need to prepare a compatible file or check the live preview.
Once the file and channel are ready, decide how you want to operate the broadcast and test that route before relying on it overnight.
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
Should a prerecorded YouTube Live file be 44.1 or 48 kHz?
For a new upload file, YouTube’s recommended encoding settings specify 48 kHz. Its upload troubleshooting reference also lists 44.1 or 48 kHz, so an existing clean 44.1 kHz file is not automatically unusable. Keep that file-stage guidance separate from live ingestion settings.
Is 48 kHz required for stereo RTMP/RTMPS?
YouTube’s live advanced settings specify 44.1 kHz for stereo and 48 kHz for 5.1. Do not treat the upload-file recommendation of 48 kHz as an override to the documented stereo ingest guidance. Check the current official settings for the protocol you use.
Is AAC-LC the only codec I can use?
No. YouTube lists AAC-LC, Opus, and Eclipsa Audio for recommended upload encoding; its live-ingest codec lists differ by protocol. AAC-LC is a practical choice for conventional stereo, but confirm the encoder output against the current RTMP/RTMPS or HLS documentation.
Should I convert stereo audio to 5.1?
No, not merely to use the 5.1 sample-rate setting. Keep a stereo programme in stereo unless you have a genuine surround mix and a compatible encode path. Check channel mapping and preview playback before the event.