The first time a church runs live translation, the nerves are rarely about the technology itself — they're about all the small unknowns around it. Where does the audio come from? What if the delay is too long? What if nobody actually scans the code? None of these need to be a mystery. Here's the setup in order, the same way it works for a church doing it for the first time this Sunday.
1. Find your audio source
Quality in is quality out, so this is the step worth getting right — and it's the one that decides how good everything downstream looks. In order of preference:
- A feed from the sound board — an aux send or tape-out into the laptop or tablet running the broadcast. This is the cleanest option and, if the church already has a mixer, usually just needs a cable.
- A USB audio interface plugged into the same board, if the computer doesn't have a spare input.
- The device's own microphone, placed close to a speaker, as a fallback when there's no board feed available. It works, but background noise and room echo come along with it.
Be aware of what happens when the audio is too quiet: recognition doesn't go silent or leave gaps, it invents. Confident, fluent sentences that nobody said. That's why the third option is a fallback rather than a plan, and why the sound check below is the most important five minutes in this article.
2. Set up the broadcasting device
Any laptop, PC, iPad or Android tablet with a modern browser works — nothing to install. It needs to stay awake and connected for the length of the service, so disable sleep on that device before going live and plug it into power. A tablet that locks its screen twenty minutes into the sermon is one of the more common first-service failures, and it's entirely preventable.
If the same machine also runs your live stream or your slides, consider a second device. Translation isn't heavy, but a laptop that's already busy is a laptop that will stutter at the wrong moment.
3. Decide the language list ahead of time
It's tempting to leave the list open-ended, but a quick ask around the office or a glance at who's been visiting recently produces a much better starting point than guessing.
Ask about reading rather than nationality — the two often differ, and someone's passport is a poor guide to the language they'd rather follow a sermon in. Attendees can always pick something that wasn't pre-announced, but having the two or three most likely ones ready, and mentioned once from the front, gets far more people to try it in the first week.
4. Put the QR code somewhere obvious
The single biggest factor in whether people use live translation isn't the translation quality — it's whether anyone knows it exists. What works reliably:
- A printed card at the welcome table and a permanent framed sign by the door. The permanent sign covers every future visitor without anyone remembering to do anything.
- Projecting the code for a minute before the service starts, not only during announcements.
- On the printed notice sheet, which is what people look at while they're sitting and waiting.
- One verbal mention from the front for the first few weeks. After that, word of mouth takes over.
Two details that quietly decide whether it works: print it big enough — a rough rule is a tenth of the distance it'll be scanned from, so a code read from three meters wants to be about thirty centimeters across — and put the plain web address underneath as text, for people whose camera won't cooperate.
The most common mistake is putting the code only on the welcome slide. That slide is replaced by song lyrics four minutes in and never comes back, which locks out exactly the latecomer who needed it.
5. Do a dry run the week before
A five-minute test during a weekday rehearsal or staff meeting catches the two or three things that would otherwise surface awkwardly during the actual service. Specifically:
- Speak a normal sentence into the microphone the preacher will actually use, from where they'll actually stand.
- Read the transcript. Properly, not a skim. If it's fluent but wrong in places, that's the audio talking.
- Have one other person scan the code on their own phone, without help, and see how long it takes them.
- Walk to the back and the corners with that phone and check the text is still arriving.
The most common first-service mistake isn't a technical one: it's placing the microphone too far from the speaker, or having a musician's monitor bleed into the feed. Both are five-second fixes once noticed, but easy to miss without a dry run.
What to say from the front
One sentence, and the wording matters more than you'd think. "If you'd rather follow in another language, there's a code on your notice sheet" is an offer anyone can take. "For those of you who don't speak English well" identifies people, and will be used by nobody.
If you're archiving the service, say that too. It takes three seconds and it's the difference between people feeling informed and people feeling recorded.
If something goes wrong on the day
| What you see | Almost always | Do this |
|---|---|---|
| Text stopped, speaker still talking | Dropped connection, muted channel, or a dead mic battery | Check the mic, then restart the broadcast — it takes seconds |
| Text is moving but reads as nonsense | Audio too quiet or too distant | Nothing mid-service. Fix the feed before next week |
| One person says it won't load | Church Wi-Fi, often a sign-in page | Suggest mobile data |
| Nothing at all appeared | Broadcast never started | Start it. It's happened to everyone |
Give whoever is operating permission to do only these things. A volunteer who's afraid of breaking something won't volunteer twice.
What to expect the first few weeks
Adoption is usually slow in week one and then grows on its own. The second and third weeks are typically when regular attendees who skipped it initially decide to try it, often after watching a visitor use it comfortably.
Don't judge it on week one, and don't judge it on numbers alone. Four people, if they're the four who needed it, is the whole point.
Set it up for this Sunday
Free credit on signup, no card required. Most churches are live within an hour of creating an account.