Sunday service translation setup — technical guide for churches

You have decided to offer live translation at your Sunday service. The concept makes sense — pastor speaks, congregation listens in their own language. Now comes the practical question: what do you actually need to set up, and how long does it take?

The short answer: less than you think. A working translation setup requires a microphone, a laptop, a projector or screen, and reasonably stable internet. No specialized equipment. No AV company on retainer. Most churches already have everything they need.

This guide covers the technical details — what to prepare, how to test, and what to watch for on Sunday morning.

Hardware requirements

Microphone — the single most important piece

Translation quality depends almost entirely on what the system hears. A clear, consistent audio feed from the speaker produces accurate translation. A muddy, echo-filled feed produces mistakes.

Recommended: A wireless lavalier (lapel) microphone or a headset mic worn by the pastor. These stay close to the mouth regardless of whether the speaker turns, gestures, or steps away from the podium. Any standard wireless lavalier system from brands like Shure, Audio-Technica, or Rode works well.

Acceptable: A podium microphone, if the pastor speaks directly into it and does not move around. The main risk is that the pastor turns to address different parts of the sanctuary and the audio level drops.

Problematic: A room microphone mounted on the ceiling or at the front of the sanctuary picking up ambient sound. These capture the room echo, organ music, and coughing from the front row along with the pastor’s voice. The translation system cannot separate the speaker from the noise.

For churches on a tight budget, the church translation on a budget guide covers how to offer multilingual services without breaking the bank.

Laptop or tablet

The person starting the translation session needs a browser. Any laptop, desktop, or tablet made in the last five years works. This is the device that generates the session code and QR code — it does not need to be powerful.

The laptop should be connected to the same audio system as the sanctuary microphone. Most church sound boards have a USB or auxiliary output that feeds directly into a computer. If your board has a USB output, connect it to the laptop — this is the cleanest audio path.

Projector or display screen

The QR code needs to be visible to the congregation. Options:

• Projection screen — display the QR code as a slide before the service and during the welcome
• TV monitors in the lobby — useful for people who arrive late or are waiting in the foyer
• Printed in the bulletin — a static backup that works even if the projector fails

Internet connection

Real-time translation requires internet access. The bandwidth needs are modest — the system streams compressed audio, not video. Here are the practical requirements:

Congregation size	Minimum upload speed	Recommended
Under 50 people	5 Mbps	10 Mbps
50–200 people	10 Mbps	25 Mbps
200+ people	25 Mbps	50 Mbps

Most home internet connections exceed these speeds. The real bottleneck is usually the church’s Wi-Fi access point, not the internet connection itself.

Wi-Fi setup

If your congregation will connect to the church Wi-Fi to listen to translation, the network needs to handle the load. Each connected phone streams audio — roughly 64–128 Kbps per listener. A congregation of 100 people using translation simultaneously needs about 10–13 Mbps of Wi-Fi bandwidth dedicated to translation traffic.

Practical steps

Upgrade the access point if needed. Many churches use a single consumer-grade router installed when the building was set up. If it is more than five years old, replace it with a business-grade access point (Ubiquiti, TP-Link Omada, or similar). One access point per 80–100 simultaneous users is a reasonable rule of thumb.

Use a separate network for translation. If your church Wi-Fi also handles streaming the service online, running presentation software, and congregants browsing during the service, consider adding a dedicated Wi-Fi network or VLAN for translation traffic. This prevents other activity from crowding out the audio streams.

Encourage cellular data as a fallback. Most modern smartphones on 4G or 5G can stream audio without any issue. Announce that congregants can use their own data plan if the Wi-Fi is slow. This takes pressure off the church network at zero cost.

Test before Sunday. On a weekday, have 5–10 people connect to the church Wi-Fi and stream audio simultaneously. If it works, scale up gradually on Sundays. If it stutters, you know the access point needs an upgrade before you invite 200 people to rely on it.

Microphone placement and audio routing

Routing the audio to the translation system

The translation system needs a clean feed of the pastor’s microphone. There are two common approaches:

Direct USB from the sound board. Most digital sound boards have a USB output that sends all audio channels to a connected computer. Connect the board to the laptop via USB, and the translation system receives the same audio the congregation hears through the speakers.

Auxiliary output. If your board has an auxiliary or monitor output, route the pastor’s microphone channel to that output and connect it to the laptop’s audio input. This gives you a clean feed of just the pastor’s voice without music or other audio.

What to avoid

• Room echo. If the sanctuary has hard surfaces and long reverb, a podium mic will pick up the echo. The translation system transcribes the echo as a second voice talking over the speaker, which degrades accuracy. A lavalier mic worn close to the mouth avoids this entirely.
• Music bleed. During worship, the instruments and singing feed into the same sound board. If the translation system receives the full mix during a sermon, it might pick up residual music. Route only the speaking microphone to the translation feed.
• Multiple speakers. If your service has a guest speaker who uses a different microphone, make sure that mic is also routed to the translation feed. Plan for every person who will speak during the translated portions of the service.

QR code distribution

The QR code is how congregants access the translation. Making it visible and accessible is essential.

Where to place it

1. Projection screen — display it as the first or second slide before the service begins, and keep it visible during the welcome. Leave it on screen long enough for people to find their phones and scan.
2. Church bulletin — print the QR code in the order of worship. Include a one-line instruction: “Scan for live translation in your language.”
3. Lobby signage — a poster or standing sign near the entrance with the QR code and a brief explanation.
4. Pew cards — small printed cards tucked into the back of each pew or chair with the QR code and instructions. These serve latecomers and visitors who miss the screen.
5. Church website and newsletter — include the session code (e.g., LOQ-7X3K) in the Sunday morning email or website announcement. People can type the code directly if they cannot scan the QR code.

Making it accessible

Not everyone is comfortable with QR codes. Always display the session code in large text beneath the QR code on the projection screen. Congregants can type the code into their phone’s browser manually. The experience is identical — QR code and typed code both lead to the same translation page.

Pre-service testing checklist

Run through this checklist 30 minutes before the service starts:

• Translation session started and QR code generated
• QR code displayed on projection screen
• Microphone connected and feeding audio to the laptop
• Tested audio clarity by speaking into the mic and checking the transcription on a test phone
• Connected a test phone via QR code and verified translation is working
• Wi-Fi network operational (or cellular data confirmed as fallback)
• Pew cards placed in seats (if using them)
• Welcome team briefed on how to explain translation to visitors
• Volume levels checked — the pastor’s voice should be clear and not clipping

This takes about 10 minutes once you have done it a few times. The first time, allow 30 minutes.

During the service

After the setup is done, the translation runs on its own. There are only a few things to monitor:

Audio levels. If the pastor moves to a different mic, adjusts their volume, or hands the mic to a guest speaker, verify that the translation feed is still receiving audio. A quick glance at the laptop screen confirms this.

Congregant questions. A volunteer near the back can help anyone struggling to connect. Most issues are simple — someone does not have earbuds, or they are not sure which language to pick. A brief, quiet conversation resolves it.

No intervention needed for the translation itself. The system handles language detection, transcription, translation, and audio synthesis automatically. You do not need to select languages in advance or adjust settings mid-service. Each listener chooses their own language on their own phone.

Troubleshooting common issues

Problem	Likely cause	Fix
Translation is inaccurate	Poor microphone audio	Check mic placement, reduce room echo, switch to lavalier
Listeners report buffering	Wi-Fi congestion	Encourage cellular data, add access point
QR code does not load	Typo in the session code	Display the code prominently, verify it matches the session
Translation stops mid-sermon	Audio feed disconnected	Check the USB/aux cable from the sound board to the laptop
Some languages not available	Language not in the supported list	Check the supported languages page — 225 are available

The bottom line

Setting up live translation for a Sunday service is a one-time, 30-minute process that becomes a 10-minute routine within a few weeks. The equipment is standard. The workflow is simple. The impact on congregants who finally hear the sermon in their own language is immediate.

Start with what you have. Improve as you go. The first Sunday does not need to be perfect — it needs to work well enough that people experience the translation and come back next week expecting it.

---

Need a hand planning your setup? Start a free session and test it during a weekday service or rehearsal. No commitment — just a working translation ready for Sunday.