The name in this guide’s title is historical: Wowza’s current cloud product documentation and onboarding use the name Wowza Video. To start a new cloud live stream, follow the current Wowza Video workflow and treat the older Wowza Streaming Cloud guide as background, not as a map of today’s screens.
A practical first test is one camera or capture source sent from OBS over RTMP, then checked in Wowza Video’s preview and hosted page. You will need access to a Wowza Video account or trial and a source; the exact choices shown during setup depend on your input type, account and broadcast location.
Wowza Streaming Cloud and Wowza Video are not interchangeable labels
Wowza Streaming Cloud is the name used in older material, including a 2017 user guide. Wowza’s current getting-started documentation is branded Wowza Video, and its detailed tutorial for creating a first live stream is explicitly marked Legacy. That label matters: a tutorial can still explain the shape of the task while showing names, choices or sequencing that you should not assume exist in the current onboarding screens.
For a new setup, start from Wowza’s current live stream quick setup documentation, then use the more detailed legacy getting-started tutorial only as supplementary context. The tutorial’s OBS example remains useful for understanding which connection values go where, but it is not proof that every screen or default is unchanged.
There is also a similarly named product that is easy to confuse with the cloud service: Wowza Streaming Engine. Engine is separate media-server software. It can be used as a source or connected to Wowza Video, but its manager interface and its server address are not the cloud service’s connection details. If you see Engine-specific fields such as an application name or its default RTMP port, do not copy them into a Wowza Video setup unless you are deliberately configuring Engine.
This distinction is useful when you are following an old forum post or guide. First identify whether the instructions refer to Wowza Video in the cloud, Wowza Streaming Cloud by its former branding, or Streaming Engine software. Product identity determines which account, connection information and interface you should expect.
Which documentation to trust for a new setup
Use current Wowza Video documentation for current product terminology, input choices and behaviour. The quick setup material describes a range of current input types, including RTMP, SRT, RTSP, WebRTC and stream-from-file, and has specific routes for some encoders and devices. The exact options visible can depend on the kind of source selected, so it is normal for a camera-to-RTMP path not to look like a setup for an IP camera or a file input.
The older tutorial is still useful for the basic OBS mapping: a server address goes in OBS’s Server field, a stream name goes in Stream Key, and generated source credentials may be needed for authentication. It also gives a worked sequence for manually starting a stream and checking a hosted page. Keep those details in the category of an example, then confirm how your current stream’s Overview page presents its connection information and start controls.
A good reading rule is to prefer the current page when a label conflicts, and to use the legacy page to understand the reason behind a step rather than to recreate a screen from memory. If you are troubleshooting, record the label you actually see and compare it against the current quick setup instructions. Do not assume that a setting documented in the legacy tutorial is editable later or available for every input.
YouTube is a separate part of the path. Wowza carries the source into a stream, while YouTube receives a broadcast through its own live control room and stream settings. Before planning a public test, check YouTube’s current live streaming eligibility and activation help and the available live-stream controls in YouTube Studio. A successful Wowza preview does not itself establish that a YouTube channel is ready to broadcast.
Start with the current Wowza Video workflow
The general job is to create a live stream in Wowza Video, select an input that matches your source, configure the processing and delivery options that you need, then connect the source and verify playback. The quick setup page is the current starting point for choices such as RTMP, SRT or RTSP, and for whether the source is pushed to the service or pulled from an endpoint. Do not try to force every source through the OBS example if the device has a more suitable documented input.
For the worked beginner route in this article, choose OBS and RTMP because it makes the relationship between encoder fields and stream connection information easy to see. You need a Wowza Video account or trial, OBS, and a camera, capture device or other video input OBS can use. The Wowza tutorial recommends a modern browser that supports HTML5 and CSS3 and says the latest Chrome has been the most extensively tested; use a supported, up-to-date browser if the setup page behaves unexpectedly.
Before creating anything, decide what you want to test. If the goal is simply to confirm that camera video reaches a viewer, a hosted page can provide a convenient playback check. If the intended destination is an existing site or a platform such as YouTube, plan to check the relevant player or destination separately as well. A test on one playback surface does not prove every downstream destination is configured correctly.
The key choices are not just technical. The source protocol must match what the device can send, the processing region should make sense for the source, and the playback route should match where viewers will watch. You do not need to optimise every setting before the first test; you do need to recognise which decisions are difficult to change later and which are optional refinements.
Create a live stream and choose its behaviour
In the current workflow, begin with Add Live Stream and give the stream a name that identifies its purpose or source. A name such as “studio camera test” is easier to distinguish from a later event than a generic label. Select an input type that matches the encoder; for the OBS walkthrough, use Other RTMP when that is the available choice for a generic RTMP encoder.
Review the broadcast location rather than accepting a default without thought. Wowza’s older tutorial says the suggested location is based on the browser’s time zone, while the general aim is to use a location close to the source to reduce network distance and latency. Current quick setup also describes region selection in relation to the source and input. Choose based on where the camera or encoder is sending from and confirm the current account’s available locations and features.
Next, complete the source and transcoder options that the current page requires. For a first test, do not treat every processing choice as mandatory. Adaptive bitrate creates multiple output renditions for different viewing conditions, whereas passthrough sends the source rendition without transcoding. Wowza documents passthrough as requiring a 24x7 subscription and notes it is not available in all broadcast locations; verify eligibility in the account before designing around it. If you are unsure whether you need multiple renditions, retain an appropriate default rather than selecting a mode solely because the name sounds simpler.
| Choice | What it changes | Practical first-test approach |
|---|---|---|
| Input protocol | How the source sends or supplies video | Match the source’s supported protocol; use RTMP for the OBS example |
| Region | Where Wowza processes the stream | Review the suggestion against the source’s actual location |
| Adaptive bitrate or passthrough | Whether outputs include multiple renditions or only the source rendition | Use the available default until you know delivery needs and eligibility |
| Hosted page | Whether Wowza provides a page for playback testing | Choose it if you want a quick browser smoke test |
The hosted page choice deserves particular attention. In the tutorial’s walkthrough, selecting Yes provides a straightforward place to test playback without building your own webpage. The same tutorial says a hosted page cannot be added after stream creation if you initially choose no. If you already have an external player or site, the supplied embed code and playback URLs may still be useful; player-specific settings can differ when you use another player.
Some current RTMP options affect how the stream starts and stops. The quick setup documentation says autostart is available and enabled by default in its RTMP flow: a valid encoder stream can start the live stream, and autostop can stop it after valid RTMP stops. It also says autostart cannot be edited after initial creation and that enabling it prevents transcoder security authentication. This is different from the legacy tutorial’s manual start sequence, so read the current options before committing to the stream configuration.
Connect OBS or another source
Once the stream exists, open its Overview page and locate Source Connection Information or the corresponding current connection panel. For the tutorial’s OBS route, the values are generated for your stream. Do not reuse example server addresses, stream names, usernames or passwords from a guide, and do not publish your own stream key or credentials in screenshots or public notes.
In OBS, the legacy walkthrough maps those values through Settings → Stream. Set Service to Custom, place Wowza’s Primary Server in Server, and place Stream Name in Stream Key. Enable Use authentication where the current connection instructions require it, then enter the generated Source Username and Source Password. Configure OBS to capture the intended camera or capture device, save the settings and check that the selected video source is visible before sending it.
Those field names explain the mapping, but your current Wowza Video screen is the authority for whether authentication is required and which values it supplies. This matters because the current quick setup notes a relationship between RTMP autostart and transcoder security authentication. If you enabled autostart or chose a different input type, the applicable connection method may not match the manual tutorial exactly.
If the camera is connected through a capture device, verify that OBS sees the device before investigating Wowza. If you are using a hardware encoder, IP camera or a software other than OBS, use its own current instructions alongside the protocol and credentials shown in Wowza Video. The useful comparison is practical: can the source send the selected protocol, does it require a push or pull connection, and can you enter the supplied authentication details in its encoder settings?
This is also where you should keep cloud and local details separate. A Wowza Video cloud stream’s generated server and stream name are specific to that stream. Wowza Streaming Engine’s manager address or server IP belongs to a different configuration. Mixing the two usually produces a connection failure that looks like a bad password but is actually the wrong endpoint.
Test playback and troubleshoot before sharing
For the manual sequence described in Wowza’s tutorial, start the live stream in Wowza Video first and then choose Start Streaming in OBS. Watch for a preview in Wowza Video, then open the Hosted Page URL and press play. If the current stream has autostart enabled, its behaviour differs: a valid incoming RTMP stream can trigger the start. Follow the current stream’s displayed instructions rather than pressing buttons in an order copied from a legacy screen.
Use the result to isolate the fault. If OBS does not show its own camera source, troubleshoot capture-device selection locally. If OBS sees the source but Wowza does not show a preview, check the selected protocol, server, stream name and any required authentication against the current connection panel. If Wowza previews the source but the hosted page does not play, investigate the playback URL, player choice and delivery settings rather than repeatedly changing encoder credentials.
The older tutorial describes a Statistics panel with connection, transcoding and delivery metrics, and says its preview thumbnail updates every five seconds. Those are useful concepts for deciding where to look, but rely on the current page’s own labels and available metrics. A healthy source connection and a playable output are separate checks: confirm both before sharing the link with viewers.
If your destination is YouTube, verify it at the destination too. The YouTube control room has its own stream status and viewer playback path; a green-looking or visible preview in Wowza only confirms part of the journey. For a channel intended to stay live, YouTube readiness also includes confirming that live streaming is enabled for the channel and that the correct event or stream is selected. Our guide to YouTube Live Streaming not being available after identity confirmation covers a separate channel-side issue that can block this last leg.
When diagnosing a looping or continuously running broadcast, distinguish source health from platform playback health. A stable feed at the encoder can still reach viewers poorly if the output settings or receiving platform are wrong. The stream health troubleshooting guide for a looping stream is relevant once the issue is on YouTube’s side rather than in the initial Wowza source connection.
When the test is complete, stop the stream deliberately. Wowza warns in its getting-started tutorial that transcoding charges accrue after a stream has been started even when it is not actively receiving content. That article also documents an automatic idle stop after 20 minutes, but it still instructs you to stop the stream when the event ends. Treat automatic stopping as a backstop, not as your normal shutdown procedure: stop in Wowza Video and stop OBS.
When older instructions still help
The 2017 Wowza Streaming Cloud user guide can help explain historic product vocabulary and why older articles refer to Cloud rather than Video. It is not current onboarding authority. Likewise, the detailed Wowza Video first-stream tutorial is marked legacy, so use it selectively for conceptual points such as mapping a generated RTMP server and stream name into OBS or checking a hosted page.
Old instructions can be especially misleading around the sequence of starting a stream, the location of a setting, or the assumption that a choice can be changed later. Current quick setup describes RTMP autostart and its interaction with authentication, while the legacy workflow walks through manually starting Wowza and then OBS. Neither description should be turned into a universal rule for every configuration. Inspect the options and connection panel in your own current stream.
If you have a specific older stream already running, historical instructions may help you recognise its settings or interpret an old account label. For a new stream, create a clean configuration using current documentation and record its current endpoint and credentials securely. If a setup does not match the guide, the mismatch is a reason to check the current documentation, not to guess which hidden menu might have moved.
If your actual aim is an always-on channel made from a repeating video file rather than a camera feed, that is a different source and operating pattern from this first OBS test. Consider whether you need a source that runs continuously without a local computer. StreamNeo removes the need to keep your own computer running for that particular uploaded-file use case, while this guide’s Wowza workflow is about connecting a live encoder source.
A longer-term channel plan should also include YouTube’s limits and day-to-day operational checks, not only the first successful preview. The article on how many live streams you can create on YouTube in one day is useful when planning separate events or repeated launches. If you later choose to run a file-based channel from a cloud source, the guide to streaming pre-recorded video to YouTube Live from a cloud server addresses that different workflow.
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 to use for a new setup?
No. The current cloud documentation and onboarding use Wowza Video. Treat Wowza Streaming Cloud as historical naming and check current Wowza Video documentation for present-day setup choices.
Can I use the legacy tutorial to set up OBS?
You can use it to understand the relationship between the generated server, stream name and OBS custom RTMP fields. Check the current connection panel and setup options before following its start sequence or assuming a setting is available, because the tutorial is explicitly labelled legacy.
Do I need OBS for a Wowza Video live stream?
No. OBS is the worked software-encoder example, not the only source route. Current quick setup covers several input protocols and device-specific paths; choose one your camera, encoder or source can actually provide.
What should I do after the test works?
Confirm playback at the intended destination, stop the Wowza stream and stop the encoder when you have finished. For a YouTube broadcast, verify the channel-side live status separately rather than treating a Wowza preview as proof that viewers can watch on YouTube.