If you are playing a prerecorded programme into YouTube Live, use YouTube’s live ingestion settings, not its recommendations for ordinary video uploads. For 1080p30, YouTube recommends 14 Mbps with H.264 or 10 Mbps with AV1/H.265; for 1080p60, it recommends 17 Mbps with H.264 or 12 Mbps with AV1/H.265.
Those are recommended video bitrates, not universal minimum connection speeds. The listed live minimums are lower, and your total outgoing connection also needs room for audio and other traffic. The right setting depends on whether you are broadcasting live or uploading a regular video, which codec you send, and whether your programme is 30 or 60 frames per second.
First identify the workflow: live ingest or upload
“Pre-recorded stream” can mean two different things. You might play a finished file through an encoder and send it continuously to YouTube Live; that is a live broadcast, even though the programme was recorded earlier. Or you might upload the file to your channel as a normal video. Those workflows have separate YouTube recommendations.
For a live broadcast, YouTube receives an encoded stream from your software or hardware encoder. Set the encoder’s output resolution, frame rate, codec and bitrate for the live ingest. For an ordinary upload, YouTube receives a file and processes it for playback; upload encoding advice applies to that file instead. A figure recommended for one workflow should not be carried over to the other.
This distinction matters for a 24/7 channel as much as for a one-off premiere. If OBS is playing a loop and sending it to the live event, use the live table below. The practical steps for getting a loop into the encoder are covered in how to loop videos in a 24/7 YouTube livestream; the bitrate choice still comes from YouTube’s live settings.
YouTube’s official live encoder settings and bitrate table is the primary reference for the ingest figures. Check that page again before a production change, as platform guidance can be revised. This article distinguishes the table’s recommended rates from its minimums rather than treating either as a promise of a particular viewer experience.
Choose 1080p30 or 1080p60 deliberately
A 1080p label is not enough to choose a bitrate. The frame rate changes the live recommendation, and motion in your programme may help determine which frame rate makes sense. A static devotional image with slow transitions may not gain much from 60 fps. A fast-moving product demonstration or footage with frequent camera movement may be better suited to a 60 fps output if the source supports it.
Start with the source file. If it is 1080p30, keeping the encoder at 1080p30 avoids converting it to a higher frame rate that the source does not contain. If it is 1080p60 and the motion matters, an output at 1080p60 preserves that temporal detail, at the cost of a higher recommended bitrate. YouTube’s table is keyed to the resolution and frame rate being ingested, so use the row matching the encoder output.
Do not select 60 fps simply because it sounds like a higher-quality default. More frames mean more data to encode and send. If your network or encoder is constrained, a stable 30 fps stream can be a more practical choice than a 60 fps stream that repeatedly struggles to send its target rate. Conversely, if 60 fps is part of the intended presentation, reducing the output frame rate changes the motion, not just the bandwidth demand.
Consider the programme as viewers will see it. A lofi station showing a mostly still scene may be entirely adequate at 30 fps. A local news loop with moving footage, graphics and clips may benefit from 60 fps where those elements were authored for it. Use a representative section to test rather than judging from a still frame.
H.264: compare the recommendation with the minimum
YouTube lists separate H.264 minimum and recommended video bitrates for 1080p30 and 1080p60. The minimum is the lower listed ingest threshold for that row; it is not the recommended target. If you can sustain the recommended rate reliably, use it as the starting point. Do not interpret the minimum as a guarantee of consistent quality across different footage or network conditions.
| YouTube Live output | H.264 listed minimum | H.264 recommended |
|---|---|---|
| 1080p at 30 fps | 5 Mbps | 14 Mbps |
| 1080p at 60 fps | 6 Mbps | 17 Mbps |
The difference between the two columns is meaningful. A stream sent at the minimum may be accepted, but complex movement, fine detail and abrupt scene changes can be harder to represent than a static image. The recommended figure gives the encoder more room to describe the picture. The exact result still depends on the source and encoding conditions; the table does not promise a particular appearance.
H.264 is a common choice when compatibility across encoder software or equipment is important. It is available in many workflows, so it can be a straightforward starting codec. If your encoder only offers H.264, choose the frame-rate row, set the recommended video rate if your connection can carry it, and test with representative audio and motion.
If you need a lower rate because of a constrained connection, know what is being traded away. Reducing the bitrate below the recommendation does not turn the minimum into a target for every channel. You may see more compression artefacts, especially in moving footage or detailed scenes. Recheck stream health and the actual outgoing rate rather than assuming the value entered in the encoder is what reaches YouTube.
AV1 or H.265: a different rate table
YouTube’s live table also gives figures for AV1 and H.265 (HEVC). At the same 1080p frame rate, their listed recommendation is lower than H.264’s in the table. That is a codec-specific recommendation, not a reason to enter the AV1 or H.265 bitrate while actually sending H.264.
| YouTube Live output | AV1/H.265 listed minimum | AV1/H.265 recommended |
|---|---|---|
| 1080p at 30 fps | 4 Mbps | 10 Mbps |
| 1080p at 60 fps | 4 Mbps | 12 Mbps |
Use the figures only if the encoder is genuinely producing AV1 or H.265 for ingestion. The minimums in YouTube’s table are 4 Mbps for both 1080p frame rates; the recommended values are 10 Mbps at 30 fps and 12 Mbps at 60 fps. These remain video bitrate figures for the incoming live stream, not a minimum upload speed for your internet service.
Before choosing a less familiar codec, check that your encoder and workflow can output it as a YouTube Live ingest stream. Codec availability varies across software, devices and configurations. If switching codecs introduces a complicated production change, the theoretical bitrate difference may not be worth it for a simple looping channel. Run a test with the intended encoder and confirm that YouTube receives the stream cleanly.
For many channels, the practical decision is straightforward: use the codec your encoder reliably supports, then select its matching row and target rate. A useful OBS loop setup guide can help with the playback side of a prerecorded programme, but it does not change which codec-specific live recommendation applies.
Set encoder output for YouTube Live
For RTMP or RTMPS live output, YouTube’s general encoder guidance specifies H.264, H.265 or AV1 video, AAC or MP3 audio, constant bitrate encoding (CBR), and frame rates up to 60 fps. It recommends a keyframe every two seconds and says the interval should not exceed four seconds. For stereo audio, the listed audio bitrate is 128 Kbps. For SDR, the colour space is Rec. 709. YouTube recommends RTMPS, the encrypted extension to RTMP.
Set the output resolution and frame rate to match the live target you chose. If the source is 1080p30, configure 1080p30 rather than upscaling or inventing additional frames. If it is 1080p60 and you intend to keep that motion, set the output accordingly. Then choose the bitrate from the correct codec-and-frame-rate row. These are practical setup steps based on YouTube’s ingestion table; prerecorded content does not have a separate live bitrate schedule.
CBR is intended to keep the outgoing bitrate steady rather than allowing large rate swings. In encoder settings, this is separate from the numerical bitrate field: select CBR where it is offered, then enter the relevant video rate. Audio contributes to the total data sent even though the bitrate tables above refer to video. Keep audio encoding and levels consistent with the production you actually need.
You do not need a standalone hardware encoder simply because the stream is 1080p. YouTube describes encoder options that include computer software and standalone hardware; its encoder overview notes hardware’s use for external audio/video gear and more advanced productions. Software can be suitable for a prerecorded loop. Hardware becomes relevant where the production depends on dedicated equipment or external inputs, not as a universal requirement.
For a 24/7 channel, the encoder is only one part of the chain: the file must keep playing, the output must stay connected, and the stream must be monitored. If a local computer is being used to loop the file, its workload and operating conditions matter. See ways to reduce CPU usage when looping video in OBS if the machine is handling both playback and encoding.
Check outgoing bitrate, bandwidth and preview
The number in the encoder is a target, not proof that the same amount is reaching YouTube. Observe the encoder’s outgoing bitrate and the live control room’s stream health. If the rate repeatedly falls, investigate the connection, competing network use, encoder load or source settings before increasing the target. Raising the configured bitrate cannot fix a bottleneck that prevents it from being sent.
YouTube advises that total outgoing stream bitrate must fit within available upload bandwidth and recommends leaving 20% headroom. Treat that as a planning margin, not an assurance that a connection will remain stable. Include audio and any backup feed in the total network load; do not compare the video number alone with the internet plan’s advertised upload figure. Other devices sharing the connection can also consume capacity.
Test before going live, using audio and movement similar to the actual programme. A static slate is not a useful test for a stream that regularly shows moving footage. Check the preview for framing, colour, audio sync and compression, and read any stream-health messages. YouTube’s streaming tips also advise testing and monitoring. Do not wait until the overnight run to discover a dropped connection or a misconfigured frame rate.
A sensible test begins with a short representative section and the intended output settings. Confirm the stream appears in the preview, then check the outgoing bitrate stays near the configured target and that YouTube reports no persistent ingest problem. If you change codec, frame rate or bitrate, test again: each change can affect encoding load and network use. For a channel that runs continuously, keep an eye on the stream after launch rather than assuming a successful preview proves every later hour will behave the same way.
If the stream drops or the encoder reports instability, reduce other network activity first and check whether the actual outgoing rate can be sustained. A lower frame rate or a codec and setting your hardware handles reliably may be preferable to repeatedly missing a higher target. Make one change at a time where possible, so you can tell whether it improved the preview or stream health.
Keep ordinary upload settings separate
If by “pre-recorded” you mean a normal video upload, use YouTube’s upload encoding guidance instead of the live ingest figures. For SDR 1080p uploads, YouTube recommends 8 Mbps at 24, 25 or 30 fps, and 12 Mbps at 48, 50 or 60 fps. These recommendations apply to the encoded file being uploaded, not the live stream sent from an encoder.
| Workflow and SDR 1080p rate | YouTube guidance |
|---|---|
| Regular upload, 24/25/30 fps | 8 Mbps |
| Regular upload, 48/50/60 fps | 12 Mbps |
You can consult YouTube’s upload encoding settings for the file workflow. Compare those values with the live tables above and the distinction is clear: an H.264 1080p30 live stream has a 14 Mbps recommended ingest rate, while a regular 1080p30 SDR upload has an 8 Mbps recommendation. The figures differ because the workflows and guidance differ; do not substitute one for the other.
This distinction is useful if you prepare a loop offline. You may encode and upload a source file at settings suitable for its file workflow, then send that file as a separate live broadcast at the live encoder’s output settings. The file’s bitrate and the outgoing live bitrate are not necessarily the same. YouTube receives the live encoder’s output, so it is that outgoing stream which should be compared with live ingest recommendations.
For more on the practical trade-offs between continuous broadcasts and ordinary publishing, see how 24/7 streams compare with regular uploads. That question is separate from the technical settings here: whichever format you choose, make the encoder or upload conform to the guidance for that workflow and check YouTube’s current official pages.
Make the setting fit the whole channel
A bitrate choice affects more than the image. It influences the upload capacity your connection must supply, the load on the encoder and the amount of network capacity left for other activity. For a small business showing a product loop from a shared office connection, a stable 1080p30 stream may be more practical than a higher-rate 60 fps stream that competes with daily work. For a study station with quiet visuals, the benefits of 60 fps may be limited.
If the source is already clean and relatively still, a higher bitrate cannot add detail that is not present in the file. If it contains fine text or quick motion, a rate below YouTube’s recommendation may show more compression. Inspect the actual programme rather than applying the same preset to every channel. Make a short test with the most demanding segment: a scene with movement, text, transitions and audio, if those are part of the programme.
Operational reliability matters alongside picture quality. If your stream depends on a computer being awake and encoding for long periods, consider the burden of keeping that workstation available and watching for interruptions. StreamNeo removes the need to leave your own computer running for a file-based YouTube broadcast: you upload the file once, provide the stream key, and the broadcast runs with monitoring and automatic restart if it drops. It is YouTube-only, so this addresses the continuous playback and computer-availability problem rather than changing YouTube’s bitrate requirements.
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 1080p30 YouTube Live stream?
For live ingestion, YouTube recommends 14 Mbps with H.264 or 10 Mbps with AV1/H.265 at 1080p30. The listed minimums are 5 Mbps for H.264 and 4 Mbps for AV1/H.265. Use the recommendation for the codec actually being sent, and check your outgoing bitrate during a test.
What bitrate should I use for 1080p60?
YouTube recommends 17 Mbps for H.264 and 12 Mbps for AV1/H.265 at 1080p60. Its listed minimums are 6 Mbps and 4 Mbps respectively. These are live video ingest figures, not universal internet upload-speed requirements; allow capacity for audio and other outgoing traffic.
Are these the same settings as uploading a normal video?
No. For SDR 1080p regular uploads, YouTube recommends 8 Mbps at 24/25/30 fps and 12 Mbps at 48/50/60 fps. A file played through an encoder into YouTube Live uses the live ingest recommendations instead.
Should I use H.264, AV1 or H.265?
Use a codec your encoder can send reliably and that your production workflow supports. YouTube publishes different recommended rates by codec, so make sure you choose the matching row rather than applying an AV1 or H.265 figure to H.264 output. Test the finished setup with representative movement and audio before relying on it for a continuous stream.