Guides

OBS Encoder Settings for Multistreaming with Castream

OBS has about forty settings that look important. Only six matter for multistreaming through Castream. This guide covers exactly those six — what to set, where to click, and which encoder to pick for your hardware.

If you haven't connected OBS to Castream yet, start with How to Stream to YouTube, Twitch & More Using OBS and Castream. This guide assumes OBS is installed and you're ready to dial in quality.

🔌 Step 1 — Point OBS at Castream

Before touching encoder settings, OBS needs to know where to send your video:

In Castream Web, grab your Castream RTMP URL and stream key (from your stream/RTMP ingest settings)
In OBS, go to Settings → Stream
Set Service to Custom
Paste the Castream RTMP URL into Server
Paste your Castream stream key into Stream Key
Click Apply → OK

That's the only stream destination OBS needs. Castream takes it from here and forwards your video to every platform you've connected — YouTube, Twitch, TikTok, Facebook, Instagram. One upload, many destinations. (New to the concept? Read What Is Multistreaming?.)

Keep your Castream stream key private, just like any stream key. Anyone with it can push video to your Castream destinations.

🎛️ Step 2 — Switch to Advanced output mode

OBS hides the good settings by default. Fix that:

Go to Settings → Output
Set Output Mode to Advanced
Click the Streaming tab

Now you can actually choose your encoder — which is the decision that matters most.

🖥️ Step 3 — Pick your encoder: x264 vs NVENC

Your encoder is the engine that compresses your video in real time. You have two realistic choices:

x264 (software encoding) — uses your CPU. Available on every computer. Quality per bit is excellent, but it eats processor power. On a laptop also running a game, a browser, and Discord, x264 can max out your CPU and make everything stutter.

NVIDIA NVENC (hardware encoding) — uses a dedicated chip on NVIDIA graphics cards (GTX 1650 and newer, all RTX cards). Nearly free in terms of CPU — your processor barely notices. Quality used to lag behind x264, but on modern cards it's essentially tied.

The rule of thumb:

NVIDIA GPU from the last ~6 years? Use NVENC. It's the best of both worlds.
No NVIDIA GPU? Use x264. It works everywhere.
AMD or Intel integrated graphics? Their hardware encoders (AMF, QuickSync) exist and work, but quality is a step behind the two above. Fine for 720p; for 1080p, x264 on a decent CPU usually looks better.

Most creators run into this when they read a forum post saying "x264 looks better" — written in 2019, when it was true. On current hardware, NVENC won.

⚙️ Step 4 — The six settings that matter

If you're using NVENC:

Rate Control: CBR
Bitrate: 6000 Kbps
Keyframe Interval: 2 s
Preset: P5: Quality (P6: Slower Quality if your card handles it without dropped frames)
Profile: high
Look-ahead: off · Psycho Visual Tuning: on

If you're using x264:

Rate Control: CBR
Bitrate: 6000 Kbps
Keyframe Interval: 2 s
CPU Usage Preset: veryfast (use superfast/ultrafast only if your CPU is struggling — quality drops fast below veryfast)
Profile: high
Tune: (none)

Why 6000 Kbps? Because your one stream goes to every destination, and the strictest one sets the ceiling — TikTok's RTMP ingest tops out around 6,000. Our bitrate guide breaks down every platform's limits if you're running a YouTube+Twitch-only setup and want to push higher.

Why keyframe 2 seconds? YouTube and Twitch expect it. Wrong keyframe intervals cause slow stream starts and buffering for viewers. Just set it and forget it.

📐 Step 5 — Video settings

Go to Settings → Video:

Base (Canvas) Resolution: 1920 × 1080
Output (Scaled) Resolution: 1920 × 1080
Downscale Filter: Lanczos (only matters if output is smaller than base)
Common FPS Values: 30

Streaming vertical to TikTok/Instagram as your main audience? Set both resolutions to 1080 × 1920 instead. See Vertical Video Looks Wrong? for the full story on orientation.

Dropping output to 1280 × 720 while keeping base at 1080p is a legitimate move if your upload is weak — 720p at 4,500 Kbps often looks cleaner than 1080p starved at the same bitrate.

🔊 Step 6 — Audio

Go to Settings → Audio and Settings → Output → Audio:

Audio Bitrate: 160
Sample Rate: 48 kHz

Bad audio kills streams faster than bad video. Viewers forgive a slightly soft picture; they leave when they can't hear you. A $30 USB mic beats a $300 camera with a built-in mic, every time.

🎯 Presets for three common setups

Don't overthink it — grab the row that matches your machine:

Older laptop, no dedicated GPU (x264) Stream to YouTube + Twitch + TikTok: 1080p30, 6,000 Kbps, x264, CPU preset veryfast, keyframe 2. If the CPU still screams, drop output to 720p60 at 4,500 Kbps before touching the preset — resolution drops look better than preset drops.

Gaming PC with NVIDIA card (NVENC) Stream anything: 1080p60, 8,000 Kbps (YouTube + Twitch) or 6,000 Kbps (with TikTok/Instagram in the mix), NVENC, preset P5, keyframe 2. Your GPU's encoder chip is separate from the part rendering your game — streaming barely touches game performance.

Mac (x264) Apple Silicon Macs handle x264 1080p30 at 6,000 Kbps comfortably on veryfast. Intel Macs: same settings, but watch thermals — if the fans sound like a jet, drop to 720p30. Either way, these settings feed Castream exactly the same RTMP stream as a Windows PC would.

If it still looks bad

Blocky/pixelated during motion: Bitrate too low for your resolution and frame rate. Either raise bitrate (if upload allows) or drop to 720p.

"Encoding overloaded" warning: Your encoder can't keep up. NVENC users: drop the preset from P6 to P5. x264 users: move the CPU preset one step toward ultrafast. Close background apps.

Stream disconnects: Usually network, not encoder. Bitrate higher than your upload can sustain. Drop to 4,500 Kbps and test.

Looks great in OBS, bad on TikTok: TikTok re-encodes aggressively and caps around 6,000 Kbps. If you're above that, you're wasting bandwidth TikTok throws away — and the re-encode of an over-compressed feed looks worse than a clean 6,000 Kbps source.

💾 Bonus: record a clean local copy while you stream

Your multistream bitrate is a compromise between platforms. Your recording doesn't have to be. OBS can record locally at much higher quality than you stream:

Go to Settings → Output → Recording
Set Type to Standard, Encoder to NVENC or x264 (a separate instance from your stream encoder — that's fine)
For NVENC recording: Rate Control CQP, CQ level 18–20 — visually near-lossless
For x264 recording: Rate Control CRF, CRF 18–20, CPU preset veryfast
Hit Start Recording alongside Start Streaming

You get the best of both: a bandwidth-friendly stream for your live audience and a pristine local file for YouTube uploads, clips, and highlights later. Just watch your disk space — high-quality 1080p60 runs about 1 GB every few minutes.

Six settings, ten minutes, and your OBS feed will look as good as your content deserves.