The One Thing That Makes or Breaks Live Translation
You can have the best microphone, the most accurate AI, and a congregation eager to hear the sermon in their own language — but if your church's internet connection stutters, none of it matters. Live translation depends on a stable connection the same way a live stream does. The good news: the requirements are modest, and most churches already have everything they need. The trick is knowing what to check before Sunday morning, not during it.
This guide walks through what live translation actually demands from your network, how to test it, and how to build in a safety net so a flaky connection never silences your translation. Whether you call it church WiFi, your sanctuary network, or simply "the internet in the building" (Danish: kirkens internet), the principles are the same.
How Much Bandwidth Does Live Translation Need?
Here is the reassuring part: live translation is far lighter on bandwidth than video streaming. The broadcaster's device sends a single compressed audio stream to the cloud and receives back text and audio. Listeners' phones each pull a small audio or subtitle stream.
As a rough planning guide:
- Broadcaster upload: a stable 2–5 Mbps upload is comfortable for sending audio to the cloud. This is the number that matters most.
- Per listener: roughly 0.1–0.3 Mbps for subtitles or compressed audio — a fraction of what a YouTube video uses.
- A congregation of 200 listeners across many languages typically stays well under 30–50 Mbps of combined download, and most listeners use their own mobile data rather than church WiFi anyway.
In practice, the broadcaster's connection is the critical link. If that one upload is solid, the system performs well even when the building's WiFi is busy.
Stability Beats Speed
A common mistake is to obsess over raw download speed. For live translation, consistency matters more than peak speed. A connection that delivers a steady 5 Mbps with low latency will outperform one that bursts to 100 Mbps but drops out every few minutes.
Three metrics are worth understanding:
- Latency (ping): how long data takes to make a round trip. Under 100 milliseconds is ideal. High latency adds delay to the translation.
- Jitter: variation in latency. High jitter causes audio to arrive unevenly, producing stutters. Keep it low and steady.
- Packet loss: data that never arrives. Even small amounts (above 1–2%) cause noticeable gaps. This is the silent killer of live audio.
Wired vs. Wireless for the Broadcaster
Wherever possible, connect the broadcast device by ethernet cable, not WiFi. A wired connection eliminates interference, congestion from listeners' phones, and the dead spots that plague older sanctuary buildings with thick stone walls. If the broadcast laptop or device sits near the sound desk, running a single network cable to it is the highest-value upgrade you can make.
If wired simply is not possible, position the WiFi access point close to the broadcast location and on a frequency band with little interference. A modern dual-band router placed within line of sight of the broadcaster will usually do the job.
Testing Your Setup Before Sunday
Never discover a problem during the service. Run a dry test at least once, ideally at the same time of week the service happens, since neighbouring businesses and homes affect shared connections.
- Run a speed test from the broadcast device's exact location. Note the upload number, not just download.
- Check stability over time — run a continuous ping test for ten minutes and watch for spikes or dropped packets, not just the average.
- Do a full rehearsal: start a real translation session, speak for several minutes, and have a colleague listen on a phone in the back row.
- Test with the building full, if you can. A network that is flawless in an empty hall can struggle when 150 phones connect at once. Even a mid-week event is a useful stress test.
Build a Backup: The Mobile Hotspot
Internet connections fail at the worst possible moments. The single most effective insurance for live translation is a backup connection on a separate network — typically a mobile hotspot on a different carrier than your main line.
The logic is simple: if your fixed broadband goes down, a 4G or 5G hotspot keeps the broadcaster online. Because live translation needs so little upload bandwidth, even a modest mobile signal is usually enough to carry the service. For a handful of euros a month, a dedicated hotspot or a spare phone with tethering turns a service-ending outage into a thirty-second switchover.
Practical backup tips:
- Use a different provider for your backup than your main internet, so a regional outage does not take out both.
- Test the hotspot regularly — a backup you have never tried is not a backup.
- Keep it charged and label it clearly so any volunteer can find and start it.
Helping Listeners Connect
Most listeners will join on their own phones by scanning a QR code, so they typically use their own mobile data. But for members on limited data plans or with weak signal inside the building, offering a simple guest WiFi network is a thoughtful touch. Keep the network name and password visible on a card or screen, and separate it from the broadcast device's network so listener traffic never competes with the critical upload stream.
Common Problems and Quick Fixes
- Translation cuts out intermittently: almost always packet loss or jitter on the broadcaster's connection. Switch to wired, or fail over to the hotspot.
- Noticeable extra delay: high latency. Check whether other devices are saturating the connection — a background backup or update can hog upload bandwidth mid-service.
- Works empty, fails when full: WiFi congestion from listener phones. Move the broadcaster to wired ethernet and put listeners on a separate guest network.
- Total outage: this is exactly what your mobile hotspot backup is for. Switch the broadcast device over and continue.
A Simple Pre-Service Checklist
Ten minutes before the service, a designated volunteer can run through a short routine: confirm the broadcast device is online and ideally wired in, check that the backup hotspot is charged and reachable, start a brief test session, and verify a phone in the congregation receives clean audio. A printed checklist taped to the sound desk turns this into muscle memory.
The Bottom Line
Live translation does not demand a fast or expensive connection — it demands a stable one, plus a backup for the moments when stability fails. A wired broadcaster, a tested network, and a cheap mobile hotspot on standby will carry your translation through almost any Sunday.
Platforms built for churches, such as OCvoice, are designed to be forgiving of imperfect networks — streaming partial results as they arrive so brief hiccups rarely interrupt the flow of worship, while a theological glossary keeps translations faithful across 60 languages. Get the connection right, and the technology quietly does the rest. For setup guidance and current pricing, visit ocvoice.dk/pricing.