RTMP Server URLs for YouTube, Twitch, Facebook and More

The standard ingest URLs are rtmp://a.rtmp.youtube.com/live2 for YouTube, rtmp://live.twitch.tv/app/ for Twitch and rtmps://live-api-s.facebook.com:443/rtmp/ for Facebook. Kick, Rumble, TikTok, LinkedIn, X and most other platforms show a server URL in your own dashboard, often specific to your account, event or session.

For the stream key that pairs with each URL, see our stream key directory.

Key takeaways

• YouTube, Twitch and Facebook publish standard ingest URLs; Facebook's is RTMPS only.
• Kick, Rumble, TikTok, LinkedIn, X and smaller platforms issue URLs in their dashboards.
• Server URL and stream key go in separate fields unless a tool wants one address.
• Per-event URLs expire, so copy fresh details for every scheduled broadcast.

How an RTMP server URL is put together

An ingest address has a few parts; knowing them makes errors easy to spot. Using Facebook's as the example:

• Protocol: rtmp:// for plain connections or rtmps:// for encrypted ones.
• Host: the ingest server's domain, here live-api-s.facebook.com.
• Port: optional when it's the default. Plain RTMP normally uses 1935 and RTMPS commonly uses 443, which is why some URLs show :443.
• Application path: the part after the host, such as /rtmp/, /app/ or /live2.

In most tools the stream key isn't part of the server URL. OBS and cloud services have separate server and key fields and join them when connecting, while some hardware encoders and FFmpeg commands expect one full address with the key after the application path. New to ingest? What RTMP is covers the basics.

YouTube, Twitch and Facebook ingest URLs

YouTube

Primary server: rtmp://a.rtmp.youtube.com/live2. YouTube also supports a backup ingest and secure RTMPS connections; YouTube Studio's live streaming settings show the addresses for your stream next to the key. If warnings appear once you're connected, see fixing YouTube stream health warnings.

Twitch

Default server: rtmp://live.twitch.tv/app/. This address is designed to route you to a suitable ingest automatically, and Twitch also lists regional servers you can choose manually. How to decide is covered in picking the best Twitch ingest server.

Facebook

Server: rtmps://live-api-s.facebook.com:443/rtmp/. Facebook requires RTMPS, so a plain rtmp:// version won't connect. Live Producer shows this URL alongside your stream key, and Facebook Live connection fixes helps when it still fails.

Platforms that issue their own server URLs

Other platforms show a server URL in your dashboard, sometimes specific to your account, event or session. Copy it from there, not from a forum post.

• Kick: an RTMPS server URL beside your stream key in the creator dashboard; see Kick stream fixes.
• Rumble: an RTMP URL and key shown when you set up a live stream, explained in finding Rumble's RTMP details.
• TikTok: a server URL and key for eligible accounts, commonly generated per LIVE session.
• LinkedIn: a stream URL and key from a live event's custom stream setup; see LinkedIn's stream URL and key.
• X: RTMP details from a source created in X's producer tools, covered in streaming on X with RTMP.
• Vimeo, Dailymotion, VK, Mixcloud and Steam: each shows its own server details in its live or broadcast settings.

RTMP or RTMPS: which address to choose

Where a platform offers both, prefer RTMPS. It encrypts the connection, protecting your stream key and feed in transit, with no meaningful quality cost. See RTMP vs RTMPS for the full comparison. When copying URLs:

• Match the protocol to the platform. Facebook accepts only RTMPS, and Kick displays an RTMPS address. Changing rtmps:// to rtmp:// to get past an error won't work.
• Keep the port. RTMPS usually runs on 443. If a URL includes a port number, leave it in.
• Watch for blocked ports. Some office, school or venue networks block 1935, the usual RTMP port, while allowing 443, so RTMPS may connect where plain RTMP can't.
• Confirm your software supports RTMPS. Current versions of OBS do, but some older hardware encoders only send plain RTMP.

Copy-and-paste mistakes that break connections

Most "can't connect" errors come from the URL or key, not the network. Check these first:

1. Key pasted into the URL field, or the URL pasted into the key field.
2. Key added twice, once on the end of the URL and again in the key field.
3. Hidden spaces or line breaks copied at the start or end of either value.
4. A missing application path, such as dropping /live2 or /app/.
5. The wrong protocol, like https:// where rtmp:// or rtmps:// belongs.
6. A stale per-event URL or key left over from a broadcast that has already ended.
7. A mismatched pair: a URL from one event with a key from another.

When in doubt, clear both fields and copy fresh values from the same dashboard screen.

Adding RTMP destinations to StreamHouse without typos

In StreamHouse, built-in destinations such as YouTube, Twitch, Kick, Rumble, TikTok, Facebook, LinkedIn Live, X, Dailymotion, Vimeo, Mixcloud and VK Live are set up per platform, and for several of them you only paste the stream key while the ingest address is handled for you. Where a platform issues its own server URL, copy it and the key from that platform's dashboard into the destination. Anything else can be added as a custom RTMP or RTMPS server, or as an SRT output.

Add several destinations to one stream and a single broadcast reaches all of them from the cloud, without extra stream slots. When a platform issues a new per-event URL, update just that destination. Create an account to connect your first platforms.

Frequently asked questions

What is the RTMP URL for YouTube Live?

YouTube's primary ingest URL is rtmp://a.rtmp.youtube.com/live2, entered as the server with your stream key in a separate field. YouTube Studio's live streaming settings show it next to your key, along with backup and secure options.

Is the Twitch server URL the same for everyone?

Yes, the default rtmp://live.twitch.tv/app/ address works for every channel, because your stream key identifies you. Twitch also lists regional ingest servers you can select manually in your encoder if automatic routing gives you an unstable connection.

Where do I find the RTMP URL for Kick, TikTok or LinkedIn?

In each platform's own dashboard, next to the stream key. Kick shows an RTMPS server URL in its creator dashboard, while TikTok and LinkedIn generate details for eligible accounts, often per session or event. Never reuse someone else's.

Do I include the stream key in the RTMP URL?

Usually not. OBS and most streaming services have separate server and stream key fields and combine them for you. Tools that ask for one full address, such as some hardware encoders or FFmpeg commands, expect the key appended after the application path.

Where to go next

• Stream to Twitch from a playlist
• Find stream keys on every platform
• Choose between RTMP and RTMPS
• Add your first destination