StreamTranslateStreamTranslate uses an audio input plus a Browser Source display URL. You do not need to configure an OBS WebSocket server or give a caption tool access to scene controls for this Browser Source workflow.
Understand the three connection details
| Item | Purpose | Where it belongs |
|---|---|---|
| Microphone or source audio | Speech to recognize | Browser microphone input or OBS audio filter |
| Plugin stream key | Connect the audio filter | StreamTranslate filter settings |
| Browser Source URL | Show caption output | OBS Browser source properties |
Do not paste an audio key into a Browser Source field or use the overlay URL as an audio destination. Get both from the same StreamTranslate account and intended caption session.
Make the preview work before adding the display
Choose the spoken and subtitle languages in Control. Use My Voice to capture your browser microphone, or follow the OBS filter setup if the audio already arrives inside OBS. For the filter route, leave the website microphone off.
Speak until Control shows recognizable source text and a translated line. This is your checkpoint before working on layout. If that preview is empty, resizing a Browser Source cannot help. Confirm the chosen audio device and permission, or inspect the filter’s connection status and the meter on its attached source.
Add the Browser Source and arrange the scene
- Copy your caption display URL from Control.
- In the intended OBS scene, select Sources, add Browser and give it a descriptive name such as English captions.
- Paste the display URL and enter the dimensions shown by StreamTranslate; the standard landscape setup uses 1920 × 1080.
- Place it above the video sources that would otherwise cover it, then position the captions within your composition.
- Speak again and confirm the same new sentence appears in Control and OBS.
Caption styling belongs in the available Control settings. Avoid cropping a narrow box before checking how longer sentences wrap.
Reuse the display without multiplying capture
When several scenes need the same captions, reuse the existing caption source where your OBS scene setup allows it, or carefully add the same display URL. A second visual placement is not a reason to start another microphone session.
Check gameplay, full-camera and intermission scenes separately. A source visible in one scene can still be absent or covered in another. Decide which scenes should contain captions and which should pause audio capture. Keep those two decisions distinct: an intermission graphic can cover the display while speech is still being sent.
Verify what viewers actually receive
The Browser Source is composited into video. Its position and chosen language are therefore the same for viewers of that output. A Twitch extension and a native CC track are separate layers with their own controls; neither appears merely because you added a Browser Source.
Record a short sample to inspect text edges, contrast and cropping. Then check the destination player with harmless speech. If Control works but OBS is blank, inspect the URL, source visibility and layer order. If OBS works but another output does not, check that output’s setup instead of replacing a functioning audio connection.
Quick answers
Do I need OBS WebSockets for this setup?
No. StreamTranslate’s Browser Source workflow displays a caption URL. Other tools can use OBS WebSockets to update text sources, but that is a different integration.
Do viewers install the Browser Source?
No. You add it to OBS. Viewers receive the resulting video with the selected captions already visible.
Can I send native YouTube captions instead?
Yes, use the separate YouTube caption-ingestion setup. It sends one selected caption language to the matching broadcast and does not require a visible OBS caption layer.
Continue with your setup
Sources and further reading
Reviewed October 28, 2026. Follow the linked provider instructions for current availability and setup requirements.