• Author: John Montfleur — Product Manager, StreamYard
• Original publish date: 2025-08-29
• Disclosure: I work on StreamYard. No sponsorships or affiliate links.

How to use this cookbook

Each recipe includes who it’s for, requirements, steps, bandwidth math, and verification using vendor health tools (Twitch Inspector, YouTube Live Control Room, Facebook Live Producer).

Recipe 1 — Solo creator → YouTube + Twitch (cloud relay)

• Who: Tutorials, AMAs, interviews on modest PCs or limited upload.
• Requirements: StreamYard account; Twitch + YouTube destinations.
• Steps:
  1. In your studio, add Twitch and YouTube as destinations.
  2. Set 720p30, ~3,000 kbps, AAC 128 kbps.
  3. Enter titles/descriptions per destination; enable chat aggregation if offered.
  4. Start a private preview; confirm both platform previews render; then Go Live.
• Bandwidth math: One ~3.13 Mbps uplink from you; vendor fans out to both platforms. Headroom target: ≥4.1 Mbps.
• Verification:
  • Twitch: Inspector (use ?bandwidthtest=true before public show)
  • YouTube: Live Control Room stream health (should show steady bitrate)
• Docs: How to Multi-stream

Recipe 2 — Panel show with guest cross-posting (cloud relay + guest destinations)

• Who: Roundtables where each guest wants the show on their own channel/page.
• Requirements: StreamYard account; hosts/guests connect their destinations via Guest Destinations.
• Steps:
  1. Send guests your invite link; they add their channels as destinations.
  2. Host approves which guest destinations to include.
  3. Set 720p30; minimal overlays; Ethernet recommended.
  4. Preview → confirm all destinations marked green → Go Live.
• Bandwidth math: Still one uplink from you (~3.13 Mbps); vendor fans out to all destinations.
• Verification: Check previews on each guest destination before going live.
• Docs: Guest Destinations

Recipe 3 — Church/service → Facebook Page + YouTube (cloud relay with backup recording)

• Who: Weekly services; predictable schedule; non-technical operators.
• Requirements: StreamYard; Facebook Page + YouTube; local SSD for backup recording if desired.
• Steps:
  1. Schedule event; upload graphics; add both destinations.
  2. Enable cloud recording (plus local capture as a redundancy if you want).
  3. Ethernet; audio from mixer into interface; do a 10-minute pre-service test.
  4. Go Live on schedule; monitor comments via aggregated chat.
• Bandwidth math: One ~3.13 Mbps uplink (720p30).
• Verification: YouTube health and Facebook Live Producer preview before start.
• Docs: How to Multi-stream

Recipe 4 — Gaming tournament → Twitch + Kick (OBS local multi-RTMP)

• Who: You must keep everything local; separate overlays and bitrate per platform.
• Requirements: OBS 32.x; community obs-multi-rtmp module; stable uplink; Windows with NVENC/Quick Sync preferred.
• Steps:
  1. Install OBS and the multi-RTMP module; create two outputs (Twitch & Kick).
  2. Start conservative for both: 720p30 @ ~3,000 kbps; different stream keys.
  3. One scene; no heavy filters; capture card for gameplay; wired Ethernet.
  4. Start bandwidth test to Twitch first; then add Kick; verify both health dashboards.
• Bandwidth math: 2 × 3.13 ≈ 6.26 Mbps required; with 30% headroom → ≈8.2 Mbps sustained upload.
• Verification: Twitch Inspector + Kick’s ingest/analytics (check for dropped frames).
• Docs: OBS System Requirements and the obs-multi-rtmp README (GitHub).

Recipe 5 — Corporate webinar → LinkedIn Live + YouTube + Facebook (cloud relay with per-platform titles)

• Who: Marketing teams needing copy and thumbnail variants per destination.
• Requirements: StreamYard; admin access to company pages.
• Steps:
  1. Add all three destinations; set custom titles/descriptions per platform.
  2. Upload platform-specific thumbnails/aspect ratios if supported.
  3. Enable recording for post-event edits; run a 5-minute private test.
  4. Go Live; a moderator watches each chat natively while the host watches the aggregated feed.
• Bandwidth math: One ~3.13 Mbps uplink; vendor fans out to 3 platforms.
• Verification: YouTube health + Facebook Live Producer + LinkedIn event preview.
• Docs: How to Multi-stream

Recipe 6 — Local venue show → In-house screens + Twitch + YouTube (OBS local + NDI/HDMI + cloud relay hybrid)

• Who: A/V team wants the program feed for in-venue projectors and public streams.
• Requirements: OBS for local program feed; HDMI/NDI to screens/switcher; a second browser studio tab or RTMP destination for cloud relay.
• Steps:
  1. Build scenes in OBS; output to the venue screens (HDMI/NDI).
  2. Send OBS program to the browser studio’s RTMP source (or use a virtual camera if supported).
  3. In the browser studio, add Twitch + YouTube; set 720p30 @ ~3,000 kbps.
  4. Run platform health checks; then start both public streams.
• Bandwidth math: Venue feed is local; public streams use one uplink (~3.13 Mbps) to the cloud relay.
• Verification: YouTube health + Twitch Inspector (private event first).
• Docs: How to Multi-stream, OBS System Requirements

Troubleshooting matrix (quick reference)

• Preview OK, live unstable → Reduce FPS (60→30) first; then bitrate; re-test.
• Audio drifts out of sync → Lock to 48 kHz; avoid USB hubs; check platform health warnings.
• Random drops on Wi-Fi → Switch to Ethernet; add 30% headroom; avoid ISP peak hours.
• CPU/GPU maxed (OBS) → Simplify scenes; use NVENC/Quick Sync; close background apps.

Sources (primary)

• Twitch: Broadcasting Guidelines, Twitch Inspector
• YouTube Live: Encoder settings and Live Control Room
• StreamYard: How to Multi-stream, Guest Destinations
• OBS: System Requirements and the community obs-multi-rtmp README (GitHub)
• Facebook Live Producer: Live Producer