Skip to content
Blink Brief
Language:

Guide · Churches and schools

AI translation for church services: free live translation on the congregation's smartphones, and where a person still matters

By Blink Brief · Updated  · How pages are made

AI translation in a church service is two machines in a row: speech recognition writes down the sermon, and machine translation turns each sentence into the listener's language a moment later, on their phone or in an earpiece. Blink Brief's free Live Captions does it as text: press Share to phones, show the QR code, and each member reads the sermon in their language with no app. For a voice in the ear, or for wording that has to be exact, a paid app or a person is still the answer.

Short answer

  • Text on phones, free: Share to phones in Live Captions, up to 200 phones and 8 languages at a time.
  • A voice in an earpiece: a paid app with a synthetic voice, or an interpreter on headsets.
  • Check with a person: verses, names, liturgy, and anything said once that must be right.
  • Before prayer requests: press Pause sharing.

What "AI translation" does in a service

Two steps, a moment behind the preacher:

  1. Speech to text. A computer near the sound desk hears the pulpit microphone and writes each sentence down. In Blink Brief, that is the speech recognition built into Chrome or Edge.
  2. Text to another language. Each finished line is translated by machine. In Blink Brief, that is Cloudflare's AI, line by line.

Some apps add a third step and read the translation aloud with a synthetic voice. Either way, a sentence has to end before it can be translated, so listeners are always a little behind. What the computer hears matters most: a clean feed from the sound desk beats a laptop microphone at the back of the room.

What it does well, and what to check with a person

  • Well: ordinary preaching in full sentences, from one speaker at a clear microphone, for listeners who read. Each person picks their own language, so one service can reach Spanish, Korean and Vietnamese speakers at once.
  • Scripture. A translated verse won't match the Bible your members read. Put key verses on a slide from both Bibles.
  • Names and titles. The pastor's name, the church's name and titles such as elder or deacon can come out wrong. Show them on a slide.
  • Liturgy and vows. Set prayers, a baptism or wedding vow, a membership covenant: use a translation your denomination or a translator has made, on the screen or on paper.
  • Songs. Recognition follows speech, not singing. Show lyrics in both languages on the screen instead.
  • Mixed languages. A Blink Brief room hears one spoken language. A preacher who switches language mid-sermon gets poor text in the second one.

Before you announce it, play last week's sermon through the sound desk and have a bilingual member read it on a phone in each language. Fix the slides for whatever they mark. An accuracy figure in a brochure doesn't replace that test.

Text on phones or a voice in an earpiece

This is the real choice between products. Blink Brief shows text only: listeners never hear a translation. Several paid church apps also read it aloud. Their own pages, read on 10 November 2026:

Product What listeners get Price on its own page
Blink Brief Live Captions, Share to phones Text on the phone, by QR code, no app; 32 entries in the spoken-language list, 8 at a time Free during the beta
Glossa Glossa says attendees "hear or read the translation"; 100+ languages $5 an hour per language pay as you go; $99 a month for 25 translation hours (1 hour in 3 languages counts as 3)
ChurchTranslator.AI "Live audio and captions", by QR code or link, no app From $39 a month for 6 service hours and 2 translated languages; one steady voice is a $9 add-on on that plan
Wordly "Audio and text output"; attendees "can choose whether they want to listen and / or read" Priced by the hours you buy; no amounts on the page

Prices in US dollars, as each vendor's page showed them on 10 November 2026. Descriptions are the vendors' own.

Text suits members who read comfortably, and it is silent in the pew. A voice suits members who would rather listen than read; each of them needs earphones. For members who follow only by ear, a human interpreter on a headset system is the route that doesn't depend on reading: church translation equipment compares headsets, receivers and phones, with makers' prices.

Free on phones: Share to phones

  1. On the laptop that hears the pulpit microphone, open Blink Brief's free Live Captions in Chrome or Edge. Chrome on Android works too; Safari works on some Macs and iPhones; Firefox doesn't.
  2. Choose the language being preached, press Start captions, and allow the microphone.
  3. Press Share to phones. Show the QR code on the screen with Show the QR code full screen, or read out the 6-character room code.
  4. Members scan it with the phone's camera, or type the room code at www.blink-brief.com/live-captions/listen, pick their language, and read. No app, no sign-up, on iPhone or Android, with an internet connection.
  5. Press End sharing at the end of the service.
  • Limits: up to 200 phones and 3 hours a room, 8 languages at a time, and 100 rooms a day per network.
  • A new code each service. Each service gets a new code, so a printed one won't work the next week: show it on the screen.
  • Prayer requests: press Pause sharing before them, and before anything that names a member. Nothing is sent while it is paused. Press Resume sharing after.

How the sermon reads on each phone, and the full language list, are in live sermon translation on smartphones.

Privacy: what goes where

  • The audio. Your browser may send the audio to its maker's speech service (Google for Chrome, Microsoft for Edge, Apple for Safari) to turn it into text. Blink Brief never receives your audio.
  • The text. When you share, the caption text goes to Blink Brief's server and to Cloudflare's AI for translation. End sharing deletes it; a room nobody ends is deleted 24 hours after its last line.
  • Who can read it. Anyone with the room code, on any phone, inside the building or not, while sharing is on.

Details are in the Privacy Policy. Ask the same three questions of any paid app before you choose it.

A church that meets every week: the church room

The free route needs the code on the screen each service. A church room keeps it the same: your church gets its own QR code that never changes, so you can print it in the bulletin. US$19 a month, billed monthly until you cancel, for as many services as you hold, each up to 3 hours. For churches in the US and Canada. The button is Get a church QR code, in the Share to phones panel of Live Captions, on a computer in Chrome or Edge (Terms); the bulletin QR code guide shows how to print it. It is still text on phones, not a voice.

Questions

Is there free AI translation for a church service?

Yes, as text on phones. Blink Brief's free Live Captions turns the sermon into text in Chrome or Edge on the captions laptop; press Share to phones and listeners scan a QR code and read each line in their language, translated by Cloudflare's AI. Free during the beta, up to 200 phones and 3 hours a room, 8 languages at a time.

What is the best AI translation for churches?

It depends on how your listeners follow. If they read, text on phones works and costs least. If they need to hear it, you need an app with a synthetic voice (Glossa, Wordly and ChurchTranslator.AI say they offer one, on paid plans) or a human interpreter on headsets. Test any of them with last week's sermon and a bilingual member before you choose.

Can AI translation take the place of a church interpreter?

Not for everything. It carries ordinary sentences across, a moment behind the preacher, for people who read. A trained interpreter still matters for members who follow by ear, for a baptism or wedding vow, for pastoral conversations, and for any wording that has to be right. Many churches use both.

Sources