A stream key is a private credential that helps a streaming service receive a broadcast at the correct destination. You enter it in broadcasting software when that service uses a key-based connection. It is not the public link viewers use to watch your channel, and it should not appear on your shared screen.
Some software connects through a supported account login instead of asking you to paste a key. Both are connection methods; neither removes the platform’s eligibility rules. If your account has no permitted broadcasting route, downloading OBS does not create one automatically.
Three items that beginners often mix up
The channel or watch link opens a page where people view the stream. It normally begins with an ordinary website address and is suitable for sharing with the intended audience.
The server URL, also called an ingest address, tells the software where to send the outgoing data. It is a delivery destination for the broadcast, not usually a page that plays your channel in a browser.
The stream key is the private value associated with the receiving account, channel or event. Depending on the platform, it can remain reusable or be associated with a particular event or setup. Read the current dashboard’s explanation instead of assuming every key has the same lifetime.
A useful comparison is a delivery system: the server tells the software which receiving service to contact, while the credential tells that service which authorised destination to use. The viewer link is the front door people use to watch the delivered result. Copying one into the wrong field will not make the others unnecessary.
Find it inside your own platform dashboard
Sign into the actual platform account and open its creator or live-streaming dashboard. Look for the service’s stream settings, connection settings or live-event setup. Confirm the channel name before revealing or copying a key.
For Kick, the documented route is Creator Dashboard → Channel → Stream URL and Key. For other services, use their current encoder-setup guidance. Menu labels and account features change, so an old screenshot is less reliable than the dashboard you can see.
YouTube’s encoder route can provide connection information for a live event. A webcam stream is a different route and may not need you to handle a key manually. Do not go searching for a private credential when the platform’s simpler built-in tool already covers the task.
On TikTok, do not assume every account with mobile LIVE access receives an OBS stream key. Desktop access and supported integrations have their own conditions. Use the account’s offered route, such as LIVE Studio, when that is what TikTok permits.
Connect it to OBS carefully
Open Settings → Stream in OBS and select the receiving service. If the service supports connecting your account, you may use that official login flow. Check the requested permissions and the channel connected afterward.
For a manual key connection, copy the current value from the platform and paste it into the stream-key field. If using a custom service route, also enter the server URL in its own field. Apply the settings without revealing the key on a live screen.
Check for leading or trailing spaces if a connection fails. A copied line break or an old value saved in a second profile can be enough to cause confusion. Do not post the key into a support message so somebody else can inspect it for you.
Keep the server and key from the same platform and intended setup. A valid credential for one service will not automatically work with another service’s server. Similarly, a key copied from another channel can send to a destination you did not intend or fail altogether.
Account connection versus pasting a key
An official account connection lets the broadcasting app obtain the access it needs through a login and authorisation process. You normally complete that on the service’s own sign-in page. It can be more convenient than manually copying credentials.
Pasting a key is useful for a supported custom setup, but it makes you responsible for storing and replacing that value correctly. Both methods require care about the account you select and the software you trust.
If the wrong account was authorised, disconnect through the app’s supported settings and reconnect the intended account. Replacing an unrelated key in another window will not necessarily change the active account connection.
When removing an app you no longer use, inspect the platform’s authorised-app controls where available. Uninstalling local software and revoking its account access are different actions. Use the platform’s current security controls rather than assuming one always performs the other.
Why the key must stay private
A stream key can authorise an outgoing broadcast to your destination. Someone who obtains it may be able to send unwanted material to your channel. It does not need to look like a readable password to deserve the same care.
The common accidental exposure is a screen share of the stream-settings page. Another is a screenshot sent for troubleshooting. Hide the field before capturing the screen and inspect the image before sharing it. A key visible for a few seconds can still be captured.
Do not place keys in public notes, video descriptions, chat messages or a downloadable example configuration. If you teach connection setup, use clearly fictional text instead of a real value, even from a small or unused account.
A legitimate helper can usually diagnose the route, service name and error message without seeing your secret. Share those non-secret details first. If a service requires access authorisation, use its official flow rather than handing credentials to somebody in a direct message.
Reset a key after exposure
If a key appears publicly or reaches someone who should not have it, open the platform’s dashboard and use its reset, regenerate or replacement control. The exact label varies. Complete the action only for the intended channel or event.
Update every broadcasting app or profile that used the old value. If one scheduled setup still has the previous key, it may fail later even though your current OBS profile works. Replace it where necessary without putting the new value in a shared document.
Run a controlled test after replacement. Resetting a key can interrupt an existing connection, so be deliberate if a session is already live. Review the platform’s session and app-access controls if you suspect broader account access rather than only a copied stream key.
Changing the account password and resetting the stream key are not universally the same operation. Check both relevant controls instead of assuming a password change definitely invalidated every broadcasting credential.
Diagnose a connection failure without exposing it
First ask whether the software cannot connect at all or the platform receives a signal but has not started the event. Those are different states. Some platforms expect an additional Go live action after receiving encoder video.
For a failed connection, verify the service selection, current server address and credential. Check account eligibility and any error displayed by the platform. Then inspect network connectivity. Do not assume the key is bad merely because a local game capture is black.
For a connected but wrong picture, inspect the active scene in the broadcasting software. The credential routes whatever the software sends; it does not select your camera or microphone. A correct connection can still deliver an empty scene or silent mix.
For repeated disconnections, look at the network statistics and upload settings. A credential that successfully connects does not guarantee the network can carry the chosen bitrate continuously.
Know what to share with viewers
Send viewers the channel or event’s watch link. Open that link on a separate device to confirm it points to the intended place and respects the chosen audience. Do not send the server address or credential as part of an invitation.
If the event is private, follow the platform’s private-sharing process. An unlisted watch link can be passed on. The stream key’s secrecy and the audience’s privacy are separate questions: keeping one private does not automatically restrict the other.
Before the next session, check the connected account, chosen event and source picture. You do not need to regenerate a working key for every ordinary broadcast unless the platform’s process or a real security event requires it. A stable, understood connection is easier to maintain than repeated unnecessary credential changes.