OBS showing “connected” does not, by itself, mean that YouTube has published your event as live. For a scheduled encoder stream, check the intended event in Live Control Room, wait for its preview, then select Go live unless you have enabled auto-start.
The useful distinction is between OBS’s encoder-side status and YouTube’s event state. If YouTube has no preview, check where OBS is sending the feed and whether it has the current credentials for that stream; if a preview is present, follow YouTube’s health message and confirm the event’s start step.
What OBS’s connected status tells you
Treat OBS’s indicator as one piece of evidence about the encoder connection, not as confirmation that the right YouTube event is live. YouTube’s documented scheduled-stream workflow has separate steps: send a feed, wait for a preview in Live Control Room, and start the event there unless auto-start is enabled. The YouTube guidance does not define the exact internal meaning of OBS’s “connected” label, so it is better not to infer more from that word than the workflow supports.
That separation explains the apparent contradiction. OBS can report a connection while you are viewing a different scheduled event, while YouTube is still waiting for you to start the event, or while the incoming feed has not yet produced a preview. The encoder status and the event’s viewer-facing state are not the same check.
First identify which of these you actually see. Is there no preview tile at all? Is there a preview but the event is marked offline? Or is there a preview accompanied by a health warning? Each points to a different next action. Changing bitrate or buying equipment before identifying the state can create new variables without addressing the reason the event is offline.
Check the intended scheduled YouTube event
Open Live Control Room from the event you mean to broadcast, rather than assuming the currently open page is the destination OBS is using. Compare the event title, channel and scheduled time with your plan. This matters if you manage more than one channel or keep separate events for different programmes: a feed arriving at one stream does not automatically mean the event open in another tab has received it.
If you run separate content on more than one channel, keep a written mapping of each channel, event and encoder profile. The practical approach in planning different schedules for two YouTube channels is relevant here: a simple naming convention can prevent you from sending a devotional loop to the channel or event intended for a news rotation. The mapping does not replace checking the destination in YouTube, but it makes a wrong selection easier to spot.
For a scheduled encoder stream, YouTube’s workflow is to send the stream, wait until the preview appears, then click Go live. Do not treat the schedule time alone as proof that a broadcast has started. You may have reached the event’s scheduled start without completing its separate start action.
Also check whether you are looking at the correct event’s Live Control Room rather than the channel’s public watch page or a different dashboard view. The event page is where you can see incoming preview and stream health. Once you deliberately start the event, verify the public or unlisted watch page as a separate check; YouTube recommends checking that viewers can access the stream from the channel and watch pages. See YouTube’s guidance for creating a live stream with an encoder for the event workflow.
Compare OBS’s server URL and current stream key
If no preview appears, confirm the destination in OBS against the settings for the intended stream in YouTube. Check the server or stream URL and the current stream key as a pair. A correct key copied from an old event or a different channel is not necessarily the right credential for the event you are inspecting.
In Live Control Room, open the settings for the selected stream and compare the displayed destination details with OBS’s streaming settings. Avoid pasting the key into chat, screenshots, a public document or a support post. YouTube describes stream keys as akin to a stream’s “password and address”; treat them as secret credentials. Its live streaming settings guidance explains where these settings are managed.
If you reset or replaced the key, update the encoder with the new value before sending again. A key reset does not update an already saved OBS profile automatically. Make the change deliberately, then reconnect and return to the matching event to see whether a preview appears. Do not repeatedly reset a key simply because the event is offline; first make sure you are comparing the current values for the intended stream.
If you use multiple OBS profiles or scenes, verify which profile is active and which destination its stream settings contain. A familiar scene can still be paired with another channel’s credentials. For a visual broadcast such as an internet radio station, the article on adding a visualiser to a YouTube livestream can help you think about the programme’s content separately from the destination settings; keep those two checks distinct while diagnosing.
Wait for the Live Control Room preview
After confirming the event and destination, start or resume sending the feed from OBS and give Live Control Room time to register it. Watch the event page for an incoming preview rather than relying on OBS’s status alone. A preview is evidence that YouTube is receiving a feed for that event, but it does not itself publish the event as live.
If the preview appears and the event remains offline, check the event’s start controls. For a scheduled stream, select Go live when you are ready unless auto-start is enabled. Preview is a readiness check; it is not the same action as making the event live. This distinction matters when you want to check framing or audio privately before viewers can watch.
The video in preview is useful for a quick content check. Confirm that the intended loop or scene is visible and that sound is present if the programme includes audio. If the image is black, frozen or showing the wrong source, the fact that YouTube has a preview does not establish that the programme is ready for viewers. Check what OBS is actually sending before starting the event.
Use the event’s status and health panel alongside the preview. A feed can be present but have an error that calls for attention. In that case, read the specific message before changing settings. YouTube’s stream health and error guidance is a better starting point than applying a generic encoder preset to every offline symptom.
Click Go live unless auto-start is enabled
When the intended scheduled event has a preview and you are ready to publish it, click Go live in Live Control Room unless you have configured auto-start for that stream. Do not assume auto-start is enabled just because OBS is sending a feed or because the event is scheduled. Check the stream settings if you expect the encoder to start the event automatically.
Auto-start changes the event-start behaviour; it does not make the preview and event status interchangeable. If you are unsure whether the setting is on, use the explicit Go live control when the event is ready rather than waiting on an assumed setting. If you are intentionally using auto-start, verify the actual event status after sending the feed instead of treating the OBS indicator as confirmation.
After starting, check the watch page as a viewer would. Confirm that the event is accessible from the channel or its direct watch page and that the picture and sound continue. A successful start action is not the last operational check for a long-running channel; keep an eye on stream health as the programme runs.
For an always-on channel, the distinction between preparing a feed and publishing it is still useful even if your programme repeats for hours. The guide to keeping video quality consistent across a 24/7 playlist covers a related operational concern: a stable-looking loop does not remove the need to check what the audience actually receives.
Troubleshoot when no preview appears
If the event remains without a preview, use the following sequence. It starts with destination checks because they are simple to verify and directly connected to the symptom; it moves to encoder, source and network checks only after the selected stream appears correct.
| What you see | What to check next |
|---|---|
| No preview in Live Control Room | Confirm the intended event is open, then compare OBS’s server URL and current stream key with that stream’s settings. Confirm OBS is sending to that destination. |
| Preview appears, but event is offline | Use Go live when ready unless auto-start is enabled; check the event’s actual status afterwards. |
| Preview appears with a health error | Read the specific message and follow the relevant YouTube troubleshooting guidance. |
| Feed is present but looks or sounds poor, or drops | Check the sources routed to OBS, encoder errors and CPU load, then investigate outbound connectivity. |
Do not start by changing every encoding setting. First read the health indicator and any error attached to the stream. YouTube’s Live Control Room checks the stream being sent and can surface errors; that message gives you more useful evidence than an offline label alone. If it identifies a format issue, investigate the stated format. YouTube’s error reference, for example, identifies H.264 video and AAC audio in connection with format mismatch errors, and describes keyframe-frequency issues between primary and backup streams. These are targeted checks, not universal fixes for an absent preview.
If a preview exists but the feed is poor or intermittent, inspect the source routed to OBS: the selected video, audio input, media playback and scene. YouTube advises checking the encoder for errors and CPU load, as well as testing outbound internet strength. Poor picture or sound can originate in the source; if the source looks and sounds right in the encoder but the stream degrades, network delivery becomes a more relevant branch to examine. You do not need to buy hardware merely because a stream is offline.
For a looping file, compare what the player is showing locally with what the preview shows, then watch for pauses or buffering in the outgoing feed. The FFmpeg buffering troubleshooting guide concerns a different encoder path, but its useful general lesson is to distinguish playback/source problems from YouTube event controls. Do not apply FFmpeg commands to OBS; use the principle of isolating the source and feed.
If the basics are correct and the message points to a format problem, make one relevant change at a time and send the feed again. Avoid treating a particular bitrate, codec preset or keyframe value as the cure unless the health message or the official format requirements support that change. For questions about a stream that is present but not healthy, YouTube’s streaming tips provide further checks on the broadcast and connection.
If the stream continues to fail after these checks, record the exact error and the time it appeared, without sharing your stream key. Use YouTube’s report-a-problem path for ongoing YouTube-side issues, or the relevant encoder’s support route for problems specific to that software. A concise record of the event, health message and change you tried will make escalation more useful than a screenshot that exposes credentials.
Keeping the diagnosis useful for a 24/7 channel
A one-off start problem can become a recurring overnight failure if the operator has no clear handover. Keep a short run sheet near the machine or in your operations notes: channel name, event name, the OBS profile that belongs to it, where the current key is managed, and the steps for confirming preview and event state. Do not write the key itself into an unsecured note. The point is to make the destination and start action unambiguous when you are tired or another person is covering the channel.
Record what state you observed before changing anything: no preview, preview without a live event, or preview with a health error. Then note the single corrective action and whether the viewer-facing page became accessible. This gives you a practical history without pretending that one successful restart proves a permanent fix. If the same pattern returns, you can tell whether it is consistently a start-step omission, a credential mismatch or a feed-health issue.
If keeping a dedicated computer running is the pain point for a repeated file-based broadcast, StreamNeo can take that computer out of the overnight loop: you upload the video, provide your YouTube stream key, and the broadcast runs while your own computer is off, with monitoring and automatic restart if it drops. It is YouTube-only, so the intended channel and event still need to be checked in YouTube, and the event’s preview and start behaviour still matter.
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 OBS say connected while YouTube says offline?
OBS’s status is not sufficient proof that YouTube has published the intended event. Check that Live Control Room is open on the right scheduled stream, then look for its preview and complete the event’s start step when ready.
Does seeing a preview mean viewers can watch?
No. A preview shows that a feed is arriving for the event, but it does not by itself publish that event as live. For a scheduled encoder stream, select Go live unless auto-start is enabled, then verify the watch page.
Should I replace the stream key if there is no preview?
Not as the first step. Compare OBS’s server URL and current key against the settings for the intended stream; if the key has been reset, update OBS with the current one. Keep the key private.
What should I check if the preview has an error?
Read the Live Control Room health message and follow the issue it identifies. For a poor or dropping feed, check the source, encoder errors and CPU load, then outbound connectivity; change format settings only when the evidence points to a format mismatch.