This guide shows you how to send an incoming stream from Wowza Streaming Engine to a YouTube Live event using Engine’s dedicated YouTube Live Stream Target. You will take the event’s server URL and generated key from YouTube Studio, enter them in the matching Engine fields, then check that the target is enabled and connecting.
The steps are for Wowza Streaming Engine, not Wowza Video. The two products use different target workflows; putting Wowza Video’s custom RTMP fields into Engine’s YouTube target form can lead to a misconfigured destination.
Confirm you are using Streaming Engine
First confirm which Wowza product you have open. In this guide, the relevant interface is Wowza Streaming Engine Manager, with an application that is already receiving a source stream. Its Stream Targets page includes a dedicated YouTube Live destination. The target takes a source stream from your application and forwards it to the YouTube event you configure.
Wowza Video has a separate workflow: its documentation describes adding a custom RTMP target and entering a primary URL and stream name. Those instructions are not a substitute for the Engine target form. If your screen asks for a custom RTMP target rather than offering YouTube Live under Third-Party Target Destinations, stop and confirm that you are in the intended product before proceeding. Wowza’s Streaming Engine YouTube procedure and its separate RTMP distribution documentation describe the product distinction.
You also need an incoming source stream already connected to the Engine application. The target does not create the pictures or sound; it distributes the source you select. If you are still deciding how to produce that source, the trade-offs in choosing a flexible YouTube live setup may help you work out whether an encoder-based setup fits your signal chain. Keep that choice separate from the destination configuration described here.
Before changing settings, note the application name and the source stream name you expect to send. You will select that source when creating the target. If the application is not receiving it, a correct destination configuration still cannot deliver the intended programme.
Create or select a YouTube Live event
In YouTube Studio, create a live stream event or open the event you intend to use. The event’s Stream Settings provide the server URL and the generated stream key. YouTube’s instructions for creating a live stream with an encoder explain where these values are provided and how an encoder uses them.
Check that you have selected the right event before copying anything. A channel may have a scheduled event, a test event or an event already used for a broadcast. The destination details belong to the event and settings shown in Studio; do not assume that a URL or key copied from an older setup applies to the event you have open now.
Keep the Studio page private while you work. Do not paste the key into a public document, chat, screenshot or support post. If you need to move between Studio and Wowza Manager, use a private password manager or another controlled method rather than leaving the value visible where others can see it. You need the generated value for the form, but you do not need to share it with viewers or collaborators who are not configuring the stream.
Find the stream URL and key in YouTube Studio
In the selected event’s Stream Settings, identify two distinct pieces of destination information: the Stream URL and the stream key. The URL tells Engine where to connect; the key is the generated destination stream name that authenticates and identifies the feed for YouTube. Treat them as separate fields when you enter the target.
The URL is not necessarily a complete address to paste unchanged into each Engine field. Engine’s YouTube form separates the destination host from the application name. For example, Wowza’s documentation illustrates a URL in the form rtmp://abc.rtmp.youtube.com/live2: in that example, the host is abc.rtmp.youtube.com and the application name is live2. Use the actual Stream URL shown for your event, not the example values. If YouTube displays a different address or its current instructions specify a different destination, follow those current event details.
The stream key is not the friendly name you may have assigned to a key in Studio. Wowza directs you to use the generated alphanumeric code, not the label, in Engine’s Destination Stream Name field. Copy the generated value from the relevant event’s settings, and take care not to include surrounding spaces or a line break. Do not put that value in a public note to make the configuration easier to find later.
A small private checklist can reduce field swaps: record that you need the URL’s host and application, the generated key, and the Engine source stream name. Avoid recording the actual key in the checklist. The continuous recorded-lessons guide covers a different kind of always-on source, but the same practical distinction applies: the material being sent and the YouTube destination are separate parts of the setup.
Open the Engine Live application's Stream Targets
In Wowza Streaming Engine Manager, open the Live application that receives your source. Choose Stream Targets, then Add Stream Target. Under Third-Party Target Destinations, select YouTube Live. This is the dedicated Engine workflow; do not choose a generic or custom RTMP destination as a workaround.
Give the target a descriptive, unique name that will make sense when you return to the application later. For example, a name can identify the channel or the purpose of the destination without including the key. A target name is an internal label for your own management; it is not the YouTube stream key and should not contain credentials.
Select the Source Stream Name that is already connected to the application. Check the selection carefully if the application has multiple incoming streams. Sending the wrong source can make the destination appear connected while the audience sees an unintended feed, so compare the selected name with the source you planned to send before saving.
If you have an existing target, inspect its settings before creating a duplicate. A duplicate may make it harder to know which destination is active. Confirm whether the existing target points to the event you intend to use and whether it is enabled before deciding to edit it or add a separate one.
Add and configure a YouTube Live target
The dedicated form separates the destination into fields. Map the values from Studio deliberately rather than copying the whole URL into a single field:
| Engine field | What to enter | Check before saving |
|---|---|---|
| Target name | A unique descriptive label of your choice | Do not include the stream key |
| Source Stream Name | The incoming stream already connected to the Live application | Confirm it is the intended programme feed |
| Destination Host | The host portion of the event’s Stream URL | Use the actual event URL, not Wowza’s example host |
| Destination Application Name | The application portion of the event’s Stream URL | For Wowza’s documented example, this is live2; follow your event URL |
| Destination Application Instance | Leave blank for YouTube Live | Do not fill it with the key or an invented instance name |
| Destination Port | 1935 by default for RTMP |
Use current event instructions if they specify otherwise |
| Destination Stream Name | The generated alphanumeric stream key from Studio | Do not use the friendly key label; keep the value private |
For the Destination Host and Destination Application Name, parse the URL shown in Studio. In the documented example rtmp://abc.rtmp.youtube.com/live2, enter abc.rtmp.youtube.com as the host and live2 as the application name. These are example values only. Your event’s URL is authoritative, so do not copy the example just because it appears in a guide.
Leave Destination Application Instance blank. Enter 1935 as the destination port by default for RTMP, unless the current instructions for the event specify otherwise. The destination stream name is the generated key, not the display label you may have given that key. This is the field where a mix-up is especially easy because both values relate to the same YouTube key in Studio.
When the values are entered, review the form once from top to bottom before adding the target. Check the source selection, host, application, blank instance, port and stream name. Avoid putting the key in a target name, comments or screenshots. Wowza’s YouTube Live target instructions are the primary reference if the form differs from this description.
Start the source and check target status
Adding a target does not necessarily enable it, and enabling the target does not start your source. In the application’s Stream Targets settings, enable Stream Targets for the application. Then check the individual YouTube target and enable it if its status is Disabled. These are separate controls, so confirm both rather than assuming that saving the form starts distribution.
Start or connect the source stream to the Live application. Once the source is running, return to Stream Targets and watch the individual target’s status. Wowza describes Waiting as an enabled target that is not yet pushing: the configured source may not be connected, or Engine may still be initialising its destination connection. Waiting alone does not prove that the key is wrong.
Allow the connection to initialise, then check the source side and destination side in order. First confirm that the selected source stream is connected to the application and that the intended video and audio are present. Next recheck whether the target is enabled, and whether its status changes as Engine attempts the destination connection. If it remains Waiting, verify the source name and connection before changing credentials. If the target reports a problem after connection attempts, compare the host, application, port and generated stream name against the event’s current settings.
If the source is not arriving in Engine, troubleshoot that input path separately rather than repeatedly editing the YouTube target. If the input is present but the destination will not connect, recheck the parsed URL and key carefully. Make one correction at a time, then observe the status again; changing several fields at once makes it harder to identify the cause.
Protect credentials and verify the live event
When the target appears to be pushing, return to YouTube Studio and verify the event itself. Check that Studio recognises the incoming feed and that its preview shows the programme you intended to send. A target status in Wowza describes the destination connection from Engine’s side; it is still worth confirming what YouTube receives before you rely on the event for viewers.
Use the event’s preview and stream health information to check for a usable picture and sound. If the event is scheduled, follow Studio’s current controls for starting or managing that event; sending an encoder feed and making an event visible to viewers are related but not necessarily the same action. Confirm the event title and visibility as well, especially when you have more than one event in the channel. YouTube’s own help pages are the source to consult for current event controls and requirements.
Keep the generated key out of public-facing materials after setup. If you capture a screenshot for your own records, crop or obscure the key. If someone needs to help diagnose the configuration, share the non-secret fields and status first rather than sending the key. If you believe the value has been exposed, use YouTube Studio’s available key-management controls and update the Engine target with the replacement value; check the current Studio interface for the exact controls.
For a 24/7 channel, the job is not finished when the first preview appears. Watch a representative stretch of playback and make sure the programme continues as expected, with audio present and the intended event receiving it. The operational concerns differ by channel: a devotional feed may need a clean hand-off between music and spoken segments, while a study loop may depend on consistent levels. For the latter, see the practical checks in normalising audio levels across videos. If your broader plan is an unattended channel, options for keeping a YouTube channel live without a computer on cover a different operating approach; they do not change the field mapping in this Engine target.
A dedicated target is useful when you already operate a source through Wowza Streaming Engine and want Engine to send that incoming programme to the event. If your actual requirement is to loop an uploaded video while your own computer is off, StreamNeo removes the need to keep that local machine running by taking the uploaded file and sending it to YouTube as a 24/7 stream; it is a YouTube-only route rather than a Wowza Streaming Engine target.
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
Is Wowza Video the same workflow as Wowza Streaming Engine?
No. This guide is for Streaming Engine’s dedicated YouTube Live target form. Wowza Video uses a custom RTMP target workflow, so do not transfer its field instructions into Engine’s form.
Should I use the friendly name of my YouTube stream key?
No. Enter the generated alphanumeric code in Engine’s Destination Stream Name field, not the friendly label assigned to the key in Studio. Treat the generated code as a credential and keep it out of public notes and screenshots.
What does Waiting mean in Stream Targets?
Wowza describes Waiting as an enabled target that is not yet pushing. The configured source may not be connected, or Engine may still be initialising the destination connection, so check the source and allow the connection to initialise before concluding that the key is wrong.
Do I need to enable both the application and target?
Yes. Stream Targets for the application and the individual target have separate enable controls. Confirm that the application feature is enabled and that the YouTube target itself is not Disabled, then start the source and verify the event in YouTube Studio.