Connecting OBS Studio to FizzyPeak

Set up OBS step by step — RTMP recommended, SRT for pros. Plus output settings, preview in the tester, and going live to Twitch/YouTube/Kick.

Connecting OBS Studio to FizzyPeak

OBS Studio is the standard encoder for PC and gaming streaming. This guide shows you the complete path: from OBS setup through previewing in the FizzyPeak tester to going live on Twitch, YouTube, or Kick.

Which encoder is right for me? - OBS — PC/gaming, Just Chatting, tutorials, static setup (this guide) - Belabox / LiveU — IRL with bonded mobile connections - Moblin / IRL Pro / Larix — smartphone IRL with just one SIM - Pre-Recorded Loop (from Creator) — 24/7 channels, lofi, waiting rooms

Requirements

• OBS Studio 28 or newer — Download
• An active FizzyPeak account
• Optional: a Twitch / YouTube / Kick stream key, if you also want to relay live to the platform

Step 1 — Create a stream destination in FizzyPeak

Without a destination, FizzyPeak won't relay anything onward. Even if you just want to test for now, create one — otherwise the "Go Live" button stays inactive.

1. Open https://fizzypeak.stream/app and log in
2. Sidebar → Multistream
3. Click + Destination
4. Pick a platform (e.g. Twitch)
5. Enter:

- Name — your choice (e.g. "My Twitch") - Stream Key — your Twitch stream key (Twitch → Settings → Stream → Primary Stream Key)

1. Check Enabled, optionally Primary
2. Save

Starter limit: 1 destination. Creator+ can run up to 7–10 in parallel.

Step 2 — Get your FizzyPeak Ingest endpoint

1. Sidebar → Live
2. At the top of the Quickstart card you'll see:

- Server URL (RTMP or SRT) - Stream Key — fp_…

1. Click the eye icon to reveal it, then Copy

Recommendation: For OBS on a PC, always use RTMP — it works in 99% of home and corporate networks. Use SRT only if you allow outbound UDP (some corporate/hotel Wi-Fi networks block UDP).

Step 3 — Configure OBS (RTMP, recommended)

In OBS:

1. In the top menu bar: File → Settings (or Ctrl+,)
2. On the left: select Stream
3. Enter the following values:

1. Apply + OK

Variant: SRT (for power users)

If you prefer SRT (lower latency, better recovery on packet loss):

OBS quirk with SRT: Some OBS builds parse & as a separator. If you get a connection error, try the variant with #!:: from the OBS SRT docs — or stick with RTMP.

Note on the server address: fizzypeak.stream is your fixed ingest address. You'll find your exact stream key (YOUR-KEY) in the dashboard under Account → Setup Guide.

Step 4 — Output settings for a stable stream

OBS → Settings → Output → set Mode to Advanced:

Streaming tab

Video tab

Audio tab

Step 5 — Start streaming

1. In OBS, bottom right: Start Streaming
2. The status indicator at the bottom right turns green (kbps + frames are shown)

Important: You're now streaming to FizzyPeak, not yet to Twitch. FizzyPeak buffers your stream and waits for your "Go Live".

Step 6 — Check the preview in the FizzyPeak tester

In the FizzyPeak dashboard on Live:

• The Stream Tester card (Starter) or Stream Control card (Creator+) shows:

- 🟢 Status: Connected - Bitrate: live value (should match OBS, ~6000 kbps) - Mini-preview with your current OBS image (auto-refresh every 2 s)

If the preview shows you → everything is configured correctly.

Step 7 — Go live (start the relay)

Only here does your stream actually get forwarded to Twitch/YouTube/Kick:

1. In the Live tab → click Go Live
2. The status switches to LIVE (blinking red in the sidebar)
3. On Twitch/YouTube/Kick you'll see yourself after 5–15 seconds

Watermark note (Starter): On the Starter plan, a FizzyPeak logo is overlaid in the bottom right. From Creator (€12/mo) it disappears.

Common problems

"Connection failed" when starting the stream

• RTMP → check the URL, did you copy the stream key? Antivirus/Windows Defender may be blocking OBS → add a firewall rule.
• SRT → probably a UDP block in the network. Switch to RTMP.

Stream goes through, but FizzyPeak shows "no signal"

• You're sending to the wrong stream key. Every account has its own — don't use the one from a test account or another user.
• The Stream Tester always responds to the currently logged-in user.

Bitrate drops / frame drops

• Unstable Wi-Fi → test with a cable
• Encoder preset too high → switch from "Slow" to "Faster"
• CPU usage > 70% → switch x264 → NVENC/AMF, or reduce resolution to 720p

Stream goes through but Twitch shows "Offline"

• The Multistream → Destination isn't "Enabled" or the stream key is wrong
• Go Live hasn't been clicked yet
• Twitch latency: 5–30 sec after clicking — wait a moment

Tip: Keep your stream key safe

The key is your password for the ingest pipeline. Don't show it in screenshots, don't make it visible in the stream itself, don't post it in Discord/Reddit. If compromised: contact support for a key rotation.

Related articles

• Copying and pasting your stream key — where to paste the key in each encoder
• Setting up Multistream — multiple platforms in parallel
• Understanding bitrate — why 6000 Kbps is the sweet spot
• Belabox setup — alternative for IRL with bonded connections
• Moblin setup — iOS app for IRL without Belabox

Noch Fragen? Öffne das Dashboard oder schreib im Discord #support.