YouTube’s resolution warning means the video arriving from your encoder does not match the resolution selected in the stream’s Ingestion Settings, or that primary and backup feeds have different resolutions. Read the entire timestamped warning in Live Control Room before changing anything: when YouTube says a resolution is unsupported, its message gives the expected dimensions.
Do not assume that the file’s resolution, an OBS canvas setting and the encoded video sent to YouTube are the same. Nor should you treat “not optimal” as another way of saying “not supported”; YouTube uses these as distinct messages, and the wording points to different conclusions.
Read the full warning before changing settings
Open YouTube Studio, go to the active stream in Live Control Room, and find the resolution message beside the stream-health indicator. Record the complete text and its timestamp. The timestamp helps you connect the warning with what was happening then: a stream starting, a playlist moving to its next file, or a configuration change, for example.
YouTube says that “The Live Dashboard and Live Control Room checks for errors in the stream you're sending to YouTube.” Its live streaming error messages page explains that these checks report issues with the incoming feed. A warning is therefore a prompt to inspect what YouTube received, not a reliable diagnosis based only on the media file’s properties.
Keep the exact phrasing. If it says the current resolution “is not supported for this configuration,” look for the expected video resolution included later in the message. If it says the current resolution “is not optimal,” preserve that distinction while investigating. The words are useful evidence; paraphrasing both as “resolution mismatch” can lead you to change a setting the warning did not identify as wrong.
The Live Control Room also marks errors by severity. YouTube describes red errors as critical, potentially stopping an event from starting or causing viewer problems, and yellow errors as moderate, potentially reducing quality. Colour is useful context, but it does not replace the message. Start with the stated problem and dimensions, not with a general attempt to improve every stream setting.
Write down the timestamp, current resolution, expected dimensions if shown, and whether the warning appeared at startup or during playback. If you are troubleshooting a channel that needs to run overnight, this small record is more useful than changing settings from memory. You can compare it with the next health check and identify whether the same issue returns at the same point.
Find the resolution selected for ingestion
In the stream’s settings, locate the selected ingestion resolution. This is YouTube’s expected incoming video size for that configuration. YouTube’s help page states: “Your video must be the height and width of the resolution you chose on the Ingestion Settings page.” Both dimensions matter; matching the width but not the height is not a match.
Compare this selection with the expected dimensions in the warning. If YouTube says the current resolution is unsupported and names an expected size, that is the relevant target for this configuration. Do not substitute a familiar resolution just because it is common in tutorials, or because a different video on your channel used it successfully. The correct choice depends on the active stream’s settings and the feed you intend to send.
There may be a choice of where to correct the mismatch. If the selected ingestion resolution is appropriate for your stream, adjust the encoder’s output dimensions to match it. If your workflow is deliberately producing another size and the available YouTube configuration allows it, select the matching ingest setting instead. Make one considered change rather than altering both sides at once; otherwise, it becomes difficult to tell what resolved the warning.
YouTube’s Live Streams API reference represents resolution and frame rate as stream configuration fields. Its listed fixed values are API configuration choices, not a recommendation to pick one for every channel. The reference also includes automatic detection as a value; variable resolution and variable frame rate must be selected together. That detail is relevant if you manage settings through the API, but it does not override the dimensions named in your Live Control Room warning.
Compare the incoming encoded dimensions
The value YouTube checks is the width and height of the video arriving from the encoder. A prerecorded file’s properties tell you about the source, but not necessarily what the encoder sends. A source may be scaled to a different output size, and a canvas or project setting may not describe the final encoded feed either.
Inspect the settings that determine the encoder’s outgoing video dimensions. In OBS, for example, check both Base (Canvas) Resolution and Output (Scaled) Resolution. If output scaling is enabled, the latter is especially relevant to the size being encoded. Confirm the result against the complete warning rather than inferring it from a preview window or from the original file alone.
This distinction matters when you prepare a playlist. One item might have different dimensions from the others, while the encoder continues to send a fixed output size; alternatively, a workflow may change its output between items. If the warning timestamp lines up with a file change, inspect that item and the output behaviour at the transition. For a continuous channel, the OBS AMD encoder settings for a 24/7 YouTube video playlist can help you review the broader playlist setup, but use YouTube’s warning as the authority for the expected resolution.
Check width and height separately and avoid relying on a label such as “HD”. Labels can hide differences in aspect ratio or exact dimensions. If a media information tool reports the file size in pixels, note those two values; then compare them with the encoder’s output setting and the ingest selection. You do not need to buy new hardware to fix a mismatch unless you have evidence of a separate hardware fault.
A rain loop or still-image ambience stream may appear visually simple, but its outgoing dimensions still need to match the selected ingestion setting. The practical concern is the encoded feed, not whether the picture contains motion. If the source itself has a different size, decide whether the encoder should scale it or whether the ingest configuration should be changed, then verify the resulting output.
Check primary and backup feed consistency
If your stream uses primary and backup feeds, compare the resolution settings on both. YouTube’s error guidance identifies different primary and backup resolutions as an issue. A primary feed that matches the selected ingest resolution does not settle the question if the backup sends another size when failover occurs.
Record each feed’s outgoing width and height, along with its relevant encoder configuration. Keep the primary and backup aligned in resolution and other settings that must remain consistent for your failover arrangement. Then check whether the warning timestamp corresponds with a switch or connection problem. Do not infer from the message alone that a failover happened; use your setup and stream history to establish that.
For a small channel running a playlist, there may be no separate backup feed at all. Do not spend time searching for failover settings if your stream has only one feed. Instead, focus on the single encoded output and, if the message recurs, whether it appears when a particular playlist item begins.
Apply only the dimensions the warning identifies
When the full message says the current resolution is unsupported and supplies an expected video resolution, use those expected width and height values as the reference for correcting the encoder output or selected ingestion configuration. Do not replace them with a universal 720p or 1080p target. The expected dimensions are specific to the active configuration, so a setting that works for another stream is not evidence that it is right for yours.
If you change OBS output scaling, verify that the output dimensions now match the chosen ingest setting. If you change the selected ingestion resolution instead, confirm that the encoder sends that newly selected size. Avoid changing unrelated settings such as bitrate, audio sample rate or codec unless another warning points to them. Multiple simultaneous changes make diagnosis harder and may introduce problems unrelated to resolution.
For a prerecorded playlist, inspect each file’s dimensions and compare them with the intended output. You may choose to standardise source files or keep a consistent scaled output, depending on your workflow. Consistent frame rate, audio sample rate and codecs across playlist items can also make the wider workflow easier to manage, but those properties are not substitutes for correcting a resolution warning. For a separate issue with sound over long playback, see how to fix OBS audio drift in a long-running YouTube lofi stream.
If you are operating from a computer that must remain on to loop prerecorded material, that creates a different operational question from the dimensions themselves. StreamNeo can remove the need to leave that computer running by turning an uploaded video into a YouTube live stream; the source file and YouTube ingest settings still need to be checked if the resolution warning appears. The warning is not proof that changing how you keep a stream running will correct a source or configuration mismatch.
Test the stream and recheck its health
After making one relevant change, reconnect or restart the feed as your streaming workflow requires, then look for a fresh message in Live Control Room. You are checking whether YouTube now receives the selected dimensions and whether the same warning returns. Do not treat an old timestamp as evidence of a current problem; distinguish the earlier alert from a new health check.
If the warning returns, note its new timestamp and wording. Confirm the selected ingest resolution again, then verify the encoder’s actual output rather than assuming a saved setting took effect. If the warning appears only when the playlist advances, inspect the item and transition at that point. If it appears when the backup takes over, compare that feed’s settings with the primary.
YouTube’s health panel may show other errors alongside the resolution message. Handle each according to its own wording. A bitrate warning, dropped frames, or an audio problem does not establish that the resolution is wrong, and changing resolution does not necessarily address those issues. The guide to exact fixes for yellow or red stream-health warnings is useful for separating issues, but the current official message should guide your response to this one.
A short test before relying on a stream overnight is practical, especially after changing scaling or playlist files. Check that the feed starts, that the expected dimensions remain in place through a file change, and that Live Control Room does not show a new resolution warning. This does not guarantee that a stream will remain uninterrupted; it confirms only what you observed during the test.
Unsupported is not the same as not optimal
YouTube’s example wording distinguishes two cases. One says, “The current resolution is X, which is not optimal.” Another says the current resolution “is not supported for this configuration” and gives an expected resolution. Do not collapse these into one diagnosis: “not optimal” is YouTube’s assessment of the current resolution, while “not supported for this configuration” explicitly identifies a configuration incompatibility and provides dimensions to use.
When the message says unsupported, compare the received dimensions with the named expected dimensions and correct the mismatch. When it says not optimal, do not claim that the feed is unsupported or that it cannot start. Review the selected setting and actual output, then decide whether a change is appropriate for the stream. The exact message and the rest of the stream-health information matter; the phrase alone does not justify an invented explanation about why YouTube considers that resolution less suitable.
Colour and wording answer different questions. Red or yellow indicates the severity category YouTube assigns to an error; “unsupported” or “not optimal” describes what the resolution message says. Use both pieces of information, but let the complete message determine what you investigate. If the stream is already running, avoid a disruptive change based solely on a paraphrase or a remembered warning from a previous session.
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 does YouTube warn about resolution in my prerecorded RTMP stream?
The encoded video arriving at YouTube may differ from the resolution selected in Ingestion Settings. A source file’s dimensions or an encoder canvas setting alone may not tell you the outgoing dimensions. Read the full warning and compare the selected ingest resolution with the encoded output.
What resolution should my encoder send to YouTube?
Use the dimensions selected in the active Ingestion Settings. If the warning says the current resolution is unsupported, use the expected width and height shown in that message rather than assuming a universal target. If it says not optimal, keep that wording distinct and review the configuration before deciding whether to change it.
Can a playlist cause the warning to appear only sometimes?
Yes, a warning that begins at a playlist transition is a reason to inspect the file that just started and the encoder’s output behaviour. The source items may differ, but YouTube checks the incoming encoded video. Compare its dimensions with the selected ingest resolution and check whether the warning recurs at that transition.
Do primary and backup feeds need the same resolution?
YouTube identifies different primary and backup resolutions as an issue, so compare both feeds and align their resolution settings. Check the timestamp and your failover history before concluding that a switch caused a particular warning. If you use only one feed, concentrate on that feed’s output instead.