A blank stream-key field in OBS can be normal when you are using its account-linked YouTube workflow. It does not, by itself, mean your key was erased: first check which connection method OBS has selected, then follow the matching account-link or manual-key steps.
If you intended to enter a key yourself, you can retrieve it from YouTube Live Control Room and switch OBS to the manual-key route. If you meant to use the connected account, keep that connection in place and check the active OBS profile before changing anything.
Identify the OBS YouTube connection method
OBS can connect to YouTube in two distinct ways. With account linking, you sign in to your Google account from OBS and use its YouTube integration. With manual setup, you choose the YouTube service and provide the stream key that YouTube gives you. A box for typing a key is expected in the latter path; its absence in an account-linked setup is not proof of a fault.
That distinction matters after reconnecting. The selected service or account connection may not have changed just because you signed in again. If OBS is still using the linked account, its interface may not show a manually entered key for you to inspect. The reviewed guidance does not confirm a current defect specifically triggered by reconnecting a YouTube account, so treat the blank field as a reason to check the workflow, not as a diagnosis.
Before disconnecting anything, ask what you want OBS to do. If you want its integrated YouTube account and broadcast controls, continue with account linking. If you want to manage the ingest key yourself, use manual setup. This choice is similar to choosing between a signed-in account route and supplying a credential directly; neither route is universally better.
For a one-off test, account linking can avoid copying a key between YouTube Studio and OBS. Manual entry can be more explicit if you already manage an event and key in Live Control Room. If you use a different encoder or script, manual keys are often part of that workflow too; the blog's guide to streaming a video folder with FFmpeg on a Raspberry Pi 5 discusses a separate encoder path, not a fix for OBS's field.
Check Settings → Stream
Open OBS and select Settings → Stream. Look at the selected service and the connection area before editing fields. Confirm that the service is YouTube RTMPS, and note whether OBS shows a connected YouTube account or instead offers fields for a stream key. Labels and layout can vary between versions, so use the selected service and visible connection state rather than relying on an exact screenshot.
If the account is shown as connected, that is evidence you are looking at the account-linked route. Do not expect this view to reveal a key you previously typed under a different configuration. Continue using the account integration if that is your intended setup. If your intention was manual entry, change the connection method only after you have the correct event's key available in YouTube Studio.
Also check which OBS profile is active. Profiles save Stream settings, including the connected account, so the settings you see may belong to a different configuration than the one you used before. If you maintain separate profiles for different channels or events, choose the expected profile before reconnecting or replacing credentials. OBS explains profile export and import in its profiles documentation; an exported profile can serve as a backup or help move settings to another installation.
A profile check is especially useful if you normally stream from a desktop setup but recently opened OBS after an update, reinstall, or account change. Write down the profile name and the selected connection method before making changes. That gives you a simple reference if you need to undo a switch, and it avoids altering the wrong channel's setup.
Distinguish account linking from manual-key setup
Use this comparison to decide what to do next:
| What you want | OBS route | What to check | What the blank key field means |
|---|---|---|---|
| Use your signed-in YouTube account and OBS's integration | Account-linked | Confirm the right Google account is connected and the intended profile is active | It can be consistent with this route; it does not establish that a key was erased |
| Supply a credential directly to OBS | Manual stream key | Select the YouTube RTMPS/manual-key path, then copy the key for the intended event | The key field should be part of this setup; retrieve the key in YouTube Studio if needed |
The key and the account connection are not interchangeable items. YouTube describes stream keys as credentials that tell an encoder where to send a feed and let YouTube accept it. Its stream setup guidance covers getting the key in Live Control Room. A Google sign-in authorises the account-linked workflow; a manual key is used by an encoder configured to send to YouTube with that credential.
If you are unsure which route you used before, look for other clues rather than guessing from the blank box. Did you sign in through an OBS browser window and see a connected account? Did you copy a key from YouTube Studio and paste it into OBS? Did the profile name recently change? Those answers usually make the intended path clearer.
A forum post from an OBS user reported that disconnecting the connected account made the manual key box appear. Treat that as a possible workaround, not a guaranteed current fix: an individual report does not establish how every OBS version behaves. If you decide to try it, make sure you can sign back into the right channel and have the key ready if manual entry is the goal.
Reconnect the YouTube account if needed
If you intend to use account linking and OBS no longer shows the right account as connected, reconnect from Settings → Stream using the available account connection control. Sign in to the Google account that owns or manages the channel you want to broadcast to. Read any permission prompts, and confirm the account name or channel context shown by OBS before moving on.
If an account is already linked but appears stale, first close any extra browser tabs or sign-in windows that could lead you to authorise a different Google account. Then disconnect and reconnect only if the controls indicate that is necessary. This is an account-authorisation step; it does not require a manual key to appear. Once connected, continue with the YouTube integration and confirm your event and channel in the broadcast controls.
Remember that an OBS profile can retain a connected account. If you reconnect while the wrong profile is active, you can end up diagnosing the wrong set of Stream settings. Switch to the expected profile first and verify the channel account there. For a channel used by a team, coordinate with whoever owns or manages the YouTube account rather than using another person's login without agreement.
If OBS's controls do not match the instructions or the account will not reconnect, record your OBS version, operating system, selected profile, and the exact service/connection label shown. Then check current OBS support guidance. The YouTube integration guide describes the account-linking approach, but its integration section is marked as work in progress and refers to OBS Studio 27.1 and newer; interface details may not match your current build exactly.
Switch to manual key entry if that is the intended workflow
If your plan is to use a stream key, select the YouTube RTMPS/manual-key configuration in Settings → Stream. The exact route through the controls can vary by OBS version. Follow the controls presented for the YouTube service and use the field intended for the key, rather than trying to force a value into an account-linked view.
In YouTube Studio, choose Create → Go Live, then open the Stream tab. Copy the stream key for the event or stream configuration you plan to use. Return to OBS and enter that key in its key field. Keep the key private: anyone who obtains it may be able to send a feed to the associated stream. Do not paste it into a public support post, screenshot, chat, or unrelated form.
Do not put the stream URL in the key field. The ingest URL and the stream key have different purposes, even if both appear on YouTube's setup screen. If OBS provides a separate server or URL field for your selected service, use the URL only there and the key only in the key field. If the form has no separate URL field, follow the service's expected configuration rather than improvising.
If the key is hidden, reveal or copy it through YouTube Studio's controls. Reset it only when there is a reason, such as believing it was exposed or needing to replace it. YouTube says a channel owner or manager can reset a key; an editor or viewer cannot. After a reset, update the key in OBS before testing, because the old credential will no longer be the one to use.
You can switch back to account linking later if that fits your workflow better. Make the change deliberately, note the profile and connection type, and test a short broadcast before relying on the configuration for a long session. For a continuous broadcast, separate concerns such as limiting FFmpeg CPU usage on a VPS apply to an FFmpeg encoder, not to the OBS account-link issue itself.
Verify the event, URL, and key
Before pressing Start Streaming, confirm that the intended YouTube channel and event are selected. A valid key associated with another event may not produce the result you expect. If you use the account-linked route, inspect the connected account and the broadcast controls instead of hunting for a manual key. If you use manual entry, compare the selected event in Live Control Room with the key you copied.
Check the service and URL fields against the intended YouTube setup. Keep a simple private note of which OBS profile goes with which channel, and avoid saving a key in a shared or untrusted document. If you have more than one channel, do not rely on a profile name alone: verify the account and event in the live controls each time you prepare a broadcast.
If a stream starts but produces errors, distinguish credential problems from network or encoder problems. YouTube's Live streaming troubleshooting page recommends checking encoder errors and the outbound connection, and keeping the encoder updated. Those checks are useful only after the correct route, event, and credentials have been established.
If you recently reset a key, make sure OBS contains the replacement rather than an older saved value. If you switched profiles, inspect the profile that will actually be used to stream. For other continuous-stream maintenance, a guide to fixing audio gaps in a 24/7 playlist stream covers a different failure mode; it can help you separate playback issues from an account or key configuration problem.
Test the feed in YouTube Live Control Room
Start with a short, controlled test rather than assuming that a connected account or populated key field proves the whole path is ready. Start the stream from OBS using the selected route, then open the matching event in YouTube Live Control Room. Check whether YouTube is receiving a preview and whether the event reports an issue. Confirm the title, visibility, and channel before making the event public or sharing it with viewers.
A successful preview tells you that YouTube is receiving the feed for that event; it does not guarantee the stream will remain uninterrupted or that every later broadcast will use the same profile. Stop the test cleanly if it is not the intended event. If YouTube reports that no data is arriving, recheck the chosen connection method, profile, event, and—when using manual entry—the key and URL placement.
If there is still no key box after you deliberately choose manual setup, note the OBS version and the labels shown in Settings → Stream. Avoid repeatedly resetting the YouTube key as a guess: a reset changes the credential but does not necessarily change which connection method OBS is using. Ask OBS support about a UI or configuration discrepancy, and use YouTube support guidance for key or Live Control Room questions.
A short test also lets you confirm practical details such as audio, loop points, and the correct source before a long session. For a 24/7 channel, OBS itself needs to remain running on the computer doing the encoding. If keeping a computer on is the pain point, StreamNeo can take an uploaded video and keep a YouTube broadcast running while your computer is off, so you do not have to maintain an OBS session for that file-based workflow.
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 a blank field mean OBS deleted my YouTube stream key?
No. A blank manual-key field can be consistent with OBS using the account-linked YouTube workflow, and it does not prove that a key was deleted. Check the selected connection method and profile before changing credentials.
Should I disconnect my account to make the key box appear?
Only if you intend to switch to manual-key setup and are prepared to reconnect the right account if needed. An OBS forum user reported that disconnecting made the box appear, but that is an anecdotal workaround rather than a guaranteed fix for current versions.
Where do I get or reset a manual stream key?
Open YouTube Studio, choose Create → Go Live, and use the Stream tab to copy the key for the intended event. Reset it only when needed; YouTube states that a channel owner or manager can reset a key, and you must update OBS with the replacement.
What should I do if YouTube still does not receive the feed?
Confirm that OBS and Live Control Room refer to the same channel and event, then check the route-specific account or key, the URL placement, encoder errors, and outbound connection. If the interface itself still differs, record your OBS version and ask OBS support rather than assuming the key was erased.