If you are sending a prerecorded video to YouTube as a live stream, choose the bitrate from the live encoder’s outgoing settings. YouTube does not provide a separate bitrate profile for prerecorded content.
For the common 1080p setup, YouTube recommends 14 Mbps for H.264 at 30 fps and 17 Mbps for H.264 at 60 fps. With AV1 or H.265, the recommendations are 10 Mbps at 30 fps and 12 Mbps at 60 fps. The file’s own bitrate does not decide which live ingest setting you should use.
How YouTube’s live bitrate recommendations apply
A prerecorded file still has to reach YouTube as a live encoder feed. The encoder reads or plays the file, creates an outgoing stream, and sends that stream to YouTube using the selected codec, resolution, frame rate and bitrate. YouTube’s published table applies to that outgoing feed.
This distinction matters because a file can have very different properties from the stream you send. For example, you may have a 1080p video encoded at 8 Mbps, then send it through an encoder as 1080p H.264 at 30 fps using a 14 Mbps constant bitrate. In that case, 14 Mbps is the live ingest setting. The source file’s 8 Mbps is not a replacement for it.
The reverse can also happen. A source file may be encoded at a high bitrate, but your encoder may be configured to send a lower-bitrate live feed. YouTube receives the encoder output, not the file’s original encoding settings.
YouTube also processes the incoming live stream into different playback formats for viewers. That is why the important decision at your end is the quality and stability of the feed going into YouTube. It is not necessary to find a special “prerecorded video” row, because YouTube’s live encoder guidance does not define one.
The official YouTube live encoder settings and bitrates page is the right reference when the available options in your encoder change. Check the current page before a long broadcast, because software menus and YouTube guidance can change.
File bitrate vs. encoder output bitrate
There are two separate bitrate questions in this workflow.
The first is the file bitrate. This describes how much data was used to store each second of the prerecorded video. It affects the detail already present in the file. If the file was heavily compressed, increasing the live output bitrate cannot restore detail that was removed during the original encoding.
The second is the encoder output bitrate. This is the rate at which your live encoder sends the video to YouTube. It affects the size and consistency of the live ingest feed. This is the bitrate you match to YouTube’s live recommendation table.
Consider a devotional channel with a loop of bhajans and still artwork. The original file might be relatively easy to play because its images change slowly. You could still choose 1080p30 H.264 and set the outgoing feed to YouTube’s recommended 14 Mbps. The source file does not need to have been created at exactly 14 Mbps for that live setting to apply.
Now consider a local news loop with scrolling text, cuts between clips and moving footage. It may need more careful testing because movement and fine text reveal compression problems more quickly. The answer remains the same: choose the live row according to the encoder output, then check whether the connection and the resulting picture are stable.
Do not treat the source bitrate as a target to copy into the encoder automatically. If your software has a separate input or playback quality setting, that controls how the file is decoded or processed. The YouTube bitrate field controls the outgoing feed.
For settings terminology, the explanation in OBS CBR or VBR for YouTube Live Streaming is useful. YouTube’s live guidance specifies constant bitrate encoding, commonly shown as CBR. A variable bitrate source file does not mean that the live output should also be variable bitrate.
Choose the row for codec, resolution and frame rate
Select a row using the three properties of what the encoder is sending:
- Codec: H.264, AV1 or H.265, if your encoder and YouTube workflow support it.
- Resolution: 360p, 480p, 720p, 1080p, 1440p or 2160p.
- Frame rate: 30 fps or 60 fps, where the chosen resolution supports it.
Then use the recommended bitrate as the starting point, provided your upload connection can sustain the total stream. If the encoder output is 1080p30 H.264, use the H.264 1080p30 row. If it is 1080p60 H.264, use the 1080p60 row. The fact that the content came from a file does not alter the row.
| Ingestion resolution and frame rate | AV1 or H.265 minimum | AV1 or H.265 recommended | H.264 minimum | H.264 recommended |
|---|---|---|---|---|
| 2160p / 4K at 60 fps | 10 Mbps | 35 Mbps | 14 Mbps | 50 Mbps |
| 2160p / 4K at 30 fps | 8 Mbps | 30 Mbps | 11 Mbps | 42 Mbps |
| 1440p at 60 fps | 6 Mbps | 24 Mbps | 8 Mbps | 34 Mbps |
| 1440p at 30 fps | 5 Mbps | 15 Mbps | 7 Mbps | 21 Mbps |
| 1080p at 60 fps | 4 Mbps | 12 Mbps | 6 Mbps | 17 Mbps |
| 1080p at 30 fps | 4 Mbps | 10 Mbps | 5 Mbps | 14 Mbps |
| 720p at 60 fps | 2 Mbps | 6 Mbps | 3 Mbps | 8 Mbps |
| 720p at 30 fps | 2 Mbps | 6 Mbps | 3 Mbps | 8 Mbps |
| 480p at 30 fps | 0.3 Mbps | 3 Mbps | 0.4 Mbps | 4 Mbps |
| 360p at 30 fps | 0.3 Mbps | 3 Mbps | 0.4 Mbps | 4 Mbps |
The table gives YouTube’s minimum and recommended ingestion values from its live encoder guidance. It is not a table of source-file requirements. A file may be 720p, while the encoder scales it to 1080p; in that case, the outgoing resolution is the value to use when selecting the live row. Scaling does not create extra detail, but it does change the format of the feed being sent.
Frame rate should also describe the output. If a 60 fps file is sent as a 30 fps live stream, use the 30 fps row. If the encoder sends 60 fps, use the 60 fps row. Avoid selecting 60 fps simply because the source file has 60 fps if your connection or hardware cannot maintain that output.
1080p H.264 recommendations
H.264 remains a practical choice for many prerecorded YouTube channels because it is widely supported by encoders and hardware. For 1080p H.264, YouTube’s recommended live ingest bitrate is:
- 1080p at 30 fps: 14 Mbps
- 1080p at 60 fps: 17 Mbps
The minimum values listed by YouTube are 5 Mbps for 1080p30 and 6 Mbps for 1080p60. Minimum is not the same as the recommended starting point. If your connection comfortably supports the recommended value, use it. If the connection cannot sustain it, lowering the resolution or frame rate may be more dependable than selecting a high-quality setting that repeatedly loses connection.
For a lofi station with slow animation, 1080p30 may be sufficient if the source and output are both 30 fps. For a study channel showing a presenter, slides and handwriting, 1080p30 is often easier to operate than 1080p60. A 60 fps output can be appropriate when the original programme contains fast movement or when smooth motion is an important part of the viewing experience, but it also raises the recommended bitrate.
Set the encoder to CBR rather than copying the source file’s encoding mode. YouTube lists a 2-second keyframe interval and says not to exceed 4 seconds. These settings affect how the live feed is structured for YouTube’s ingest and playback systems, so check that the encoder has not silently selected a different interval.
Audio is a separate part of the outgoing stream. YouTube lists AAC and MP3 among the supported audio codecs. A video can meet its selected video bitrate while still having an audio routing or level problem, so include representative audio in your test. This is particularly important for devotional music, lectures and ambience channels where the programme is mostly sound.
If you are building a loop rather than a one-off broadcast, first make the loop reliable for a shorter test. The guidance in Uploading Once vs Streaming Forever: How Cloud Loops Handle Your File is relevant to the operational difference between preparing a file and keeping a live feed running. The bitrate choice still belongs to the live output, whether the encoder is running on your computer or the workflow is managed remotely.
1080p AV1 and H.265 recommendations
For 1080p output, YouTube’s recommended values for AV1 or H.265 are lower than the corresponding H.264 recommendations:
- 1080p at 30 fps: 10 Mbps
- 1080p at 60 fps: 12 Mbps
The listed minimum is 4 Mbps for both 1080p30 and 1080p60. The codec matters because YouTube’s table provides different bitrate guidance for H.264 and for AV1 or H.265. Do not select the AV1 or H.265 value while the encoder is actually sending H.264.
The codec choice also depends on what your chosen encoder supports, what your hardware can process continuously and what YouTube accepts in the relevant live workflow. YouTube lists H.264, H.265 and AV1 as video codecs in its live encoder guidance, but a menu option appearing in one piece of software does not by itself confirm that every workflow will behave identically. Test the exact configuration you plan to use.
For example, if a prerecorded 1080p30 file is being sent as H.265, start with the 10 Mbps recommended row. If the same file is sent as H.264, start with 14 Mbps. The source file has not changed, but the live encoder output has changed, so the appropriate recommendation changes too.
Do not assume that the codec with the lower recommended bitrate is automatically the better choice. A useful setting is one your encoder can maintain, your connection can carry and your workflow can monitor. A less familiar codec may introduce additional testing requirements, while H.264 may be simpler where broad compatibility matters.
Upload capacity and the 24/7 trade-off
The bitrate field is only one part of a reliable broadcast. Your upload connection must carry the complete outgoing stream without repeated interruptions. YouTube’s streaming tips state that the total bitrate being streamed cannot exceed the available upload bandwidth and recommend leaving 20% headroom.
That headroom is not a promise that every connection will remain stable. It is room between the selected stream rate and the connection’s usable upload capacity. Wi-Fi variation, other devices, background uploads and changes in the connection can reduce what is available to the encoder.
Suppose your selected video output is 14 Mbps. Do not assess the connection only by asking whether a speed test briefly displayed 14 Mbps upload. You need capacity above the stream rate, with room for the connection to vary. If the connection is shared with other users or services, the practical margin may be smaller than the result shown by a single test.
For an always-on channel, reliability is usually more useful than choosing the largest available resolution. A 720p stream that remains connected can be more suitable for a devotional channel or local information loop than a 4K stream that drops when the connection changes. YouTube’s table lets you step down by resolution or frame rate when the available upload cannot support the chosen row.
Before putting the stream in front of viewers, run a test with the same type of audio, movement and transitions as the real programme. YouTube specifically advises testing before starting the live stream. A still image with quiet audio may not expose the same problems as a news loop with scrolling text or a music video with frequent cuts.
If your channel is based in India and the connection is shared at home or in a small office, test during the hours when the broadcast will actually run. The aim is not to produce a perfect speed-test screenshot. It is to find a setting that remains steady when the surrounding conditions are ordinary.
Send the feed and verify stream health
In YouTube Live Control Room, create or select the stream and copy the stream key into the encoder. YouTube describes the key as the password-like value that tells the encoder where to send its feed. Treat it as sensitive. If you need to replace it, the guide on how to reset or replace a YouTube stream key explains the operational concern without requiring you to rebuild every other setting.
Use RTMPS when your encoder supports it and the workflow is configured correctly. YouTube describes RTMPS as RTMP over TLS/SSL, adding encryption to the connection between the encoder and YouTube. The relevant YouTube RTMPS setup guidance should take priority over an old tutorial or a copied server address.
After the feed starts, look at the stream health messages in Live Control Room. Check whether YouTube is receiving the stream, whether the incoming bitrate is behaving as expected and whether warnings point to dropped frames, connection problems or an invalid setting. A selected bitrate in the encoder is not proof that the same feed is reaching YouTube consistently.
Watch the actual picture as well as the status message. Look for blockiness in moving areas, unreadable small text, audio interruptions, frozen images and changes in sync. For a bhajan channel, listen for gaps at the beginning and end of a loop. For a study channel, check that speech and slides remain aligned. For local news, inspect ticker text and scene changes.
If the stream health warning points to an unstable connection, first remove competing upload activity and check the physical connection. If that does not solve it, lower the outgoing resolution or frame rate and select the corresponding table row. Do not simply raise the bitrate to fix a connection that cannot sustain the existing feed.
A cloud workflow can remove the need to leave your personal computer running all night, but it does not remove the need to choose and verify the outgoing settings. For a file-and-key workflow where the repeated pain is overnight restarts and monitoring, StreamNeo turns the uploaded video into a YouTube live stream that can continue while your computer is switched off, with automatic monitoring and restart if the broadcast drops.
Keep a record of the working configuration: outgoing codec, resolution, frame rate, bitrate, keyframe interval, audio setting and the connection used during the test. This makes it easier to restore the channel after a software update or a stream-key change. It also prevents you from confusing the file’s properties with the live feed’s settings the next time you prepare a loop.
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 bitrate should I use for a prerecorded 1080p video on YouTube?
Choose the row for the live encoder output, not the file. YouTube recommends 14 Mbps for H.264 at 1080p30 and 17 Mbps for H.264 at 1080p60; for AV1 or H.265, the recommendations are 10 Mbps and 12 Mbps respectively.
Does the source file need to have the same bitrate as the live stream?
No. The source file bitrate describes how the file was encoded, while the encoder output bitrate describes what is sent to YouTube. The file bitrate does not determine the recommended live ingest bitrate.
Is 60 fps better for a 24/7 channel?
Not automatically. Use 60 fps when the programme and workflow benefit from smoother motion and your connection can sustain the corresponding recommendation. For many devotional, ambience and study loops, 30 fps may be a simpler and more dependable choice.
What should I do if YouTube reports an unstable stream?
Check the connection, competing uploads and stream-health messages first. Leave the recommended upload headroom, test with representative audio and movement, and lower the outgoing resolution or frame rate if the connection cannot reliably carry the selected feed.