How to Stream to a Custom RTMP Server or Restreamer
Not every destination is a big-name platform. Here's how to stream to a custom RTMP server or restreamer — self-hosted or third-party — using just a URL and stream key.
On this page
The big platforms have one-click buttons, but RTMP works far beyond them. If a destination gives you an ingest URL and a stream key, you can broadcast to it — including a server you host yourself or a third-party restreamer. Here's how to stream to a custom RTMP endpoint.
Key takeaways
- Any RTMP destination is just an ingest URL plus a stream key.
- This covers self-hosted servers, restreamers and niche platforms.
- Pair it with a looping playlist to run the destination 24/7.
- Prefer RTMPS where the endpoint offers it.
What a custom RTMP destination is
A "custom RTMP" destination is simply any endpoint that isn't in a service's preset list but still speaks RTMP. That includes a self-hosted server (like an Nginx-RTMP setup), a third-party restreaming service, a corporate or education portal, a regional platform, or a white-label player on your own site. If it issues an ingest URL and a stream key, it's a valid target.
Get the URL and key
Every RTMP destination provides two values: the ingest (server) URL and a stream key. On a self-hosted server you configure these; on a third-party service they're shown in its dashboard. Together they tell your streaming tool where to send the feed and which stream it is. Copy both.
Common use cases
- Self-hosting: broadcast to your own Nginx-RTMP or media server for full control.
- Restreamers: send to a service that further distributes your feed.
- Private portals: stream to a company or school platform that accepts RTMP.
- Your website: feed a custom player embedded on your own site.
Stream to it 24/7
- Get the ingest URL and stream key from your destination.
- Upload your videos and build a looping playlist.
- Add a custom RTMP destination with the URL and key.
- Press Start — your playlist streams there continuously.
With StreamHouse, a custom RTMP destination works just like a built-in one, so you can run any endpoint around the clock.
Security and reliability
Two tips make a custom setup solid. First, prefer RTMPS if your endpoint supports it, so your stream key and feed are encrypted in transit. Second, lean on pre-encoded, cloud delivery for stability — a steady bitrate and automatic restart matter just as much for a custom server as for a big platform. That way your niche destination runs as reliably as any mainstream one.
Frequently asked questions
Can I stream to my own RTMP server?
Yes. If your server provides an ingest URL and stream key, you can broadcast a pre-recorded playlist to it 24/7 via a custom RTMP destination.
What's a restreamer?
A service that receives your feed and redistributes it. You send to its RTMP ingest with a URL and key, like any other destination.
Should I use RTMP or RTMPS for a custom server?
Prefer RTMPS when your endpoint supports it, so your stream key and feed are encrypted in transit.
