Church livestream translation: captions in the stream or a link for every viewer

Two ways to translate a church livestream: burn one caption language into the video with an OBS or vMix overlay, or share a listener link so each online viewer picks their own language.

By SermonLingo TeamUpdated 8 min read

How do you translate a church livestream?

Church livestream translation works in one of two ways. Either you burn one caption language into the video with a transparent overlay in OBS or vMix, so every viewer sees it, or you share a listener link in the stream description and chat so each online viewer follows along in their own language on a phone or a second browser tab. Many churches do both.

The right mix depends on who watches online. If most remote viewers share one language, an overlay is simplest for them: nothing to open, nothing to choose. If they are spread across several languages, a link scales better, because one SermonLingo service room serves up to 8 listener languages and unlimited listeners.

How do you add the caption overlay in OBS or vMix?

In OBS Studio

  1. In the SermonLingo console, copy the caption overlay link and confirm which language it displays.
  2. In OBS, select your sermon scene, click + under Sources, choose Browser, and paste the link into the URL field.
  3. Set the width and height to match your canvas, usually 1920 × 1080, so the overlay lines up with the frame. The background is transparent, so only the caption text sits over your video.
  4. Leave "Shutdown source when not visible" unticked so a scene change doesn't reload the captions.
  5. Add the same source to every scene you cut to during the sermon (wide shot, close-up, slides) with Add Existing, so captions don't vanish when the director switches cameras.
  6. Lock the source once it is positioned, so a stray click can't drag it.

In vMix, add an input of type Web Browser, paste the same link, and set the resolution to match your production. Assign the input to an overlay channel so one button brings captions on for the sermon and takes them off for worship.

Keep captions in the lower part of the frame but clear of the very bottom edge, where the player controls of YouTube and other platforms appear when a viewer moves the mouse. Check that captions don't collide with your lower-third name graphics. If your platform offers automatic captions, ask viewers of the translated overlay to turn those off so two caption layers don't stack.

How do you test the delay between the stream and the captions?

The listener page follows the speaker in the room, usually by a second or two. The livestream reaches viewers later, often many seconds later, because the encoder, the platform and each viewer's player all buffer video. So an online viewer reading the link can see a sentence in captions before the preacher says it on screen. The overlay doesn't have this problem, because captions are added to the picture before it leaves the building.

Measure the gap once, with your real settings:

  1. Start an unlisted test stream with your normal encoder and platform settings.
  2. Open the stream on one device and the listener page on a phone beside it, ideally on a home connection or mobile data rather than the church Wi-Fi, as a remote viewer would.
  3. Have someone at the pulpit count slowly from one to ten and clap on five.
  4. Film both screens with a third phone. Afterwards, compare when the clap shows up in captions with when it is heard on the stream.
  5. If the gap is large, try your platform's latency setting. YouTube, for example, offers normal, low and ultra-low latency for live streams; lower latency usually shrinks the gap, but can mean more rebuffering for viewers on weak connections.

Then set expectations honestly in your description and chat, as in the wording above. A few seconds of lead is fine for reading; it is only confusing when nobody has explained it.

Can your stream encoder send audio for translation?

There are two sensible audio paths for a streaming church:

  • A mixer feed into the operator's computer. This works on every plan and is the easiest way to keep the translation feed speech-only. Our guide to church audio setup for live translation explains the aux send and USB interface.
  • Encoder input over RTMP (or SRT) from OBS, vMix or ProPresenter, included on the Advanced and Premium plans. The console shows step-by-step encoder settings, including the server address and stream key.

A few practical notes on the encoder route:

  • vMix can send to more than one streaming destination at once in its streaming settings, so SermonLingo can sit alongside your platform (check what your edition allows).
  • OBS Studio streams to one destination out of the box. A second destination usually means a multi-output plugin, so weigh whether a mixer feed is simpler for your team.
  • In ProPresenter, use Capture → Custom RTMP destination.
  • Whatever travels over RTMP is your stream mix. If that mix leans on room mics and the band for atmosphere, recognition gets harder, and a dedicated speech feed will give cleaner captions.
  • Treat the stream key like a password: never paste it into chat or show it on a projected screen.

SRT here means the streaming protocol (Secure Reliable Transport), not the SRT subtitle file format that transcript exports use.

What does translating the livestream add to your costs?

Listeners are unlimited on every plan, so 30 viewers online or 300 makes no difference to the bill. Translation hours depend on spoken time and the number of listener languages. Usage counts only while someone is speaking, so worship sets cost nothing.

Worked example: a church streams a service with 55 minutes of speech each week in Spanish, Portuguese and Korean.

  • 4 Sundays × 55 minutes = 220 minutes of speech.
  • 220 minutes × 3 languages ÷ 60 = 11 translation hours a month.

If audio comes from a mixer feed, the Standard plan ($99 a month with 25 hours) covers this, including the OBS overlay and AI voice. If you want the encoder to send audio over RTMP, you need Advanced ($299 a month with 100 hours). In other words, your audio path, more than your audience size, decides the plan. Compare the options on the pricing page, or book a guided walkthrough to see the overlay and encoder settings before you change your stream. If you run in-room and online congregations at the same time, our hybrid service translation checklist covers roles and failure plans for both.

Questions

Can online viewers choose their own language during a church livestream?

Yes, if you share the SermonLingo listener link in the stream description or chat. Each viewer opens it on a phone or in a new browser tab and picks from the service's listener languages, up to 8 per service. A caption overlay burned into the video shows only one language for everyone.

Why do translated captions run ahead of our church livestream?

Streaming platforms buffer video, so the stream often reaches viewers several seconds after the room hears the words, while the listener page follows the speaker by a second or two. A caption overlay added in OBS or vMix avoids the gap, because the captions travel inside the video itself.

Can SermonLingo take audio straight from OBS, vMix or ProPresenter?

Encoder input over RTMP (or SRT) is part of the SermonLingo Advanced and Premium plans, and the console shows step-by-step encoder settings. ProPresenter uses Capture with a Custom RTMP destination. On other plans, send a speech feed from the sound desk into the operator's computer instead.

Should we burn translated captions into the church service recording?

Burn captions in only when most online viewers need that one language, because overlay captions are part of the picture and cannot be switched off in the replay. If remote viewers speak several languages, keep the video clean and share the listener link, or use the overlay for your largest language group only.

All articles