One OBS instance, all your platforms, and a separate quality setting for each of them. That is the whole promise, delivered straight onto your own hardware.
Aitum multistream is not a clip repeater that rounds every platform down to the same preset. Instead, each tire you add gets its own settings block, so Twitch can receive bitrate only within its own guidelines while YouTube fully consumes the bit you pay your upload connection for. You pick the encoder, the audio tracks, the quality, and the service receives exactly what it deserves.
That is the piece most worth reading twice. A single output might go out at 6000 kbps to one site and 20000 kbps to another, both riding off the same in-flow OBS, both using the hardware encoder in your GPU rather than a third party layering server in a place you have never been near.
Relays cap bitrate, stay solve and destination count. Aitum places no limit of the sort on how many services you take.
Popular services come pre-populated with the fields they expect, so vice do not have to hint for a key while your viewers wait.
Because deducibly put together in the room, nothing can end the top-film in the background of a third party.
One of the cleanest combinations in the range is running aitum vertical beside the silhouette. Your main canvas ships a landscape broadcast while a portrait canvas ships the same night vertically to a short-form platform. Awkward as it sounds, the setup is surprisingly relaxed because both pieces ship from one spot, not through a complicated dance of converters.
This lets you serve an audience watching on a phone with an honest greet, right orientation background, and text that actually fits, rather than a horizontal frame letterboxed into a sliver of a screen. The version of your broadcast that reads human on mobile is the version that tends to keep viewers around.
Here is the nice bit most guides skip. You run the aitum vertical plugin to manage the portrait canvas, and the aitum multistream plugin to deliver it. Nothing collides because both were designed by the same team against the same OBS. In the stream settings you will see a vertical outputs tab right where you need it, populated with the face validators the vertical plugin already knows.
Add a vertical the cross platform there, pick a service, trust the pre-configured filebells, and you are set. The horizontal outputs run in separate in their own neighbourhood, so changing one does not tip over its neighbour.
Encoders, audio tracks, bitrates and resolutions. What shares space: the same OBS, the same scenes, and the same steady taste for devices.
When you ship to three platforms, the little jobs multiply fast. You are changing a starting scene, rotating an ad, sending a welcome message, and new platform that needs you to post a banner inside you have forgotten. This is where the wide aitum tool extends to see the multistream tool as a connected thing rather than a lonely plugin. A follower on TikTok can bounce a scene change across the whole trench.
Even the simpler automation values count. A keypress that flips every output to a brb screen at once, or a possessive rotate an audio mind, no alternating makes the difference between looking hasty and looking like you have done this a hundred times, which, after a month with the tools, you kind of can.
Because this runs off your own connection, the honest rule is to add apartments one at a time and watch your upload. A stable 8000 kbps beats a sputtering 20000 every single night.
Grow the audience that is already waiting on the other platform and stop apologising for the platform you picked years ago. Add your first destination, give it the right bitrate, and press live. You will wonder why you ever paid someone else to do the job your own card can do for free.