A YouTube stream-health warning after an FFmpeg codec change is a clue, not a diagnosis. Read the exact warning first, then compare the settings you changed with YouTube’s ingest guidance and return to a configuration you know worked before testing again.
There is no single FFmpeg command that fits every build, input, encoder, resolution, frame rate and ingest protocol. Without the warning text and your old and new settings, a safe recovery is a parameter-by-parameter process rather than a guessed replacement command.
Capture the warning and the changes
Open Live Control Room and record the complete health message, including its issue type and any corrective text. A paraphrase such as “the stream is unstable” may hide the useful distinction between an unsupported codec, an open GOP, a bitrate problem or a feed that is not arriving steadily. Keep the message visible while you investigate; do not make several changes first and then try to remember what YouTube reported.
Next, note exactly what changed in FFmpeg. Compare the previous command or configuration with the current one, including video and audio encoder names, codec options, resolution, frame rate, bitrate mode and value, keyframe interval, GOP mode and output protocol. If you use a script, save both versions. A small change to an encoder-specific option can have a different effect from changing the codec name itself.
Also note when the warning began. Did it appear as soon as the stream connected, after a resolution change, or only when the source became more complex? If you changed a setting and the warning appeared immediately, that is useful evidence, but not proof that the setting is responsible: a network or source problem may have started at the same time.
Keep the ingest mode in view. YouTube’s published encoder guidance in YouTube Help describes its recommendations for RTMP/RTMPS, but the protocol and encoder options you are actually using still matter. A setting accepted by one FFmpeg build or backend is not necessarily available, interpreted identically or appropriate in another.
If you maintain a loop or playlist, keep the content path separate from the encoding change. The guide to making FFmpeg rotate through videos concerns the input sequence; first establish whether the warning concerns the outgoing stream rather than a file transition. That separation helps avoid “fixing” a playlist when the encoder setting is at fault.
Identify the warning category
Use the issue type to decide which parameter deserves attention first. Google’s YouTube Live Streaming API health messages list categories and corrective descriptions. Match the text as closely as possible, rather than treating every warning as a generic signal to lower quality.
| Warning category | First comparison to make | Avoid changing first |
|---|---|---|
| Video codec or encoder | Selected codec, encoder implementation and ingest mode | Resolution and bitrate together |
| Keyframe or GOP | Keyframe interval, GOP size and open/closed GOP setting | Audio settings |
| Bitrate or ingestion starvation | Configured bitrate against YouTube guidance and sustained upload capacity | Codec, frame rate and bitrate all at once |
| Resolution or frame rate | Output dimensions and actual frame rate against the intended mode | Unrelated GOP options |
| Audio | Audio codec and whether audio is present in the stream | Video encoder preset |
| Primary/backup mismatch | Codec, profile, dimensions, frame rate, keyframes and audio/video rates on both feeds | One feed in isolation |
The table is a triage aid, not a substitute for the message. A warning about a primary and backup feed, for example, calls for comparing the feeds with each other as well as checking whether each feed is otherwise supported. Changing only the primary may leave the mismatch in place.
If the text points to ingestion starvation, separate encoder configuration from network delivery. A stream can be encoded at an appropriate rate and still fail to reach YouTube consistently if the available outbound connection cannot sustain it. If you record locally, check whether the recording continues to grow; that can help distinguish a live-ingest problem from a stopped input or encoder, though it does not by itself establish the cause.
Check the codec and encoder backend
For RTMP/RTMPS, YouTube’s current published guidance lists H.264, H.265/HEVC and AV1 video, AAC or MP3 audio, CBR bitrate encoding and frame rates up to 60 fps. Confirm your actual ingest mode and the encoder implementation in use before applying that list. Codec support in YouTube’s guidance does not mean that every local FFmpeg build has the encoder available or that every option applies to it.
Identify both the output codec and the encoder name. In FFmpeg, a codec such as H.264 can be produced through different encoder backends, and their private options may differ. Check the local build’s encoder help or documentation for the selected encoder. If a changed option is unrecognised, silently ignored or has a backend-specific meaning, the command line alone may not tell you what output you are actually producing.
When the warning explicitly identifies an unsupported codec, change only the implicated codec selection to one supported for the actual ingest path and available in your build. Keep the other output properties fixed for the first test. If the message concerns audio, make the corresponding audio change rather than switching the video encoder unnecessarily. This makes it possible to tell whether the correction addressed the reported issue.
FFmpeg’s official documentation describes general options and notes that encoder-specific options depend on the selected encoder. Treat a generic example command found elsewhere as a starting point for understanding option names, not a configuration to paste unexamined. The same option can be unavailable or behave differently across builds and backends.
For a long-running channel with a repeatable file source, retain a known-good copy of the complete configuration, not only the command’s codec fragment. The AAC rather than MP3 audio encoding guide may help when the warning is specifically about audio, but do not switch audio format to address a video codec issue.
Review resolution and frame rate
Read the reported output resolution and frame rate, not merely the source file’s properties. A source may have one frame rate while the encoded output is set to another, and a scale filter may alter dimensions. Confirm what FFmpeg is sending and compare it with the mode you intended to stream.
YouTube’s guidance allows frame rates up to 60 fps. That is an upper limit in the cited guidance, not a recommendation that every channel should stream at the maximum. A static devotional image, a lofi visual loop and fast-moving gameplay have different motion characteristics and encoding needs. Select a resolution and frame rate the source, encoder and connection can sustain, then keep them stable while diagnosing another category.
Bitrate recommendations are conditional on codec, resolution and frame rate. YouTube Help’s published H.264 examples list 5 Mbps minimum and 14 Mbps recommended for 1080p30; 6 Mbps minimum and 17 Mbps recommended for 1080p60; and 3 Mbps minimum and 8 Mbps recommended for 720p30. These are not interchangeable targets for every codec or stream. Consult the current YouTube bitrate and resolution guidance for your specific mode rather than selecting a number from another row.
If bitrate or starvation is implicated, compare the configured stream rate with the appropriate guidance and with sustained outbound capacity. Leave enough room for connection variation; a connection that can briefly upload at a given rate may not sustain it throughout a live session. Do not infer that a lower resolution alone will solve a connection issue without checking the actual output rate and delivery warning.
If you changed several of resolution, frame rate and bitrate together, return to the last known values and alter one at a time. This is slower than swapping a whole command, but it gives each test a useful result. For a wider review of the choices involved in a continuous channel, see how to optimise a 24/7 YouTube live stream.
Restore a known-supported configuration
Begin recovery from the last configuration that produced a healthy stream, if you still have it. Restore the full relevant set of values, including encoder, codec, output dimensions, frame rate, bitrate mode and rate, audio configuration, GOP options and protocol. Do not assume that changing only the codec label restores the previous behaviour if the other parameters changed at the same time.
If no known-good copy exists, use YouTube’s current guidance and your encoder’s own supported options to build a conservative baseline for the exact ingest mode. Keep the source and output mode simple, choose a supported codec available in the build, and avoid adding private encoder flags unless their meaning is clear for that backend. Record the resulting configuration so it becomes a reference if a later change causes trouble.
For keyframes, YouTube recommends a two-second frequency and says not to exceed four seconds. FFmpeg documents -g as a GOP size in frames. Converting an interval to frames involves multiplying by the output frame rate: at 30 fps, two seconds corresponds to 60 frames. This conversion does not guarantee that all encoders interpret GOP-related private options alike, so verify the selected encoder’s documentation and the warning itself.
Pay particular attention to open GOP. YouTube’s API health reference identifies open GOP as unsupported and asks for closed GOP. FFmpeg documents -cgop as disabling closed GOP and enabling open GOP, which is the opposite of the desired mode for this warning. If -cgop appears in the changed settings, remove it when restoring closed GOP behaviour, then check the selected encoder’s own controls rather than assuming that one flag settles every implementation.
Do not try to correct a GOP warning by changing resolution, audio codec and bitrate at the same time. For a bitrate warning, the implicated repair may instead be a different rate or output mode; for an audio warning, the video GOP is unlikely to help. If you are operating from India and weighing a continuously running local setup against other operating choices, the 24/7 stream cost guide for India provides context, but it does not replace checking the exact health message.
Test before relying on the stream
After restoring the baseline, run a private or otherwise appropriate test before depending on the stream for a scheduled programme. YouTube recommends testing with audio and movement similar to the eventual broadcast, then monitoring stream health. A still image with silence will not expose the same problems as a moving playlist with music, speech or changing scenes.
Keep the test long enough to observe whether the warning clears and whether it returns when the relevant content or transition appears. Watch the Live Control Room messages while the stream is running. If the warning recurs, note its exact text and time rather than changing several parameters immediately. A configuration that connects successfully is not necessarily healthy under sustained load.
For a suspected starvation issue, observe whether delivery remains steady while the source continues and compare the configured bitrate with the connection’s sustained upload capacity. If a local archive is enabled, confirm that it continues to grow. A growing local file with a struggling live feed suggests different paths may be involved, but it does not prove the network is the only issue.
Make one targeted adjustment for each repeated warning, then test again with the same representative material. Keep a short log of the setting changed, the message before and after, and the test conditions. If a change worsens health or introduces a new warning, revert that change rather than stacking another guess on top of it. For an always-on channel, this disciplined sequence is more useful than restarting repeatedly without preserving what happened.
StreamNeo can remove the particular burden of keeping your own computer running and watching for a dropped broadcast when the task is simply to turn an uploaded file into a continuous YouTube stream; it does not diagnose an FFmpeg configuration or make codec warnings irrelevant. If you are troubleshooting a stream you intend to run directly through FFmpeg, resolve and test that configuration on its own terms.
What to include when seeking targeted help
If the warning remains after a controlled test, share evidence that lets someone compare what YouTube reports with what FFmpeg is configured to send. Include the complete warning text and its issue category, the time it occurred, the FFmpeg version and build information, and the selected video and audio encoders. State the ingest protocol, output resolution, frame rate, bitrate mode and value, keyframe interval, GOP mode and relevant encoder-specific options.
Include the old and new settings if you have them, and identify the exact change after which the warning began. If the command contains a stream key or other private credential, redact it before sharing. The useful details are the relevant options and output behaviour, not access credentials.
For an ingestion-starved warning, add what you know about sustained outbound capacity and whether a local recording continues to grow. For primary and backup feeds, provide the corresponding settings for both feeds so that parity can be checked. If the source is a playlist or file loop, say whether the warning appears at a transition or throughout the stream.
Avoid asking for “the right FFmpeg command” without those particulars. A precise repair depends on build, input, backend, protocol and output mode; the title of a warning alone cannot supply them. With the warning and configuration together, help can focus on the implicated parameter instead of proposing an unrelated full rewrite.
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 about my stream after I changed the codec?
The warning may identify the codec itself, but it can also concern a related setting changed at the same time, such as GOP, bitrate, resolution, frame rate or audio. Read the issue type in Live Control Room and compare the old and new configuration before editing further.
How do I fix an unsupported video codec warning?
Confirm the ingest mode and the encoder build, then select a video codec supported for that path and available in your build. Change only that implicated setting first and test; a universal command cannot be chosen without the exact configuration.
What GOP or keyframe interval does YouTube need?
YouTube recommends a two-second keyframe frequency and says not to exceed four seconds. FFmpeg’s GOP size is expressed in frames, so translate the interval using the output frame rate and verify the selected encoder’s option behaviour; also check that the mode is closed GOP if YouTube reports open GOP.
How can I tell whether the warning is bitrate or my internet connection?
Use the health message to distinguish a bitrate configuration issue from ingestion starvation, then compare the rate with YouTube’s guidance for the actual codec, resolution and frame rate and with sustained outbound capacity. A local recording that continues to grow can provide a clue, but it does not by itself establish the cause.