RTMP-In in Streamlabs Talk Studio is called Stream Forwarding. You select the linked destinations in Talk Studio, copy its Ingest Server URL and Stream key into your source application's custom streaming-server settings, then start the broadcast from that source application.
The direction matters: Stream Forwarding receives a signal from an external application and sends it to destinations linked in Talk Studio. It is different from Talk Studio's Custom RTMP destination, which sends a Talk Studio broadcast out to another platform.
What Stream Forwarding means
Talk Studio uses Stream Forwarding for the workflow some broadcasting applications call RTMP-In. The source application produces the live signal; Talk Studio provides the connection details and forwards that signal to the destinations you select there. Streamlabs names OBS, Streamlabs Desktop and Zoom as examples of source applications. The labels in another application's settings may differ, but the essential handoff is its custom server URL and key.
It helps to picture the two sides before opening settings. Talk Studio is where you choose the destinations and obtain the ingest details. The source application is where you enter those details and begin sending video and audio. Starting a stream in Talk Studio alone does not complete this workflow; the external source must send its broadcast.
Do not confuse this with a feature called Custom RTMP destination in Talk Studio. With that separate, outbound workflow, Talk Studio is the source and the destination platform supplies its RTMP URL and key. With Stream Forwarding, Talk Studio supplies the Ingest Server URL and Stream key to the source application. Swapping the two sets of details is a common conceptual mistake, so check which product is receiving the signal before pasting anything. Streamlabs explains the separate destination workflow in its Talk Studio Streaming Destinations guide.
This is a software configuration task, not a special hardware requirement. You can choose the source application around your existing workflow: for example, whether you need custom scenes, several camera sources or a particular participant layout. For a broader explanation of connection protocols, see our guide to RTMP, RTMPS and SRT for always-on streams. Protocol knowledge can make the URL/key handoff easier to understand, but you do not need to change protocols to follow Streamlabs' documented steps.
Choose linked destinations in Talk Studio
Sign in to Talk Studio and open your profile or account settings. Choose Stream Forwarding. On that page, select the destinations that should receive the forwarded broadcast, or add a destination if the option is available to you. Then enter the stream title and description and save the settings. These choices define where Talk Studio will forward the source application's signal; they are not configured by selecting a destination inside the source application's custom-server form.
Use the destination list shown in your Talk Studio account rather than assuming that every service you have used elsewhere is available for forwarding. Streamlabs' help article explicitly lists LinkedIn and Twitter as unsupported for Stream Forwarding. Availability can change, and the actual destination set can depend on the current product and account, so verify it in Talk Studio before planning a broadcast around a particular destination.
The distinction is useful when you are comparing workflows. If you want to use an external application for your scenes or cameras but keep destinations managed in Talk Studio, Stream Forwarding is the feature to configure. If instead you are broadcasting from Talk Studio's browser studio to an external RTMP destination, that is the separate Custom RTMP destination workflow. Streamlabs' official Stream Forwarding instructions describe the linked-destination step and the incoming handoff.
For an always-on channel, a destination workflow is only one part of planning. A continuous prerecorded broadcast has different operating needs from a scheduled conversation or interview, so be clear about whether this setup is for a session or a longer-running channel. Our guide to cloud services for a 24/7 prerecorded YouTube live stream covers that separate decision. Stream Forwarding should not be read as a promise that a source application or any destination will run continuously without attention.
Get the ingest URL and stream key
After choosing the destinations and saving the stream title and description, locate the connection details on the Stream Forwarding page. Talk Studio supplies an Ingest Server URL and a Stream key. Copy both into the source application's custom streaming-server settings in the next step. Treat the key as a credential: do not paste it into public notes, show it in a screen recording, or share a screenshot that exposes it.
The ingest URL tells the source application where to send the broadcast signal. The stream key identifies the stream configuration on the receiving side. The two values work as a pair for this handoff, so do not substitute a URL from a destination's own setup page or a key from another service. If Talk Studio provides new details after you change settings, use the current values shown there rather than relying on an older copied note.
Talk Studio's terms are especially helpful if you are looking up instructions. Search for Ingest Server URL and Stream key on the Talk Studio side, then look for a Custom Streaming Server or equivalent option in the source application. The exact labels and location may vary with application versions, so follow the current help for the application you are using if its menus no longer match an older guide.
This is also where the inbound/outbound distinction prevents wasted troubleshooting. For Stream Forwarding, copy Talk Studio's URL and key into the source. For a Custom RTMP destination, you would instead obtain the destination platform's URL and key and enter them in Talk Studio. Streamlabs' guide to streaming to a Custom RTMP from a browser documents that other direction; it is not a replacement for the Stream Forwarding instructions.
Enter the details in the source application
Open the streaming settings in the application that will produce the broadcast. In Streamlabs Desktop, Streamlabs' documented route is to open the gear or settings menu, choose Stream, then Stream Type, and select Custom Streaming Server. Paste Talk Studio's Ingest Server URL into the server field and its Stream key into the key field, then apply or save the change as the application requires.
For OBS or Zoom, use the equivalent custom-server or streaming destination controls in the current version of that application. Streamlabs names these applications as examples, but the reviewed official guidance does not establish current menu clicks for every OBS or Zoom version. Check the application's own current help for those source-specific steps rather than assuming the Streamlabs Desktop menu names apply unchanged.
Before going live, check that the URL is in the server or URL field and the key is in the key field. Keep the key private, especially if you are sharing your desktop during a call. If the source offers a choice between a preconfigured platform and a custom server, use the custom-server route for this Talk Studio handoff; a preset for another platform may use different receiving details.
Source choice should follow the job you need done rather than a guess about which application is universally best. OBS may suit a workflow built around custom scenes; Zoom may suit sending a call; Streamlabs Desktop may suit people already working in that application. These are examples of how the applications can fit the use cases Streamlabs describes, not a test ranking. Our article on running a church YouTube sermon stream with Docker and FFmpeg discusses a different source workflow, which may be more relevant if you are planning an automated, long-running broadcast rather than a live Talk Studio session.
A stable connection remains important because the source has to send a live signal while Talk Studio forwards it. Streamlabs' Talk Studio Getting Started page says a stable internet connection is required and prefers Ethernet. Its listed upload guidance is shown below; these are Streamlabs' stated figures, not a guarantee for every source, destination, video layout or network.
| Output resolution | Required upload listed by Streamlabs | Recommended upload listed by Streamlabs |
|---|---|---|
| 720p | 5 Mbps | 10 Mbps |
| 1080p | 10 Mbps | 20 Mbps |
Streamlabs also lists Google Chrome or Safari in its Talk Studio requirements. These browser requirements concern Talk Studio; they do not establish which browser or computer setup a separate source application requires. Check the Talk Studio Getting Started requirements alongside the current requirements for your source application. If you are using Wi-Fi, test from the place where you intend to broadcast; a speed result taken elsewhere does not show how stable the link will be at the stream location. Ethernet is a practical option where available, not an obligatory purchase.
Start the source stream
Once destinations are saved in Talk Studio and the source application has the correct URL and key, start the stream from the source application. That is the application sending the broadcast signal. Then check Talk Studio and the selected destination views to confirm that the signal is arriving where expected. The documented order is configuration first, then start from the source; it is not to begin by guessing at a destination's RTMP settings.
If nothing appears, work through the handoff in order. Confirm that the selected destinations remain the ones you intend to use and that the title and description were saved. Check that the source is using Talk Studio's current Ingest Server URL and Stream key in its custom-server fields. Confirm that the source application has actually started sending, and that its own stream status does not show an error. A problem in any one of these places can look like a destination issue from the outside.
If the source says it is live but a destination does not show the broadcast, avoid changing several settings at once. Recheck the selected destination set in Talk Studio, then inspect the source connection details and status. Use the current Talk Studio help when a menu has changed, and check the relevant destination's own account or live-stream settings if access is in question. The available research does not establish a universal recovery procedure for every source and destination combination.
For a one-off interview or community programme, it is sensible to rehearse the full path before the planned start: configure the intended destinations, send a brief test, and confirm the result. That rehearsal checks more than whether a URL is accepted; it gives you a chance to verify the intended layout, audio and destination. Keep the stream key out of any test notes that will be shared. A rehearsal reduces avoidable surprises but cannot guarantee that a later network or service interruption will not occur.
Review Streamlabs' listed use cases
Streamlabs identifies several reasons to use Stream Forwarding: sending a Zoom call to social destinations, showing custom layouts or scenes made in OBS, putting more than nine participants on screen, and adding multiple camera sources. These are vendor-listed use cases, not capabilities independently tested for this article. Consider them as examples of the workflows Streamlabs says the feature is intended to support, then confirm the particular combination you need in the current product guidance.
The examples point to the practical choice you make when selecting a source application. If your main need is a call, the example names Zoom. If you need a custom scene, Streamlabs names OBS. If you need several camera sources or a larger on-screen group, consider how you will build that layout in the source application and whether it fits your session. The forwarding setup itself does not create a scene, add a camera or arrange participants; those choices belong to the source workflow.
Do not extend the examples beyond what Streamlabs lists. The support article names LinkedIn and Twitter as unsupported for Stream Forwarding, and it does not establish that every possible destination or account configuration works. The destination options shown in your Talk Studio account and current official documentation are the appropriate checks before you schedule a broadcast.
Streamlabs also notes an Instagram caveat in its destination troubleshooting guidance: Instagram Live RTMP settings may not be available to every account, and it advises checking the account's Live settings. Its guidance about using a third party to obtain a dedicated server URL and key, and selecting Portrait Mode for an Instagram Custom RTMP destination, concerns that Instagram/custom-destination workflow. It does not change the general Stream Forwarding steps described above, and it should not be taken as evidence that Instagram is a universally available Stream Forwarding destination. See Streamlabs' destination troubleshooting guidance for the current caveat.
If your separate goal is a prerecorded channel that continues when your own computer is off, the operational question is no longer only how to forward a live source. A cloud-based service can remove the need to keep a local computer running for that specific workflow. StreamNeo addresses that particular pain by letting you upload a video once and run it as a YouTube live stream without your computer left on; it is YouTube-only, so it is not a substitute for Talk Studio's multi-destination live-session 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 RTMP-In the same as Stream Forwarding in Talk Studio?
Yes. Talk Studio calls its incoming external-source workflow Stream Forwarding, also known as RTMP-In. It receives the source application's signal and forwards it to destinations linked in Talk Studio.
How do I connect OBS to Talk Studio?
Select and save the destinations in Talk Studio's Stream Forwarding page, then copy its Ingest Server URL and Stream key into OBS's current custom-server settings. Menu names can change, so use OBS's current help for the exact clicks. Start the broadcast in OBS after the connection details are in place.
Which side supplies the URL and stream key?
For Stream Forwarding, Talk Studio supplies the Ingest Server URL and Stream key, and you enter them in the source application. For Talk Studio's separate Custom RTMP destination, the destination platform supplies its RTMP details to enter in Talk Studio.
Does Stream Forwarding support every destination?
No. Streamlabs lists LinkedIn and Twitter as unsupported, and the destinations available to you should be checked in Talk Studio. Do not assume that an account or destination works simply because it can be used in another streaming workflow.