You can send a YouTube Live Redirect only if your channel has more than 1,000 subscribers and no Community Guidelines strikes. To receive a redirect, a channel must allow it; the recipient does not need to meet the sender’s subscriber threshold just to grant permission.
Those are separate from YouTube’s general rules for starting a livestream, which include channel verification and no live streaming restrictions in the previous 90 days. This guide separates the conditions, shows where to configure them in Studio and explains what to check when a destination is missing.
What Live Redirect requirements govern
Live Redirect moves viewers from a source broadcast to a selected destination when the source stream ends. You can direct viewers to a Premiere or to another channel’s live stream. It is a hand-off between YouTube viewing experiences, not a way to merge channels or transfer control of the destination broadcast.
There are two roles to keep straight. The sender is the channel whose stream is ending and whose creator sets the destination. The recipient is the channel hosting the destination live stream, if you are sending viewers to another creator. The sender has YouTube’s feature-specific eligibility rules; the recipient controls whether other channels may send viewers to it.
That distinction matters when a destination is another channel’s stream. A sender can meet YouTube’s requirements and still be unable to select a particular recipient if that recipient has not allowed the sender. Conversely, a recipient can choose to allow redirects without crossing the sender’s subscriber threshold. Permission and eligibility answer different questions.
A Premiere has a different relationship to the sender’s channel: it is a scheduled video experience rather than another channel’s live stream. YouTube recommends setting up the Premiere before configuring the source livestream. That gives you a destination to select and time to check its title, scheduled start and audience-facing details before the hand-off.
Live Redirect is also distinct from making a continuous loop or a 24/7 stream work technically. It does not create the source broadcast, keep a computer awake or fix an encoder problem. For those production questions, see this guide to connecting OBS for a pre-recorded stream; the redirect settings matter after YouTube has a source event to configure.
Sender threshold and strike status
YouTube’s current Help page says the feature is available to creators sending a redirect who have more than 1,000 subscribers and no Community Guidelines strikes. “More than” is important: do not read it as “at least 1,000”. The statement concerns the channel sending viewers, not the channel receiving them.
Check the exact condition on YouTube’s Live Redirect Help page before planning a hand-off. YouTube can change feature rules or Studio labels, and the official page is the appropriate place to confirm the current wording. This is not a threshold for being allowed to receive redirects.
The strike condition is also specific. YouTube says the sender must have no Community Guidelines strikes. Do not substitute a different status, such as whether the channel has a copyright claim, for the stated criterion. If you are uncertain about your channel’s standing, review the channel’s status in YouTube Studio and consult YouTube’s current guidance rather than assuming that an unrelated notice has the same effect.
If your channel does not meet the sender rule, plan the source stream without relying on a redirect. You can still end a broadcast normally and tell viewers where to find your next event, but that is not the same automated transition. Do not make a scheduled programme depend on a feature that Studio does not offer to your account.
It can be useful to separate editorial planning from feature availability. For example, a devotional channel might schedule a bhajan Premiere after an evening live stream. First confirm the sender channel can configure a redirect; then set up the Premiere and verify that it appears in the destination picker. A calendar entry or a link in chat is not proof that the redirect itself is available.
Recipient permission to receive a redirect
For a redirect to another channel’s live stream, the recipient channel must allow it. YouTube provides controls in Studio for deciding who may direct viewers to the channel’s content. The recipient’s choice is an access permission, not an alternate way of meeting the sender’s subscriber or strike requirements.
YouTube documents three permission scopes. A channel can allow channels it subscribes to, allow all channels, or approve specific channels manually. The subscription-based choice is the default, but it depends on the recipient’s subscriptions being public. If subscriptions are private, do not assume the recipient is allowing followed channels through that setting.
The “all channels” choice cannot be combined with the subscriptions setting or the manual approval list. The manual list can be combined with the subscription-based choice, so a recipient may allow subscribed channels and add named channels that do not otherwise qualify under that scope. YouTube allows up to 100 channels on the manual approval list, according to its Help guidance.
| Recipient setting | Who can send a redirect to the recipient? | Combination notes |
|---|---|---|
| Subscribed channels | Channels the recipient subscribes to, subject to the subscription visibility condition | Can be combined with manual approvals |
| All channels | Any channel | Cannot be combined with the subscriptions setting or manual list |
| Manual approvals | Channels specifically added by the recipient | Can be combined with the subscriptions setting |
These controls belong to the recipient channel. If you are sending viewers to a partner’s stream, ask the partner to check its permission setting before the event rather than changing your own channel and expecting that to override their choice. If you operate both channels, check the destination channel’s setting separately; Studio roles and permissions can make it easy to edit the wrong account.
A practical check is to agree the destination and permission scope with the recipient, then return to the sender’s event and inspect the picker. If the intended recipient still does not appear, verify the channel identity, the recipient’s settings and the status of its live event. Permission is one condition; the destination must also be a suitable stream available for selection.
General channel livestream eligibility is separate
YouTube’s general livestream rules apply to the channel that wants to go live. The official getting started with live streaming guide says a channel must be verified and must not have had live streaming restrictions in the previous 90 days. YouTube also says a creator must be at least 16 to livestream.
Those requirements do not replace the Live Redirect sender threshold. A verified channel with no recent live streaming restriction may be able to start a livestream, yet still fail the separate sender rule because it has 1,000 or fewer subscribers or has a Community Guidelines strike. Equally, satisfying the sender rule does not by itself establish that a channel has livestreaming enabled.
Think of this as two checks in sequence. First, can the channel create and run the livestream under YouTube’s general eligibility rules? Second, can that channel send a redirect under the feature’s separate conditions? For cross-channel destinations, there is a third check: has the recipient allowed the sender?
The distinction is useful when troubleshooting. If you cannot go live at all, investigate verification and live streaming restrictions. If you can broadcast but cannot configure a redirect, check the sender’s feature eligibility and the destination permission. Applying the wrong set of rules can waste time, particularly when a partner’s channel is ready to receive but your own channel cannot send.
YouTube’s live feature comparison also lists Live Redirect for horizontal live streams and not for the vertical live feed. Treat that as a feature availability distinction, not as a substitute eligibility test for all possible stream configurations. If your programme relies on a vertical presentation, check the current Studio options and YouTube’s comparison before promising viewers that the redirect will be part of that viewing path.
Where to configure the redirect in Studio
For a livestream source, YouTube’s Help instructions place the setting in Studio under Content > Live. Find the source event, open its edit controls, choose Customization, and use Add in the Redirect area. From there, select a Premiere or an eligible, permitted channel’s live stream as the destination.
The exact labels can change, so use the current YouTube instructions if your screen differs. The important workflow is to edit the source event, not the recipient’s event, when you are choosing where the source viewers should go. Recipient permission is configured separately by the recipient channel.
Before saving, confirm that you are editing the intended source event and that the selected destination is the one agreed with the other channel. Check the date and event title carefully if you have several similar streams in Studio. A redirect to the wrong event can be more confusing than no redirect, especially for a news loop or a scheduled devotional programme where the destination changes by day.
YouTube’s guidance recommends preparing a Premiere first when that is the destination. It also suggests telling viewers to wait a few seconds after the source ends so their screens can reload, and pinning a live-chat message on the Premiere page to direct viewers to the live stream. Those are audience-transition practices, not eligibility requirements, but they help make the hand-off understandable.
For a recurring channel, build the destination check into the same routine as checking the stream title and scheduled time. A technical setup article such as this YouTube Live setup guide can help with the broadcast side, but the redirect itself still needs to be set on the individual source event in Studio.
Why a destination may not appear
A missing destination does not point to one universal cause. Work through the sender, recipient and event separately rather than assuming that a single subscriber count explains every picker problem.
First, confirm the sender’s eligibility against YouTube’s current Live Redirect rule: more than 1,000 subscribers and no Community Guidelines strikes. Then check that you are editing the correct source video and that you opened the redirect control under Customization. A destination cannot be selected from the wrong event’s settings.
Next, consider recipient permission. If the recipient only allows subscribed channels, its subscriptions must be public for that setting to work as expected, and the sender must fall within the allowed group. If the recipient uses a manual list, confirm the sender channel was added. If the recipient allows all channels, remember that this setting cannot be combined with the subscription or manual list options.
Then verify that the destination is actually the right kind of event and is available in the picker. YouTube supports a Premiere or another channel’s live stream as destinations. A regular uploaded video is not the same as a Premiere, and a channel’s general permission does not turn every past or upcoming video into a valid live destination.
If you are using a vertical live feed, check the documented horizontal/vertical distinction. YouTube’s feature comparison lists Live Redirect as available for horizontal live streams, not the vertical live feed. Avoid inferring broader compatibility from the fact that a channel can otherwise start a live broadcast.
Finally, refresh your understanding of Studio rather than repeatedly changing unrelated stream settings. The redirect does not depend on an encoder bitrate, playlist format or the computer used to broadcast. If the stream itself is unstable, that is a separate production issue; this guide to resolving a rejected 4K 60fps RTMP stream covers a different class of problem and should not be mistaken for redirect troubleshooting.
Review requirements before scheduling or ending a stream
Treat the redirect as part of the event plan, not as a last-minute button. Confirm sender eligibility, recipient permission and destination availability while there is still time to change the plan. For a cross-channel hand-off, make sure the recipient knows which stream is intended and has allowed your channel under the right permission scope.
Run through the source event in Studio before scheduling or going live. Check that the redirect field is populated with the agreed destination, that the destination is a Premiere or a live stream, and that the event you are editing is the one that will actually end. If the setting is unavailable, do not promise viewers an automatic transition until you have found and resolved the specific cause.
Set expectations in the source stream. Explain where viewers are going and, if useful, name the destination channel or Premiere. YouTube says autoplay moves viewers to the chosen destination after the source stream ends. TeamYouTube’s announcement dated 3 May 2022 added that viewers with autoplay disabled may need to press play; because this is a detail from that historical announcement, treat it as a helpful caveat rather than a guarantee of identical behaviour in every current interface.
The hand-off is not a substitute for a clear destination page. The recipient should have the correct event scheduled and ready, with a title and opening that make sense to people arriving from another stream. If the recipient is hosting a live programme, agree who will be live at the moment the source ends and what viewers will see if the destination has not started yet.
For an always-on channel, the source may be a scheduled event or a deliberate end to a stream rather than a single one-off broadcast. The redirect only governs the transition from that source event; it does not keep the source running indefinitely or ensure the next programme is prepared. Your operating plan still needs a named person or process to check the event sequence and respond if the destination changes.
Some channels prefer to run the source from a computer; others need the stream to continue while the computer is off. In that latter case, StreamNeo can remove the specific task of keeping your own machine running for the broadcast, while the YouTube redirect conditions and recipient permissions still need to be checked in Studio. It does not change who is eligible to send or who has allowed a recipient hand-off.
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
Who can use Live Redirect?
A channel sending viewers must have more than 1,000 subscribers and no Community Guidelines strikes, according to YouTube’s current Help page. It must also meet YouTube’s separate general requirements to livestream if it is creating a live source event. The recipient’s permission is another distinct condition for a redirect to another channel.
How do I allow other creators to Live Redirect to my channel?
In YouTube Studio, open the recipient channel’s live redirect settings and choose whether to allow subscribed channels, all channels, or specific channels you approve. The all-channels option cannot be combined with the other scopes; subscribed channels can be combined with manual approvals. Check YouTube’s current Help page for the latest Studio labels.
Does the recipient need more than 1,000 subscribers?
YouTube states the more-than-1,000 threshold for creators sending a redirect, not for a recipient merely allowing redirects. The recipient controls who may send to it through its permission setting. Do not treat the sender threshold as a recipient qualification.
Can I redirect viewers to another channel’s live stream?
Yes, if your channel meets the sender rules and the destination channel allows your channel to redirect to its content. In Studio, edit the source event, open Customization and add the permitted live stream under Redirect. You can also choose a Premiere as a destination.