For a general YouTube Live stream, use constant bitrate, set the keyframe interval to two seconds, and choose the bitrate for your codec, resolution and frame rate. For H.264, YouTube’s live guidance also recommends progressive scan, two B-frames, one reference frame and CABAC.
You do not need to find a supposed universal YouTube profile or preset. YouTube does not mandate one H.264 profile or one encoder preset for every live stream, so test the complete configuration with representative movement and audio before relying on it overnight.
The short answer: what to set
Start with these choices:
- Rate control: CBR, or constant bitrate.
- Keyframe interval: two seconds. Do not set it above four seconds; YouTube’s live guidance, checked in September 2026, gives four seconds as the maximum interval.
- Bitrate: use YouTube’s recommendation for the selected codec, resolution and frame rate.
- H.264 scan mode: progressive.
- H.264 B-frames: two.
- H.264 reference frames: one.
- H.264 entropy coding: CABAC.
- Transport: RTMPS where your encoder offers it.
- Profile and preset: choose an available setting that your encoder can sustain, then validate it with a real test. Do not treat High Profile or a particular software preset as a universal live requirement.
These settings describe the stream sent to YouTube, not the quality of the original video file. A clean 1080p recording can still produce a poor live broadcast if the encoder cannot maintain its target bitrate or the upload connection repeatedly falls behind.
Start with YouTube’s live encoder guidance
YouTube separates live ingestion from uploaded-video encoding. For a live stream, an encoder sends a continuous stream to YouTube, which receives it and creates the viewer versions. An encoder may be software running on a computer or a standalone hardware video encoder for live streaming. YouTube describes both approaches in its encoder setup guidance.
The important distinction is that the live page tells you how to send that continuous stream. It does not require you to reproduce every setting from YouTube’s upload recommendations. The YouTube live encoder settings page is the primary reference for live codecs, protocols, bitrates, keyframes and advanced options.
YouTube lists H.264, H.265/HEVC and AV1 for live video. The useful choice depends on what your encoder exposes, what your computer or hardware can process continuously, whether you are sending SDR or HDR, and how much upload capacity is available. There is no need to change codec merely because another codec appears newer. A setting that runs steadily is more useful than one that is theoretically efficient but drops frames during a long broadcast.
YouTube also says to choose a quality that is reliable for the available upload connection and recommends running a speed test. A speed test is only a starting point. Your stream needs a sustained connection, not a brief result reached when nothing else is using the line. This matters particularly for channels running from a shared home connection, a shop, an office or a mobile network.
If your channel uses a prepared playlist, the encoder settings are only one part of the system. You also need to check the source files and transitions. For example, guidance on preventing black frames between videos on a YouTube loop stream addresses a problem that bitrate changes will not fix.
Set CBR and choose the bitrate for the format
CBR means constant bitrate. The encoder aims to send data at a steady rate instead of allowing the bitrate to vary widely from one scene to the next. Set the rate-control mode to CBR, then enter a bitrate value. CBR alone is not the value; it is the method used to control the value.
Choose the number from YouTube’s live recommendation for the codec, resolution and frame rate you are actually sending. The following table shows the H.264 figures from YouTube’s live guidance. They are platform recommendations, not results from an independent study.
| Ingest resolution and frame rate | H.264 minimum | H.264 recommended |
|---|---|---|
| 2160p at 60 fps | 14 Mbps | 50 Mbps |
| 2160p at 30 fps | 11 Mbps | 42 Mbps |
| 1440p at 60 fps | 8 Mbps | 34 Mbps |
| 1440p at 30 fps | 7 Mbps | 21 Mbps |
| 1080p at 60 fps | 6 Mbps | 17 Mbps |
| 1080p at 30 fps | 5 Mbps | 14 Mbps |
| 720p at 60 fps | 3 Mbps | 8 Mbps |
| 720p at 30 fps | 3 Mbps | 8 Mbps |
| 480p at 30 fps | 0.4 Mbps | 4 Mbps |
| 360p at 30 fps | 0.4 Mbps | 4 Mbps |
For example, if your devotional loop is 1080p at 30 fps and uses H.264, the table gives 14 Mbps as the recommended ingest bitrate and 5 Mbps as the minimum listed value. That does not mean a connection that briefly reaches 5 Mbps is a sensible choice. Leave room for other traffic and for normal variation in the connection.
A 60 fps stream is not automatically better. It sends more motion information and may suit a gaming or camera stream, but it also asks more from the encoder and connection. A mostly static prayer card, study timetable or ambience scene may be easier to operate at 30 fps. Pick a frame rate that matches the source material and that the system can hold without dropped frames.
Do not copy the H.264 figures across to HEVC or AV1 without checking YouTube’s current table. YouTube provides separate bitrate guidance for those codecs. The codec, frame rate and resolution are connected choices, so changing one of them can change the appropriate bitrate.
If the stream shows dropped frames caused by an overloaded connection, lowering the bitrate or choosing a less demanding format may help. The diagnosis matters: encoder overload, network congestion and YouTube-side processing are different problems. The guide on fixing a YouTube Live bitrate that is too high is useful when the symptom is dropped frames, but do not lower settings blindly before checking which counter is increasing.
Set a two-second keyframe interval
A keyframe is a complete reference image in the compressed stream. The frames between keyframes can describe changes from an earlier reference, which saves data but makes the stream depend on that reference being available. The keyframe interval controls how often those complete reference points are inserted.
Set the interval to two seconds. If your encoder asks for a frequency rather than a duration, the value must match the frame rate. At 30 fps, two seconds corresponds to 60 frames. At 60 fps, it corresponds to 120 frames. Some encoders let you enter the interval in seconds, while others ask for a keyframe distance in frames.
YouTube recommends two seconds and says not to exceed four seconds. This is a live-stream instruction, not a reason to copy a keyframe value from a video-export workflow. If your encoder has both an automatic keyframe option and a manual interval, use the manual two-second value when the control is available.
A wrong keyframe interval may not be obvious in a short preview. The stream can look acceptable while the timing makes recovery, joining and processing less predictable. Check the actual encoder field rather than assuming that a preset labelled “streaming” has selected the value you need.
For an overnight channel, keyframes are especially worth checking after a software update or profile change. Some applications expose the setting under Output, Advanced, GOP size, I-frame interval or Keyframe distance. The label varies, but the intended timing remains two seconds.
Configure the documented H.264 options
If you use H.264, configure the advanced options that YouTube lists for live encoding:
- Progressive scan: send complete frames in normal progressive order rather than interlaced fields.
- Two B-frames: allow two bidirectional frames where the encoder supports the control.
- One reference frame: use one reference frame for the listed live configuration.
- CABAC: use Context-Adaptive Binary Arithmetic Coding when the encoder exposes the option.
- Square pixels: avoid a non-square pixel aspect ratio unless your source workflow specifically requires it.
- Rec. 709 for SDR: use the listed colour space for standard dynamic range content.
These are separate from CBR and keyframes. Choosing CBR does not automatically prove that the advanced H.264 fields are correct, and selecting two-second keyframes does not set the colour space. Open the encoder’s advanced controls and review each available field.
The names can differ between software and hardware. One application may show B-frame count, while another places it under codec options. A hardware encoder may expose fewer controls than desktop software. You should not invent a value for a control that is unavailable. First satisfy the documented settings that your encoder exposes, then test the resulting stream.
For HDR, YouTube’s guidance recommends H.265 over RTMP(S), and AV1 is not supported for HDR according to that guidance. That is a different case from a normal SDR devotional, music, news or study channel. If you are preparing HDR, check the current official instructions rather than applying an SDR configuration with a different colour label.
Audio is part of the live configuration as well. YouTube lists AAC and MP3 for live audio. Its guidance lists 44.1 kHz for stereo and 48 kHz for 5.1, with 128 Kbps stereo and 384 Kbps 5.1 as the listed audio bitrates. Most small continuous channels use stereo, but a quiet video with a broken or delayed audio track can still make the stream feel unreliable. Test the actual audio route, not only the video encoder.
Profile and preset are not universal commands
The H.264 profile describes a set of codec capabilities. The encoder’s preset usually balances processing effort against compression efficiency, and the available names depend on the encoder implementation. They are related to the way the stream is encoded, but they are not interchangeable settings.
YouTube’s live encoder guidance does not name one required H.264 profile. It also does not specify one universal encoder preset such as a particular software speed mode. Therefore, do not tell every reader to use High Profile, or to use a named preset, as though YouTube Live requires it.
The confusion often comes from YouTube’s separate upload page. The recommended upload encoding settings include upload-specific guidance such as H.264 High Profile and variable bitrate. Those instructions concern a file uploaded for processing. They are not evidence that YouTube Live requires High Profile or variable bitrate at ingest.
For live streaming, choose a profile that your encoder and target devices support, provided it does not conflict with YouTube’s documented live settings. If the application offers a broadly compatible default and your test is stable, there may be no practical reason to force a more demanding profile. If you are using a named hardware preset, check that hardware manufacturer’s current documentation for what the preset actually changes.
The same applies to presets. A slower preset may use more processing time, while a faster preset may leave more headroom for a modest computer. The right choice depends on the encoder, resolution, frame rate, scene complexity and whether the device must also play a playlist, capture a camera or render overlays. There is no honest single preset recommendation for every channel.
Watch the encoder’s CPU or hardware-load indicator during a representative scene. A static logo can hide an overload that appears when a news ticker moves, a camera pans, a devotional video changes scene or a game produces rapid motion. If the encoder cannot maintain its output, reduce the workload or change the format before the scheduled broadcast.
Use RTMPS and test the complete stream
YouTube lists RTMP and RTMPS as live transport protocols and recommends RTMPS. Use RTMPS when your encoder supports it. The transport choice does not replace correct bitrate, keyframe or codec settings; it is the route used to send the configured stream to YouTube.
Paste the stream key into the encoder carefully and keep it private. A stream key is an access credential for the live ingest path, so do not place it in a screenshot, public tutorial or shared document. If you suspect it has been exposed, use YouTube’s current channel controls to replace or reset it.
Run a private or otherwise appropriate test before the real broadcast. YouTube’s own instruction is direct: “Make sure to test before you start your live stream.” Use the same resolution, frame rate, codec, bitrate, keyframe interval, audio and transport that you plan to use later.
The test should resemble the real programme. For a lofi station, include the moving visualiser and continuous audio. For a local news loop, include the ticker, transitions and speech. For a temple or church channel, include a real camera segment or representative sermon audio if that is part of the planned stream. A test made only from a still image can miss the load created by motion and scene changes.
While testing, check three places:
- The encoder: look for dropped frames, skipped frames, rendering lag, encoding overload and audio warnings.
- The network: watch for upload instability and network-related dropped frames rather than relying only on a speed-test result.
- YouTube’s stream health: confirm that the ingest is recognised and that warnings do not appear when the representative content is running.
Do not stop the test immediately after the preview appears. Let the source run through the scenes that are most demanding, then review whether the counters remain stable. The aim is not to prove that a stream can connect once. It is to find out whether the chosen settings remain sustainable for the type of broadcast you intend to leave running.
If you are building a channel around recorded files, test the hand-off between files as well as the encoder. A playlist can be technically connected while still showing a gap, a black frame or a silent transition. For a longer playlist, streaming different videos without a gap requires attention to the source and playback workflow as well as YouTube’s ingest settings.
Make the configuration practical for a 24/7 channel
Save a copy or screenshot of the working configuration, excluding the stream key. Record the resolution, frame rate, codec, bitrate, keyframe interval, audio settings and the profile or preset that was actually tested. This makes it easier to restore the stream after an update or a change of computer.
Decide where the encoder will run. A local computer gives you direct control, but it must stay powered, connected and available for the entire broadcast. A Windows VPS can be useful for some workflows, although it adds its own setup and monitoring tasks; the guide on setting up a Windows VPS for a continuous YouTube stream covers that category of arrangement.
For a prerecorded channel, StreamNeo removes the need to keep your own computer running: upload the video, add the YouTube stream key and let the broadcast run while the service monitors and restarts it if the stream drops. It is suited to YouTube-only channels where the main problem is keeping a prepared file live continuously, rather than producing a live camera programme with changing scenes.
Whichever route you choose, keep a recovery plan. Know where the source file is stored, how to replace the stream key, how to confirm the broadcast from another connection and how to restart the encoder without changing the tested settings. If the channel matters overnight, check it from a phone or another network rather than assuming that a running application window proves viewers are receiving a healthy stream.
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
Does YouTube Live require H.264 High Profile?
No. YouTube’s live encoder guidance does not name High Profile as a required H.264 profile. High Profile appears in YouTube’s separate upload encoding guidance, so do not transfer that upload recommendation into a live requirement.
What is the best YouTube Live preset?
There is no universal preset named by YouTube for every encoder. Presets vary by software, hardware and processing load, so choose one your encoder can sustain and verify it with representative movement, audio and stream-health checks.
Should the keyframe interval be two seconds or 120 frames?
Both can describe the same interval when the stream runs at 60 fps: two seconds equals 120 frames. If the encoder asks for frames rather than seconds, calculate the value from the selected frame rate and confirm the result in a test.
Can I use the H.264 bitrate table for AV1 or HEVC?
Do not assume that the H.264 values apply to another codec. YouTube provides codec-specific live recommendations, so check the current official table for AV1 or H.265/HEVC before setting the bitrate.