If your video file uses HEVC (also called H.265), you usually do not need to convert it before trying it in OBS. File playback and the codec OBS sends to YouTube are separate decisions: test the source, then check that your chosen YouTube ingest protocol and OBS output encoder work together.
That distinction matters because YouTube documents HEVC for both RTMP/RTMPS and HLS, but that does not guarantee every file, OBS build, encoder, or stream-key setup will work. Convert only when you have found a real playback or output-compatibility problem, or when your workflow needs a different stream format.
The file codec and stream output are different things
An HEVC file is an input to OBS. When you add it as a Media Source, OBS has to read its container, decode its video and audio, and present the result in your scene. Separately, OBS encodes the finished scene for transmission to YouTube. That outgoing stream may use a codec selected in OBS; the input file's codec does not, by itself, determine the output codec.
In practical terms, OBS is not simply forwarding the original compressed file to YouTube. The OBS documentation describes media files as sources and separately describes output configuration; it does not document HEVC passthrough from a Media Source. So do not assume that an HEVC source means YouTube will receive HEVC, or that changing the source file to H.264 will automatically fix an incompatible output encoder.
This separation is useful if you are building a devotional loop, a lofi station, or a lecture broadcast. You can test the video file inside an OBS scene and make a separate decision about the outgoing codec. If audio quality is also part of the setup, the guide to preserving podcast audio quality for YouTube Live explains why audio settings deserve their own check rather than being treated as a side effect of the video format.
Test the file as an OBS Media Source
Start with a short, representative segment rather than converting the whole programme. In OBS, add the video as a Media Source, select the file, and check that picture and sound play together. Test a section with motion, scene changes, and the audio you expect to use; a static opening frame alone is not a useful compatibility test.
OBS's Media Sources documentation lists common video containers including MP4, TS, MOV, and MKV. Its Audio/Video Formats Guide describes HEVC in those container formats. Container recognition is not a promise that every file will work: profiles, bit depth, audio tracks, corruption, and the installed OBS build can all affect playback.
Check the source properties and watch for a black frame, missing audio, stuttering, or a source that stops unexpectedly. If OBS offers hardware decoding for the file and your GPU supports it, you can test that option, but hardware decoding is not necessary for every file. Change one setting at a time so that you can tell whether the result improved.
For a long-running channel, include the start and end of a loop in your test. A file that plays for a few minutes may still have an awkward end, mismatched audio, or a restart issue. If your channel relies on a sequence of files rather than one programme, a playlist workflow for a 24/7 YouTube music stream can help you think through the programme structure separately from codec compatibility.
Choose the YouTube ingest protocol
Before configuring the output encoder, confirm how OBS is sending the stream to YouTube. YouTube's general live encoder guidance covers RTMP and RTMPS, while its separate HLS setup instructions describe another ingest route. In YouTube's current guidance, HEVC appears in the RTMP/RTMPS codec list, and HLS is also documented as supporting HEVC.
That does not make the two routes interchangeable in every setup. Your stream key or destination configuration needs to match the protocol you intend to use, and the OBS build and encoder you select must support that route. For HLS, follow YouTube's specific instructions, including its requirements for transport stream segments and the rolling playlist. Do not assume a standard RTMP configuration can be relabelled as HLS without changing the relevant settings.
HLS also has a latency trade-off. YouTube says HLS has higher latency because it sends video segments rather than a continuous stream like RTMP. For a pre-recorded devotional or ambience channel, that delay may be acceptable; for a local news loop with live interaction, it may matter more. Consider how quickly viewers need to see a change, not only whether the codec is listed as supported.
Match the protocol with an output encoder
After choosing a protocol, confirm the actual streaming encoder in OBS. This is a separate setting from the decoder OBS uses to read the source file. YouTube's live encoder settings list H.264, HEVC/H.265, and AV1 for RTMP/RTMPS. Its HLS setup instructions describe HEVC support and name OBS among HLS-capable encoders.
Treat that as a documented compatibility path, not a guarantee that every combination on your computer will connect. Available encoder choices can depend on the OBS version, operating system, and hardware. Check the streaming encoder dropdown and confirm it is the encoder you intend to use; do not infer the output codec from the file extension or the Media Source label.
| Route | What YouTube documents | What you need to check | Practical trade-off |
|---|---|---|---|
| RTMP/RTMPS with HEVC | HEVC is included in YouTube's general live encoder guidance | The OBS output encoder, destination settings, and stream health | A continuous-stream path; assess it against your interaction and latency needs |
| HLS with HEVC | HLS supports HEVC, and OBS is named as a compatible encoder | HLS destination, segment settings, playlist behaviour, and encoder support | More configuration detail and higher latency than RTMP |
| Convert the source, then stream | Conversion changes the input file; it does not by itself settle output compatibility | Whether the converted file plays and the outgoing encoder-protocol pair is supported | Adds a processing step and may be useful when the original file cannot be decoded reliably |
For the outgoing stream, follow the settings for the selected codec in YouTube's current guidance. YouTube recommends CBR, a two-second keyframe interval (not over four seconds), and codec-specific bitrate guidance. Do not copy a bitrate recommendation from a different codec column as if it were universal. The settings you need also depend on resolution and frame rate, so check the relevant row for the actual output you plan to send.
For example, YouTube's guidance checked in 2026 lists a recommended 12 Mbps for AV1/H.265 at 1080p60 and 17 Mbps for H.264 at the same resolution and frame rate. Those figures are YouTube's codec-specific recommendations, not a guarantee of quality or a rule that every channel must use those exact values. Use the current official table, then test the broadcast and monitor YouTube's stream health before relying on the configuration overnight.
Diagnose playback and decoding problems first
If the Media Source fails, begin with the source rather than changing the YouTube protocol. Confirm the correct file path, restart playback within OBS, and check whether both video and audio are present. Try a different short sample from the same export if one is available. This helps separate a file-specific fault from a broader limitation in the installed OBS version or decoding hardware.
If the image is black or unstable, record the file's container, resolution, frame rate, bit depth, and whether it is SDR or HDR. These details can help explain why a file that another player opens may not behave the same way in OBS. Check the OBS log and source properties for useful errors. If hardware decoding is enabled, test with it disabled, and if it is disabled, test the available hardware option where appropriate. Avoid changing several properties together, since that makes the cause harder to identify.
If playback is fine but YouTube does not accept the stream, the problem may be in the output path instead. Verify the ingest protocol selected for the YouTube destination, the encoder shown in OBS, the key or destination settings, and the outgoing frame rate, keyframe interval, and bitrate. A working source does not prove the stream output is compatible; a listed codec does not prove that a particular OBS encoder is available on your machine.
For a channel that depends on a playlist, distinguish a codec failure from a missing or ended source. A backup file or playlist will not repair an encoder mismatch, but it can keep a programme from going blank if the main file is unavailable. The OBS backup-playlist guide covers that separate failure mode.
When conversion is actually useful
Convert when testing identifies a concrete reason. That might be a file that the installed OBS build cannot decode reliably, a damaged or unusual export, or an output workflow where the available encoder and chosen YouTube protocol do not form a supported combination. Conversion may also fit a wider production workflow that requires another codec, bit depth, or format for editing or distribution.
Do not convert simply because the source is HEVC. If OBS plays the file cleanly and your outgoing protocol-encoder pair is supported, conversion adds processing time and another opportunity to alter quality, audio synchronisation, or colour. It can also create a large intermediate file, which matters when storage or upload time is limited. First establish whether the source or the outgoing stream is the part that is failing.
If you do convert, choose settings based on the source and intended output rather than a universal preset. Preserve the frame rate and audio layout unless you have a reason to change them, and pay attention to HDR versus SDR. A conversion from HDR to SDR is a colour-management decision, not just a codec change. After conversion, play the new file in OBS and test the outgoing YouTube stream again.
For an HDR live stream, check YouTube's dedicated HDR live streaming guidance rather than applying SDR advice by habit. YouTube specifies 10-bit video and compatible BT.2020 colour primaries and matrix with PQ or HLG transfer characteristics. Its OBS instructions describe a hardware HEVC encoder for the RTMPS HDR procedure and identify an OBS version requirement; check the current page before using those instructions. An SDR HEVC file is not automatically ready to be sent as HDR, and converting it does not create genuine HDR picture information.
Make the choice before leaving a stream overnight
A useful test is a short private or unlisted broadcast, checked in YouTube Studio, before you rely on the configuration for a full night. Confirm the selected ingest route, whether the stream is receiving video and audio, and whether YouTube reports issues with the incoming signal. Watch for dropped frames in OBS and make sure the source loops or advances as intended.
Keep a note of the working configuration: OBS version, source file properties, protocol, output encoder, resolution, frame rate, keyframe interval, and bitrate. If a later update changes the encoder list or a replacement file behaves differently, that record gives you a point of comparison. It is especially useful when several people maintain a channel or when a devotional, study, or news schedule has to keep running across routine changes.
If the channel's main requirement is that a prepared video continues as a 24/7 YouTube broadcast without your computer staying on, a managed workflow can remove the need to keep a local OBS session running. StreamNeo turns an uploaded video into a YouTube live stream, so the specific pain of keeping a computer and local playback session running is no longer part of that workflow. It is still worth testing that your source is ready and checking the channel's current YouTube 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
Can OBS play an HEVC file?
OBS can play video files as Media Sources, and its documentation lists common containers that can hold HEVC. Whether a particular file plays depends on its details and your OBS and decoding setup, so test the file instead of assuming either universal support or universal failure.
Does an HEVC source mean OBS sends HEVC to YouTube?
No. The source codec is what OBS reads; the stream output encoder is configured separately. Check the encoder selected for streaming and the YouTube ingest protocol to determine what OBS is sending.
Does YouTube Live support HEVC through OBS?
YouTube's encoder guidance lists HEVC for RTMP/RTMPS, and its HLS documentation also describes HEVC and lists OBS as a capable encoder. Those documents do not guarantee that every OBS build, hardware encoder, source file, or destination configuration will work without adjustment.
Should I convert HEVC to H.264 before streaming?
Only if a test shows that the HEVC file cannot be decoded reliably, or that your intended output setup cannot use a supported protocol and encoder combination. If the file plays and the outgoing setup is supported, conversion is not required solely because the source is HEVC.