Checking the Recording Settings Before the Broadcast Starts
Collaborative broadcasts on most platforms are not a single merged stream but separate video feeds from each participant. Before going live, each creator must check whether their own recording or archive setting is turned on. If a participant has the save-to-channel option enabled, their version of the broadcast will appear as a separate video on their channel after the stream ends.
The key detail is that the collaborative feature only synchronizes the live audio and video between participants during the broadcast. It does not create one unified recording file. Each participant’s local recording captures only their own camera, microphone, and the shared screen or guest feed as seen from their perspective, which naturally results in distinct videos.
Comparing the Viewing Record and Archive Labels
After a collaborative broadcast ends, each participant’s channel shows a viewing record or archive video with a label that matches the broadcast title. However, the actual video content differs because each file was recorded from a different participant’s stream. The archive on your channel contains your own audio and video, while the archive on a co-host’s channel contains their audio and video.
To confirm this, open the archive video on your channel and compare the camera feed and audio levels with the archive on your co-host’s channel. You will notice that the camera layout, audio timing, and even the chat overlay may differ slightly because each recording was captured independently from each participant’s broadcast software or platform settings.
Understanding Why the Platform Treats Each Feed Separately
Platforms design collaborative broadcasts this way to give each creator full control over their own content. If the platform merged all feeds into a single video, a participant would lose the ability to edit, trim, or delete their own recording without affecting the other creator’s archive. Keeping each feed separate also respects each creator’s channel policies, copyright claims, and moderation rules.
This separation also prevents technical conflicts. If one participant experiences a dropped connection or a corrupted recording, the other participant’s archive remains unaffected. The viewer record on each channel is therefore a reliable backup from that specific participant’s perspective, not a shared file that could be lost if one person’s stream fails.
Checking the Archive Visibility and Privacy Settings
After the broadcast, each participant can independently set the visibility of their own archive video. One creator may choose to make the video public, while another may set it to unlisted or private. This means that even if the broadcast was collaborative, the viewing record on your channel might not appear on a co-host’s channel if they changed their privacy settings afterward.
To avoid confusion, confirm the archive status and visibility label on your channel immediately after the stream ends. If you want the collaborative broadcast to appear as a single video on both channels, you would need to download one participant’s recording and upload it to the other channel manually. Otherwise, each channel will retain its own separate version of the broadcast.
FAQ
Question: Can I merge the two separate collaborative broadcast videos into one file later?
Answer: Yes, you can download both archive videos from each channel and combine them using video editing software. Check the export settings in your editor to match resolution and audio sync before merging.
Question: Why does the collaborative broadcast show up on my channel but not on my co-host’s channel?
Answer: Your co-host may have disabled the save-to-channel option before going live or changed the archive visibility to private after the stream. Ask them to check their archive settings and adjust the visibility label if needed.
Question: Will deleting my archive video delete the collaborative broadcast from my co-host’s channel?
Answer: No, deleting your archive removes only the video from your channel. Your co-host’s recording remains unaffected because each participant’s archive is stored and managed independently on their own channel.