YouTube Live Redirect is configured in YouTube Studio on the source stream; FFmpeg sends that source stream’s video and audio to YouTube. The redirect destination is not selected in the FFmpeg command.
The useful order is to prepare the destination, create the source event, send and test its feed, then set the redirect in Studio. This keeps the two jobs distinct and gives you time to confirm eligibility and permissions before viewers arrive.
Keep the feed and redirect as separate jobs
An FFmpeg stream has an encoder job: read a file or capture input, encode or package it as needed, and send it to YouTube’s ingest URL using the stream key. A YouTube Live Redirect has a separate Studio job: associate the source event with a Premiere or an eligible live stream so YouTube can present the handoff when the source ends.
This distinction matters when something goes wrong. If the source video is black, silent or missing from Live Control Room, inspect the input, encoding, URL, key and network path. If the source plays correctly but the intended destination is absent or incorrect, inspect the source event’s Customization settings in Studio. Changing FFmpeg options will not select a redirect destination.
A redirect is also not the same as placing a URL in the stream description or telling viewers to search for the next broadcast. Studio controls the redirect relationship, while the outgoing feed remains the stream you are currently broadcasting. YouTube describes redirect as a way to send viewers from a live stream to a Premiere or another channel’s live stream; the current controls and eligibility are documented in its Live Redirect Help page.
Check eligibility and permission first
Before preparing the encoder, confirm that the channel sending the redirect meets YouTube’s stated eligibility conditions: more than 1,000 subscribers and no Community Guidelines strikes. These are YouTube’s current rules, not a guarantee that every individual event will show the same controls. Check the official help page in Studio if the option is missing, because platform requirements and interface labels can change.
A redirect to another channel’s live stream also depends on permission from that destination channel. YouTube lets destination creators manage which channels may redirect to their content in Studio under Settings, then Community. The available permission choices include allowing subscriptions, all channels, or specific channels. If you are sending viewers to another creator, agree the handoff in advance and ask them to enable an appropriate permission; do not assume that knowing the stream link grants access.
If you manage both channels, check the destination channel’s setting directly. If another person manages it, ask them to verify permission while both channels are accessible. This is easier to resolve before an event than while your source is already live.
Decide whether the destination is a Premiere or another live stream. For a Premiere, arrange and schedule it first so that it exists when you configure the source. For another channel’s live event, coordinate its timing and permission. The destination is a YouTube-side choice; neither its URL nor its stream key belongs in the source FFmpeg command.
Prepare the destination and source event
For a Premiere, create or schedule the video before setting the source redirect. Check its title, scheduled time and visibility from the account that will own it. For another live stream, confirm that the destination event is the intended one and that the destination channel has granted permission. These checks help avoid selecting an event that is private, mistimed or not ready when the source concludes.
Next, create or schedule the source live stream in YouTube Studio. Open its Live Control Room and make sure you are working with the correct event. The source event is the one that FFmpeg will feed and the one whose Customization settings will later hold the redirect destination.
If this is your first time enabling live streaming on the channel, YouTube says activation can take up to 24 hours. Account for that before you schedule a public handoff. For a fuller look at file-based channel planning, see this guide to running a 24/7 YouTube stream from prerecorded Hindi news clips. The same principle applies here: prepare the YouTube event and source material before relying on a scheduled transition.
Also check what your input file actually contains. A file that plays locally may still have a codec or container combination that does not suit the path you intend to use. If your source is an MP4, this guide on MP4 compatibility in a YouTube live stream can help you diagnose that separate issue. A destination setting cannot repair a feed YouTube cannot decode.
Copy the stream URL and protect the key
In the source event’s Live Control Room, find the stream URL and stream key. FFmpeg needs those credentials to send the source feed to YouTube. YouTube calls stream keys password-like, so treat them as secrets: do not paste a live key into a public post, shared screenshot, source-control repository or an example command that other people can copy.
Use the URL and key shown for the source event, not information from the destination channel. The redirect destination is configured later in Studio; the stream key authenticates the incoming source feed. If you think the key has been exposed, replace or reset it in YouTube Studio and update the encoder configuration before going live.
Keep the values out of logs and screen recordings wherever practical. If you are documenting the setup for a colleague, use a placeholder such as YOUR_STREAM_KEY rather than the real value. YouTube’s guide to managing live stream settings explains where stream keys and encoder settings fit into the process.
Send the source feed with FFmpeg
Configure FFmpeg for the source you have. A prerecorded file and a genuine live capture input have different timing behaviour. When a file is read faster than real time, FFmpeg’s -re option can pace file input at its native frame rate to simulate a live feed. FFmpeg warns against blindly using this option with an actual capture device or live stream, where it can cause packet loss. Use the FFmpeg documentation for input options when checking the behaviour of your installed version.
There is no single YouTube-specific FFmpeg command that can be responsibly presented as correct for every file, capture source, operating system and FFmpeg build. Build the command around your input, choose a supported output format and encoding, and provide the source event’s current ingest URL and key in the way your setup expects. Validate the actual output in Live Control Room. Do not add a destination channel or Premiere to the command: that does not configure Live Redirect.
YouTube’s encoder guidance supports RTMP or RTMPS, and recommends RTMPS, the secure extension. Its published guidance lists H.264, H.265 or AV1 video and AAC or MP3 audio, with constant bitrate (CBR). Match settings to the capabilities of the source and your available upload capacity. The table gives two YouTube H.264 recommendations as reference points, not universal presets; YouTube’s recommendations vary with codec, resolution and frame rate.
| Example H.264 output | YouTube recommended video bitrate | What to consider |
|---|---|---|
| 1080p at 30 fps | 5 Mbps | Allow for audio and normal network variation in your upload capacity. |
| 1080p at 60 fps | 17 Mbps | Higher frame rate raises the video bitrate recommendation; do not use it unless the source and connection can sustain it. |
YouTube recommends a two-second keyframe interval and says not to exceed four seconds. A keyframe interval expressed in frames depends on the chosen frame rate, so do not copy a fixed GOP frame count without calculating what it means for your output. Check the current encoder settings, bitrates and resolutions guidance before choosing values.
If you are using a looped file, inspect its resolution and frame rate rather than assuming every section has the same properties. This article on different resolutions in a YouTube loop stream is relevant when clips in one playlist do not match. Mixed properties may affect what you need to test, but they still have no bearing on which redirect destination Studio holds.
Start FFmpeg and check the source preview in Live Control Room. Confirm that moving video and representative audio are present, and watch stream health for errors. If the picture is absent, silent, delayed or repeatedly disconnecting, resolve that before adding a viewer handoff to the plan. Keep a record of the working input and output settings without recording the secret key.
Set the redirect in YouTube Studio
Once the source event exists and you have confirmed the destination and permission, open YouTube Studio and go to Content, then Live. Edit the source video and open its Customization settings. Add the redirect there, choosing the prepared Premiere or eligible live stream that viewers should reach.
The setting belongs to the source event, not to FFmpeg and not to the destination event’s encoder settings. Recheck the selected destination and the source event before saving. If a destination channel’s stream does not appear, revisit permission and eligibility rather than trying a different FFmpeg flag.
YouTube may show a confirmation when the source stream ends that viewers will be redirected. Treat that as an important final check in the Studio workflow, not a signal that FFmpeg should stop itself or switch to another feed. The encoder continues to send the source until you end it; the YouTube-side redirect governs the viewer transition.
Tell your audience what is happening before the source ends. YouTube advises allowing a few seconds for screens to reload, so viewers may see a short pause during the transition. Avoid promising an instant or guaranteed handoff; connection, device and platform behaviour can vary.
Test the handoff and end the source deliberately
Test well before the scheduled event. YouTube’s guidance says to set up an encoder at least two hours before the event and start it at least 15 minutes before the scheduled time. These are planning recommendations from YouTube, not a guarantee that a test will uncover every problem. Use the interval to preview the feed, check stream health and make sure the source and destination event details match your plan.
Use representative audio and movement in the test feed. A static frame can conceal a broken file segment, a silent section or timing issues. Check the watch page as well as the Live Control Room preview where practical. YouTube notes that streams under 12 hours are automatically archived; if an archive matters to you, confirm the relevant event and result in Studio after the broadcast rather than assuming it will serve as your only backup.
At the end of the source event, stop the FFmpeg feed using the method appropriate for your process and finish the source broadcast in YouTube. Follow the Studio confirmation if it appears, then check the source watch page and, where possible, the destination page from a viewer’s perspective. Allow time for the page to reload and verify that the intended destination is shown. The purpose of the test is to learn how your own channel and audience devices behave, not to infer a guaranteed transition time.
If viewers remain on the source page or report that they did not move, check that the source stream was ended, the redirect was saved on the correct source event and the destination permission was active. Confirm that the destination was live or that the Premiere was prepared as intended. Keep FFmpeg diagnostics separate from Studio settings: encoder errors explain the feed, whereas an incorrect redirect selection is a Studio configuration issue.
For a channel that runs long sessions, reliability also depends on where and how the encoder process is operated. This guide to running a YouTube 24/7 stream on a VPS covers a different operating choice; it does not change the fact that the redirect itself is configured in Studio. If the burden you are trying to remove is leaving a computer running for a file-based channel, StreamNeo can take an uploaded video and run the YouTube broadcast without keeping your own computer switched on; you still configure and verify the YouTube-side redirect separately.
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 FFmpeg choose the Live Redirect destination?
No. FFmpeg sends the source feed to YouTube using the source event’s stream URL and key. You select the redirect destination in the source event’s Customization settings in YouTube Studio.
Can I redirect to another channel’s live stream?
YouTube allows this when the destination channel has given permission, and the channel sending the redirect meets YouTube’s eligibility conditions. Ask the destination owner to check the relevant Community settings before the event.
Should I use -re for every FFmpeg input?
No. It can be useful when FFmpeg reads a file and needs to pace it as a live feed. For a genuine live capture or live stream input, follow the input’s natural timing and FFmpeg’s guidance rather than adding -re automatically.
What should I do if the redirect is not available in Studio?
Check the sender channel’s eligibility, confirm that you are editing the correct source event, and verify destination permission if another channel is involved. Then consult YouTube’s current Live Redirect Help page, since Studio controls and platform requirements can change.