OBS saying it is streaming means it is attempting to send a feed from your computer; it does not confirm that YouTube has received it. YouTube Studio saying the event is offline can also mean the feed has arrived but a scheduled broadcast has not yet been started for viewers.
Work through the checks in order: open the intended event in Live Control Room, look for its preview and stream-health messages, compare that event’s URL and key with OBS, then inspect the encoder and network. If the event is scheduled, wait for its preview and select Go live in Live Control Room before treating it as live.
Why the two status messages can disagree
OBS reports the local state of its connection attempt. YouTube Studio reports what YouTube sees for a particular stream or scheduled event, and whether that event has been taken live. Those are related but separate facts. An OBS status reading “Streaming” does not establish that the right YouTube event is receiving data, that the feed is healthy, or that viewers can watch it.
There are several plausible points of failure. OBS may be sending to an old or different stream key, its server URL may not match the selected event, or the outbound connection may be interrupted. You could also be looking at a different event in Studio from the one OBS is configured to use. If YouTube does receive the feed for a scheduled event, viewers may still see it as not live until you use the event’s launch control.
That distinction matters when you are trying to recover a channel overnight. Restarting OBS without checking the event could simply repeat the same failed connection. Changing a key at random can create a new mismatch rather than fix one. Start with the evidence in Live Control Room, then use OBS’s logs and connection indicators to narrow the problem.
Think of the investigation as three questions: is this the intended event, is YouTube receiving a usable feed for it, and has YouTube started the event for viewers? The first two concern event configuration and delivery; the last concerns the event’s state. Keeping them separate prevents you from treating every offline message as an encoder fault.
Open the intended event in Live Control Room
In YouTube Studio, open Go Live and select the stream you mean to run. Check its title and schedule, and make sure you have not opened an older event or another stream with a similar name. If you manage more than one channel, confirm the account and channel as well. A healthy connection sent to one event will not make a different event’s status change.
For a scheduled stream, open that event’s Live Control Room rather than relying on a general channel page or a saved browser tab. A reused encoder setup may retain details from an earlier broadcast, so an event that looks familiar is not necessarily the one OBS is targeting. YouTube’s encoder streaming setup guidance describes setting up and starting an encoder stream; use the current instructions in Studio if the interface has changed.
Before changing anything, note what the selected event reports. Is it waiting for data, showing a preview, or reporting an issue? Is it scheduled, already live, or ended? A short note or screenshot of the status can help you compare the result after each change. Avoid making several changes at once: if the status then changes, you will not know which check resolved the mismatch.
If a stream is already live and viewers report trouble, do not create a second event as a first response. Confirm the active event and its watch page, then check whether the current event is receiving the intended feed. Duplicate events can split attention and leave the original problem unexplained.
Look for a preview and stream-health messages
The preview in the correct Live Control Room is the most useful next signal. If it appears, YouTube is receiving enough of the feed to show a picture in that event. Check whether the image is current, whether motion is visible, and whether audio meters or other available indicators respond to the programme. A frozen frame or silent preview is not the same as a sound, usable broadcast.
If there is no preview, keep the diagnosis focused on delivery: the selected event, destination URL, key, OBS connection, encoder output and outbound network. Read any warning or stream-health message shown in Studio before restarting or changing settings. YouTube recommends monitoring stream health and responding to messages; its streaming troubleshooting guidance is a useful reference when Live Control Room reports a problem.
If a preview is present but the event still looks offline to viewers, check whether you have launched the scheduled event. The preview answers whether a feed has reached the event; it does not by itself establish that YouTube has put that scheduled broadcast live. Check the event’s state and viewer-facing watch page separately.
A practical checkpoint is to observe the preview long enough to tell whether it updates, not just whether a thumbnail appears once. If it remains black, frozen, or intermittently disappears, record the exact Studio message and compare it with OBS’s connection or output warnings. Avoid assuming the Studio display is delayed until you have checked the event and the feed; a delay is possible, but so are a wrong destination and a broken connection.
For a 24/7 channel, verify recovery from more than one place. Once the preview is current and healthy, check the event’s public watch page or channel view as appropriate. YouTube’s live-stream preparation guidance also discusses checking the stream before and during a broadcast. A public-facing check catches the case where the encoder looks fine locally but the intended event has not become accessible to viewers.
Match the event’s URL and key to OBS
With the intended event open, compare the streaming server URL and stream key shown for that event with OBS. In OBS, open Settings → Stream and check the service and server details. The precise labels can vary by OBS version, but the values should correspond to the event selected in Live Control Room. YouTube explains that a stream key is used by the encoder to send the feed to YouTube; it is a credential, so do not share it in screenshots, messages or public posts.
If the values differ, use the current values shown for the intended event and update OBS carefully. If you are uncertain whether a key is stale, reset, or associated with another event, copy the current one from Live Control Room rather than guessing. Changing the key is not a universal fix: it only helps when the mismatch or invalid key is the cause. A wrong event, an unstable connection, a faulty output, or a scheduled event not yet launched will require a different correction.
Some creators use a persistent stream key across broadcasts, while others use an event-specific key. Do not assume either arrangement is wrong solely because it is persistent or because it changes. What matters in this diagnosis is that the selected event and the destination details configured in OBS are compatible. Follow the options displayed for that event, and take care not to expose the key while checking it.
After saving a correction, start the encoder if needed and return to the same Live Control Room event. Give it time to report the connection and display a current preview. If it still has no preview, do not keep rotating keys without evidence; move on to OBS’s connection and output checks. You can also compare this process with the OBS update troubleshooting checklist, which is relevant if the mismatch began after changing OBS or its configuration.
Inspect OBS output and network connection
If the event and credentials match but YouTube has no preview, inspect what OBS is actually sending. Confirm that the intended scene is active, that the video source is visible, and that the audio source is present and moving where expected. A local preview can help distinguish a missing source from a delivery problem. Check OBS’s status or logs for encoder errors, and notice whether CPU load is unusually high while encoding. An overloaded encoder can fail to produce a reliable feed even when the stream button remains active.
Next, look at OBS’s dropped-frame and disconnection indicators. OBS’s stream connection troubleshooting guide distinguishes network-related dropped frames and intermittent disconnects from other output problems. If these indicators are increasing, test the outbound connection rather than assuming the stream key is still at fault. A Wi-Fi signal that works for browsing may not sustain the upload a live feed needs.
Use a wired connection if one is available, pause large uploads or downloads on the same connection, and check whether other people or devices are consuming upload capacity. A VPN, firewall or security tool can also affect the connection; test changes cautiously and restore protections afterwards. If the problem persists across tests, speak with your internet provider and share the times and symptoms rather than buying equipment before you know the network is involved.
Compare the total bitrate configured in OBS with sustained outbound upload capacity, leaving headroom rather than using every bit of available bandwidth. YouTube’s bandwidth guidance recommends room beyond the stream’s bitrate, and its encoder settings recommendations vary by codec, resolution and frame rate. For example, the guidance lists H.264 at 1080p and 30 fps with a 5 Mbps minimum and 14 Mbps recommended; those figures apply to that encoding row, not to every stream or every internet connection. Check the current row for your own output settings.
If the connection is dropping frames, a lower video bitrate or another available server may help test whether the current path can sustain the feed. The trade-off is reduced picture quality, and a server change will not correct a wrong event or key. Change one setting at a time, then watch both OBS’s connection indicators and the Live Control Room preview. A continuous OBS stream setup guide may be useful if the immediate mismatch turns out to be part of a broader overnight reliability problem.
For a small local news loop or devotional playlist, the best test is the configuration you intend to use for the actual stream. A short trial with lower resolution may establish whether the connection is stable, but remember that it does not prove the original higher-bitrate configuration will hold overnight. If your ongoing workflow depends on a computer staying on, compare that operating requirement with the cloud options for a continuous YouTube stream only after you have ruled out an event or credential mismatch.
Start a scheduled stream only after its preview appears
If the event is scheduled, use the sequence in Live Control Room rather than assuming that OBS’s local state launches it. Start the encoder, wait until YouTube shows the preview for the intended event, and then select Go live in that event’s control room. YouTube’s encoder guidance documents this step. Until you take it, the feed may be arriving while the scheduled event is not yet live for viewers.
Before selecting the control, make sure the preview is the content you want to publish. Check picture, sound and any opening card or notice. This is especially useful for channels that loop recorded material, where the opening frame might be blank or a source could be muted. The launch action should follow a positive check of the event and preview, not a guess based on OBS saying “Streaming”.
After the launch, confirm that Live Control Room reports the event live and check the viewer-facing page. If Studio shows a preview but the channel still appears offline, make sure you are checking the correct event’s watch page and that the event state has changed. A public link to a different scheduled stream can make a successful launch look like a failure.
Verify recovery and keep a short incident record
Call the problem resolved only when the intended event shows a current preview, stream health is acceptable, and the scheduled event has been taken live when required. Then check the public watch page from a viewer’s perspective. For a long-running channel, verify that the picture and sound continue beyond the initial recovery, and, where you use a local archive, check that it is being created and growing as expected. OBS’s status alone is not enough evidence of viewer access.
Keep a brief record of the time, event, Studio message, OBS warnings and change made. If the same issue returns, those details can show whether it follows a particular event, network interruption or encoder setting. Avoid changing multiple settings during a live incident unless you have to; an ordered test makes it easier to restore a known-good configuration.
If repeated tests point to the network, take the connection evidence to your internet provider. If OBS reports an encoder or source issue, investigate those components before rebuilding the event. If only a scheduled event remains offline despite a healthy preview, revisit the launch step and viewer-facing page. The aim is to match the remedy to the layer that failed, rather than treating all offline states as the same fault.
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
Does OBS saying “Streaming” mean YouTube is receiving my feed?
No. OBS reports its local streaming state, while the preview and stream-health messages in the correct Live Control Room show what YouTube is receiving for that event. Confirm the preview and check the viewer-facing page before concluding that viewers can watch.
Should I change my stream key if Studio says offline?
Only if the selected event’s current key and the value in OBS do not match, or you have another reason to believe the key is stale or invalid. First confirm the correct event and compare both the URL and key. A key change will not fix a wrong event, encoder problem or network interruption.
Why is there a preview but the stream is still offline to viewers?
For a scheduled broadcast, receiving a preview and taking the event live are separate steps. Once you have checked that the preview is correct, select Go live in that event’s Live Control Room, then verify the event and its watch page.
What should I check if the correct event and credentials still show no preview?
Look at OBS’s output, encoder errors, source visibility and dropped-frame or disconnection indicators. If the connection is unstable, test outbound capacity and reduce bitrate cautiously; if problems persist, contact your internet provider. Make one change at a time and confirm recovery in Studio.