Custom RTMP Destinations let you send your LIGR Live stream output to any platform or service that accepts an RTMP endpoint, beyond the built-in options like YouTube Live or Facebook Live.
What is a Custom RTMP Destination?
A Destination is where your stream is sent after it leaves LIGR Live. While LIGR supports direct integrations with common platforms, a Custom RTMP Destination lets you push your stream to any third-party service, internal distribution system, or secondary platform that provides an RTMP URL and stream key.
Common reasons to use a Custom RTMP Destination:
• Streaming to a platform not listed in the built-in Destination options
• Sending the stream to a secondary CDN or distribution partner
• Pushing to an internal monitoring or archive server
• Multi-streaming to additional platforms alongside your primary Destination
Before You Start
Make sure you have:
• A match created in LIGR Live with an Input configured
• The RTMP server URL from your target platform
• The stream key or stream name from your target platform
• Appropriate permissions (Owner, Admin, or Gameday Operator)
[ Image placeholder: The Streaming tab in the left sidebar with a match selected ]
Adding a Custom RTMP Destination
1. Open the Matches tab from the left sidebar and select the match you want to configure.
2. Navigate to the Stream View or streaming settings page for that match.
3. Find the Destinations section.
4. Click Add Destination.
5. Choose Custom RTMP as the Destination type.
6. Enter a recognisable name for the Destination so you can identify it later.
7. Paste the RTMP URL provided by your target platform.
8. Paste the Stream Key provided by your target platform.
9. Save the Destination.
[ Image placeholder: Custom RTMP Destination form showing name, RTMP URL, and Stream Key fields ]
Starting the Stream to Your Destination
1. Confirm your Input is connected and healthy.
2. In the Destinations list, enable the Custom RTMP Destination you just created.
3. Start the stream from the match.
4. Verify the stream is being received on your target platform.
[ Image placeholder: Destinations list with a Custom RTMP Destination enabled and streaming ]
Tips
• Always test your Custom RTMP Destination with a short test stream before going live.
• Keep your RTMP URL and stream key private — anyone with these details can push to your Destination.
• You can add multiple Destinations to a single match, including a mix of built-in and Custom RTMP options.
• Use the Multiview in the Streaming tab to monitor that your output is flowing correctly.
• Label each Destination clearly (e.g. "Backup CDN" or "Partner Feed") so operators can identify them quickly.
Common Issues
Stream not appearing on the target platform
• Double-check the RTMP URL and Stream Key for typos or extra spaces.
• Confirm the target platform is ready to receive an incoming RTMP stream.
• Verify your Input is active and healthy in LIGR Live.
Connection drops or reconnects
• Check your encoder and network stability on the Input side.
• Confirm the target platform supports the bitrate you are sending.
• Review stream health indicators in the Stream View page.
Stream key rejected
• Some platforms regenerate stream keys periodically — get a fresh key and update the Destination.
• Ensure you are not already streaming to the same key from another source.
Graphics and overlays not visible at the Destination
• Custom RTMP Destinations receive the final output with overlays burned in. If graphics are missing, verify they are triggered correctly in the Control Room before starting the stream.