If YouTube shows a stream health warning while your encoder is set to CBR, check the warning itself and the stream configuration it names. CBR controls how the encoder handles bitrate; it does not verify that the video, audio, keyframes, format or connection match YouTube’s requirements.
Start in Live Control Room or the Live Dashboard, note the exact message and its timestamp, then compare the stream actually being sent with the selected ingestion settings. Work through the warning category rather than changing several encoder values at once.
Start with YouTube’s specific message
YouTube’s health indicator evaluates the incoming stream and displays timestamped messages beside it. The wording matters: a bitrate warning, a keyframe warning and an incorrect-format warning point to different checks. YouTube classifies red errors as critical, which may prevent an event from starting or cause problems for viewers; yellow errors are moderate and may reduce quality. A warning that remains unresolved can continue to appear. See YouTube’s live streaming error messages for the current categories and their descriptions.
Write down the full message, its time, and whether it appeared during setup or after the broadcast began. If you changed settings shortly before it appeared, record those too. This creates a useful baseline: if the warning is about keyframes, changing the audio format is unlikely to help; if it names the resolution, first check the actual output dimensions rather than assuming the bitrate mode is at fault.
Treat these mappings as a way to prioritise checks, not as a diagnosis of a stream you cannot inspect. For example, a bitrate warning could involve the configured target or the upload connection available at that moment. A format message may refer to the selected ingestion workflow. YouTube’s error page is the authority for the message you see; do not substitute a generic encoder checklist for its specific instructions.
If the message is not clear, check the selected stream settings in YouTube and compare them with the encoder’s output. For a custom stream key with manually chosen resolution settings, the selected configuration is particularly important. YouTube’s encoder settings and bitrate guidance varies recommendations by codec, resolution and frame rate. Keep the settings page open while checking rather than relying on a remembered value or one copied from another channel.
What CBR does and does not confirm
Constant bitrate, or CBR, is a bitrate-encoding mode. In practical terms, it asks an encoder to keep its output bitrate relatively steady around a target rather than letting it vary freely with the complexity of each moment. YouTube recommends CBR for live encoding, so leaving it enabled is a sensible starting point. It is not a general stream validation setting.
YouTube checks properties separately. A stream can use CBR and still have a target bitrate that does not fit its selected codec, resolution and frame rate. It can also have an unsupported or mismatched format, incorrect dimensions, an unsuitable frame rate, a keyframe interval outside the recommendation, or invalid audio. Missing or multiple audio or video streams can also trigger a warning. CBR cannot correct any of those conditions.
Think of the incoming stream as a set of related choices, not one encoder switch. The codec defines how the video is encoded; resolution and frame rate describe its picture output; bitrate describes the amount of encoded data; keyframes and GOP structure affect how frames are grouped; audio has its own format and stream count. The connection must then carry the total output reliably. A warning can come from any one of these layers while the CBR setting itself is correct.
For a practical diagnosis, change only the setting related to the message, then test again. If you change codec, resolution and bitrate together, a cleared warning will not tell you which adjustment mattered. If the settings are managed by software or a cloud service, check the output configuration and YouTube’s selected ingestion settings; do not assume that a CBR label proves every other field is correct.
Check bitrate for the stream configuration
Keep CBR selected, then verify the numerical target against the exact ingestion configuration. YouTube’s recommendation is not one universal bitrate. The relevant value depends on codec, resolution and frame rate, and the Live Control Room may reflect the selected ingestion settings. Use YouTube’s current table for the combination you are sending, not a value copied from a different resolution or codec.
As listed on YouTube Help’s encoder settings page in October 2026, its examples for H.264 are 17 Mbps for 1080p60, 14 Mbps for 1080p30, and 8 Mbps for 720p60 or 720p30. For AV1 or H.265/HEVC, the examples are 12 Mbps at 1080p60, 10 Mbps at 1080p30, and 6 Mbps at 720p60 or 720p30. These are YouTube’s recommended examples for those configurations, not universal targets or guarantees of a healthy stream. Check the page for other combinations and confirm which codec and ingestion settings apply to your stream.
| Check | What to compare | What to do if they differ |
|---|---|---|
| Codec | The encoder’s actual output and YouTube’s selected ingestion configuration | Use a codec supported for that workflow, then recheck its applicable bitrate recommendation |
| Resolution | Actual encoded dimensions and selected ingestion resolution | Match the configured output to the selected resolution, or choose a lower supported resolution if needed |
| Frame rate | Actual output frame rate and selected configuration | Make them agree, then use the recommendation for that rate |
| Bitrate | Encoder target and YouTube’s recommended value for the combination | Adjust the target for that combination; do not treat the mode alone as sufficient |
| Upload capacity | Total bitrate for all feeds versus available outbound bandwidth | Reduce the load or choose a lower output if the connection cannot support it reliably |
A correct target still depends on the connection. YouTube recommends leaving 20% room within available outbound bandwidth for the total stream bitrate, and notes that other use of a shared connection can reduce what is available to an individual stream. This is headroom, not an encoder setting: a target that appears correct on paper can still exceed the capacity available during a busy evening. See YouTube’s streaming tips for its advice on bandwidth and testing.
If the available upload cannot support the selected output with headroom, lower the resolution where the workflow allows it and check the corresponding bitrate recommendation again. Do not increase the target simply because YouTube shows a bitrate warning before checking the actual upload capacity. Conversely, do not reduce bitrate arbitrarily without confirming that the new target fits the selected configuration. The aim is a compatible output the connection can carry, not the largest number in the table.
For a long-running channel, include every feed sharing the same connection in the capacity check. A primary and backup feed, other household traffic, or another upload can use bandwidth that seemed available during a quiet test. The guide to running a recorded-language lesson stream all day is also relevant when the content is pre-recorded: continuous playback does not remove the need to match output settings and account for the connection.
Verify codec, resolution and frame rate
Check what the encoder is actually sending, rather than only what its interface is set to request. YouTube’s live encoder guidance lists H.264, H.265/HEVC and AV1 for RTMP/RTMPS workflows, but the supported choice depends on the selected ingestion configuration. A format warning may point to a mismatch between the chosen workflow and the output, so follow the applicable error message and settings page rather than assuming a codec is interchangeable in every setup.
Resolution is the dimensions of the encoded picture. Confirm that the output dimensions agree with the ingestion resolution selected in YouTube. A preset with a familiar label can be misleading if the actual output has been scaled or the selected stream settings specify something else. If the error mentions unsupported dimensions or a resolution mismatch, inspect both sides of that pairing before adjusting bitrate.
Frame rate is likewise an independent output property. Confirm the actual frame rate and the rate selected for the stream, then check the recommendation and error message for that configuration. YouTube’s encoder guidance supports up to 60 fps, but an error message or selected configuration can specify a lower maximum. Do not assume that because a preset offers a particular rate it is suitable for every stream key or ingest setup.
YouTube also says incoming video should be progressive; interlaced video is not supported. If you see an interlacing or format-related warning, check whether the encoder is sending progressive frames. That is separate from CBR and from the numerical bitrate target.
A stable channel often benefits from a configuration that is straightforward to repeat. Choose a resolution and frame rate your source material and connection can sustain, then make the encoder and YouTube settings agree. If the source is a still devotional image with music, for instance, a high frame rate may not add useful motion detail; the right choice still depends on the output and ingestion configuration rather than a universal rule. For more involved format handling, the guide to streaming multiple video formats in one YouTube loop can help frame the issue of matching varied source files to a consistent output.
Review keyframe frequency
Keyframes are independently decodable reference frames in the video stream. YouTube recommends a keyframe frequency of two seconds and says not to exceed four seconds. This is not the same as CBR: an encoder can hold bitrate mode constant while emitting keyframes at the wrong interval. Check the keyframe interval directly in the encoder or encoding workflow when the warning names keyframes or GOP timing.
Some interfaces express the interval in seconds; others express it as a number of frames. At 30 frames per second, YouTube’s error guidance illustrates a two-second interval as one keyframe every 60 frames. If you enter a frame count, convert from the actual frame rate rather than reusing a number from another profile. The official error guidance describes keyframe-related errors and their context.
If the encoder exposes a GOP option, YouTube recommends a closed GOP for optimal transcoding. GOP means group of pictures: it defines how frames are grouped around keyframes. Not every interface makes this control visible, and labels vary, so check the encoder documentation if you cannot find it. Do not change unrelated GOP options based on a guess; first establish whether the warning points to keyframe frequency or structure.
Frame rate and keyframe frequency are connected in the way an encoder translates a time interval into frames. A two-second interval corresponds to a different frame count at 60 fps than at 30 fps. This is why a copied “60” value is not automatically correct: it would represent two seconds at 30 fps, but not at 60 fps. Set the intended interval in seconds where possible, or calculate the frame count from the configured output rate.
After a change, start a test stream and watch for the same health message. If it persists, note the timestamp and check that the encoder really applied the new profile; a saved preset that is not active will not change the output. For low-level encoder workflows, timestamp handling can also matter, as discussed in the FFmpeg guide to configuring timestamps for a YouTube replay stream. That is a separate check from keyframe interval, but it illustrates why a stream’s apparent settings and actual output both matter.
Check audio and stream count
A video encoder set to CBR can still send audio YouTube cannot use, or no audio at all. Confirm that an audio stream is present and that its format matches the requirements for the selected workflow. YouTube’s RTMP/RTMPS settings guidance lists AAC or MP3 audio; its error messages also identify unsupported audio codecs, channel configurations, missing audio and multiple audio streams as possible issues. Follow the specific message for sample-rate and channel requirements rather than assuming that every configuration accepts the same values.
Check the number of tracks or streams being sent, not just whether you can hear sound in the encoder preview. YouTube lists absent or multiple audio/video streams among potential problems. A playlist or scene setup can accidentally route more than one audio source, or a file may lack an audio track even though the video itself plays correctly. Confirm that the outgoing stream has the intended single audio and video streams for the selected setup.
For a test, listen at the YouTube end as well as at the encoder. The preview can confirm local playback while failing to tell you whether the transmitted stream has the expected format or track count. Include representative audio in the test: speech, music or other sound similar to what viewers will hear in the actual channel. A silent test does not exercise the same audio path as a bhajan loop or a local news programme with narration.
If the warning says audio is missing or unsupported, address that before changing video bitrate. If the warning identifies multiple streams, inspect scene routing, playlist tracks or muxing settings. Keep notes on what changed so you can restore the prior working configuration if the test introduces a new issue.
Test the complete configuration before relying on it
A test should resemble the real broadcast closely enough to exercise its moving parts. YouTube recommends testing with audio and motion similar to the planned event and monitoring health messages during the broadcast. A static image and muted track may not reveal a problem that appears only when motion increases or audio begins. Test the actual encoder profile, file or scene, audio path, and network that you intend to use.
Check the health indicator during the test, and note new warnings with their timestamps. If a warning appears only after some time, compare what changed: the connection may have become busier, the source may have switched, or a different scene may have introduced another track. You cannot infer the cause from timing alone, but it gives you a more useful starting point than changing every encoder option at once.
For a 24/7 channel, repeat the check after a meaningful change to the source, output profile, stream key settings or network arrangement. A test that passed before a playlist was replaced does not verify the new files or audio routing. If you need a continuous channel without leaving a personal computer running, StreamNeo removes that specific need to keep your own computer on for the broadcast; it does not remove the need to choose compatible stream settings or check YouTube’s health messages.
Keep a short record of the working configuration: selected codec, resolution, frame rate, bitrate target, keyframe interval, audio format, and the warning status observed in YouTube. This is useful when a profile is changed or another person takes over the channel. It also helps distinguish a persistent configuration error from a temporary change in available upload bandwidth.
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
Why is YouTube warning me when CBR is enabled?
CBR concerns bitrate encoding mode only. YouTube checks other properties independently, including the numerical bitrate, format, codec, resolution, frame rate, keyframe frequency and audio. Use the exact warning to decide which check to make first.
Does CBR mean my bitrate target is correct?
No. CBR does not select or validate the correct numerical bitrate for your stream. Compare the target with YouTube’s recommendation for the selected codec, resolution and frame rate, then consider whether your connection has enough outbound capacity with headroom.
What keyframe interval should I check?
YouTube recommends keyframes every two seconds and says not to exceed four seconds. If the encoder asks for a frame count, calculate it from the actual frame rate; YouTube’s example for 30 fps is 60 frames for two seconds. Check closed GOP as well if your encoder exposes that control.
What should I do if the warning keeps returning?
Read the message and timestamp again, verify the output actually matches the saved encoder profile, and test the real programme with representative sound and motion. Change the setting related to the warning, then observe whether that message clears or another one appears. If it persists, use YouTube’s current error guidance for that specific category.