A Restream job owns one source-to-destination path. Create one job per destination so a platform error, credential change or output profile can be isolated without disturbing the other outputs.
Before you start
A source that plays correctly before it enters the Restream job.
A destination URL/key or supported destination account.
A tested output codec, resolution and bitrate when transcoding is required.
Settings explained
These are the controls an operator needs to understand. Internal field names and implementation events are intentionally omitted.
Input
Choose one verified media source.
- Input source
Select an SRT, RTMP, NDI, WebRTC/conference, file or supported URL source.
- Source-specific connection
Provide the server, stream identity, participant or URL required by that input type.
Output
Choose one destination for this job.
- Destination type
Supported social platform, RTMP/SRT/HTTP/RTSP/UDP endpoint, NDI output or conference participant.
- Destination URL and key
Credentials and address supplied by the receiving platform.
Media processing
Enable only processing that the destination actually needs.
- Video profile
Codec, resolution, frame rate and bitrate for a transcoded output.
- Audio track and channels
Choose the required source audio and output layout.
- Image overlay
Place a prepared graphic over the outgoing video.
- Pass through
Avoid re-encoding when source and destination requirements already match.
Safe first workflow
- 01
Verify the source independently.
- 02
Create one Restream job and select the source preset.
- 03
Choose one destination and enter its exact URL/key.
- 04
Keep pass-through when compatible; otherwise select a tested transcoding/audio profile.
- 05
Start the job and verify its statistics plus playback at the destination.
Workflow examples
Send one contribution feed to multiple platforms
The same source should reach YouTube, Facebook, Twitch or private endpoints.
How to build it
- 1
Create one Restream job for the first destination and verify it end to end.
- 2
Duplicate the workflow as a separate job for each additional destination.
- 3
Use destination-specific credentials and output settings.
- 4
Monitor and restart only the destination that reports a failure.
Create a continuous channel from a file
A prepared media asset should run as an always-on output.
How to build it
- 1
Upload and preview the file in File manager.
- 2
Use the file as the Restream input and configure continuous playback.
- 3
Choose the output protocol and transcode only if the endpoint requires it.
- 4
Start the job and validate the transition from the end of the asset back to the beginning.
Bridge a conference participant to NDI
One WebRTC participant should appear as a named NDI source in a production network.
How to build it
- 1
Create the video room and verify the participant in the browser.
- 2
Select that participant as the supported input preset.
- 3
Create the NDI output with a production-friendly name.
- 4
Discover and monitor the output on the receiving NDI system.
Verify the result
- The source is healthy before the job starts.
- Restream statistics show active media and the destination confirms ingest.
- Output codec, resolution, audio and overlay match the receiving requirement.
- A failed destination can be stopped or restarted without stopping other jobs.
Troubleshooting
The job is active but the platform is offline
Check- Check the destination URL/key and platform event state.
- Confirm output bitrate.
- Verify codec compatibility.
Repair the destination or output profile while leaving the verified source unchanged.
CPU usage rises after enabling transcoding
Check- Compare source and requested output.
- Remove unnecessary resize/frame-rate changes.
- Review host capacity.
Use pass-through when possible or reduce the profile to a measured capacity target.