How to stream to YouTube and Aparat at the same time

The cleanest signal path

The signal path is OBS → iobase → YouTube + Aparat. OBS does not need two simultaneous outputs or a multistream plugin. iobase receives one source, then starts and monitors one output for each saved destination.

The YouTube and Aparat events still need to be prepared in their own dashboards. iobase routes media; it does not replace platform privacy, scheduling, moderation, or copyright controls.

Setup from start to finish

Create the YouTube live event and copy its stream URL/key. Open Aparat’s live dashboard and copy its Stream URL and Stream Key. Treat both keys like passwords.

• Add YouTube and Aparat as separate destinations in iobase.
• Enable both destinations and select Source Copy or a compatible profile.
• Paste the iobase RTMP server and private key into OBS Settings → Stream → Custom.
• For the test, make YouTube private or unlisted and select Aparat’s Experimental category; Aparat documents this category as visible only to you.
• Confirm audio, motion, delay, and output status before making the events public.

A conservative shared OBS baseline

There is no universal best quality. The source must fit your upload and the lowest compatible destination limit. These settings are a practical starting point for Source Copy, not a guarantee for every account or event.

Choose bitrate for the shared destination, not the biggest number

Aparat’s support material suggests 3000 Kbps for 720p and recommends keeping bitrate below 70% of upload capacity. YouTube currently publishes higher H.264 recommendations for some resolutions. For one copied source, select a value accepted by both and stable on your connection.

If you need a higher YouTube output, keep a suitable source and assign a transcode profile to the destination that needs a different format. Source Copy cannot lower bitrate or repair keyframes after OBS has encoded the stream.

When one platform works and the other does not

Check the failing destination independently. A Live connection with a blank or loading player often points to incompatible media settings rather than a routing failure.

• Re-copy the failing platform’s stream URL and key; remove accidental spaces.
• Confirm the event has not expired and the destination is enabled in iobase.
• Verify H.264/AAC, CBR, two-second keyframes, and a supported frame rate.
• If OBS reports dropped frames, reduce source bitrate and test the network.
• Use the iobase output status and platform preview together; neither alone proves playback.

Before the public simulcast

• YouTube visibility and Aparat live settings are intentional.
• Both platform previews have synchronized picture and sound.
• The source bitrate stays stable for at least 10–15 minutes.
• Both iobase outputs remain Live after a scene change and fast motion.
• No stream key appears in screenshots, chat, or logs you share.