Live translation for church services
Most congregations need translated audio for a small number of listeners, delivered to their own phones, with volunteers rather than staff running it. That points to simple setups — captions on a screen or audio to personal devices — rather than conference interpreting equipment.
This is a common need with an unusually poor fit to the tools built for it. Conference interpreting equipment assumes a budget, an AV team and a schedule. A congregation typically has none of the three, and runs the same event every week.
What is actually different here
- Weekly, not occasional. Cost per session matters far more than setup cost.
- Volunteers, not AV staff. Whatever you choose has to be operable by someone different each week, with no training.
- A small number of listeners, often two or three families, sometimes one.
- Specialised vocabulary that general translation handles poorly — liturgical terms, scripture references, names that must not be translated.
- A mixed room, where most people need nothing and a few need everything.
The three practical setups
Captions on a screen. A second screen, or a corner of the existing one, showing translated text. Cheapest, works for any number of listeners at once, and needs nobody to distribute hardware. It fails for people who cannot read the language quickly, or who cannot see the screen from where they sit.
Audio to personal phones. Listeners open a link and use their own headphones. No receivers to buy, charge, sanitise or lose. This is usually the right answer for a small number of listeners, and it scales without cost.
Dedicated receivers. The traditional approach: a transmitter and a box of headsets. Reliable and offline, but someone has to own the hardware — charging, distribution, collection, replacement. For a weekly service this becomes a recurring volunteer burden that quietly kills the programme after a few months.
The vocabulary problem is the real one
General-purpose translation handles ordinary speech well and religious register badly. Scripture citations, liturgical formulas, theological terms and proper names are precisely the words that must not be improvised, and they are the ones a general model is least sure about.
If your tooling supports a glossary, this is where the effort belongs — more than anywhere else. Build a list of:
- Recurring liturgical phrases
- Names of people, places and books, with the spelling used in the target language’s own tradition
- Terms with a specific meaning in your tradition that differ from everyday usage
Most tools that support glossaries let you reuse them week to week, which turns a one-off hour of work into a permanent improvement.
Practical notes from the format
Music. Live translation of sung content generally does not work and is not worth attempting. Provide translated lyrics as text instead, in advance or on screen.
The sermon is the priority. If you can only translate one part well, translate that.
Test from the back. The person who needs the translation is often not sitting where the person who set it up was standing.
Have a fallback that a volunteer can execute. If the system fails, the answer should be a printed summary or a person who can whisper-interpret, not a scramble at the sound desk.
Be realistic about scale
If two families need translation, a phone-based setup and a glossary will serve them well at almost no cost. If you are a congregation of 400 in five languages with a broadcast stream, you are running an event and should plan it like one.