How to translate a church service in real time

There are exactly three ways to translate a church service live: a human interpreter, dedicated interpretation hardware, or an AI live-translation platform that puts captions and a spoken voice on each listener’s own phone. This guide walks through all three honestly — what each costs, what each takes to run, and how to set up your first translated service step by step.

What “translating a church service” means today

Twenty years ago, a church translation system meant a booth, a stack of receivers, and a volunteer interpreter whispering into a headset. Today the most common setup is one microphone and the phones your guests already brought: whoever is preaching speaks normally, and each listener follows along in their own language — as live captions on their screen, a natural spoken voice in their earbuds, or both at once.

The shift matters because the old model quietly excluded people. There were never enough headsets, never enough interpreters for every language in the room, and the back row got left out. Phone-based translation scales to the whole congregation and to every language at once — and it removes the weekly burden of finding, scheduling, and paying a person per language.

The three options, honestly compared

Option 1: Human interpreters

The traditional answer, and still the right one for some settings. A trained interpreter — simultaneous (speaking over the sermon from a booth or a corner) or consecutive (the preacher pauses, the interpreter repeats) — brings real human judgment, handles humor and idiom well, and is a pastoral presence in their own right.

The tradeoffs are structural, not quality problems. Each interpreter covers exactly one language, every week, forever — so a church with Spanish, Korean, and Portuguese speakers needs three skilled people every Sunday. Professional interpreters bill per service; volunteer interpreters vary widely in skill and burn out. Consecutive interpreting doubles the length of everything said. And whisper interpreting only reaches the two or three people sitting next to the interpreter.

Option 2: Dedicated interpretation hardware

The middle era: an interpreter speaks into a transmitter, and listeners wear dedicated radio (FM) or infrared receivers with headsets. The audio is reliable, it works without internet, and no one needs a smartphone.

But the hardware doesn’t remove the interpreter — it just amplifies one. You still need a human per language, plus a channel per language, plus the receivers themselves (often a couple hundred dollars each), purchased in advance for a crowd size you have to guess. Someone charges them, sanitizes them, hands them out, and chases them down after the benediction. Your capacity is capped by the number of receivers in the bin, and adding a language means buying more equipment and finding another interpreter.

Option 3: AI live-translation platforms

The current generation: the preacher’s microphone feeds a translation service, and the service delivers live captions and a synthesized natural voice to every listener’s own phone. Guests scan a QR code, tap their language, and they’re in — no app, no account, no headset, nothing to hand out or collect.

The strengths are the mirror image of the other two options: one broadcast covers many languages simultaneously, capacity scales with the congregation instead of a hardware bin, there’s no weekly staffing burden, and you get a transcript of every service. The honest tradeoffs: you need a clean audio feed and a working internet connection, machine translation must be controlled with a glossary so names and theological terms come out right, and quality varies meaningfully between platforms — some quietly paraphrase, which matters more in a sermon than almost anywhere else (more on that below).

One more honest note: these aren’t mutually exclusive. Churches with a beloved interpreter keep them — the platform runs underneath, covering the languages the interpreter doesn’t, and handing them a transcript to lean on.

How real-time sermon translation actually works

With a platform like MyOpenDoor Translate, the path from pulpit to phone looks like this: the preacher’s microphone (or a feed from the sound board) streams to the translation engine, which turns the speech into whole, complete sentences in each listener’s language — arriving as captions on their screen in about a second, with the spoken voice following just behind. Each listener’s phone is connected live for the whole service, so captions, audio, announcements, and response cards all arrive the moment they’re sent.

The person running it sees a single web page — the broadcast console — with a Connect button, a Go Live button, and a mic toggle. We wrote a full walkthrough of every control: using the broadcast console. Your guests see a church-branded page with a language picker; that side is covered in how guests join and listen.

What you need to run it

• One audio source. Whatever you already preach with — a handheld mic, a lavalier, or a direct line out of your sound board. Cleaner audio gives cleaner translation, but a normal sermon setup is plenty.
• A booth device with a browser. The laptop or tablet your AV volunteer already uses. The broadcast console is a web page, not software to install.
• An internet connection. Standard church Wi-Fi or a wired connection for the booth. Guests use their own data or your guest Wi-Fi.
• A way to share the link. A QR code on the screen and in the bulletin, or a short URL. That’s how people join.
• A list of the languages your people speak. More on choosing these below.

That’s the whole equipment list. No booth to build, no receivers to charge, nothing for guests to download.

Step by step: your first translated service

1. Pick your starting languages. Start with the languages already in your pews — ask greeters and small-group leaders who is informally translating for family members today.
2. Load your glossary. Add your pastor’s name, your church’s name, ministry names, and the theological terms you care about, so they render correctly in every language instead of being guessed at. This is the single highest-leverage ten minutes of setup.
3. Set up the booth device once. Open the one-time setup link on the AV laptop and bookmark the console. From then on the device is trusted — no password to type on Sunday morning.
4. Run a weekday dry run. Ten minutes of real speech before you rely on it in a service. Read Scripture aloud — it’s the hardest test — and check the captions and the voice on a phone in the room.
5. Go live on Sunday. Connect, go live, and start the mic from the console — or put the service on the schedule and let it start automatically when the mic is on. Then preach exactly as you always do.
6. Show the QR code early. On screen before the service, not after the sermon starts, so guests can join during the welcome. They scan, tap their language, and captions begin — with an audio button for anyone who’d rather listen.
7. End the service and review. End it from the console (scheduled services also end on their own), download the transcript, and skim it. Anything that came out wrong becomes next week’s glossary entry.

What your congregation experiences

A guest’s whole journey is: camera → QR code → a web page with your church’s name on it → tap a language → captions. If they arrive early, the page shows the countdown to the service and starts on its own when you go live. Listeners who prefer audio tap once more and hear a natural voice in their language — and it keeps playing with the phone locked in a pocket, the way people actually listen. After the service, the message is still theirs: sermon notes and the full transcript, in their language.

This isn’t hypothetical. Cape Vineyard Church runs every Sunday service this way: Spanish-speaking members scan the code, pick Español, and follow the whole sermon as live captions with a natural Spanish voice — on the phones they walked in with.

Choosing which languages to offer

Start with the languages already in your pews, not a wish list. Your greeters and small-group leaders know who is translating informally for family members today — that’s your real demand. Spanish, Mandarin, Korean, Vietnamese, Tagalog, and Portuguese are common first choices in U.S. congregations. You can always add more later; the cost of an extra language is near zero when it’s software, not headsets and staffing.

We wrote focused walkthroughs for the two most common starting points: Spanish translation at church and Korean translation at church.

The one thing that matters most: faithfulness

Generic tools like web translators or video auto-captions translate word-by-word, quietly paraphrase, and have no idea what your congregation’s vocabulary means. In a sermon, that’s not a rough edge — it’s a problem. “Yahweh” should stay “Yahweh.” A Scripture reference should arrive intact, not smoothed into something the speaker never said.

This is why purpose-built church translation uses a controllable glossary and a faithful engine that delivers complete sentences without reinterpreting the speaker. (Ours is MODVOICE, the engine inside MyOpenDoor Translate — it fixes how the words were heard and never changes what was said.) When you evaluate any tool, ask the blunt question: does it ever rewrite, summarize, or complete a thought the speaker didn’t finish? It shouldn’t.

Common mistakes to avoid

• Feeding it bad audio. A mic across the room picks up the room. Use the speaker’s mic or a board feed.
• Skipping the glossary. Names and theology terms are exactly what generic translation gets wrong. Ten minutes of glossary work fixes it permanently.
• Skipping a dry run. Do a 10-minute test on a weekday before you rely on it Sunday.
• Forgetting to show the QR early. Put it up before the service, not after the sermon starts.
• Treating it as a gimmick. Tell your multilingual families it exists — promotion is half the value.

How much does it cost?

Interpreters cost per service, per language, indefinitely. Hardware costs up front per receiver — before the interpreter you still have to pay. Platforms are a monthly subscription based on how much you use it: entry plans for a single weekly service start around $149/month, every feature included, and adding a language adds no hardware and no staffing. We broke the whole comparison down in how much church translation costs, or see full pricing for current plans.

Frequently asked questions

Try it on your own service

The best way to know if it works for your room is to run it in your room. Book a free live test and we’ll set you up with a temporary link, run a real service with you, and review the transcript together afterward — no commitment.