> For the complete documentation index, see [llms.txt](https://help.zipcaptions.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.zipcaptions.app/translation/broadcasting-and-obs-translation.md).

# Broadcasting, OBS & Bilingual AI

Live Translation works seamlessly across Zip Captions' sharing and streaming tools—including [Broadcast Streams](https://help.zipcaptions.app/streaming-captions/broadcasting-your-captions-to-others.md), [OBS Studio](https://help.zipcaptions.app/streaming-captions/captioning-with-obs-for-live-streams.md), and [AI Captions (Azure Cognitive Services)](https://help.zipcaptions.app/settings/ai-captions.md).

***

## Broadcasting Translated Captions to Viewers

When you host a [Broadcast Stream](https://help.zipcaptions.app/streaming-captions/broadcasting-your-captions-to-others.md) with **Live Translation** enabled, Zip Captions automatically transmits **both** your original captions and your translated captions to everyone watching your stream.

### What This Means for Viewers

* **Works on Any Device or Browser:** Because the broadcaster's computer performs the translation and sends the translated text over the stream, **viewers do not need a browser that supports on-device translation**. Attendees on **iPhones, iPads, Android phones, Safari, or Firefox** can view your translated captions live!
* **One-Click "Show Translation" Button:** When a viewer joins a broadcast that offers a translation, a **Show translation** button (for example, `Show translation: FR`) appears in the top right of their screen. Clicking it immediately opens the translated pane.
* **Viewer Display Controls:** Each viewer can independently choose how they want to view the broadcast on their own device using their Quick Access sidebar (**Split (Bilingual)**, **Translated Only**, or **Original only**, as well as **Stacked** or **Side by side** orientation).
* **Broadcaster "Original Only" Mode:** If you want your own screen (such as a podium monitor) to show only the spoken language while still sending live translations to your audience's devices, set your **Caption Display Layout** to **Original only**.

### Viewer-Side Local Translation (Additional Languages)

If a viewer joins your broadcast using a supported desktop browser (**Chrome 138+** or **Edge 148+**), their language dropdown lists:

1. **Translated by the broadcaster:** The language you are already broadcasting (no model download required by the viewer).
2. **Translated on this device:** All other supported translation languages. This allows a desktop Chrome/Edge viewer to translate your original broadcast into a different language of their choice right on their own device—even if you aren't translating at all!

***

## Sending Translated Captions to OBS Studio

When using [Zip Captions with OBS Studio](https://help.zipcaptions.app/streaming-captions/captioning-with-obs-for-live-streams.md) via WebSocket (`SendStreamCaption`), you can choose whether OBS receives your **original** spoken captions or your **translated** captions.

1. Open **Settings** and click on the **OBS Studio** tab.
2. Under **What OBS receives**, choose between:
   * **Original captions** *(Default)*: Sends the spoken language to your OBS stream.
   * **Translated captions**: Sends the real-time translated caption feed to your OBS stream.

{% hint style="info" %}
If you select **Translated captions** while Live Translation is turned off or unavailable, OBS automatically falls back to receiving your **Original captions** so your stream never loses subtitles. While a phrase's translation is still pending, Zip Captions waits until the translation is ready rather than sending untranslated text.
{% endhint %}

### CEA-608 Character Set Limitations in OBS

OBS Studio transmits embedded stream captions using the standard **CEA-608** broadcast caption format, which only supports Latin/Western European character sets (Basic North American, Special North American, and Extended Western European characters).

{% hint style="warning" %}
**Unsupported Scripts in OBS CEA-608 Captions**

Because of CEA-608 format limitations inside OBS Studio, OBS cannot display characters from non-Latin scripts, including:

* **Arabic** (`ar`)
* **Chinese** (`zh`)
* **Japanese** (`ja`)
* **Korean** (`ko`)
* **Hindi** (`hi`)
* **Russian** (`ru`)
* **Ukrainian** (`uk`)

If your effective OBS language uses one of these scripts, Zip Captions will display a warning in the OBS Studio settings tab. To show non-Latin translated captions in OBS, we recommend capturing the Zip Captions window using an [OBS Browser Source](https://help.zipcaptions.app/advanced/captioning-with-obs-browser-source.md) or [OBS Application Source](https://help.zipcaptions.app/advanced/captioning-with-obs-application-source.md) instead of WebSocket CEA-608 captions.
{% endhint %}

***

## Bilingual Speech Recognition with Azure AI Captions

When using [AI Captions (Microsoft Azure Cognitive Services)](https://help.zipcaptions.app/settings/ai-captions.md), several regional dialects natively recognize **both the selected language and English** within the same session—allowing speakers to switch between languages naturally without changing settings.

### Supported Bilingual Azure Dialects

* **French (Canada)** (`fr-CA`) — Recognizes **French + English**
* **Spanish (United States)** (`es-US`) — Recognizes **Spanish + English**
* **Arabic Dialects** (`ar-AE`, `ar-BH`, `ar-DZ`, `ar-IL`, `ar-IQ`, `ar-KW`, `ar-LB`, `ar-LY`, `ar-MA`, `ar-OM`, `ar-PS`, `ar-QA`, `ar-SA`, `ar-SY`, `ar-TN`, `ar-YE`) — Recognizes **Arabic + English** *(Note: `ar-EG` and `ar-JO` do not include bilingual English support)*

When you select one of these dialects with the Azure engine, Zip Captions displays a hint letting you know that **this dialect also recognizes English**, and whichever of the two languages is spoken will be shown in that language in the live captions.

### How Bilingual Detection Works with Live Translation

When you combine an Azure bilingual dialect (for example, **French (Canada)**) with **Live Translation** into **English** (or vice versa):

1. **On-Device Language Detection:** As each caption segment is finalized, Zip Captions uses Chrome's built-in on-device `LanguageDetector` to identify whether the phrase was spoken in French or English. (Very short or uncertain phrases automatically keep the previous phrase's language.)
2. **Dedicated Language Panes:** In **Split (Bilingual)** view, each pane is dedicated to a specific language (one **FR** pane and one **EN** pane).
   * When the speaker talks in **French**, the French text appears as spoken in the **FR** pane and is translated into English in the **EN** pane.
   * When the speaker switches to **English**, the English text appears as spoken in the **EN** pane and is translated into French in the **FR** pane.
3. **Both Translation Directions:** Clicking **Download Translation Model** on the captioning screen automatically prepares both translation directions (e.g., `fr → en` and `en → fr`) so seamless two-way translation is ready whenever the speaker switches languages.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.zipcaptions.app/translation/broadcasting-and-obs-translation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
