OBS Studio can send an RTMP stream to Wowza, but the right settings depend on whether your destination is Wowza Video or Wowza Streaming Engine. Identify the product first, then copy the connection details from that specific stream or application rather than using values from a general example.
The practical test is at the receiving end: OBS showing that it has started does not by itself confirm that Wowza is receiving usable video and audio. Set up the destination, enter its own connection values in OBS, and verify the incoming stream before relying on it for an event or an overnight broadcast.
Identify which Wowza product you have
Wowza Video is a hosted service. You create or select a live stream in its control panel and configure that stream to receive an RTMP encoder as its source. The service presents the connection information for that particular live stream.
Wowza Streaming Engine is media-server software installed and managed in your own deployment. You work with applications in Wowza Streaming Engine Manager, and the application’s connection settings provide the values for a publisher such as OBS. You or your administrator may also manage the network and application authentication.
The distinction matters because the products do not share one universal RTMP address or credential set. An example copied from a different product, account, or application may point to the wrong destination or fail authentication. Keep the product’s own control panel open while configuring OBS.
| Destination | Where to get its details | What to verify at the receiving end |
|---|---|---|
| Wowza Video | The selected live stream’s Overview or source connection details | Start the live stream and inspect its preview and metrics |
| Wowza Streaming Engine | The selected application’s Application Connection Settings in Manager | Check the application and live source status in Manager |
If you do not know which product you have, check who hosts and administers the destination. A Wowza Video account is a hosted service with a live-stream page. A Streaming Engine destination is tied to an installed deployment and an application in Manager. Ask the account owner or administrator if that distinction is unclear; guessing from the word “Wowza” is not enough to choose connection values.
Prepare the live-stream destination
For Wowza Video, create or select the live stream you intend to use and make sure its source is configured for an RTMP encoder. Open that stream’s details and locate its source connection information. Do not proceed with a connection copied from a different live stream: the assigned application and stream name are specific to the destination.
For Wowza Streaming Engine, create or select the live application that will receive the publication. In Manager, open its Application Connection Settings. Those settings describe the destination and identify whether source authentication is required. If an administrator manages the Engine, coordinate before changing application settings or network rules.
Prepare a short test scene in OBS before the scheduled broadcast. Use a camera, a media source, or a still scene with audio, depending on what you plan to send. A test gives you a chance to catch a blank source, muted audio, or a profile mismatch while it is safe to adjust. If your source is a long pre-recorded video, it can help to review practical compression choices for long videos before loading it into the workflow.
Write down which destination and application you are configuring, but handle the actual connection values as credentials. Avoid putting a stream key, username, or password into a public document, screenshot, or support post. If you need to share a screenshot for help, obscure secrets first. Keep a private record of the source file, OBS profile, and destination name so that you can distinguish a test from the production setup.
Find the product-specific RTMP connection details
In Wowza Video, use the source connection information displayed for the selected live stream. It includes the ingest server, port, application, stream name, and source credentials where required. Wowza’s guide to connecting an RTMP encoder to Wowza Video describes the connection fields and notes that RTMPS on port 443 is available when the encoder supports it. Use the address and assigned values shown for your own stream, not a URL reconstructed from a sample.
In Wowza Streaming Engine, use the Application Connection Settings for the selected application in Manager. The endpoint and stream name belong to that application and deployment. Wowza’s publisher connection documentation explains the application connection workflow and source authentication. Its documentation identifies TCP port 1935 as the default streaming port; your deployment can use different settings, so confirm the displayed port rather than assuming the default applies.
There are several separate pieces to understand: the server address identifies where OBS connects, the application identifies the receiving context, and the stream name identifies the published stream. Authentication details, if required, are another part of the connection. The control panel’s presentation may combine fields differently, so follow its labels and the receiving product’s instructions rather than forcing them into an example from elsewhere.
The distinction is especially important when an OBS screen offers a server field and a stream key field. A complete RTMP connection may be represented across more than one field; do not assume that the stream name, application, and authentication all belong in one box. Match each value to the field and format specified by your destination and OBS. If a detail is absent or ambiguous, stop and consult the relevant account documentation or administrator before testing.
Configure OBS output
Open OBS Studio and go to Settings > Stream. Choose the custom service or custom streaming-server option rather than a preset for another platform. OBS’s streaming setup guide explains how to select a custom server and enter the server URL and stream key.
Enter the server address and stream name or key using the mapping required by your Wowza product’s connection details. If Wowza Video supplies separate source username and password fields, enter them in the corresponding OBS fields if available and follow Wowza’s encoder instructions. For Streaming Engine, provide source credentials when the application requires authentication. Do not place a password in a field intended for the stream name merely because the OBS form has fewer fields than you expected; check the product-specific instructions for the correct arrangement.
Then configure the picture and sound under OBS’s output and video settings. There is no single bitrate, resolution, frame rate, or audio setting established for every Wowza product and deployment. Choose values appropriate to your source, available upload capacity, and the destination’s requirements. OBS’s general guidance notes that video bitrate should be considered against upload speed and the service’s limits; it is not a guarantee that one particular setting will suit every connection.
If you are sending a continuous music or devotional stream, listen to the scene locally before publishing and confirm that the intended source is active. If you are sending a camera, check the framing and lighting as well as audio. A stream can connect successfully while transmitting a silent or unintended scene. Keep a note of the working OBS profile, but do not let saved settings substitute for checking that they still match the destination’s current connection values.
Check stream health and audio
Treat the OBS status and the Wowza status as two different checks. OBS can report that it is attempting or maintaining a connection, but the destination’s preview or application status is the evidence that the receiving side has accepted the publication. For Wowza Video, start the live stream as its instructions require, start OBS, and inspect the stream preview and metrics. For Streaming Engine, check Manager for the application and live source status.
Check the picture in the receiving preview. Confirm that it is moving when expected, has the intended orientation and crop, and is not blank or frozen. For a looped video, watch long enough to see that the source is progressing; a preview that appears briefly is not proof that the planned programme will run as intended.
Check sound separately. Listen for the intended microphone or media audio, make sure it is not muted, and check that it remains intelligible at the receiving end. If your source has several audio channels, confirm the result required by your workflow rather than assuming every destination retains every channel. OBS documents multichannel RTMP ingestion scenarios, but notes that in the described server-side recording context only the first two channels are retained; do not rely on multichannel behaviour without checking the exact path you use.
For an always-on YouTube workflow, Wowza may be one stage in a longer publishing chain rather than the final audience destination. Make a short test of the entire path, including any onward delivery or platform hand-off, before treating the Wowza ingest preview as proof that viewers can see the final broadcast. If the goal is to keep your computer off for a continuous YouTube channel, a separate cloud streaming workflow for a 24/7 channel may address the specific problem of leaving a local machine running; it does not change which Wowza values OBS needs when publishing to Wowza.
Test the connection and troubleshoot
Before a real broadcast, make a short test that includes the same scene, audio source, network path, and OBS profile you intend to use. OBS’s Quick Start guide recommends testing before a first live broadcast. Check the receiving Wowza destination during the test, not only the OBS interface. Stop and correct any issue before announcing the stream or relying on it for a scheduled programme.
If OBS fails immediately, compare the full server, port, application, and stream name with the settings for the correct Wowza product. Check for extra spaces or a value copied from another account. Do not swap a Wowza Video address with a Streaming Engine application endpoint, even if the fields look similar.
If the destination reports an authentication problem, verify the source username and password and whether authentication is enabled for that application. Streaming Engine source authentication is required by default unless the application has been configured otherwise. For Wowza Video, use the source credentials assigned or displayed with the selected stream. Do not respond to an authentication error by disabling protection without understanding who else could publish to the application.
If the connection stalls or cannot reach the destination, confirm the configured port and ask the network administrator to review any relevant firewall rules. TCP 1935 is the documented Streaming Engine default, not proof that a particular deployment is reachable on that port. Wowza Video documents RTMPS on port 443 for encoders that support it; this may be an available configuration, not a universal fix for network problems. Check the current product instructions and the actual account settings before changing protocols.
If Wowza shows a connection but no usable picture or sound, return to the OBS scene and output settings, then check the receiving preview again. Confirm that the right source is visible, that audio meters respond when expected, and that the chosen output profile suits the destination’s requirements. Change one setting at a time and repeat the test so you know which change affected the result.
For a continuous channel, a successful first test is only a starting point. Check the workflow again after changes to the source file, audio devices, network, OBS profile, or destination application. Keep the working connection details private and maintain a clear record of which OBS profile is for which destination. If you are also planning a long-running YouTube channel, the practical considerations in the cost of 24/7 church streaming in India can help separate the publishing setup from the broader operating plan.
When you are testing a different kind of continuous channel, the source material and publishing destination still deserve their own checks. A YouTube playlist workflow for an always-on bhajan stream is one example of a source-specific setup; it is not a substitute for verifying a Wowza RTMP connection when OBS is the encoder.
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 use the same RTMP URL for Wowza Video and Wowza Streaming Engine?
No. Use the connection details shown for the particular live stream in Wowza Video or the selected application in Streaming Engine Manager. Do not carry an endpoint, application, stream name, or credentials across products or accounts.
Does OBS have a Wowza preset?
You can configure OBS using its custom service or streaming-server option and enter the destination’s supplied values. Follow the field mapping in the instructions for your specific Wowza product, especially when source credentials are separate from the stream name.
Is port 1935 required?
No universal port applies to every Wowza destination. Wowza documents TCP 1935 as the default for Streaming Engine, while the actual application settings control your connection; Wowza Video also documents RTMPS on port 443 for encoders that support it.
How do I know the stream is working?
Check both OBS and the receiving Wowza destination. Confirm the incoming preview or live source status, then verify picture and sound during a short test before relying on the setup.