Translate a Restream broadcast in real time

Restream is the multistream backbone of choice for creators who want one broadcast reaching every platform at once — Twitch, YouTube, Kick, Facebook, X, LinkedIn, plus a long tail of less common RTMP destinations. It can take input from OBS, Streamlabs, or its own browser-based Restream Studio, and fan that single stream out to anywhere viewers might be watching.

For creators with a global audience that lives on different platforms — Brazilian viewers on YouTube, Japanese viewers on Twitch, professional contacts on LinkedIn — Restream’s value is exactly that fan-out. The complication for translation is that each destination has its own chat, its own viewer base, and its own discovery community. The translation track needs to be visible from every destination at once.

Loquira fits this naturally because it doesn’t care about destinations. The translated audio track is generated once from the source microphone and made available through a single join link — accessible by any viewer on any destination who scans the QR code from the on-screen overlay.

The multistream–translation match

The mental model for Restream + Loquira is straightforward:

• Restream fans out the video and original audio to every destination platform.
• Loquira generates the translated audio track once, available everywhere, via a single join link.

This is the cleanest match between the multistream model and translation, because both are doing the same thing in different layers: one broadcast reaches many destinations / one translation track reaches many language listeners.

Recommended setup

• Encoder choice. Restream accepts input from OBS Studio (most common for high-quality streams), Streamlabs, or its own Restream Studio (browser-based, simpler). The OBS Studio platform page covers the local-encoder setup; this page focuses on the multi-destination part.
• Microphone. Same as always — close-mic positioning matters more than price. The microphone guide covers the trade-offs.
• Loquira device. A phone with the Loquira presenter open, positioned near your microphone, on AC power for long broadcasts.
• QR overlay. Upload the Loquira QR as an overlay in Restream Studio (or as a browser source / image source in OBS if you’re encoding locally). Add it to your intro/outro scenes and a small persistent corner element during the main broadcast.

Distribution across destinations

This is the part that’s unique to multistream and worth making explicit. Restream broadcasts to multiple chats simultaneously. The join link needs to land in each one.

The simplest pattern:

1. At the start of the broadcast, paste the Loquira link into each destination’s chat manually (or via a Restream chat-broadcast extension if you use one).
2. Mention the link verbally during the intro segment.
3. Re-post every ten to fifteen minutes for late arrivals — late-arrival traffic is the biggest miss on multistream broadcasts.

For destinations that don’t have chat (custom RTMP, some embedded players), the QR on screen carries the entire weight. Make the QR large enough to scan from a typical viewing distance.

Restream Studio vs OBS as input

Restream Studio is a browser studio similar to StreamYard. Restream also accepts OBS Studio as input via standard RTMP, giving creators with more advanced setups the full OBS feature set. The Loquira parallel pattern works identically in both:

• Restream Studio. Phone alongside, QR overlay in Studio’s graphics library, link in each destination chat. Closer to the StreamYard pattern.
• OBS → Restream. Phone alongside (or same-machine virtual audio cable for power users), QR as an image/browser source in OBS, link in each destination chat. Closer to the OBS pattern.

Known limitations

• Chat-only destinations vary in link allowance. Some destinations restrict links from non-moderator accounts. Pre-pin the link as a moderator-posted message before going live, especially on Twitch and YouTube where rate limits apply.
• Live captions on Restream’s destinations. Each destination has its own caption system (YouTube auto-captions, Twitch’s beta captions, Facebook’s auto-captions). They’re independent of Loquira and don’t conflict. Some viewers will use destination-native captions plus Loquira’s audio in parallel; both work.
• Restream’s recording feature. Restream can record the multistream input. The recording captures the broadcast audio; Loquira’s per-language audio is separate. For VOD distribution with translated tracks, the published recording and the Loquira session output are two separate files.
• Variable broadcast latency by destination. Different destinations have different CDN delays — Twitch is typically the lowest, YouTube and Facebook are higher. Loquira’s translated track is the same low latency everywhere. Translated-track listeners will hear the translation slightly ahead of the buffered native audio on slower destinations. This is normal and the usual recommendation applies: listeners mute the destination audio and listen exclusively to Loquira.