The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →For a straightforward YouTube Live setup with Restreamer, use H.264 video and AAC audio over RTMP or RTMPS. That is a practical baseline, not a guarantee that every MP4 file will work: MP4 is a container, and the video and audio codecs inside it matter. Restreamer can pass a compatible incoming stream through or encode using H.264/libx264; choose based on the actual source and the options available in your installed build.
Keep the source, Restreamer processing, and YouTube ingest separate
A working stream depends on three different things: what Restreamer can receive, whether it copies or encodes that input, and what YouTube accepts over the selected ingest protocol. A filename extension alone does not answer all three.
As an Amazon Associate I earn from qualifying purchases.
- Source into Restreamer: Restreamer’s source wizard lists HTTP, HTTPS (including HLS and DASH), RTP, RTSP, RTMP, and SRT network sources. The actual video and audio codecs still need to be checked. Restreamer source wizard documentation.
- Processing in Restreamer: the source documentation describes passthrough, which copies the unedited video stream, and an H.264/libx264 encoding option. Passthrough does not convert an unsuitable codec into a suitable one. Available options can vary by build, so check the settings in your installed version. Restreamer source documentation and encoding documentation.
- Publication to YouTube: Restreamer’s YouTube guide describes using Publication Service with a valid YouTube streaming ID. Publication sends the stream to a remote destination using a configured output, such as HLS, RTMP, or SRT, and a streaming key. Restreamer YouTube guide and publication documentation.
- YouTube ingest: the accepted codec, audio, and transport details depend on whether the destination uses RTMP/RTMPS or HLS. Follow the instructions for the selected ingest path.
Recommended RTMP or RTMPS settings
YouTube’s live encoder settings list H.264, H.265/HEVC, and AV1 video for RTMP/RTMPS, with AAC or MP3 audio. For a broad-compatibility starting point, use H.264 and AAC. YouTube recommends RTMPS, the secure extension to RTMP.
| Setting | YouTube guidance |
|---|---|
| Frame rate | Up to 60 fps |
| Bitrate mode | Constant bitrate (CBR) |
| Keyframe interval | Two seconds recommended; no more than four seconds |
| SDR color | Rec. 709; 8-bit |
| Video options | Square pixels, progressive scan, two B-frames, one reference frame, and CABAC |
| Stereo audio | AAC or MP3; YouTube’s advanced recommendations include 44.1 kHz and 128 Kbps |
| 5.1 audio | For RTMP/RTMPS, 5.1 surround is supported only with AAC; YouTube lists 48 kHz and 384 Kbps |
The YouTube page’s displayed H.264 bitrate recommendations include 14 Mbps for 1080p at 30 fps, 17 Mbps for 1080p at 60 fps, and 8 Mbps for both 720p at 30 fps and 720p at 60 fps. These are the values shown on the cited English-language page; recommendations can change, and YouTube lists different values for HEVC and AV1. Check the current table for the codec, resolution, and frame rate you intend to send.
#1 Best Overall
These are encoder-to-YouTube ingest settings, not a promise that every viewer receives the same encoded stream. YouTube says it transcodes a live stream into multiple output formats for viewers. Test with representative movement and sound, and watch stream health during the test.
Use different rules for HLS
HLS is a separate YouTube ingest route, not another name for RTMP. YouTube’s HLS setup guidance supports H.264 or HEVC video and AAC, AC3, or EAC3 audio. It requires MPEG-TS segments that are 1–4 seconds long, a rolling playlist with no more than five outstanding segments, HTTPS POST/PUT, and no encryption other than HTTPS. HLS has higher latency because it sends segments instead of one continuous stream.
The TS-segment requirement applies to YouTube’s HLS instructions. Do not treat it as a universal YouTube Live file-format requirement or apply it to RTMP/RTMPS without reason.
Recommended Free Tools
HDR needs a separate configuration
For HDR, YouTube’s HDR live-streaming guidance specifies HEVC video, 10-bit depth, BT.2020 color primaries and matrix coefficients, and either ST 2084 PQ or HLG transfer characteristics matching the source. YouTube’s general encoder guidance recommends HEVC for HDR and says AV1 is not supported for HDR. Do not use the SDR Rec. 709 and 8-bit recommendations for an HDR stream.
For an HDR HLS output, YouTube also specifies TS segments of 1–4 seconds, a rolling playlist with no more than five outstanding segments, and HTTPS POST/PUT. Match both the HDR signal characteristics and the selected ingest protocol.
Choose passthrough or encoding
Passthrough
Use passthrough when the incoming video stream already has the codec and properties you intend to publish, and the audio and output path are also suitable. It copies the video rather than re-encoding it, so it avoids a conversion step—but it cannot fix an incompatible source.
Rank #4
H.264 encoding
Choose Restreamer’s H.264/libx264 encoding option when the incoming stream needs conversion to H.264 for the planned YouTube output. Confirm that your installed Restreamer build offers the needed encoder and set output properties to match the target protocol and YouTube recommendations. Do not assume Restreamer automatically converts every unsupported input.
Set up and check a YouTube publication
- Inspect the source: identify its protocol, container, video codec, and audio codec. Do not infer codecs from a suffix such as
.mp4. Restreamer’s documentation does not provide a complete file-container-and-codec compatibility table for every build; use the connection check or probe information available in your installed version. - Choose processing: select passthrough if the input already matches the destination needs, or configure H.264 encoding if conversion is necessary and supported by the build.
- Configure the YouTube output: in Restreamer, select Publication Service, enter a valid YouTube streaming ID, save, and connect, following the YouTube guide. Set output for the actual ingest route—RTMP/RTMPS or HLS—rather than borrowing settings across protocols.
- Provide audio: Restreamer’s wizard notes that services such as YouTube require an active audio channel. If the source is silent, configure silent audio rather than leaving the required channel absent.
- Run a representative test: include motion and sound like the real stream. Check YouTube stream health and the output bitrate displayed in Restreamer’s main window.
- End the event cleanly: Restreamer’s YouTube guide advises ending the stream on YouTube first. Interrupting it in Restreamer may prevent YouTube from saving the DVR archive.
Troubleshoot common format and connection failures
| Symptom | Likely issue | What to check |
|---|---|---|
| YouTube rejects or does not play the output | The source’s actual codecs or output protocol settings do not match the intended ingest. | Check the codecs inside the source, confirm RTMP/RTMPS versus HLS, and verify the configured output against YouTube’s instructions for that route. |
| Passthrough connects, but the stream is unsuitable | Passthrough copies the incoming video instead of converting it. | Use a compatible source or configure a supported encoder such as H.264/libx264. |
| YouTube reports stream health problems | Encoder settings may not meet the selected resolution, frame rate, bitrate, or keyframe guidance. | Check CBR, the current codec-specific bitrate table, frame rate up to 60 fps, and the two-second recommended keyframe interval (four seconds maximum). |
| Video works but audio is missing | The source may have no audio channel, or the audio codec may not suit the ingest route. | Confirm an active audio channel; for a silent source, configure silent audio. Match audio choices to RTMP/RTMPS or HLS requirements. |
| HLS output fails despite apparently valid video settings | HLS has segment and playlist requirements that do not apply as a generic RTMP rule. | Check TS segments, 1–4 second duration, rolling playlist limit, HTTPS POST/PUT, and encryption restrictions in YouTube’s HLS instructions. |
| HDR appears wrong or is rejected | SDR settings or mismatched HDR metadata may be used. | Verify HEVC, 10-bit, BT.2020, and PQ or HLG matching the source; use the HDR instructions for the chosen ingest path. |
Copyright and YouTube live rules still apply
A technically valid stream is not automatically permitted content. Before publishing a recording, confirm you have the rights to its video and audio, including music and embedded third-party material, and review YouTube’s current copyright and live-streaming policies. A codec or container choice does not establish permission to rebroadcast content.
Or let it run in the cloud
If your goal is an always-on YouTube stream of uploaded videos, StreamNeo is a separate cloud option rather than a Restreamer format setting: upload a recording or build a playlist, add your YouTube stream key, and go live. Nothing has to stay on at home; it loops your uploads in the cloud, supports any quality up to 4K 60fps at one price per slot, and can automatically recover if YouTube drops the stream. The first day is free with no card. Monthly is $9.99 per month. See StreamNeo, then start your free first day.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
