To add a YouTube stream key to FFmpeg on Ubuntu, copy both the server URL and stream key from the selected stream in YouTube Live Control Room. The key is not the destination by itself: FFmpeg needs the destination URL and the key in the format YouTube provides for that stream.
In a direct FFmpeg command, the server URL and key are commonly combined into the output destination, but you should not invent the endpoint or assume every stream uses the same path. This guide shows where to find the two values, how to place them in a command, and how to check whether YouTube has received the feed.
Open the selected stream in Live Control Room
Sign in to YouTube Studio and open Live Control Room. You can create a new stream or choose a scheduled stream you have already prepared. Open that stream’s settings and find the section for connecting streaming software or an encoder. YouTube’s encoder setup instructions describe this workflow; the labels and layout can change, so follow the current page rather than an old screenshot.
Make sure the selected item is the stream you actually intend to broadcast. A channel can have more than one scheduled event or stream configuration, and the key and server details displayed for one selection should not be assumed to apply to another. Check the title and scheduled time before copying anything. If you are preparing a devotional loop for the morning, for example, do not take the connection details from a different evening event simply because it is already open in the control room.
If you are creating a stream, complete its basic details and save it before copying the connection information. If it is scheduled, keep the Live Control Room page available: it is where you will later confirm that FFmpeg has reached YouTube and, depending on the stream setup, manually start the broadcast. The stream must also be eligible to go live. A technically correct FFmpeg command cannot enable live streaming on an account that has not completed YouTube’s requirements.
Copy both connection values
In the selected stream’s settings, locate the server URL and the stream key. Copy each value exactly as shown. YouTube describes these as separate settings for the encoder: the server URL identifies the destination, and the key identifies the stream. Its guidance describes a stream key as behaving like a password, so treat the value as a credential, not as harmless metadata. See YouTube’s stream key guidance for its current explanation of keys and resetting them.
Do not copy a URL from a forum post, a previous command, or a tutorial and treat it as your own. Likewise, do not take a key from an unrelated stream or rely on a remembered key. The exact values belong to the selected stream’s settings. If the page offers a regular RTMP server URL and a secure RTMPS URL, choose the one you plan to use and copy that complete value rather than editing the protocol from memory.
A practical way to avoid a mix-up is to copy the URL and key into a private temporary note while preparing the command, then remove the note when the command is working. Do not put either value in a public ticket, screenshot, chat room, or example command. If the key has already been exposed, reset it in Live Control Room and replace it in your encoder configuration.
Understand the FFmpeg destination
The server URL and stream key do different jobs. The URL is the destination address; the key is the stream-specific credential appended or supplied according to the endpoint format YouTube displays. In many direct FFmpeg commands, there is one output destination argument, so the two pieces appear together there. That presentation does not make the key a replacement for the URL.
Think of the final destination as a composed value: start with the copied server URL and apply the key convention shown for that stream. Follow the exact path and separator convention in the displayed connection details. Do not assume a universal /live/ path, add a slash automatically, or remove part of the server address just because an example on another site looks different. The values YouTube provides for your selected stream take precedence over generic examples.
FFmpeg’s protocol documentation gives the general pattern of sending a real-time file input to an RTMP destination with FLV output, for example ffmpeg -re -i myfile -f flv rtmp://myserver/live/mystream. The host and path in that documentation example are illustrative, not your YouTube settings. The FFmpeg protocol documentation also documents RTMPS as a supported protocol, while the exact protocol support available to you depends on your installed FFmpeg build.
Put the values in the command
For a file input, a starting template is:
ffmpeg -re -i INPUT -c:v libx264 -preset veryfast -c:a aac -b:a 128k -f flv 'SERVER_URL/STREAM_KEY'
Every capitalised term is a placeholder. Replace INPUT with your local media file path, SERVER_URL with the server URL copied from the selected stream, and STREAM_KEY with that stream’s key. The final quoted value is only a template for a common arrangement; use the joining format and path supplied in Live Control Room. If YouTube presents the destination differently, reproduce that format rather than forcing this example to fit.
The -re option reads a file at its native rate instead of sending it as quickly as the machine can process it. -f flv selects the output container commonly used for this RTMP streaming pattern. The video and audio options shown are illustrative encoding choices, not a promise that they suit every source or channel. A video without an audio track, an unusual input format, or a machine with limited processing capacity may call for different options. Start with the simplest command that suits your media and inspect FFmpeg’s output for errors.
Do not paste your real command into a public post for help unless you have first removed the key and any sensitive local file paths. The command line may remain in shell history and may be visible to other users of the same machine. For a one-off test, running it in a private terminal is straightforward; for a long-running process, think carefully about where credentials are stored and who can read the configuration. The FFmpeg-based VPS walkthrough is useful if you are moving from a local Ubuntu test to a continuously running setup, but its endpoint details should not replace the ones in your own Live Control Room.
Choose RTMP or RTMPS from the displayed URL
The important choice is to match FFmpeg’s destination protocol to the URL you actually copied. RTMP is the conventional option; RTMPS is the secure variant, which YouTube describes as RTMP over TLS/SSL. If Live Control Room gives you an RTMPS URL for the secure connection, use that URL as shown. YouTube’s RTMPS setup and troubleshooting guidance explains how to reveal and use the secure address.
| What you see or need | What to do |
|---|---|
| The regular RTMP server URL is selected | Use that copied URL and its associated key convention in the output destination. |
| You choose the secure RTMPS connection | Copy the RTMPS URL from Live Control Room and make sure the destination uses it as displayed. |
| FFmpeg reports an RTMPS protocol or SSL problem | Confirm both the scheme and host match the copied secure URL, then check whether your local build supports RTMPS. |
Do not change an RTMP URL to RTMPS by replacing a few letters and assume the result is correct. Copy the secure URL from the control room when you choose that option. YouTube’s troubleshooting page discusses port 443 for certain SSL errors, but it is not a universal fix for every timeout or connection failure. Use it only when relevant to the error and the current guidance.
Ubuntu installations can differ by release, package source, and build configuration. This guide does not assume that a particular package-install command works for every Ubuntu version or that every FFmpeg binary includes every protocol. If you need RTMPS and FFmpeg rejects it, inspect the available protocols with ffmpeg -protocols and consult the documentation for the package you installed. That check is diagnostic; it does not establish that a remote connection will succeed.
Keep the key private
A stream key allows the encoder to send a feed to the associated YouTube stream. Treat it like a password. Anyone who obtains it may be able to send content to that stream, so do not publish it in a blog, a public command example, a screen recording, or a support screenshot. YouTube’s own stream key guidance explains that a key can be reset if necessary.
The main risk in an FFmpeg workflow is that a destination containing the key can be copied into shell history, process listings, logs, or shared notes. This does not mean every Ubuntu setup exposes the key in the same way, but it is a reason to keep access to the account and machine limited. Avoid committing a real destination into source control. If you share a troubleshooting excerpt, replace the URL and key with obvious placeholders before sending it.
If a key may have been exposed, reset it in Live Control Room and update every encoder using the old value. Do not assume changing a title or scheduled time invalidates a compromised key. If FFmpeg stops connecting after a reset, check that the command or saved configuration no longer contains the old value and that the new key belongs to the selected stream.
Start FFmpeg and verify the preview
Run the command from a terminal with the intended input available. Read the initial FFmpeg output rather than closing the terminal as soon as it begins: connection refusals, authentication errors, missing codecs, and input-file problems point to different causes. A running process by itself does not prove that YouTube is receiving a usable picture and sound.
Return to Live Control Room and look for the incoming preview or connection status. If the preview appears, check the picture, audio, and the selected stream before proceeding. For a scheduled stream, you may still need to select Go live in Live Control Room after the encoder preview appears. An encoder connection can be ready while the scheduled broadcast remains waiting. For an immediate-start workflow, YouTube’s steps may instead make the stream live when the encoder starts; follow the state shown for your stream.
If there is no preview, verify the stream selection first, then compare the copied server URL and key against the command. Check for a missing character, a changed key, or a separator that does not match the supplied endpoint format. Also confirm that live streaming is enabled for the account. YouTube notes that first-time activation can take up to 24 hours and that account verification and restrictions affect eligibility; check its live streaming requirements for the current rules.
If a scheduled stream is still waiting, make sure FFmpeg is running and the preview is present, then look for the separate Go live action. If you get an SSL error while using RTMPS, check that the complete scheme and host are secure, that the local build supports RTMPS, and whether YouTube’s current troubleshooting steps apply to your error. When you change the key or URL, restart FFmpeg with the corrected destination rather than expecting an already-running process to update itself.
For a short test, staying at the terminal makes it easier to see whether FFmpeg exits or reports repeated errors. A 24/7 stream has a different operational burden: if your Ubuntu computer sleeps, loses power, or disconnects, a locally running FFmpeg process cannot continue sending video. The article on automatic recovery for a 24/7 YouTube stream covers the separate question of keeping a long-running broadcast recoverable. If your goal is a channel built around playlists rather than a terminal session, playlist scheduling alternatives may help you assess a different workflow.
When the ongoing pain is keeping a personal computer on and responding when a feed drops, StreamNeo removes that particular task by letting you upload a video and run it as a YouTube live stream without leaving your computer switched on; the choice is relevant only if that file-based workflow fits your channel.
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
Can I put only the stream key in FFmpeg?
No. FFmpeg needs the destination server URL as well as the stream key. In a direct command, they are often combined into a single output destination, but use the exact URL and key convention shown for the selected stream in Live Control Room.
Where do I find my YouTube server URL and key?
Open the intended stream in YouTube Studio’s Live Control Room and inspect its streaming or encoder settings. Copy both values from that stream. Do not reuse a URL or key from a different scheduled event or rely on a generic endpoint from an example.
Why does FFmpeg connect but the scheduled stream is not live?
The encoder may be sending a preview while the scheduled broadcast is still waiting for you to start it. Check Live Control Room and select Go live when the preview is ready, if that action is shown for your stream.
What should I do if my stream key appears in a screenshot or log?
Treat it as exposed. Reset the key in Live Control Room, replace it in your FFmpeg command or saved configuration, and restart the encoder. Remove the exposed value from any public material you control.