How to Split Stream on Multiple Cam Sites: OBS, RTMP & Bitrate Setup
This is the technical side of multistreaming — encoder settings, RTMP destinations, bandwidth budgeting and troubleshooting. If you are still deciding whether a second platform is worth it, the strategic case is covered in diversifying your cam income. This article assumes you have decided and want the workflow.
What split streaming actually is
Your encoder — OBS in most cases — takes your camera and audio, compresses them once into a video stream, and pushes that stream to a URL using RTMP. An RTMP destination is just an address plus a stream key: the address says which server to send to, the key says which account the stream belongs to.
Split streaming means that one encode reaches more than one of those destinations. There are only two ways to do it, and the difference between them decides almost everything else about your setup:
| Method | How it works | Upload cost | Trade-off |
|---|---|---|---|
| Relay service | You send one stream to a relay; the relay duplicates it to each platform. | One stream’s worth, no matter how many platforms. | A third party handles your video. Adds a little latency. Usually a paid tier for multiple destinations. |
| Direct multi-output | A plugin makes OBS push the same encode to several RTMP URLs itself. | Multiplied by the number of platforms. | No third party, but your upload and CPU absorb the whole cost. |
If your upload is anything short of excellent, use a relay. The bandwidth arithmetic below is usually the deciding factor rather than any preference about software.
Budget your bandwidth before you touch settings
Run an upload speed test, then take about 70–75% of the result as your working ceiling. The remainder is headroom — upload speed fluctuates, and a stream configured to use every last kbps will drop frames the moment anything else on your network wants bandwidth.
With a relay, your total need is one stream: a 6000 kbps broadcast needs roughly 6000 kbps of working ceiling whether it lands on one platform or four. Going direct, multiply: the same 6000 kbps to three platforms needs around 18,000 kbps, which is beyond most residential connections.
Choose your resolution and bitrate for the strictest platform
Platforms do not all accept the same maximum bitrate or resolution, and a single encode has to satisfy all of them. Whatever your lowest destination ceiling is, that is your encode — sending above a platform’s limit gets you re-encoded, rejected, or unstable, not rewarded.
Look up the current accepted bitrate and resolution for each destination before configuring anything, then set OBS to the lowest of them. The practical consequence is that adding a stricter platform lowers quality everywhere, which is a real cost worth weighing.
On resolution: 1080p at a constrained bitrate looks worse than 720p at the same bitrate, because the same data is spread across more pixels. If your ceiling is tight, 720p60 or 1080p30 will both look cleaner than 1080p60. Movement is what costs bitrate — a mostly static room tolerates lower settings than one with constant motion.
Encoder: hardware or software
In OBS, the encoder setting decides which part of your computer does the compression, and this is where split streaming most often goes wrong.
- Hardware encoding (NVENC on NVIDIA cards, AMF on AMD, Quick Sync on Intel) offloads the work to your GPU. This is almost always the right choice for camming, because it leaves the CPU free and because modern hardware encoders are good enough that the quality gap no longer matters at typical bitrates.
- Software encoding (x264) uses the CPU. It can look marginally better at low bitrates, but it competes with everything else running — browser, chat windows, toy software — and going direct to multiple destinations multiplies that load.
If OBS reports encoding overload, switch to hardware encoding first, before lowering resolution. It solves the problem more often than any other single change.
Setting up the destinations
Collect each stream key. Every platform shows a server address and a stream key in its broadcaster or external-encoder settings. Treat a stream key like a password: anyone holding it can broadcast to your room. Never show these on camera, and regenerate any key that appears in a screenshot.
Configure the primary destination. In OBS, set Service to Custom, then enter the server and key for the platform you consider primary. Get this working alone before adding anything else — debugging one stream is far easier than debugging three.
Add the secondary destinations. Through a relay, you enter the other platforms’ keys in the relay’s dashboard and point OBS only at the relay. Going direct, you add each additional RTMP URL and key in the multi-output plugin.
Set keyframe interval to 2 seconds. Most platforms expect this, and leaving it on automatic is a common cause of a stream that connects but plays back badly on one site while looking fine on another.
Audio routing
Audio is where split-streaming setups quietly go wrong, because problems are less visible than a frozen video feed. Two things matter most.
First, be deliberate about which sources are captured. If you capture desktop audio wholesale, every notification, alert and browser tab goes out to every platform simultaneously. Capture the specific applications you intend to broadcast instead, and mute the rest.
Second, watch your levels. Aim for peaks around −6 dB with normal conversation nearer −18 dB, and add a limiter so a sudden loud moment does not clip. Platforms process audio differently, so something that sounds acceptable on one can distort on another — leaving headroom protects you on all of them at once.
Scenes: one layout, or one per platform
A single encode means every platform sees identical video, including any on-screen text. That matters more than it first appears, because overlays naming a platform, its currency, or a platform-specific goal will be visible on the others too — which can read as an invitation to leave, and on some sites is a rules problem.
The safe approach is one neutral scene: no platform names, no token amounts tied to one site’s currency, no site-specific promotions burned into the overlay. Keep those in chat, where they stay on the platform they belong to. Genuinely per-platform visuals require a separate encode per destination, which means separate scene collections and considerably more machine.
Test before you go live
- Start the stream to all destinations while your room is private or offline, if the platforms allow it.
- Watch the OBS stats panel for dropped frames. Anything above about 1% sustained means bandwidth trouble; lower the bitrate and retest.
- Open each platform’s own player and confirm the picture and sound actually arrive there. A green connection indicator in OBS only proves the handoff succeeded, not that the platform accepted and is serving the stream properly.
- Check for audio drift — if sound and picture separate on one platform but not another, that platform is re-encoding differently and the keyframe interval is the usual culprit.
- Run it for a full ten minutes. Most bandwidth and thermal problems only appear after several minutes of sustained load, not in the first thirty seconds.
Troubleshooting the common failures
| Symptom | Most likely cause | What to try |
|---|---|---|
| Dropped frames climbing steadily | Upload bandwidth exceeded | Lower the bitrate; if going direct, move to a relay so you upload once instead of three times. |
| “Encoding overloaded” warning | CPU saturated by software encoding | Switch to hardware encoding; close browser tabs; lower resolution before frame rate. |
| One platform fine, another stuttering | Bitrate above that platform’s ceiling | Re-encode to the lowest ceiling among your destinations. |
| Connects, then disconnects minutes later | Unstable upload or wireless | Move to wired ethernet; lower bitrate to widen headroom. |
| Audio and video drift apart | Keyframe interval not fixed | Set keyframe interval to 2 seconds explicitly rather than automatic. |
| Quality degrades after 20–30 minutes | Thermal throttling | Check temperatures under sustained load; hardware encoding usually reduces this considerably. |
Deciding whether the second platform earned its place
Once the technical side is stable, the workload question is worth settling properly. Split streaming does not double your income; it adds a second chat to monitor, a second set of regulars to remember, and a second payout schedule to reconcile.
Track earnings and hours per platform separately for several weeks, then compare effective hourly rates. The honest comparison is not “did the second platform make money” but “did my hourly rate across both beat my hourly rate on one.” Divided attention often lowers earnings in the primary room enough to cancel out the secondary one — and that outcome is invisible unless you measure per platform.
CamCash tracks earnings and hours separately by platform, so you can compare effective $/hour on each and tell whether the second stream is actually paying for the extra workload.
Compare My Platforms Free →Frequently asked questions
No. One machine can send a single encode to multiple destinations, either through a restream relay service or through a plugin that duplicates the RTMP output. A second machine only becomes useful if you want genuinely different scenes or resolutions per platform, or if your CPU is already saturated by a single encode.
It depends entirely on your method. Through a relay service you upload one stream, so a 6000 kbps broadcast needs roughly 6000 kbps of headroom regardless of how many platforms receive it. Sending directly to three platforms from your own machine means uploading three copies — roughly 18,000 kbps for the same quality. This is the single biggest reason most models use a relay.
That depends on the specific platform and sometimes on your specific contract. Some sites permit it, some restrict it, and studio or exclusivity agreements can override the general rule. Check each platform’s current terms and your own agreement before you go live on two sites at once — do not rely on what other models say is allowed.
Usually because the second platform re-encodes to a lower bitrate ceiling than the first. Platforms do not all accept the same maximum bitrate or resolution. Set your encode to the lowest ceiling among your destinations, or accept that the stricter platform will look softer.
Yes, and you will need to. Each platform has its own chat that your viewers cannot see across. Most models designate one platform as the primary chat they actively work, and check the others on a timer or through a multi-chat dock in OBS.