Multistream one live stream to every platform at once
Send a single feed from your encoder to StreamShark and rebroadcast it to YouTube, Facebook Live, LinkedIn Live, Twitch and any RTMP or SRT destination, alongside your own player. Go live everywhere with one button.
Trusted by the world's most demanding enterprises
How multistreaming (simulcasting) works on StreamShark
Multistreaming, also called simulcasting or restreaming, is broadcasting one live stream to several destinations at the same time. Your encoder sends a single feed to StreamShark, and StreamShark sends a copy to each destination from its own network. A broadcast to four platforms costs you the upload bandwidth of one stream, and the connection at the venue is never asked to carry four.
StreamShark has native integrations for Facebook Live, YouTube, LinkedIn Live and Twitch, and takes any other destination as a custom RTMP or SRT target, which covers Steam Broadcast, other video platforms and your own servers. A standard event streams to the StreamShark player and the social platforms together, a multistreaming-only event skips the player, and a VOD2Live schedule can carry its own multistream targets, so a prerecorded premiere goes out to the social platforms on a timer. The live streaming platform handles the rest of the event, from ingest and encoder management to the player, analytics and the archive.
Multistream to YouTube, Facebook Live, LinkedIn Live, Twitch and any RTMP or SRT server
One feed arrives at StreamShark and leaves for each destination from there. Add the destinations per event, as many as your plan allows, and the event's title and description become the default title and description on every platform.
Custom RTMP and SRT targets take a stream key or stream ID, an SRT latency and a passphrase, so a destination without a native integration still gets a secure, tuned feed.
Go live on every platform with one button
The native integrations give you remote control of each platform from inside StreamShark. Every target shows whether the platform is ready, a preview of the picture it is receiving and a direct link to the stream once it is up. Tick the targets you want, press Go Live and they all start at the same moment, and End Stream stops them together.
Multistreaming is a tab on the event itself, alongside the ingest settings, the player and the real-time analytics, so there is no second dashboard to watch.
Every platform's chat in one moderation view
Switch Live Chat on and the comments from the platforms you stream to arrive in one feed, alongside the chat from your own player. A moderator stars the questions worth answering and sends them to the Presenter View, a teleprompter page the speaker opens on a phone, tablet or teleprompter, so the person on camera sees the question and not the noise.
StreamShark chatPublish to a client's pages without sharing passwords
Agencies and production companies often stream to pages they do not own. From the event, you send your client a request for publishing access, as a link or by email. They open it, sign in to Facebook, YouTube, LinkedIn or Twitch and grant StreamShark the right to publish to their page, and that page then appears in the event as a multistream destination.
Nobody trades usernames and passwords, your operator is never made an admin of the client's account, and deleting the target after the event revokes the access.
Book a demo and we'll walk through a multistream event with you.
Book a DemoSee multistreaming on a real event
Book a walkthrough of the native integrations, the one-button go live and the unified chat.
Multistreaming questions we get asked
Multistreaming, also called simulcasting or restreaming, is broadcasting one live stream to several destinations at the same time. With StreamShark your encoder sends a single feed to the platform, which rebroadcasts it to YouTube, Facebook Live, LinkedIn Live, Twitch and any RTMP or SRT destination, as well as to your own StreamShark player.
Facebook Live, YouTube, LinkedIn Live and Twitch through native integrations that sign in with each platform's own login, and anything else as a custom RTMP or SRT target. That covers Steam Broadcast, other video platforms and your own servers, and the custom targets take a stream key or stream ID plus an SRT latency and passphrase where the destination needs them.
No more than a single stream. Your encoder sends one feed to StreamShark and StreamShark sends a copy to each destination from its own network, so adding a fifth platform does not touch the upload link at the venue.
Yes. With Live Chat switched on, the comments from the social platforms you stream to are pulled into StreamShark's moderation view alongside the chat from your own player. A moderator can star questions, send them to the presenter's teleprompter view, and export the full chat as CSV or JSON afterwards.
Through StreamShark's permissions management. From the event you send the client a request for publishing access, as a link or by email. They open it, sign in to the platform themselves and grant StreamShark the right to publish to their page, and the page then appears in your event as a multistream destination. No credentials change hands, the stream operator is never made an admin of the client's account, and deleting the target after the event revokes the access.
Yes. A VOD2Live schedule can carry its own multistream targets, so a prerecorded premiere or a recurring program plays to the StreamShark player and the social platforms at the set time without anyone pressing Go Live.
Each plan sets a maximum number of multistreams per live event. The Standard plan allows 2, Team 5 and Business 10, and Enterprise plans set a custom number.
Yes. StreamShark publishes to Facebook Live in up to 1080p, and each Facebook page or profile you add to the event gets its own stream from StreamShark's network, so a brand page, its regional pages and a founder's profile can all go live on one click from a single feed at the venue.
Yes. Send a primary and a backup stream to StreamShark's primary and backup ingests and StreamShark passes both through to Facebook's primary and backup ingests. If Facebook detects a problem with the primary it fails over to the backup on its own, and your operator can force the switch by hand.
