If you are looking up how to stream from vMix to Wowza Streaming Cloud, the practical route is to create a live stream in Wowza Video, copy the connection details generated for that stream, and enter them in vMix. The receiving service is currently called Wowza Video in its surfaced documentation and interface; “Wowza Streaming Cloud” is familiar legacy wording.
Wowza documents vMix as a supported stream input. The exact setup screens and available controls depend on the workflow and account interface you see, so use the current stream details in your account rather than copying an old screenshot or an example address.
Wowza Streaming Cloud and the current Wowza Video name
Wowza’s current documentation calls the service Wowza Video. Some older documentation and search results use Wowza Streaming Cloud, and some setup pages are explicitly marked legacy. The change in naming matters because a guide that says “Streaming Cloud” may still explain the underlying RTMP concepts, but its screen sequence should not be treated as a description of the current interface.
The connection itself is a hand-off between two applications. Wowza Video receives the incoming contribution from vMix, then processes it according to the stream’s configuration. vMix is the encoder in this arrangement: it sends the programme output to the server address and stream-specific name or key provided for the Wowza stream.
Wowza’s current quick live stream setup documentation and custom stream setup documentation both describe vMix among the supported input choices in relevant workflows. Depending on the path offered to you, you may select vMix specifically, or use the generic RTMP encoder workflow. Neither route makes the values interchangeable between streams.
This guide focuses on the Wowza side of creating the receiver and the practical checks on both ends. It deliberately does not give a sample server, key, or credential as though it would work for your account. Those values are generated for the particular stream you create.
Prepare the Wowza Video live stream
Start by creating a live stream in Wowza Video, using the quick or custom setup path available in your account. Where the interface asks for an input or stream input type, choose vMix if it is offered and you want its specific connection assistance. If it is not offered in your workflow, the generic RTMP encoder path is the relevant alternative.
Think through the stream choices before you create it. The source resolution or profile should reflect what vMix will send. Wowza notes that input resolution affects the adaptive bitrate output ladder, so selecting a profile that does not match the actual source can lead to unnecessary conversion or an unsuitable output. If your vMix project is produced at a particular resolution, use the corresponding supported input choice rather than guessing from the eventual viewer playback quality.
If manual region selection is shown, choose a processing region near where the stream originates. This is a choice about the path from your encoder to the service, not a promise about viewer experience. Some documented flows select a region automatically when RTMP autostart is enabled; in those flows, region and push/pull controls may be hidden. Read the options visible in your account rather than expecting every control to appear.
Also decide whether the workflow’s start and stop behaviour suits your use. Autostart is documented as enabled by default in relevant quick and custom flows, and some settings cannot be changed after stream creation. If this is a scheduled broadcast, consider whether the stream should wait for the encoder or start when the source connects. If you run a channel continuously, consider how you will stop the receiver during maintenance and whether an automatic stop is appropriate.
Recording is another setup decision where it is offered. A recording can be useful if you need a copy of a programme, but it is separate from the live ingest working correctly. Do not assume that a recording setting is enabled just because vMix is sending video, or that a saved recording replaces the need to verify the live preview.
For a channel built around a recurring file or a long-running programme, the wider operating plan matters as much as the initial connection. The practical considerations in running a Marathi devotional YouTube livestream from a cloud server can help you think about continuity when production and the receiving stream are not on a single desk.
Select the vMix input workflow
There are two useful ways to frame the setup, but the available controls vary with the Wowza workflow. A vMix-specific input choice may expose a dedicated connection method or connection code. The generic RTMP encoder route treats vMix as an encoder that publishes to the stream’s server and application details. Use the route your account actually provides; do not attempt to force a legacy set of menu steps onto a different interface.
| Setup route | What it is for | What to check before proceeding |
|---|---|---|
| vMix as the selected input | A specialised input workflow where offered, with connection assistance for vMix | Whether the stream details provide a connection code or other vMix-specific instructions, and which controls are available in this workflow |
| Generic RTMP encoder | A general route for an encoder that can publish over RTMP | The server/address, port, stream name or key, and any source authentication shown for this stream |
The comparison is about workflow, not quality. A vMix-specific route is useful when it gives you clear details for the software you are using. A generic RTMP route is a sensible fit when the specialised option is absent or when you are following Wowza’s encoder guidance. The stream-specific endpoint and any credentials remain the authority in either case.
Push and pull describe which side initiates or supplies the media connection in the documented workflow. You do not need to change those concepts casually to make a connection work. In some flows, RTMP autostart is enabled and the interface hides manual push/pull selection; in others, you may see those controls. Follow the choice associated with the stream you created and confirm the service is in the state required to receive the encoder.
Do not assume that one setup route supports every feature or presents every field in the same place. The Wowza custom stream setup page describes choices such as input, region, profile, recording and start behaviour; the quick setup page describes a different path. Both are primary references, and both are more reliable for current wording than an old walkthrough with screenshots from an earlier dashboard.
Copy the stream-specific connection details
Once the stream exists, open its details or Overview and locate its source connection information. Depending on the selected workflow, copy the server or address, port if shown, stream name or key, and source username and password if Wowza provides them. Treat these as private connection credentials. Do not post them in a public support thread, video description, or screenshot.
The field labels may differ across account interfaces and workflows. The important point is to map each Wowza-generated value to the corresponding destination or authentication field in vMix, rather than to enter a remembered example. If the details provide a complete connection code or URL for vMix, use that as directed by the workflow and avoid rebuilding it from fragments unless the instructions ask you to.
Wowza’s legacy RTMP encoder guide documents an RTMP URL format and describes RTMP on its default port, as well as RTMPS on port 443 when supported by the encoder. That page is specifically marked legacy, so regard those as format notes from that guide, not as universal connection values or a guarantee that every current workflow uses the same fields. Use the endpoint and security options displayed for your own stream.
A common source of wasted time is copying only part of the connection information. A server address without the stream name or key is not a complete destination; a key from another stream is not a substitute. If the interface provides a source username and password, do not confuse them with the key or paste them into an arbitrary field. Keep the details open while configuring vMix, and copy them exactly, including punctuation and case where applicable.
If you are documenting the setup for someone else, record the names of the fields and where to find them, not the secret values. That leaves you a usable runbook without exposing credentials. If the stream is recreated or its details are regenerated, revisit the runbook and replace the old private values in the encoder configuration.
Configure vMix and start streaming
In vMix, open the streaming destination configuration for the output you intend to send. Enter the Wowza-provided destination information in the matching server or URL, stream or key, and authentication fields. The exact labels and locations can differ between vMix versions, so consult the documentation for your installed version if a label does not match what the Wowza details call the value.
Avoid adding encoder settings that have not been requested by the Wowza workflow. The goal at this stage is to establish the destination and send the intended source profile. If the Wowza setup asked you to select an input resolution, make sure the vMix output is consistent with that choice. A mismatch can make diagnosis harder, because a successful connection and a usable picture are different tests.
Before starting, confirm that the intended vMix production is on programme output, audio is present if required, and the destination fields correspond to the stream you just created. If the Wowza workflow requires the receiving stream to be started first, start it in Wowza Video. Then start vMix’s stream output. If the chosen workflow autostarts on connection, follow the instructions shown for that stream rather than assuming a separate manual start is needed.
For an event, keep the receiving stream details and the vMix configuration available to the operator, but protect the credentials. If a second person is monitoring the service, give them the stream name and the checks to perform, not the secret key. This distinction makes it easier to coordinate a handover without turning connection details into public information.
A stream that is intended to run as part of a broader channel has different failure points from a one-off event. The guide to improving live stream quality and preventing dropped frames is useful for separating encoder-side instability from a receiving-service connection problem. If the production relies on a schedule, the vMix scripting guide for switching playlists covers a related production concern; it does not replace configuring and checking the Wowza destination.
Verify reception in Wowza Video
After vMix begins sending, return to the stream’s details or preview/status view in Wowza Video. Look for evidence that the source is connected and that video is arriving. A connected state alone may not tell you whether the intended picture and audio are present, so check the preview as well as the status text where available.
The legacy encoder guide describes preview frames refreshing at intervals and notes that a push connection can take time after the service starts. Those are observations from a legacy workflow, not a current-interface timing guarantee. Give the selected workflow a moment to establish its connection, then use the status and preview shown for your stream. Do not conclude that a key is wrong solely because a preview has not changed immediately.
If no picture arrives, work through the chain rather than changing several settings at once. First confirm that the Wowza stream is in the state needed to receive the encoder. Then compare the vMix destination against the stream-specific server, port, stream name or key, and any source authentication. Confirm that you selected the intended input workflow and that the source profile is compatible with the profile chosen in Wowza.
If the preview appears but the result is not what you intended, check the vMix programme output, video format and audio routing separately. A successful ingest does not establish that the right camera, playlist, or soundtrack is being sent. Likewise, a clean vMix output monitor does not prove that the destination credentials or receiving workflow are correct. Use the two applications’ status views to isolate which side needs attention.
Once reception is confirmed, note the working configuration without recording secrets in an unsecured place. For repeated broadcasts, include the stream name, the selected workflow, the profile choices, and the order used to start the receiver and vMix. A short operational note is more useful at the next session than a screenshot of an old dashboard.
Stop the stream and keep the setup maintainable
At the end of a broadcast, stop the vMix output and stop the Wowza stream if the selected workflow does not stop it automatically. Start/stop behaviour depends on the choices made during setup, including autostart or autostop where those controls are available. Check the live status after stopping rather than assuming that ending the encoder output ended every part of the service.
For a scheduled event, a deliberate stop avoids leaving an unintended idle or stale output in place. For a continuous channel, stopping may be part of planned maintenance, so write down how to resume the same stream and how to confirm it is receiving again. Do not create a replacement stream simply because a dashboard control is unfamiliar; first check the current details and the workflow guidance for the existing stream.
Treat credentials as changeable operational data. If you recreate the stream, rotate or replace its connection values, or change the selected workflow, update vMix and the runbook together. Keep a secure copy accessible to the people responsible for the broadcast, and remove exposed values from screenshots or public notes. This is basic access hygiene, not a substitute for checking Wowza’s current account controls.
For channels that loop recorded material rather than produce a live programme continuously, the workflow choice has operational consequences beyond the connection. The article on how prerecorded YouTube streams loop addresses a separate viewer-facing question; it should not be read as guidance about Wowza ingest or as a reason to skip testing the actual receiving path.
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 Streaming Cloud still the name of the service?
Current surfaced documentation uses the name Wowza Video, while older material and search queries may use Wowza Streaming Cloud. Some older pages are clearly labelled legacy. Use the current Wowza Video documentation and the interface in your account for present-day setup decisions.
Can I use vMix with Wowza Video?
Wowza’s quick and custom setup documentation lists vMix as a supported input in relevant workflows. You can choose the vMix-specific route if your account offers it, or follow the generic RTMP encoder route. The available fields and workflow controls may differ.
Can I reuse a server address or stream key from a tutorial?
No. The server and other connection details are specific to the stream, and any credentials shown in a tutorial are not yours to reuse. Copy the values from your own stream’s details and treat credentials as private.
What should I check if Wowza Video does not show my vMix picture?
Confirm that the receiving stream is started or configured to autostart as required, then check the endpoint, stream name or key, and any source authentication against that stream’s details. Also confirm the chosen input workflow and that vMix is sending the intended source profile. Use the current status and preview in Wowza Video to verify reception.