If you are sending a prerecorded video to YouTube Live through an encoder at 1440p and 30 fps, YouTube recommends 21 Mbps for H.264 or 15 Mbps for AV1 or H.265. Those figures describe the incoming live video feed, and you should use the recommendation for the codec your encoder actually sends.
A normal upload of a finished video is a different workflow: YouTube recommends 16 Mbps for SDR 1440p at 24, 25 or 30 fps. That upload figure is not the recommended setting for a live encoder, even when the pictures in the file were recorded in advance.
First decide what “pre-recorded” means
People use “pre-recorded” to describe two different things. You might mean uploading a finished video to YouTube, where viewers watch it on demand. Or you might mean feeding a video file to an encoder that broadcasts it as a live programme. The pixels can come from the same file, but YouTube receives them through different processes.
For a live broadcast, the encoder reads the file and sends a continuous video signal to YouTube’s live ingest. You schedule or start a live event, provide the stream key to your encoder, and send the stream while it is running. A recording made earlier does not turn this into an ordinary upload; while it is being sent through the live encoder, it is an incoming live feed.
That distinction answers the search question, “What bitrate should I use to stream a prerecorded video on YouTube Live at 1440p 30 fps?” Choose the live recommendation by outgoing codec: 21 Mbps for H.264, or 15 Mbps for AV1/H.265. The live table is organised around codec, resolution and frame rate, not whether the source images were recorded earlier. YouTube does not give prerecorded content a separate live bitrate allowance.
If instead you are preparing a video file for an ordinary upload, follow the upload encoding guidance. The difference matters for a devotional loop, a study playlist, a music programme or a local information channel: choosing “live” as a way of presenting a file does not make the live encoder use the upload recommendation. You can read about planning material for a persistent channel in this guide to changing content on a 24/7 YouTube stream, but first settle which delivery path you are using.
Choose the codec your encoder sends
The incoming codec determines which recommended live bitrate applies. YouTube’s live settings documentation lists H.264, H.265 (HEVC) and AV1 for RTMP/RTMPS ingestion. For 1440p at 30 fps, the recommendation is 21 Mbps for H.264 and 15 Mbps for either AV1 or H.265. Do not pick a bitrate first and assume that the encoder will use the matching codec: check its output settings.
H.264 is often the most straightforward choice when compatibility with existing encoder software or a familiar workflow matters. AV1 and H.265 can be attractive when the encoder supports them and your setup can produce a stable stream using that codec. The table’s lower recommended figure for those codecs is YouTube’s published configuration guidance; it is not a guarantee that any particular computer, application or network will handle them well.
If you do not know what your encoder sends, inspect the video output or streaming profile before going live. Some applications let you select the codec directly, while others hide it in an advanced output panel or choose from a preset. Make sure the displayed codec describes the encoded live output, rather than the codec of the source file. A source file can be H.265 while the encoder sends H.264, for example; in that case use the H.264 live row.
For a channel built around long-running video, stable playback matters more than using a codec merely because it appears newer. A practical choice is the codec your encoder can produce consistently at the required resolution and frame rate, then a test to confirm YouTube receives it correctly. If the workflow is a playlist of varied clips, this guide to streaming mixed video resolutions covers a related source-file concern; it does not change the bitrate row for a given incoming resolution and codec.
Set the 1440p30 live-feed bitrate
Use this comparison for the outgoing video feed to YouTube Live:
| Workflow and outgoing video | 1440p / 30 fps guidance | What the figure applies to |
|---|---|---|
| YouTube Live, H.264 | Recommended 21 Mbps; listed minimum 7 Mbps | Video bitrate sent by the live encoder |
| YouTube Live, AV1 or H.265 | Recommended 15 Mbps; listed minimum 5 Mbps | Video bitrate sent by the live encoder |
| Ordinary SDR video upload, 24/25/30 fps | Recommended 16 Mbps | Encoding guidance for the finished file upload |
For an H.264 live output, enter 21 Mbps as the video bitrate target. For AV1 or H.265, enter 15 Mbps. Keep the resolution at 1440p and the frame rate at 30 fps so that the selected row matches the signal being sent. The recommendation is for video, not a combined figure for video and audio.
YouTube also lists CBR, or constant bitrate, for the documented RTMP/RTMPS settings. CBR is a sensible place to begin because it keeps the outgoing video rate near the configured target rather than varying widely as picture complexity changes. A busy visual scene may still be harder to encode cleanly than a mostly static frame; the bitrate is a setting for the feed, not a promise that every scene will look identical.
Keep audio settings separate. YouTube lists AAC or MP3 for audio in the relevant setup, with 5.1 audio over RTMP/RTMPS supported only with AAC. If your programme is stereo devotional music, a study ambience or a news loop with speech, choose a suitable audio format and test the balance as part of the whole stream. Do not add the audio rate to the video number and then enter that sum as the video bitrate.
YouTube’s current live encoder settings documentation is the primary reference for the live codec and ingest setup. Check it again when configuring a real channel, since YouTube’s guidance may change; the 21 Mbps and 15 Mbps values here are YouTube’s stated 1440p30 incoming-feed recommendations, not an independent benchmark.
Minimums are not recommendations
The same live table gives lower minimums: 7 Mbps for H.264 and 5 Mbps for AV1 or H.265 at 1440p30. A minimum and a recommended target answer different questions. The minimum is a lower bound in the published table; it is not the rate YouTube recommends you deliberately aim for when setting up this resolution and frame rate.
If your connection cannot sustain the recommended rate reliably, sending a stream that repeatedly falls below its configured target is not a useful solution. A lower bitrate can sometimes keep a feed going, but it may also reduce picture detail, especially in footage with movement, texture or fine patterns. Consider lowering the stream resolution or frame rate to a level your connection and encoder can maintain, then select the corresponding guidance for that output. Do not treat the minimum as a universal fallback that ensures acceptable quality.
A 1440p source file also does not compel you to send 1440p live. If the source is mainly a static image, a text slide or a slow-moving ambience scene, you may decide that a lower outgoing resolution is adequate. If there is moving text, detailed artwork or a camera feed, the trade-off may be different. The relevant goal is a stable, legible live output, not matching the source file’s nominal resolution at any cost.
The viewer’s eventual playback quality is another matter. YouTube says it creates multiple output formats for different devices and network conditions. That means your encoder’s incoming bitrate is not a promise that each viewer will receive a 1440p stream at the same rate. It is your contribution to the ingest; YouTube then processes the live feed for playback. For long-form planning around a loop, see how to make a YouTube Live piano loop seamless; seamless source material is useful, but it does not change the ingest recommendation.
Keep live ingest separate from regular uploads
The ordinary upload figure is easy to confuse with the live one because both refer to 1440p at common frame rates. For SDR uploads at 24, 25 or 30 fps, YouTube’s upload guidance recommends 16 Mbps. For a 1440p30 live feed, the recommendation instead depends on outgoing codec: 21 Mbps for H.264 or 15 Mbps for AV1/H.265.
These are not competing answers to one universal bitrate question. Each applies to a different delivery workflow. A finished file uploaded normally is encoded and delivered as a video upload. A file played through an encoder into a live event is processed as live ingest. Using 16 Mbps simply because the source is a 1440p30 file does not follow the live table when the encoder sends H.264.
The YouTube upload encoding settings provide the upload recommendation and should be consulted for that path. Use that page for a finished-file upload and the live encoder page for an incoming stream. Do not infer that matching resolution and frame rate make the two rates interchangeable.
For a 24/7 channel, there can be both workflows in one production routine: you might upload a finished programme for on-demand viewing, and separately send a loop through YouTube Live. Write down which output each setting belongs to. That small note can prevent a later edit from carrying an upload preset into a live encoder, or a live ingest value into a file export. For a playlist-driven channel, this article on scheduling a YouTube Live playlist for exam-preparation music is relevant to the programme flow, while bitrate remains tied to the outgoing live encoder configuration.
Test the whole outgoing setup
Before relying on a bitrate setting overnight, test the stream with a representative section of the programme. Use material with similar movement, text, audio and transitions to what viewers will see. A motionless logo is not a good test for a sequence with scrolling lyrics or changing scenes, just as a silent preview does not reveal an audio configuration problem.
YouTube advises checking the upload bitrate your connection can sustain and choosing a stream quality it can reliably carry. Treat that as a practical constraint. The line’s advertised speed is not by itself confirmation that the upload path will remain steady while other devices, backups or household use compete for it. Run a test during conditions similar to the intended broadcast, and watch the stream health indications in YouTube Studio.
For a documented RTMP/RTMPS setup, YouTube recommends RTMPS, lists CBR and recommends a two-second keyframe frequency, with four seconds as the maximum. Match those supporting settings to the current YouTube guidance and to the encoder’s available controls. If you change codec, resolution, frame rate or bitrate, test again rather than assuming the previous test still represents the output.
Inspect both the encoder and YouTube’s received-stream status. An encoder may report that it is sending, while YouTube reports a health warning or an unexpected incoming format. Check the selected stream key, ingest protocol, codec and configured rate before changing several variables at once. The practical sequence in this guide to verifying a YouTube stream-health warning after an ingest change can help you distinguish a configuration issue from a wider connection problem.
If you are keeping a live channel running while your own computer is off, the operational burden includes more than selecting a bitrate: the stream still needs a ready source file and a method of recovering if the broadcast drops. StreamNeo removes the repeated need to leave your own computer running by turning an uploaded video into a YouTube live stream that can be monitored and restarted if it drops; it does not change the codec-specific bitrate guidance or replace checking YouTube’s current stream-health information.
Make the setting part of a repeatable checklist
A useful channel note should record the outgoing codec, resolution, frame rate, video bitrate, rate-control mode and keyframe interval. Include which workflow the preset belongs to: “YouTube Live ingest” or “ordinary upload”. If you operate several channels or hand the work to another person, this is more reliable than a label such as “1440p settings”, which leaves the most important distinction unstated.
For example, a live preset might read: 1440p, 30 fps, H.264, 21 Mbps video, CBR, two-second keyframes, RTMPS. If the encoder sends AV1 or H.265 instead, record 15 Mbps as the recommended video target for that live output. These are examples of applying YouTube’s settings, not guarantees of picture quality or stream continuity; connection capacity and encoder behaviour still need testing.
Keep a separate export preset for a normal SDR upload if you produce one. Its 16 Mbps recommendation at 1440p and 24, 25 or 30 fps comes from YouTube’s upload guidance. Keeping the two profiles separate makes it less likely that an operator will choose a number based only on resolution and overlook the delivery path.
After a successful test, avoid needless changes immediately before a long programme. If you must alter the source, encoder, codec or network path, make another test and review the received stream. For channels that use repeated content, a clear operating procedure also makes it easier to spot whether a visual or schedule change affected the stream rather than the ingest setting.
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 1440p30 prerecorded video on YouTube Live?
For a prerecorded file sent through a live encoder, use YouTube’s incoming live-feed recommendation for the codec being sent: 21 Mbps for H.264 or 15 Mbps for AV1/H.265. These are video bitrate recommendations, not a universal quality guarantee.
Is 16 Mbps the YouTube Live recommendation for 1440p30?
No. YouTube recommends 16 Mbps for SDR 1440p uploads at 24, 25 or 30 fps. For 1440p30 live ingest, use 21 Mbps for H.264 or 15 Mbps for AV1/H.265.
Can I use the minimum bitrate instead?
YouTube’s table lists minimums of 7 Mbps for H.264 and 5 Mbps for AV1/H.265 at 1440p30, below the recommendations. A minimum is not the recommended target, and a lower setting may reduce detail or fail to provide the result you need. Test a quality your connection can sustain reliably.
Does the source file’s codec decide which bitrate to use?
Use the codec the encoder sends to YouTube, not necessarily the codec used to store the source file. An encoder can decode one format and send another, so check its outgoing stream settings before selecting the matching live bitrate.