If you send pre-recorded footage through a YouTube Live event, H.264 and H.265 are both supported live-ingest choices. The practical decision depends on the bitrate YouTube recommends for your resolution and frame rate, and on whether your encoder or relay can send the selected codec reliably.
For most SDR streams, choose the codec your complete workflow supports consistently, then match YouTube's live-ingest settings. H.265 is not a guarantee of better pictures for viewers, and the codec you send to YouTube is not necessarily the codec a viewer receives.
How pre-recorded footage reaches YouTube Live
A pre-recorded live stream still has a live-ingest path. Your video file is played by software, hardware or a cloud-based relay. That system encodes the moving output and sends it to YouTube over RTMP or RTMPS using your stream key. YouTube receives that encoded stream as the input to a live event.
This is different from uploading a finished file as a normal YouTube video. A normal upload has its own recommendations, including separate guidance for upload encoding. Those settings should not be copied into a live event simply because the source footage is pre-recorded. You can compare the distinction in YouTube's upload encoding guidance and its live encoder settings.
The source file and the outgoing live stream also do not have to use the same codec. For example, you might have an H.264 recording that a relay decodes and sends to YouTube as H.265. Or you might have an H.265 master that is decoded and sent as H.264 because the available encoder supports only that format. The live-ingest choice concerns the stream sent to YouTube, not simply the format of the file stored on your drive.
That distinction matters for an always-on channel. A file can play correctly in a media player while the live encoder fails to start, produces an unsupported combination of settings, or loses frames under sustained load. Before scheduling a long broadcast, confirm the full chain: file playback, decoding, outgoing codec, bitrate control, keyframes, audio, network connection and YouTube's live preview.
If you are using OBS, the first connection step is covered in how to connect OBS to YouTube Live for a pre-recorded stream. The same principle applies to a hardware encoder or relay: configure the outgoing live signal, not just the source file.
Does YouTube Live accept H.264 and H.265
YouTube's current live encoder guidance lists H.264 and H.265, also called HEVC, among the supported live-ingest codecs. It also lists AV1. Support at YouTube's receiving end does not mean that every playback application, hardware encoder or pre-recorded streaming product can create the required output.
Check the exact combination offered by your encoder. A device may support H.265 for local recording but not for RTMP output. Software may support H.265 decoding while offering only H.264 for live transmission. Some tools may support the codec but expose only certain frame rates, bit depths, colour spaces or transport options. The word “supported” is therefore only the starting point.
For a standard SDR broadcast, H.264 is often the simpler compatibility choice when your existing workflow already uses it successfully. H.265 may be suitable when the encoder and relay explicitly support HEVC live ingest and your available upstream bandwidth makes the lower recommended rate useful. Neither choice removes the need to test the actual output.
YouTube says that it automatically transcodes incoming live streams into multiple output formats for viewers. In practical terms, your encoder's H.264 or H.265 setting describes the ingest signal. It does not tell you that every viewer will receive H.264 or H.265, and it does not establish a fixed playback codec for every device or connection. See YouTube's explanation of how live streams are transcoded for viewers before making claims about playback.
This is also why an H.265 ingest setting should not be presented as a universal quality upgrade. Quality depends on the source, encoder implementation, rate control, motion, detail, scaling and the later processing applied by YouTube. YouTube's bitrate table gives configuration guidance for the incoming stream; it is not an independent visual-quality comparison between the two codecs.
Recommended bitrate by resolution and frame rate
YouTube recommends different live-ingest bitrates for different codecs, resolutions and frame rates. The figures below are selected examples from YouTube's current live encoder table, accessed in October 2026. They are settings guidance for the stream sent to YouTube, not measured quality results.
| Resolution and frame rate | AV1/H.265 recommended bitrate | H.264 recommended bitrate |
|---|---|---|
| 720p at 30 fps | 6 Mbps | 8 Mbps |
| 1080p at 30 fps | 10 Mbps | 14 Mbps |
| 1080p at 60 fps | 12 Mbps | 17 Mbps |
| 2160p at 30 fps | 30 Mbps | 42 Mbps |
For a 1080p recording played at 30 frames per second, the table points to 10 Mbps for AV1/H.265 or 14 Mbps for H.264. At 60 fps, the corresponding examples are 12 Mbps and 17 Mbps. This does not mean H.265 will always look better at 10 Mbps, or that H.264 at 14 Mbps will always produce a particular result. It means YouTube publishes different recommended input settings for those codec and frame-rate combinations.
The table is deliberately limited to examples. Use the current full table on YouTube's live encoder settings, bitrate and resolution page for the exact resolution and frame rate you intend to send. Do not calculate an unlisted setting by simply multiplying or dividing one of these figures.
YouTube also publishes minimum rates. A minimum is not the same as a recommended target for a detailed, fast-moving source. If your devotional loop contains mostly static artwork, the visual demands may differ from a sports replay or a gaming recording, but that does not replace the platform's published live settings. Start with the matching recommendation, then test the real material.
You should also use constant bitrate encoding for the live output and set a keyframe interval of two seconds. YouTube's guidance says not to exceed four seconds. These are properties of the outgoing live signal. A pre-recorded file with a variable bitrate or different keyframe pattern may still be usable as a source, because the live encoder can create a new output stream with the required settings.
Do not confuse the bitrate in the table with your entire internet requirement. The stream itself needs room for its selected bitrate, and your connection needs additional headroom for normal traffic, protocol overhead and temporary variation. If a 1080p H.264 stream is configured at the recommended 14 Mbps, a connection that barely reaches 14 Mbps upstream is not a robust operating plan.
Choose the codec your encoder and workflow can sustain
The first question is not which codec sounds more advanced. It is whether your complete path can decode the source, encode the live output and transmit it for the length of the broadcast without intervention.
Use this checklist when comparing H.264 and H.265:
- Output support: Confirm that the encoder can send the selected codec to YouTube over the protocol you intend to use. Local H.265 recording support is not enough.
- Resolution and frame rate: Select the row in YouTube's live table that matches the outgoing signal, rather than the dimensions of the original file alone.
- Rate control: Confirm that the live encoder can use constant bitrate encoding and the required keyframe interval.
- Upload capacity: Measure the upstream connection at the location where the live signal is created. A fast download result does not demonstrate adequate upload capacity.
- Sustained operation: Test for several hours if the channel is intended to run overnight or continuously. A successful five-minute preview does not prove that a long broadcast will remain stable.
- Recovery behaviour: Find out what happens after a brief network interruption, application restart or source-file error. YouTube's codec support cannot provide recovery features that your encoder does not have.
H.264 can be the sensible choice where compatibility and straightforward troubleshooting matter more than reducing the recommended ingest rate. It is also the practical choice if your existing hardware or software exposes a reliable H.264 live output but has uncertain HEVC support.
H.265 can be the sensible choice where the encoder explicitly supports HEVC live output, the settings match YouTube's requirements and the lower recommended ingest rate helps your available upstream connection. It may also be required for an HDR workflow, which has additional conditions described below. Those benefits depend on the actual implementation and source; they should not be turned into a promise about the final picture.
If your local computer struggles with decoding, scaling and encoding at the same time, changing codecs may not solve the underlying problem. Reduce unnecessary processing, use a suitable source format, or move the live encoding task to a workflow designed to run without the computer being left on. For a channel built around a single uploaded file, StreamNeo removes the need to keep your own computer running for the broadcast, while you still need to verify the file, YouTube settings and live result before relying on it overnight.
Bandwidth, dropped frames and overnight operation
A codec decision is only useful if the outgoing stream remains steady. YouTube's network guidance recommends leaving headroom rather than using every available bit of upstream capacity. Your connection may be shared with other people, Wi-Fi conditions may change, and an internet service may deliver different performance at different times.
For an always-on channel, wired networking is preferable where the encoder is on site. If the stream is created on a computer, watch the encoder's dropped-frame and network indicators while the live preview is running. A source file that repeats cleanly does not prove that the network is delivering every encoded packet on time.
Dropped frames can come from more than one place. The computer may be unable to encode at the selected settings, the source drive may not read smoothly, the connection may be congested, or the relay may have its own limitations. If OBS is part of your setup, the guide to preventing OBS from dropping frames on a 24/7 YouTube stream gives the problem its own troubleshooting path.
For a cloud-based relay, check what it does with the uploaded file and which outgoing codec, bitrate, frame rate and keyframe settings it actually sends. Do not assume that choosing H.265 in a source-file export menu changes the live-ingest codec. Ask for, or inspect, the live output settings. The evidence that matters is the signal arriving at YouTube and the stability of the running event.
Audio deserves its own check. A video can appear healthy in the live preview while the audio is silent, delayed or using an unexpected sample configuration. For RTMP workflows, use the YouTube live stream no-sound troubleshooting guide if the picture works but the audio does not.
For a channel serving viewers in India or elsewhere, the same technical rule applies: plan for the actual upload location and connection. If you are deciding between running a machine at home and using a managed cloud workflow, which cloud service can run a 24/7 YouTube playlist with Indian-language videos discusses the operational question separately from codec selection.
HDR has separate requirements
HDR live streaming is not simply SDR with H.265 selected. YouTube's dedicated guidance requires an HEVC/H.265 workflow with 10-bit video, BT.2020 colour and HLS output. It also has specific transport and playlist requirements, so the standard live settings table should not be treated as a complete HDR setup recipe.
YouTube states in its live encoder guidance that H.265 is recommended for HDR, while the dedicated HDR live streaming requirements provide the implementation details. Check that page before configuring an HDR event, because a device that can encode ordinary H.265 does not automatically meet the full HDR requirements.
The source must also genuinely be prepared for HDR. Selecting BT.2020 or 10-bit output for an SDR file does not create HDR detail or correct colour information. Confirm the source's colour properties, the encoder's bit-depth and colour-space controls, the transport method and the YouTube event configuration as one chain.
HDR is therefore a stronger reason to choose H.265 only when every part of the workflow supports it. If your source is SDR and your viewers do not need HDR, an H.264 or H.265 SDR workflow can be assessed on encoder support, bitrate, bandwidth and reliability instead. Do not use the HDR requirements as evidence that H.265 is generally superior for every pre-recorded live stream.
Test the live preview before going overnight
Run a private or unlisted test event with the same file, codec, resolution, frame rate, bitrate, audio and network path you plan to use for the public broadcast. Watch the YouTube live preview before you publish. The purpose is not only to see whether the event starts, but to verify that the entire workflow produces the intended result.
Check these points during the test:
- The event accepts the incoming signal without codec or format warnings.
- The output resolution and frame rate match your configuration.
- Motion remains continuous during scenes with detail or movement.
- Audio is present, at the expected level and synchronised with the picture.
- The encoder reports no sustained overload or dropped frames.
- The connection has headroom rather than operating at its limit.
- The file reaches its end and behaves as expected if it is meant to loop.
- A brief interruption does not leave the workflow requiring an unplanned manual fix.
Do not judge the codec from a single still image on your own monitor. Compare the actual live result at normal viewing size and on more than one connection if possible. YouTube may deliver different output formats to different viewers, and the viewer's device, connection and selected quality can affect what they see.
Keep a short record of the working configuration: codec, resolution, frame rate, bitrate, keyframe interval, audio settings and the date you tested it. If you later change the source file or move the workflow to another encoder, repeat the test rather than assuming the old result still applies.
A practical decision for your channel
Choose H.264 when your encoder already provides a dependable H.264 live output, compatibility is your main concern, or you cannot verify HEVC support throughout the chain. For 1080p30, use YouTube's published H.264 recommendation of 14 Mbps as the starting configuration shown in its table, then check the current guidance and your connection before going live.
Choose H.265 when the encoder or relay explicitly supports HEVC live ingest, the workflow meets YouTube's settings, and the codec's recommended rate fits your bandwidth plan. For 1080p30, YouTube currently lists 10 Mbps for AV1/H.265. Treat that as an ingest recommendation, not as proof that the stream will look better than H.264 in every case.
Choose the HDR path only when you need HDR and can satisfy the separate HEVC, 10-bit, BT.2020 and HLS requirements. For an SDR devotional loop, lofi station, local news sequence or study channel, there is no reason to add HDR complexity unless the content and workflow justify it.
Finally, decide where the live encoding should happen. A local OBS setup gives you direct control and can be appropriate when you are comfortable monitoring the computer and connection. A cloud workflow can be more suitable when the aim is to upload a file once and avoid leaving a personal computer switched on, but its exact codec and setting support still needs verification. The decision is operational as much as technical.
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 H.264 or H.265 for a pre-recorded YouTube live stream?
Use the codec your complete encoder or relay workflow supports reliably. H.265 may use a lower YouTube-recommended ingest bitrate for some matching settings, but that is not a guarantee of better viewer quality. H.264 remains a sensible choice where its live output is better tested or more compatible.
Does YouTube Live accept HEVC?
Yes. YouTube currently lists H.265, or HEVC, as a supported live-ingest codec. Your particular software or hardware still needs to support HEVC output over the protocol and settings you intend to use.
What bitrate should I use for 1080p YouTube Live?
YouTube's current examples list 14 Mbps for H.264 at 1080p30 and 10 Mbps for AV1/H.265 at 1080p30. At 1080p60, the listed recommendations are 17 Mbps for H.264 and 12 Mbps for AV1/H.265. Check YouTube's current full table and leave upload headroom.
Can I stream HDR to YouTube Live with H.265?
Yes, but HDR has separate requirements. YouTube's guidance specifies HEVC/H.265, 10-bit video, BT.2020 colour and HLS output, so test the complete HDR workflow rather than selecting H.265 alone.