How-To ·
Stream Your 24/7 Loop to Twitch, Facebook, or Any RTMP Platform
Key takeaways
- Loopcast's YouTube integration (auto-created broadcasts, thumbnails, analytics) is still the deepest and easiest path — but a stream's manual-key field now also accepts Twitch, Facebook Live, and any other RTMP-compatible destination.
- Setup takes one field: paste your platform's ingest URL and stream key, or just the key if you picked Twitch from the built-in tab.
- Each stream still has one destination at a time — this isn't simultaneous multi-platform broadcasting, it's the choice of where a single loop runs.
Loopcast was built around YouTube first, and that's still where the fully automated experience lives — connect your account once and Loopcast creates the broadcast, thumbnail, and stats for you. But the underlying mechanism was never actually YouTube-specific: it's an RTMP relay, the same protocol every major streaming platform accepts. So a stream's manual-key field now works with more than YouTube.
What changed
Every Loopcast stream has a "Stream key" card with a manual option — previously labeled specifically for YouTube. It now has three tabs:
- YouTube — unchanged. Paste your bare key from YouTube Studio → Go Live → Stream.
- Twitch — paste just your key from Twitch Creator Dashboard → Settings → Stream. Loopcast adds Twitch's ingest address for you.
- Custom RTMP — paste a full destination URL, including your key. This covers Facebook Live, Kick, or a self-hosted RTMP server — anything that publishes a standard
rtmp://ingest endpoint.
Once saved, Go Live behaves exactly the same regardless of destination: the same 24/7 looping, the same live playlist editing (add/remove/reorder/trim without stopping the stream), the same reliability engineering underneath.
What's still YouTube-only
Connecting your YouTube account unlocks a layer of automation that's specific to YouTube's own API — there's no equivalent for Twitch or Facebook to plug into the same way:
- Auto-created broadcasts (no stream key to copy)
- Custom broadcast thumbnails
- YouTube Analytics stats (views, watch time, subscribers) in your dashboard
- Scheduled Go Live
A Twitch or custom-RTMP stream skips all of that and goes straight to relaying your loop — which is exactly what most 24/7 ambience, radio, or rerun channels actually need.
Setting up a Twitch stream
- In Twitch Creator Dashboard, go to Settings → Stream and copy your Primary Stream Key.
- In your Loopcast dashboard, open the stream you want to route to Twitch and switch its Stream key card to the Twitch tab.
- Paste your key and save.
- Build (or reuse) a playlist for that stream and hit Go Live.
Your Twitch channel goes live with the same looping playlist you'd otherwise run on YouTube — no re-uploading, no separate encoder.
Facebook Live, Kick, or a custom server
These don't have a dedicated tab (yet), but work the same way via Custom RTMP:
- In the platform's live-producer settings, find its RTMP ingest URL and stream key (Facebook Live's is under Live Producer → Stream Setup).
- Combine them into one full URL, e.g.
rtmp://live-api-s.facebook.com:80/rtmp/<your-key>. - Paste that full string into the Custom RTMP tab and save.
What doesn't work
Instagram and TikTok don't currently offer public RTMP ingest to regular accounts — that access exists only behind platform-specific approval processes most creators don't have, not something any third-party tool can add. If a platform doesn't hand you an RTMP URL + key from its own settings page, Loopcast can't reach it either.
Frequently asked questions
Can I run the same content on YouTube and Twitch at once?
Not from one stream — each stream has one destination. If you want the same loop live on two platforms simultaneously, set up two separate streams (available on Pro), each pointed at a different platform, with the same videos in both playlists.
Does switching to Twitch or Custom RTMP cost extra?
No — it uses the same manual-key mechanism already included on Creator and Pro plans. The auto-broadcast, thumbnail, and analytics features that stay YouTube-only were already gated the same way before this change.
Will my existing YouTube streams keep working the same way?
Yes — nothing changes for the YouTube tab or for any account already using OAuth-connected YouTube. This is additive.