Everywhere at once
Twitch, YouTube, Facebook or any other RTMP server, all from one OBS, with nothing in between.
Stream to Twitch and YouTube at the same time.
One broadcast from OBS to every platform you use. Your PC sends it to each one directly, so nothing routes through a middleman and there’s nothing to pay.
Version 0.7.0 for Windows, macOS and Linux. No PlasmaStream account needed.
How it works
Add your destinations once. Go live everywhere.
You tell the plugin where your stream should go, and it sends to all of them when you press Start Streaming. That’s the whole setup.
Nothing leaves your machine that shouldn’t
- The encoding happens on your PC. Your video goes straight to each platform and never anywhere near us.
- Your stream keys stay on your computer. The plugin asks for each one once and keeps it there. There’s deliberately nowhere on this website to put one, because a stream key lets anybody broadcast as you.
- It’s open source. For something that runs inside OBS and holds your keys, that seems like the least it could be. The source sits next to the download.
If you already use the bot
- Your destinations sync from your dashboard. Set them up once and every computer you stream from picks up the same list, instead of you retyping server URLs on a laptop at 2am.
- Keys still stay local. Only the server addresses sync. The keys are typed into the plugin on each machine.
What’s in iteverything on this page is in the free download6 features
A real 9:16 stream
Crop to fill or place your stream as a band, per scene, then add your camera and chat around it.
Record the clean scene
Record a scene with no chat or alerts on it while your stream shows the one that has them.
Drop one, keep going
Switch any destination off and back on while you're live, without ending the stream.
Numbers you can trust
Bitrate measured from what actually went out, plus dropped frames and reconnects, per destination.
Share one, or give each its own
Every destination shares the encoder OBS already runs, unless you give one its own bitrate.
Download
Install it in a couple of minutes.
Pick your system. The Windows and Mac builds need OBS 31.1 or newer, because vertical and scene recording both use something OBS added in that release.
Windows
Download the .zip- Close OBS.
- Press Windows+R, paste
C:\ProgramData\obs-studio\pluginsand press Enter. ProgramData is hidden, so clicking through C: won’t get you there. - Drag the whole
plasmastream-multistreamfolder out of the zip into that window, with its bin and data folders still inside it. - Start OBS again.
macOS
Download the installer- Run the installer.
- The first time, right-click it and pick Open instead of double-clicking. It isn’t signed: signing costs $99 a year with Apple, and we’d rather put that into the hosting.
- Start OBS.
Linux
Download the .deb- Run
sudo apt install ./plasmastream-multistream-0.7.0-x86_64-linux-gnu.deb - It’s built against Ubuntu 24.04’s OBS 30, so it does everything except vertical and scene recording, which need a newer OBS than Ubuntu ships. Build it yourself against 31.1 to get them; the README covers it.
- OBS from Flatpak won’t find it, because Flatpak keeps its plugin folder inside the sandbox. Building from source is the answer there too.
Then open it
- Open the Docks menu and tick PlasmaStream Multistream. Docks is its own menu along the top of OBS, next to View, not something inside View, which is where most people look first.
- On Windows, check it landed. It worked if this file exists:
C:\ProgramData\obs-studio\plugins\plasmastream-multistream\bin\64bit\plasmastream-multistream.dll
If it doesn’t show up
- ProgramData is not Program Files. They sit side by side on C:, and the OBS folder inside is called plugins in one and obs-plugins in the other. Only ProgramData works. Program Files and AppData fail silently, with nothing in the log to say why, so the file path on the left is the thing to check.
Vertical
Build a vertical stream, not a cropped one.
Any destination can be set to 9:16, and what goes on that frame is up to you, scene by scene.
Your normal stream goes on the tall frame as a block: the whole thing cropped to fill, or a band across the top, middle or bottom with the rest of the frame free. A full-bleed crop suits gameplay and ruins a talking head, which is why it’s chosen per scene.
Then put your own things around it
- Your camera and chat overlay are already in your scenes. Add them to the tall frame and drag them where a phone wants them. They stay exactly where they are in your normal scenes.
- Everything drags. Click it, move it, pull a corner to resize. Transform and Properties open OBS’s own dialogs, not worse copies of them.
- See both frames at once. A second dock shows your wide and vertical streams side by side, live, with the vertical one larger. Drag it onto a spare monitor and leave it there.
- Worth knowing: vertical always encodes separately, so it has a real CPU cost. And the tall frame doesn’t get its own scene list, so you can move your wide stream on it but not pull one source out of it. If you need that, Aitum Vertical does it and is free.
Recording
Record the scene nobody is watching.
Your stream scene has chat, alerts and everything else live viewers want. None of that belongs in the video someone watches next week.
Pick your clean scene once
- It records that scene while your stream shows the other. The recorded scene runs even though nobody is watching it, which is the whole trick.
- Files land where OBS already saves recordings, named the way your other recordings are named.
- OBS’s own Start Recording still works. Run both if you want the stream on file as well.
What it costs
- A second encode, the same as a vertical destination.
- Audio inside the recorded scene plays into your main mix, because the scene is genuinely running. If it has sound of its own, give it a separate audio track and point the recording at that.
Running it
Know what it costs before you plan around it.
Once you’re live
- Each destination has a tick box that works mid-stream. If one platform starts rejecting frames at 1am, drop just that one, keep broadcasting, and switch it back on when it settles.
- Beside each one: the bitrate actually going out, how long it’s been connected, dropped frames as a percentage, and a count of reconnects. The bitrate is measured from bytes sent, not read back from the setting you typed, because when something starts dropping the gap between those two numbers is the whole question.
Bandwidth and CPU
- Two places means uploading twice, so you need roughly double the upload you use now.
- Encoding is the part you control. By default every destination shares the encoder OBS is already running, so a second one costs nothing but bandwidth. If your upload can’t carry two copies of a 6000 kbps stream, give the second destination its own encoder and bitrate, and pay in CPU instead.
- A relay service moves both costs onto their hardware and charges you monthly for it. Neither answer is wrong, they just cost different things.
Try it on your next stream.
We’ve tested it against a local server with three destinations at once, one of them vertical, and a destination dropping without taking the main stream down. What we haven’t done yet is a six hour stream to Twitch and YouTube at the same time. If it misbehaves, the OBS log will say why, and sending us that is the most useful thing you can do.