You add a YouTube stream key to Castr by copying the server address and key from YouTube Studio, then creating YouTube as a Castr destination with Setup with Server/Key. YouTube supplies the credentials; Castr receives them so it can send your live source to the channel.
The YouTube broadcast settings remain in YouTube Studio. Castr handles the destination connection, but it does not create or replace your YouTube stream key.
Before you start: access to YouTube and Castr
You need access to the YouTube channel that will carry the broadcast and access to the Castr livestream project where you want to add the destination. Sign in to both before starting, particularly if you manage several Google accounts or more than one YouTube channel.
You also need a live source ready, or at least enough of a source to test the connection. Castr can be configured before the source is live, but its help guidance recommends leaving the destination switched off while the source is offline and enabling it after the source starts. This avoids treating an inactive source as a failed destination during setup.
The key-based method is useful when YouTube is already set up as the place where you manage the broadcast. It does not require you to give Castr control of the YouTube channel through an account connection. The trade-off is that some YouTube details, including the stream description, remain editable in YouTube’s dashboard rather than in the Castr destination setup.
If you are preparing an always-on devotional or study channel, decide first whether the same YouTube live setup will be reused. A persistent stream may use a stable stream key, while a particular scheduled event may have its own details. Do not copy a key from a different channel or event simply because the label looks familiar.
Keep the key private. Treat it as a credential for sending a broadcast to the selected YouTube channel. If you are unsure which value is current, return to YouTube Studio and copy the present server and key again rather than relying on an old note or screenshot.
For wider planning, the YouTube 24/7 stream recovery guide explains why a connection that works during the day can still fail overnight, especially when the source computer or local internet connection is involved.
Find the YouTube server and stream key
YouTube is the starting point for the key. Open YouTube Studio and select Create, then Go live. Choose the encoder stream source so that YouTube shows the fields used by an external streaming application.
In the live setup, open Stream Settings. Copy the stream server and the stream key shown there. The names and placement of controls can change as YouTube updates Studio, so use the current labels in your account rather than looking for an identical screen from an older tutorial. You can also check YouTube’s current official live-streaming help if the live setup is arranged differently in your account.
The server and key have separate jobs:
| YouTube value | What it tells Castr | Where to get it |
|---|---|---|
| Stream server | The YouTube endpoint that receives the live feed | YouTube Studio, under Stream Settings |
| Stream key | The credential associated with sending the feed to the selected YouTube setup | YouTube Studio, under Stream Settings |
Copy both values carefully. A missing character, extra space, or value from another channel can prevent the destination from connecting. Do not replace the server with the channel URL, a YouTube watch URL, or the URL of the live control room. The server field is for the server address that YouTube presents in its encoder settings.
If YouTube offers a way to reveal or copy the key, use that control rather than trying to read a partially hidden value. If the key or server address has changed since you last configured Castr, retrieve the current values from Studio and update the destination.
At this point, leave YouTube Studio available in another browser tab. You will use the copied values in Castr, then return to Studio to check the broadcast state and edit YouTube-controlled details.
Add YouTube as a Castr destination
In Castr, open the livestream dashboard or project that should send the source to YouTube. Look for the destination control and choose Add destination. This is the wording used in the current Castr workflow described in its live-streaming help.
Some Castr help pages and account views use Add Platform for the same part of the workflow. That difference in wording does not mean you need a different type of YouTube account. If you see Add Platform instead of Add destination, use it to begin adding the YouTube output.
Select YouTube from the available platforms. Read the next choices rather than selecting the first option automatically. Castr documents two relevant routes:
- Setup with Server/Key, which uses the server and stream key copied from YouTube Studio.
- Connect to YouTube Events, which links a Google account, lets you choose a channel and event, and then creates the platform through that connected flow.
For the task covered here, choose the manual server-and-key route. The account-linked route is not a way to retrieve a key from Castr. It is a separate connection method that uses Google sign-in and event selection instead.
The choice matters if you need a feature tied to the connected YouTube account. Castr says its chat overlay use case requires adding the platform through direct account login or API connection, while custom RTMP does not provide that overlay use case. If you only need Castr to send a live source to YouTube, the server/key route may be the more direct setup.
Choose Setup with Server/Key
After selecting YouTube, choose Setup with Server/Key. This tells Castr that you will supply the connection details manually rather than signing in to Google through the YouTube Events option.
You should now be working with the values that came from YouTube Studio. Castr is not generating a new YouTube key at this stage. It is receiving the key that YouTube has already provided for the channel or stream setup.
If you expected to see a control that creates, rotates, or replaces the YouTube key inside Castr, stop and return to Studio. Key management belongs to the YouTube side of this handoff. Castr’s role in this route is to store the supplied destination details and use them when the livestream is enabled.
This separation is useful when troubleshooting. If the YouTube channel, stream settings, title, description, privacy choice, or event selection is wrong, inspect YouTube Studio. If the destination has the wrong server or key, inspect the Castr platform configuration and compare it with the current values in Studio.
Before saving, check that you are adding the platform to the intended Castr project. A correct key placed in the wrong livestream project can look like a YouTube authentication problem when the real issue is simply that the source and destination are not in the same workflow.
Paste the details and create the platform
Enter the YouTube stream key in Castr’s key field. If the setup form also asks for the server, enter the server details copied from YouTube Studio in the matching server field. Keep each value in its corresponding field rather than combining them into one entry.
Review the fields before creating the platform. A practical check is to compare the beginning and end of each copied value with the value still visible in YouTube Studio, without publishing the key anywhere else. If you copied through a password manager or shared document, make sure formatting has not changed.
Create the platform. Castr should then show YouTube as a destination for the selected livestream project. The exact status presentation may vary with the dashboard version, but the important point is that the destination has been saved with the server and key you supplied.
Do not assume that saving the platform means YouTube is already receiving a live picture. The source still needs to be running, and the Castr destination needs to be enabled when you are ready to send it. Castr’s documented workflow recommends keeping destinations off while the stream is offline and turning them on after the source is live.
When you are ready, start the source, enable the YouTube destination in Castr, and watch both sides of the handoff. YouTube Studio should provide the place to inspect the incoming stream and broadcast state. If the destination does not connect, first compare the server and key with the current values in Studio. The available documentation does not establish one universal fix for every authentication or connection error, so avoid changing several settings at once.
For a long-running channel, configuration is only one part of reliability. If your current source is OBS, the guide to OBS stopping after a few hours covers a different class of failure: the destination details may be correct while the local application or computer stops sending.
What remains controlled in YouTube Studio
Adding the key to Castr does not move all YouTube controls into Castr. YouTube Studio remains the place to manage the YouTube-side broadcast information and to inspect what YouTube is receiving.
With the manual server/key method, Castr’s documentation says the stream description must be edited in YouTube’s dashboard. Plan titles, descriptions, visibility, and other YouTube presentation choices there, according to the controls currently shown in your Studio account. Do not expect changing a Castr destination label to change the public YouTube description.
YouTube Studio is also where you return to retrieve the current server and key if the connection details need updating. If a key is replaced or a stream setup changes, update the corresponding Castr destination rather than continuing to test with an old value.
The account-linked Connect to YouTube Events route works differently. Castr’s documented flow has you sign in with Google, choose the channel, select an event, enter the event details, and create the platform. That may suit you if the event itself is the centre of your workflow. It is not the same as manually pasting a stream key.
| Connection route | You provide | YouTube-side implication | Relevant limitation |
|---|---|---|---|
| Server/key | Server address and stream key from Studio | Stream description remains managed in YouTube’s dashboard | Does not provide Castr’s chat overlay use case through custom RTMP |
| YouTube Events | Google sign-in, channel and event selection | The connected event is part of the Castr setup flow | Requires account access and event selection rather than a manual key paste |
Choose based on the job, not only on which button appears first. A local news loop that needs a straightforward destination may only need the server/key method. A workflow built around YouTube events or Castr’s chat overlay requirement should consider the account connection route instead.
If the main problem is that your own computer must stay on all night, changing the Castr destination fields will not solve that source problem. A cloud-based workflow such as StreamNeo removes the need to keep that source computer running by turning an uploaded video into a YouTube-only 24/7 stream, with the YouTube key supplied during setup.
For a broader choice between running your own source and using a managed workflow, compare OBS with a cloud service for a church stream. If your content is a meditation or ambience loop, the guide to cloud services for an always-on meditation stream covers the operating trade-offs rather than the key-entry screen itself.
A short verification routine
Once the source is live and the destination is enabled, check the result in a deliberate order. First confirm that the source is producing a picture and sound in Castr. Next confirm that the YouTube destination is enabled. Then inspect YouTube Studio for the incoming stream and the public broadcast state.
If YouTube does not show the expected feed, return to the two copied values. Confirm that the server came from the server field and the key came from the key field. Then check that the YouTube channel in Studio is the one you intended and that the Castr destination belongs to the intended project.
If the connection worked previously but stopped after a change, do not immediately create several new destinations. Retrieve the current server and key in Studio, compare them with Castr, and update the existing setup where appropriate. Keep a simple record of which channel and project a destination belongs to, but do not store the key in a document that is shared more widely than necessary.
A successful first connection also does not prove that an overnight broadcast will continue indefinitely. Test the complete source, destination, and YouTube workflow for the sort of period you actually need, and decide what you will do if the source goes offline. For a channel serving viewers in India overnight, include power, broadband, and restart behaviour in that plan rather than treating the stream key as the whole reliability solution.
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 Castr create a YouTube stream key?
No. YouTube Studio provides the stream key and server details. Castr receives those values when you choose Setup with Server/Key and create the YouTube destination.
Is Add Platform different from Add destination in Castr?
They are alternate labels used in Castr guidance and dashboard versions for beginning a platform or destination setup. Use the label shown in your account, select YouTube, and continue to the server/key option.
Where do I edit the YouTube stream description?
For the manual server/key connection, Castr says the stream description is edited in YouTube’s dashboard. Return to YouTube Studio rather than expecting the Castr destination form to control that description.
Should I use YouTube Events instead of a stream key?
Use Connect to YouTube Events if you want to sign in with Google, select a channel and event, and manage the connection through that event flow. Use Setup with Server/Key when you already have the YouTube server and key and want to enter them manually.