If you play a finished video file into a YouTube Live event, YouTube treats the outgoing feed as live ingest: use the applicable live bitrate guidance and constant bitrate (CBR), not a CRF value presented as YouTube’s recommendation. If you are encoding a file for an ordinary YouTube upload, use YouTube’s separate upload guidance instead.
The right live target depends on codec, resolution and frame rate. There is no single bitrate for every pre-recorded stream, and YouTube’s live encoder guidance does not specify a CRF setting. Identify which job you are doing first, then use the matching official table row.
What “pre-recorded YouTube Live” means
The phrase can describe two different jobs. In one, you have a finished video and send it continuously to a YouTube Live event. Viewers receive a live broadcast, even though the pictures and sound were prepared earlier. The file is a source for a live production; the output that reaches YouTube is a live feed.
In the other job, you encode a video file and upload it to YouTube in the usual way. It may later be associated with a scheduled premiere, a channel programme, or a live-streaming plan, but the encoding step is still an upload. The fact that you intend to use the content around a live channel does not turn upload guidance into live-ingest guidance.
That distinction settles the CRF question. For a finished file played into a live event, follow YouTube’s current live encoder settings for the outgoing feed. For a file being uploaded, consult the upload recommendations. A creator might do both with the same programme: create a good upload master, then prepare or configure a separate live output. Make a decision for each stage rather than carrying one setting across by habit.
This matters whether you run a devotional loop, a study channel, a local information channel or a small shop’s continuous playlist. The content’s subject does not change the encoder guidance. What matters is how the signal reaches YouTube.
Live ingest is different from video upload
A live encoder sends a stream to YouTube while an event is under way. The connection has to deliver a steady feed, and the recommended bitrate is stated in the live guidance according to technical characteristics such as codec, resolution and frame rate. YouTube’s live page says the bitrate encoding should be CBR. That guidance applies when a pre-rendered programme is being played out as a live feed, just as it does when a camera or software scene is the source.
An uploaded file is different: YouTube receives a completed asset, not a real-time feed. Its upload encoding page recommends variable bitrate and gives reference figures by resolution and frame rate. Those values are useful when preparing a file for upload; they are not substitutes for the Live table when you are sending a live event.
| Job being encoded | Guidance to use | Practical decision |
|---|---|---|
| Finished programme played into a YouTube Live event | YouTube’s live encoder settings: CBR and a bitrate selected by codec, resolution and frame rate | Match the outgoing feed to the applicable Live row |
| File prepared for an ordinary YouTube upload | YouTube’s upload encoding settings: variable bitrate with separate references | Use the upload page for that file, not the Live ingest table |
The same video can pass through both workflows. For example, you might encode a file for an ordinary upload, then later send that programme from a playout tool to a live event. In the second step, the tool’s outgoing stream has live settings of its own. If you are unsure which setting a guide is discussing, ask whether it describes a file being uploaded or a signal being sent during the event.
If your setup includes a playlist or automation, encoding is only one part of keeping the channel continuous. The practical workflow for a rotating programme is covered in automating a rotating video playlist for YouTube Live. Keep the playlist question separate from the bitrate decision: a reliable hand-off between files does not change the live ingest recommendation.
Why CRF is not YouTube’s live recommendation
CRF is a quality-oriented rate-control mode used by some encoders. Rather than setting one fixed target rate for every moment, an encoder adjusts output bitrate in response to the material and the requested quality level. A quiet still image and a detailed moving scene can therefore produce different data rates. That behaviour can be useful when making a file, particularly where you want an encoder to balance quality and file size without assigning a fixed bitrate in advance.
CBR takes a different approach. It aims to maintain a constant bitrate for the stream, which aligns with YouTube’s stated live encoder recommendation. For a live event, choose the target from YouTube’s Live table for the selected codec, resolution and frame rate, then configure the encoder to use CBR. CRF may exist as an encoder option, but its presence in a software menu does not make it YouTube’s recommended live setting.
YouTube’s live guidance does not name a CRF number, nor does it provide a general conversion from a CRF value to the right Live bitrate. A CRF number can yield different bitrates as content and encoder settings change. It is therefore not sound to claim that a particular CRF setting is the correct YouTube Live value, or to infer a guaranteed target rate from it.
That does not mean CRF is inherently wrong for every stage of a production. You could make a source file using a quality-based mode and then have a live encoder send a CBR feed to YouTube. Those are separate encoding decisions. If your playout software reads the file and encodes the outgoing feed, check the output settings rather than assuming the file’s original encoding mode carries through to the stream.
The distinction is useful when you compare encoder screens or follow a tutorial. A setting labelled “quality” or “CRF” may control a file-generation stage; a “CBR” mode and bitrate field may control the live output. Confirm the target being encoded before changing a value. For a broader example of a YouTube Live setting with a specific timing recommendation, see why YouTube recommends a two-second keyframe interval.
Choose the applicable Live bitrate row
Start with the output that YouTube will receive. Select the codec, resolution and frame rate you actually intend to send; then locate the matching row and codec column in YouTube’s live encoder settings, bitrates and resolutions. The figures below are YouTube’s recommended H.264 live ingest bitrates in its current guidance, accessed 3 October 2026. They are not universal targets for other codecs or output formats.
| H.264 live output | YouTube recommended bitrate |
|---|---|
| 720p at 30 fps | 8 Mbps |
| 720p at 60 fps | 8 Mbps |
| 1080p at 30 fps | 14 Mbps |
| 1080p at 60 fps | 17 Mbps |
| 1440p at 30 fps | 21 Mbps |
| 1440p at 60 fps | 34 Mbps |
| 2160p at 30 fps | 42 Mbps |
| 2160p at 60 fps | 50 Mbps |
These rows are useful only when the output is H.264 and the resolution and frame rate match. For example, if you are sending a 1080p30 H.264 feed, the listed recommendation is 14 Mbps. If you are sending 1080p60 H.264, it is 17 Mbps. Do not choose between those values based on whether the video is a bhajan, a still study backdrop or a news loop; the relevant distinction is the outgoing technical format.
YouTube publishes separate minimum and recommended columns for AV1 and H.265 (HEVC), as well as H.264. Its 1080p30 recommendation, for example, differs by codec: 10 Mbps for AV1 or H.265 and 14 Mbps for H.264. At 1080p60, the listed recommendations are 12 Mbps for AV1 or H.265 and 17 Mbps for H.264. If you use one of those codecs, consult its own column rather than applying the H.264 table above.
A table entry is a recommendation, not a promise that a stream will look identical in every scene or remain stable on every connection. If the codec or frame rate is not settled, decide those first. Avoid selecting a number from a row that looks close enough: a different frame rate, resolution or codec means you should recheck the official table. YouTube can update guidance, so verify the current page before an important event.
Set CBR for the live feed
Once you have selected the applicable Live row, set the outgoing encoder to CBR and enter that row’s target bitrate. In a programme that reads a prerecorded file, this means configuring the live output path, not merely checking how the source file was compressed. If your software has separate settings for recording, proxy generation and streaming, make sure you are editing the stream output.
YouTube’s live encoder page also recommends a two-second keyframe frequency and says not to exceed four seconds. Use the recommended two seconds unless your production has a specific reason to configure otherwise, and confirm that the encoder’s keyframe interval is expressed in the form its interface expects. Keyframes are another live output setting; they are not a replacement for matching the bitrate row.
Audio deserves a check alongside video. YouTube’s live encoder guidance lists AAC or MP3 audio. If your programme is mostly music or speech, listen to the encoded output at the start and after a file transition. A correct video bitrate cannot fix an audio track that is missing, clipping or silent between playlist items.
For a 24/7 channel, keep a record of the output profile that worked: codec, resolution, frame rate, CBR target and keyframe setting. That makes it easier to restore a known configuration after a software update or a change in programme material. It is also useful when more than one person manages a channel and an overnight operator needs to identify the settings quickly.
Use separate guidance for upload files
If you are preparing a file for ordinary upload, use YouTube’s recommended upload encoding settings, which recommend variable bitrate and give reference bitrates by resolution and frame rate. As accessed 3 October 2026, YouTube’s SDR H.264 references include 8 Mbps for 1080p at standard frame rates of 24, 25 or 30 fps, and 12 Mbps at high frame rates of 48, 50 or 60 fps. For 2160p, the listed references are 35–45 Mbps at standard frame rates and 53–68 Mbps at high frame rates. These are upload figures, not targets for a live feed.
The difference is easy to miss because both tasks may begin with the same rendered programme, and both involve an encoder. For an upload, the finished file is the deliverable. For Live, the encoded output is a continuing signal. Use the method and values for that deliverable rather than assuming “YouTube bitrate” is one universal setting.
You might choose to create a high-quality master file, upload it, and later play it into a live stream. In that case, the upload’s variable-bitrate settings describe how the master was made. The CBR target from the Live table describes the outgoing stream. The source file’s average bitrate does not itself tell you whether the live feed is configured correctly.
If an upload appears softer than expected, investigate the file’s export and YouTube’s processing separately from the later Live encoder profile. Likewise, if a live event drops frames or reports poor health, changing the source file’s CRF value may not address the network or outgoing stream configuration. Diagnose the stage that is failing before re-encoding the whole programme.
Test stream output and adjust carefully
Before relying on a profile overnight, test it with representative content. Include the busiest visual section, a section with little motion, speech or music as applicable, and any transition where one file gives way to another. A quiet title card can conceal a problem that only appears during scrolling text, moving footage or a change in audio level.
Check YouTube’s stream health while testing, and confirm that the selected resolution, frame rate and codec are actually being sent. Review both picture and sound on a viewer device. A local preview can confirm what the encoder is producing, but it does not confirm the entire path to YouTube. For long-running channels, leave enough time to spot a playlist transition or audio gap rather than stopping the test at the first successful connection.
Network capacity is part of the choice. YouTube’s streaming tips say the total streaming bitrate must fit the available upload bandwidth and recommend leaving 20% headroom. Treat this as capacity for the full outgoing stream, including audio, rather than as an invitation to raise the video target above YouTube’s applicable recommendation. If other people or devices share the connection, account for that real use as well.
If health warnings appear, check the basics in order: verify that the output profile matches the selected Live row; confirm the encoder is using CBR; check the actual upload capacity and whether it fluctuates; then inspect the software’s logs or health messages. Avoid changing resolution, frame rate, codec and bitrate all at once. If a change helps, you want to know which change made the output more stable.
A stream source can be simple, but continuity still needs attention. If your main concern is keeping a pre-recorded devotional programme running without leaving a computer on, StreamNeo removes the need to keep your own computer switched on for that broadcast; the encoder decision still needs to match YouTube’s current Live guidance. For a local setup, the practical trade-offs of using a spare machine are covered in streaming devotional songs from a spare PC.
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 I use CRF or CBR for a pre-recorded YouTube Live stream?
For the feed sent to a YouTube Live event, use CBR and the target bitrate from the Live row that matches your codec, resolution and frame rate. YouTube’s live guidance does not specify a CRF value. CRF may be relevant when making a source file, but that is a different encoding stage.
What bitrate should I use for a prerecorded 1080p YouTube Live stream?
There is no single answer without the codec and frame rate. In YouTube’s current H.264 Live guidance accessed 3 October 2026, 1080p30 is listed at 14 Mbps and 1080p60 at 17 Mbps; other codecs have their own columns. Check the current table before setting the encoder.
Can I use the YouTube upload bitrate for a live event?
No: upload recommendations apply to a completed file, while Live guidance applies to the outgoing feed. YouTube’s upload page recommends variable bitrate, whereas its Live encoder guidance specifies CBR. If you do both, configure each stage according to its own guidance.
What else should I check before leaving a stream running?
Confirm the keyframe interval, audio output, stream health and upload bandwidth as well as the target bitrate. YouTube recommends a two-second keyframe frequency, not exceeding four seconds, and recommends leaving 20% bandwidth headroom. Test a representative section and a file transition before depending on the setup.