A YouTube Live stream health warning is a prompt to investigate the incoming stream, not proof that your recorded video is the problem. Read the exact message beside the Health Indicator in Live Control Room, then adjust the encoder or connection setting that message identifies and check the stream again.
The warning may concern format, codec, bitrate, audio, video, resolution or keyframe frequency. The same diagnostic approach applies whether you send the video with OBS, another encoder or a cloud-based workflow: follow the warning rather than changing settings at random.
Start with the message in Live Control Room
Open Live Control Room and find the Health Indicator for the event. Note the complete warning text and its timestamp before you change anything. YouTube displays error messages alongside stream health, and a warning can recur while the underlying issue remains. A change that appears to help briefly is not enough if the same message returns.
Pay attention to the severity as well as the words. YouTube describes red errors as critical; they may inhibit an event or cause problems for viewers. Yellow errors indicate a moderate issue that may affect quality. Treat either as a reason to investigate, but do not assume that every yellow warning means the broadcast has stopped or that every red warning has the same cause. The specific message is the useful diagnostic clue.
Write down when the warning appeared and whether it persists, clears or returns. If you changed an encoder setting just before it appeared, record that too. This gives you a simple before-and-after comparison and avoids losing track when several messages arrive during a test.
YouTube’s live streaming error messages page groups problems by the issue reported, including format, bitrate, audio and video configuration, resolution and keyframe frequency. Use it to interpret the wording you see. An OBS-specific search may be useful if that is your encoder, but the warning is about what YouTube receives; it is not inherently an OBS or prerecorded-video warning.
Check what the encoder is sending
Before adjusting a value, check the outgoing stream configuration. Confirm which encoder and protocol are in use, what video and audio codecs are selected, and whether audio and video are both enabled. Compare those details with the warning and YouTube’s current instructions for your stream type. A label in an encoder’s settings is not enough if the actual outgoing stream differs from what you intended.
For RTMP or RTMPS, YouTube lists H.264, H.265 (HEVC) or AV1 for video and AAC or MP3 for audio in its encoder guidance. Those are not a reason to switch codecs without a matching warning. Check the exact message and protocol, because accepted settings can depend on the configuration. YouTube also describes problems such as incorrect format, unsupported audio settings, interlaced video, or a missing or multiple audio or video streams. If the warning names one of these, inspect that part of the output rather than lowering bitrate as a reflex.
A stream can be technically connected while still sending an unexpected configuration. For example, an audio track may be disabled, a source may produce more than one stream, or the video may be interlaced when the warning calls for a different format. If you use a playlist or a file-based encoder workflow, check that the encoder is still sending the intended audio and video after a file change. This is a useful distinction from a warning about insufficient bandwidth: a quiet or absent audio stream is not fixed by changing the network.
If the warning describes a connection or bandwidth problem, check the upload connection at the time the stream is running. A speed test taken at another time is only a clue, not a guarantee of what the connection can sustain during the event. Other devices, wireless interference or a changing connection can affect available upload capacity. Use a stable connection where practical, and compare the encoder’s chosen output with what the connection can reliably carry.
If you keep a local encoder running overnight, a power or network interruption can also affect delivery. That is a separate operational issue from a codec warning. A checklist for automatically starting a PC after a power outage may help you think through recovery for a computer-based workflow, but it does not diagnose the specific Live Control Room message.
Change the setting named by the warning
Make one relevant adjustment at a time, then allow the stream to settle and check Live Control Room again. Changing several values together can make it difficult to tell which one mattered, and can introduce a new problem while you are trying to address the original one. If the warning remains, return to its exact wording and the matching section of YouTube’s guidance rather than cycling through unrelated encoder presets.
For a bitrate or insufficient-bandwidth warning, use YouTube’s live encoder table for the combination you actually send: codec, resolution and frame rate. YouTube does not offer one universal live bitrate suitable for every stream. Its recommended figures vary by those settings, so do not take a number from an upload-video guide or another resolution and assume it applies. You can review the live encoder settings, bitrates and resolutions guidance and run an upload speed test as YouTube advises. Choose a quality the connection can carry reliably, not simply the highest setting available in the encoder.
If the chosen resolution is too demanding for the available upload bandwidth, lower it to a supported resolution and consult the live table for the new combination. Then set the bitrate accordingly. Lowering resolution without revisiting bitrate, or lowering bitrate without considering frame rate and codec, can leave the output mismatched. Make the change at the encoder that creates the outgoing stream; altering the recorded source file does not necessarily change the stream configuration being sent.
For a keyframe or GOP warning, check the keyframe interval and frame rate together. YouTube recommends a two-second keyframe frequency and says not to exceed four seconds. The error guidance notes that changing frame rate may require a corresponding change to keyframe frequency. If the warning concerns GOP structure, check the encoder’s relevant option; YouTube’s guidance describes closed GOP as required for optimal transcoding in relevant configurations. Do not adjust keyframes to address an audio warning.
For an audio warning, check that audio is enabled and that the outgoing stream has the requested audio configuration. Follow the message for details such as format, channel count or sample rate. YouTube’s encoder settings list 44.1 kHz and 128 kbps as recommended advanced settings for stereo audio, but use the current instructions for your protocol and the warning you have. A warning about missing audio calls for checking the audio stream itself; merely changing its bitrate may not restore a disabled track.
For video configuration or resolution warnings, inspect the video stream the encoder is producing: format, scan type, dimensions and frame rate. Match the specific warning to the corresponding setting. If it reports an unsupported or unexpected configuration, changing bitrate alone will not convert interlaced video to progressive or correct a wrong resolution. Make the smallest change that addresses the stated issue, then verify the result.
Recheck the preview and health status
After the adjustment, inspect the incoming preview in Live Control Room. Check that the picture is present, the expected video is playing, and the audio can be heard. Then look at the current stream health and the message list again. A setting change is only a test until YouTube reports the updated stream and you can confirm that it looks and sounds right.
Allow enough time for the new output to reach YouTube and for the interface to reflect it. Check whether the original warning clears, whether it returns, and whether a different warning replaces it. If the original persists, review the timestamp and confirm that you changed the encoder setting actually being used by the live event. It is possible to change a saved profile while the active broadcast uses another one.
YouTube recommends testing before an event, checking the preview and monitoring audio and video quality. For a scheduled stream, start the encoder early enough to inspect the incoming feed before you rely on it. The live metrics guidance also explains where stream status and health appear. Continue to monitor after a change rather than assuming a clear indicator at one moment settles the issue for the rest of a long broadcast.
If you run a recorded playlist through an encoder, test more than the opening seconds. Confirm that playback continues when one file ends and the next begins, and check that audio remains present across the transition. A problem at a file boundary may suggest a change in the outgoing stream, but the warning still tells you which category to investigate. For a playlist-based setup, a guide to streaming a YouTube Live playlist from an S3 bucket with FFmpeg can help you understand the role of the playlist and encoder configuration; use the warning itself for this diagnosis.
Separate bitrate warnings from other causes
Bitrate gets attention because it is adjustable and can affect how much data the connection must carry. But a stream health warning is not automatically a bitrate warning. YouTube documents distinct categories for format, codec, audio and video configuration, resolution and keyframe frequency. An adjustment that reduces bitrate may be irrelevant to a missing audio stream or an incorrect format, and can reduce picture quality without resolving the reported issue.
Use the message to choose a branch. The table is a quick sorting aid, not a replacement for YouTube’s detailed instructions or the exact text shown in your event.
| Warning category | First check | Avoid assuming |
|---|---|---|
| Bitrate or bandwidth | Match bitrate to codec, resolution and frame rate; compare with available upload capacity | That one bitrate fits every live stream |
| Format or codec | Check the protocol and the actual outgoing video and audio formats | That changing bitrate changes the codec |
| Keyframe frequency or GOP | Check the interval alongside frame rate and GOP settings | That a frame-rate change leaves keyframes appropriate |
| Audio configuration | Confirm audio is enabled and inspect the setting named in the message | That a video adjustment will restore audio |
| Video configuration or resolution | Check the outgoing dimensions, scan type and frame rate | That prerecorded content is itself the cause |
Severity gives you a second way to prioritise, but it does not identify a setting. A red critical error deserves prompt attention, especially if the event or viewers may be affected. A yellow moderate warning can still matter during a long channel run, where a quality issue may persist unnoticed. Use both pieces of information: severity tells you how urgent the problem may be, and the message points towards what to inspect.
The same discipline helps with recurring or intermittent warnings. If the message returns during busy network periods, compare the event conditions and upload capacity with your encoder output. If it returns at a file transition, check the stream configuration around that transition. These observations narrow the search; they do not prove a cause until the relevant setting and incoming preview support it.
Make the fix practical for a long-running channel
For a one-off event, you may have time to watch the encoder and adjust it manually. A 24/7 channel needs a repeatable test routine, because an apparently small configuration mismatch can remain in place through the night. Keep a short record of the encoder, output profile, protocol, warning text and change made. If you need to revisit the problem, that record is more useful than a vague note that the stream was “unstable”.
Run a test before making a profile your normal setting. Check the image and sound in the preview, observe whether the warning clears, and let the stream continue long enough to expose a recurring issue. If you change frame rate, revisit keyframe frequency; if you change resolution, revisit the bitrate recommendation for that configuration. Keep the test focused so you can connect the outcome to the adjustment.
Also distinguish a transmission issue from a content workflow issue. A file may have a silent section or a playback gap without the encoder failing; conversely, a clean source file can be sent with an incorrect stream configuration. For a music channel, separate the health warning from questions about loudness and balance. The guide to loudness normalisation for a 24/7 YouTube music radio stream covers a different audio-quality task; it is not a substitute for fixing an ingestion warning.
If the warning is resolved but you cannot keep a local computer and encoder running through the hours you need, StreamNeo removes that specific burden by letting you upload a video, add your YouTube stream key and leave the broadcast running without your computer switched on. That addresses the need to keep a computer-based encoder available; it does not make YouTube’s warning categories irrelevant, nor does it guarantee a particular health status. StreamNeo is for YouTube, so check that it suits your workflow before relying on it.
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
Is a stream health warning caused by prerecorded video?
Not necessarily. YouTube’s documented warnings concern the incoming stream and its configuration, including format, bitrate, audio and video settings, resolution and keyframes. Check the exact message before changing the recorded file or assuming its prerecorded nature is the cause.
Should I lower bitrate whenever a warning appears?
No. Lower bitrate is relevant when the warning points to bitrate or insufficient bandwidth, and the right setting depends on codec, resolution and frame rate. For other warnings, follow the named configuration issue instead.
Does this advice only apply to OBS?
No. The diagnostic steps apply to encoder-based streams generally. The menu names vary by encoder, but you can use the warning to identify the relevant output setting in OBS or another encoder.
What if the warning returns after I change a setting?
Check that the active event is using the profile you changed, then read the warning and timestamp again. If it persists, compare the current output against the relevant YouTube instructions and test one targeted change at a time. A cleared message is not a guarantee that every other stream setting is correct, so keep checking preview and health.