Skip to content
Blink Brief
Language:

Guide · Churches and schools

Live translated subtitles in OBS: free plugins, paid services, and church translation apps

By Blink Brief · Published  · Updated  · How pages are made

Translation in OBS comes from outside it. Add the free LocalVocal plugin, which turns speech into text and can translate it on the streaming computer, or add a translation service's caption page as a Browser source. Church translation services such as Glossa, CaptionKit, LiveSunday and ChurchTranslator give you that page, so the same service puts the sermon on phones in the room and in the stream. Subtitles placed in the picture are the same for every viewer, so plan on one language on screen, or two at most; YouTube's own player takes only one caption track per live stream. Test the language pair with last week's sermon before Sunday.

Short answer

  • Free, on the streaming computer: LocalVocal 0.6.2, with a translation model on your computer or a cloud provider.
  • The church already uses a translation service: its caption page as a Browser source, from $18 a month (CaptionKit) or $5 an hour per language (Glossa).
  • A streamer's service: StreamTranslate, $14.99 a month for 25 hours with one language on screen, or $34.99 for two.
  • Captions in the spoken language only: see the Web Captioner replacement guide, which covers the captions plugins.

What OBS does and doesn't do on its own

OBS Studio combines sources, such as cameras, slides, text and web pages, into one picture and sends it to YouTube, Facebook or another destination. Two of its sources carry subtitles:

  • Browser source. OBS's knowledge base calls it "quite literally, a web browser that you can add directly to OBS". Its default Custom CSS sets the page's background to transparent, so a translation service's caption page sits over your video.
  • Text source. A plugin writes the words into it, and you style it like any other text in the scene.

The words, and their translation, come from a plugin or a service. Subtitles added this way are part of the picture: every viewer sees them, in the language you chose, and can't turn them off. YouTube's own player captions are a separate route with limits of their own, covered below.

If you need captions in the language being preached rather than a translation, the OBS Closed Captioning Plugin and LocalVocal's captions are set up in the Web Captioner replacement guide. This page is about the translated part.

LocalVocal: free, on your computer, with translation

LocalVocal is a free, open source (GPL-2.0) OBS plugin. It runs OpenAI's Whisper speech model on the streaming computer, and its README says "Translation is done with CTranslate2". What the README lists:

  • Speech to text "in real time in 100 languages".
  • Translation of the captions "in real time to major languages", with Whisper's built-in translation, translation models on your computer, or cloud providers; its README links guides for DeepL, OpenAI and a local language model.
  • Where the words go: "Display captions on screen using text sources", a .txt or .srt file, or "Send captions on a RTMP stream to e.g. YouTube, Twitch".
  • What it runs on: version 0.6.2, released 21 April 2026 and marked Latest, for Windows 10 and 11 (generic, NVIDIA and AMD builds), macOS 12 to 15 on Intel or Apple silicon, and Ubuntu 22.04. "No GPU required": it uses the processor by default, and you choose GPU acceleration in the plugin's settings.

The README promises "Privacy first - all data stays on your machine". That holds when the transcription and the translation both run locally. If you pick DeepL, OpenAI or another cloud provider for the translation, the text of the sermon goes to that provider.

The trade-offs: someone in the booth installs and updates a plugin, a laptop without a strong processor or GPU may lag behind the preacher, and a local translation model may read less smoothly than a paid service. The plugin's repository has moved to github.com/royshil/obs-localvocal; the old locaal-ai address forwards there.

After you install it, the README says, LocalVocal "should now be available in OBS Studio's filters": add it to the audio source that carries the pulpit microphone. It "ships with the Tiny.en model", which hears English only; for a sermon preached in another language, choose a multilingual model from its model dropdown. The README's setup is a video, its Usage Tutorial. We haven't run it: this page describes the README and the releases page, not a test.

A browser source from a translation service

A translation service runs in the cloud: it hears the preacher, translates, and serves the subtitles as a web page. OBS shows that page as a Browser source. StreamTranslate's own steps on the OBS forum show the pattern:

  1. In the service, choose the audio source, the spoken language and the target caption language.
  2. Copy the Browser Source URL it generates.
  3. In OBS Studio, add a Browser Source, paste the URL and match its size to your canvas, with the captions above the video sources they cover.
  4. Start the caption session, record a short test, then start the broadcast in OBS.

Two services built for streamers, from their own pages:

  • StreamTranslate says it needs no OBS plugin and that "Speech processing runs in the cloud", in 65 languages. Free: 3 active hours a month, card required. Starter: $14.99 a month for 25 hours and one language on screen (new customers can get the first month for $1). Pro: $34.99 for 50 hours and two subtitle languages. A Stream Pass is $12 for 12 hours, once.
  • Maestra writes its captions into an OBS text source through OBS's WebSockets server, or shows a shareable session in a Browser source, and "Runs in Chrome on the same computer as OBS Studio". Its pricing page lists "OBS, vMix & broadcast tools" under Organizations: $449 a month, or $359 a month billed annually, with 3 languages per session. The free plan gives 10 minutes a week in 1 language.

Church translation apps that already output to OBS

A church translation service does the job a streamer's service does, and also sends the translation to the phones of people in the room. Four say on their own pages that their caption page works in OBS:

Service What it gives OBS Entry price In the room
Glossa "A browser source or embed page drops translated text into ProPresenter, OBS, vMix and more" $5 per hour per language; 4 hours free Listeners read or hear the translation on their phones
CaptionKit "Every language gets lower-third and full-screen display links", to add to OBS, ProPresenter, vMix or FreeShow "like any web page" $18/month for 4 speaking hours in 1 language; 4 hours free Read in the browser; audio translation $2.50 per language per hour
LiveSunday An overlay URL: "a transparent browser overlay URL that you can add as a browser source in OBS Studio" $5 an hour with 1 language; 2 hours free Text; a voice on its $99 Advanced plan
ChurchTranslator Its caption page: "add the caption page as a Browser Source and it sits over your livestream as a transparent lower-third"; it can also take its audio from OBS over RTMP $39/month for 6 hours in 2 languages; first 4 hours free Live audio and captions on phones

Each vendor's own words and prices, in US dollars, read on its site on 6 November 2026. The other church services, with their screen outputs and free tiers, are in church translation apps compared.

Give the service the pulpit microphone from the sound desk, not the stream's mix with the band in it. If you use ChurchTranslator's route that takes the audio from OBS, make sure that output carries the speech, not the band. Glossa says "Silence, songs & music don't count"; CaptionKit and ChurchTranslator count the time the service is live, so songs left in the feed use up hours there. For choosing among them on price, see Glossa alternatives.

One stream, one subtitle language: what viewers see

You can't send YouTube several translated caption tracks for one live stream and let viewers choose. YouTube's help page on live caption requirements says that "While the 608/708 standard supports up to 4 language tracks, YouTube currently only supports one track of captions", and, for captions sent over HTTP, "Each stream entry point can have one caption feed only." YouTube's own automatic captions for live streams "are available in English only".

Subtitles placed in the picture with a Browser or Text source are the same for every viewer. That leaves three choices:

  • One language on screen, the one most of your online viewers need.
  • Two languages stacked: StreamTranslate's Pro plan shows two subtitle languages; with a church service that gives one caption page per language, add two Browser sources, one above the other. Two lines of moving text take a large part of the picture on a phone.
  • Each viewer's own language on their own device: put the translation service's listener link in the stream's description, and viewers open it beside the video. ChurchTranslator, for one, describes attendees on Zoom opening its listener link "to hear or read the service in their language".

We haven't read Facebook's rules for live caption tracks; check them before promising viewers there a choice.

Translation for the people in the room

A volunteer asked for subtitles on the stream may be asked next about the Spanish or Korean speakers in the pews. They don't watch the stream: they need the sermon on their own phones, by QR code. The church services in the table above do both from one feed. The church translation guide covers the room's setup and a first Sunday, and church translation equipment compares phones with headsets.

For the main screen in the room, the free Live Captions tool shows the sermon as large captions in the language being preached, in Chrome or Edge. On that screen it doesn't translate, and it doesn't feed OBS: the captions stay on the computer that runs it and, if you press Share to phones, on listeners' phones. The browser may send the audio to Google, Microsoft or Apple to turn it into text. Blink Brief never receives the audio; with Share to phones, the caption text goes to Blink Brief's server and to Cloudflare's AI for translation.

Our product · free beta

Share to phones, in Live Captions, is for the room, not the stream: each listener scans one QR code and reads your sermon in their own language, on their own phone, while you preach. Its page names no OBS or livestream output. Free during the beta.

How phone captions work

Questions

Can OBS translate live?

Not by itself. Translation comes from a plugin that runs inside OBS, such as the free LocalVocal, or from a translation service whose caption page you add to OBS as a Browser source. Church translation services such as Glossa, CaptionKit, LiveSunday and ChurchTranslator give you that page.

How do I add translated subtitles in OBS?

With a service: copy its caption page's URL, add a Browser source in OBS, paste the URL and size the source to the area the subtitles should cover; OBS makes a Browser source's background transparent by default. With LocalVocal: install the plugin and send its translated captions to a Text source. Either way, test the language pair with a recorded sermon before going live.

Is there a free OBS translation plugin?

Yes. LocalVocal is free and open source (GPL-2.0). It transcribes speech in 100 languages on your computer and translates the captions into major languages, with a translation model on your computer or a cloud provider you choose. With a cloud provider, the text goes to that provider.

Sources