Yes. YouTube Live accepts H.265 (HEVC) for HLS playlist ingestion, and it also lists HEVC for RTMP/RTMPS, so you do not need HLS simply to use this codec. For HLS, the important question is whether your encoder can produce YouTube’s required playlist and segments, not just whether it can encode HEVC.
Choose an HLS-configured stream key, follow the playlist contract, and test the complete path in Live Control Room before relying on it overnight. HLS is segmented and has more latency than a continuous RTMP stream; if that trade-off does not suit your channel, RTMP/RTMPS is also a valid HEVC route when your encoder supports it.
Can YouTube Live accept HEVC for a playlist stream?
Yes. YouTube’s HLS setup guidance includes HEVC video, alongside H.264, and its general live encoder settings also list H.265 for RTMP/RTMPS. This means HEVC is not confined to playlist-based delivery. The protocol and the codec are separate choices: HEVC describes how video is compressed, while HLS or RTMP/RTMPS describes how the encoder sends it to YouTube.
That distinction matters when you see “HEVC supported” in an encoder’s feature list. It does not by itself tell you whether the device can send HEVC through HLS, whether it can build the playlist in the required form, or whether the exact settings and firmware are compatible. Check support for the protocol you plan to use, not only the codec name.
For a playlist stream, HLS is the path with explicit playlist and segment requirements. YouTube expects a rolling playlist of Transport Stream (TS) segments, with limits on segment length and how many segments can be outstanding. An encoder that emits a valid HEVC file may still be unsuitable if its live HLS output uses another segment format or playlist behaviour.
If you are choosing between an HLS workflow and a continuous stream for a channel that loops recorded material, consider the whole operating setup as well as the codec. A guide to looping a devotional channel from a Linux VPS is useful for thinking through how the playback process fits around the YouTube ingest connection; it does not remove the need to meet YouTube’s protocol requirements.
HEVC over RTMP/RTMPS and HLS
RTMP/RTMPS and HLS both carry video to YouTube, but the workflows differ. With RTMP/RTMPS, an encoder sends a continuous stream. With HLS, it creates segments and updates a playlist that points to them. YouTube lists HEVC for both paths, but the HLS playlist contract applies only to HLS.
| Decision | HLS | RTMP/RTMPS |
|---|---|---|
| HEVC support | Listed in YouTube’s HLS guidance | Listed in YouTube’s general encoder settings |
| Delivery shape | Playlist plus separate TS segments | Continuous stream; no HLS playlist contract |
| Latency | Higher than continuous RTMP; ultra-low latency is unavailable for HLS | Use the latency options available for the selected stream |
| Main check | Playlist updates, segment format and duration, request method | Encoder’s HEVC support for the selected RTMP/RTMPS mode and current YouTube settings |
| HDR | Supported with HEVC and the required HDR signalling | Also documented by YouTube; check the encoder’s supported path and settings |
The table describes protocol differences, not a universal recommendation. HLS may fit a workflow or encoder that publishes playlists, but its segment delivery introduces more latency. For a local news loop where viewers need to see a change promptly, that may weigh against HLS. For an always-on music or ambience channel, the delay may be acceptable, but test it rather than assuming that the word “live” means both methods behave identically.
YouTube recommends RTMPS for general encoder streaming. Its current live encoder page also gives codec- and profile-dependent bitrate guidance, along with recommendations such as constant bitrate and a two-second keyframe interval (not over four seconds). Do not transfer a bitrate from a different resolution or frame rate: use the current table for your chosen profile. You can review the YouTube Live encoder settings before configuring either protocol.
If the project is a file played repeatedly rather than a live camera feed, the looping system still needs to feed a compatible live encoder. The cloud playlist workflow for a Kannada music channel offers a separate perspective on keeping playback continuous. Whichever playback method you use, confirm that the encoder’s actual output—not merely the source file—matches the selected YouTube ingest protocol.
Choose a stream key configured for HLS
In Live Control Room, create or select a stream key whose protocol is HLS. A key configured for RTMP/RTMPS is not a substitute for an HLS key just because the encoder can produce HEVC. Match the stream key, the encoder’s output mode and the ingest URL to one another before the test begins.
YouTube provides the HLS server URL in Live Control Room. Use that supplied URL in the encoder’s HLS configuration; YouTube’s instructions specify that the URL begins with https. If you configure backup ingestion, use the backup URL provided there rather than guessing a second address. Treat both the stream key and ingest URL as operational credentials: do not put them in a public post, screenshot or shared document that does not need access.
Check the encoder’s own documentation for where to set the protocol, URL, key and HEVC profile. Menu names vary by product and software version. A specification that says “HEVC” may refer to file recording, network output, or only a particular mode. You need confirmation for live HLS output on the exact device and software version you will run.
YouTube’s HDR guidance has an additional stream-key instruction: HDR stream keys must use HLS, with “Turn on manual resolution” left unchecked. Do not apply that HDR-specific setting blindly to an SDR stream; follow the current Live Control Room prompts for the stream you are creating. YouTube also says that HDR streaming currently uses HEVC, but that does not mean every HEVC stream is HDR.
Meet the playlist and segment requirements
For HLS, inspect the playlist and segments rather than relying on a green encoder status alone. YouTube specifies TS segments between 1 and 4 seconds, a rolling playlist, and no more than five outstanding segments. It does not support byte-range addressing. These are output requirements for the HLS workflow; they are not properties you can infer just by opening the original HEVC file.
A rolling playlist is updated as new segments become available, so the receiver can keep following the current edge of the stream. In a test, look for a playlist that advances over time and references separate segments. Check that segments are TS, that their durations fall within the supported range, and that the playlist does not retain more than five outstanding segments. If the encoder creates a playlist that references byte ranges within a larger file instead of standalone segments, it does not meet YouTube’s stated HLS requirements.
These checks are practical because output labels can be misleading. “HLS enabled” might mean the software can publish HLS for playback by viewers, while YouTube ingestion requires a particular submission workflow. Ask the manufacturer or software vendor whether the product supports YouTube Live HLS ingest, HEVC video, and the specified playlist behaviour together. If the answer covers only HLS generally or only HEVC encoding, ask for clarification.
Segment length also affects how quickly changes can reach viewers. YouTube says ultra-low latency is turned off for HLS because the protocol sends segments. Shorter segments within the permitted range can affect latency, but do not tune them in isolation: a setting that looks responsive in a short test is not useful if the encoder cannot maintain stable segment generation over a long run. Test the profile with the content and network conditions you expect to use.
If your goal is an always-on loop, file playback and HLS packaging are separate jobs. A playlist can be correct while the source loop freezes, repeats an unintended frame or loses audio. A guide on why FFmpeg can repeat the first frame in a loop addresses a different failure point in the chain; it is worth checking the source playback as well as the HLS packaging.
Use HTTPS requests and supported encryption
Send HLS requests over HTTPS using POST or PUT, as YouTube specifies. The endpoint URL begins with https; the encoder’s request method should match YouTube’s HLS guidance. If the device provides additional transport or encryption settings, do not assume they are compatible simply because they are described as more secure.
YouTube’s HLS guidance says encryption beyond HTTPS is unsupported. In practice, use HTTPS transport as instructed rather than layering another encryption method onto the ingest requests. This is a protocol compatibility point, not a reason to weaken account or stream-key security. Keep credentials private, restrict who can access the encoder configuration, and use the secure connection YouTube provides.
If a test fails, check the request method, destination URL, authentication/key configuration and the encoder’s error log before changing codecs. A rejection may come from an HLS request or playlist issue rather than from HEVC decoding. Make one change at a time and repeat the test, so you can identify whether the problem is the transport configuration or the video output.
Check encoder output before going live
Compatibility depends on the exact encoder and its configured mode. YouTube names Cobalt encoders and Telestream Lightspeed Live Stream as examples in its HDR guidance, but those examples are not a complete compatibility catalogue, and support can differ between models. Check the manual for the specific model and the software or firmware version you will use. Do not infer that every product in a manufacturer’s range supports HEVC HLS or HDR.
A useful validation run starts with the same source, frame rate, resolution, audio and protocol you expect for the real channel. Confirm that the encoder is sending HEVC over the intended protocol; for HLS, inspect the playlist and segment properties described above. Play representative content with both still passages and motion, and listen for the audio you intend to broadcast. A still graphic alone will not reveal all timing, motion or sound problems.
Open the Live Control Room preview and check stream health while the test is running. YouTube recommends testing representative sound and movement, reviewing the preview and monitoring stream health. Leave upload bandwidth headroom rather than sizing the connection exactly to the encoder’s target bitrate; YouTube’s streaming tips recommend 20% headroom. That recommendation is not a guarantee against network interruptions, so also check the connection at the place and time the channel will operate.
For HDR, verify the whole signal chain. YouTube documents HEVC at 10-bit, BT.2020 colour primaries and matrix, and either ST 2084 PQ or HLG transfer characteristics, matched to the source. The encoder must preserve the intended signal, not merely label its output as HDR. Follow the instructions for your encoder’s particular hardware or software path and see YouTube’s current HDR streaming guidance.
A practical checklist is:
- The stream key uses the intended protocol, HLS or RTMP/RTMPS.
- The exact encoder model and version supports HEVC output for that protocol.
- For HLS, the output is TS segments of 1–4 seconds in a rolling playlist, with five or fewer outstanding segments and no byte ranges.
- The HLS requests use HTTPS with POST or PUT, without encryption beyond HTTPS.
- For HDR, the source and encoder agree on 10-bit, BT.2020 and PQ or HLG signalling.
- A representative test appears in Live Control Room, with stream health monitored and audio and motion checked.
If your current computer is the weak link in an always-on loop, you may be weighing whether to keep a local machine running overnight. StreamNeo removes that particular need by taking an uploaded video and running it as a YouTube live stream while your computer is switched off; it does not change the need to choose a compatible format and check the YouTube stream. The cost of keeping an always-on YouTube PC is a useful comparison if you are deciding whether to maintain a local setup.
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
Can I use H.265 HEVC for a YouTube Live playlist stream?
Yes. YouTube’s HLS ingest guidance supports HEVC, provided the encoder also meets the playlist, segment and HTTPS request requirements. Confirm the output from the specific encoder and configuration you plan to use.
Does YouTube Live accept HEVC over HLS, or do I need RTMP?
YouTube lists HEVC for HLS and for RTMP/RTMPS, so HLS is not required just to send HEVC. Choose based on the encoder’s supported output and your latency needs; HLS is segmented and does not offer YouTube’s ultra-low-latency option.
Can I send HEVC in any HLS playlist format?
No. YouTube specifies TS segments of 1–4 seconds, a rolling playlist with no more than five outstanding segments, no byte ranges, and HTTPS POST/PUT requests. A generic HLS output or an HEVC file alone does not establish that those conditions are met.
Is HEVC required for HDR on YouTube Live?
YouTube’s current HDR guidance says that HDR streaming is supported with HEVC. HDR also requires matching signal settings, including 10-bit, BT.2020 and PQ or HLG; check YouTube’s official guidance and your encoder manual before testing.