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. 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.
Whichever source is used, a quick sound check before the first real service catches problems while they're still easy to fix.
2. Set up the broadcasting device
Any laptop, Windows PC, iPad or Android tablet with a modern browser works — nothing to install. It just needs to stay awake and connected to the internet for the length of the service, so it's worth disabling sleep mode on that one device before going live.
3. Decide the language list ahead of time
It's tempting to leave the language list open-ended, but a quick ask around the office or a glance at who's been visiting recently produces a much better starting list than guessing. Attendees can always pick a language that isn't pre-announced, but having the two or three most likely ones ready — and mentioned once from the front — gets more people to actually try it 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:
- Projecting the QR code on the screen for a minute before the service starts, not just during announcements.
- A printed card at the welcome table, in the language(s) most likely to be needed.
- One verbal mention from the front in the first few weeks — after that, word of mouth tends to take over.
5. Do a dry run the week before
A five-minute test during a weekday rehearsal or staff meeting — checking mic placement, confirming the translation appears with a reasonable delay, and having one other person scan the code on their own phone — catches the two or three things that would otherwise surface awkwardly during the actual service.
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 expect the first few weeks
Adoption is usually slow the first week 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 seeing a visitor use it comfortably. It rarely needs more than the habits above to keep growing from there.
Set it up for this Sunday
Free credit on signup, no card required. Most churches are live within an hour of creating an account.