How to translate a sermon in real time: a Sunday setup guide with timings

A step-by-step plan from the week before to the closing prayer: audio routing, a 30-minute rehearsal, a Sunday countdown, operator cues during the service, and quick fixes when something breaks.

By SermonLingo TeamUpdated 9 min read

How do you translate a sermon in real time?

To translate a sermon in real time, send the preacher's microphone audio into live translation software, choose the languages your guests need, and give those guests a QR code or link so translated captions, and in some languages an AI voice, appear on their own phones. Prepare during the week, rehearse once, and start setting up 30 minutes before the service.

The rest of this guide is a timeline you can hand to whoever runs translation. It assumes one operator, a laptop, an ordinary sound desk and SermonLingo, though the order of work suits most live translation tools. Adjust the timings to your building and your team. Still choosing a tool? Start with what to look for in a church translation app.

If you have never watched live sermon captions, spend two minutes in the scripted demo service on your phone first. Everything below will make more sense.

What do you need before your first translated Sunday?

Your translation kit
ItemWhyTip
Laptop with a current browserRuns the operator consoleKeep it plugged in, and switch off sleep and automatic updates for the morning
Audio from the sound deskClean speech gives cleaner captionsAn aux or matrix send into a USB audio interface; the laptop microphone is your fallback
Internet connectionThe operator and every guest need oneWired, or a dedicated network for the operator if possible; guests can use mobile data
QR codes and the listener linkHow guests joinSeat cards, the bulletin, the welcome desk and a slide
Projector or TV (optional)Stage display with up to 4 languages and a welcome slide with a large QR codeIncluded from the Standard plan up
A spare phone and earbudsYour view of what guests see and hearNever test the voice through a speaker near a live microphone

You also need people. One operator is enough for most services. Add a greeter who can help guests scan the code and, for the first few weeks, a bilingual reviewer who follows along and takes notes. In a small church the sound volunteer can double as operator once the routine settles.

Seven days out: decide languages, audio route and wording

  1. Confirm the languages. Ask your welcome team which languages guests have actually spoken over the last few months. You can run up to 8 listener languages in one service, but each one adds metered time, so start with the languages you know are needed.
  2. Pick the audio route. In order of preference: a feed from the sound desk into the laptop; an RTMP feed from your streaming encoder if you already broadcast with OBS or vMix (RTMP input comes with the Advanced and Premium plans); or the laptop's own microphone placed close to the pulpit or a loudspeaker.
  3. Set up the account and room. Sign in with Google to create a SermonLingo account; it starts with 4 free translation hours, enough to rehearse and run a first service in a language or two. In the operator console, create a service room, then set the speaker's language and the listener languages.
  4. Collect the preacher's notes. Ask for the passage, unusual names and any words in another language. Add them to the glossary now, and paste the outline into Sermon notes in room settings.
  5. Print the join materials. Print the QR code on seat cards and in the bulletin, and paste the listener link into the slides and onto the church website.
  6. Write the announcement. Keep it short and ask a bilingual member to translate it for the slide.

"If you would like this message in another language, scan the QR code on the screen or on the card in front of you. It opens in your phone's browser, with nothing to install and no sign-up. Pick your language, and use earbuds if you would like to listen."

The rehearsal: 30 minutes on Saturday or midweek

One rehearsal in the real room catches most of the problems that would otherwise surface during the sermon. Book the sound volunteer for half an hour and work through this sequence.

  1. Minutes 0 to 5, connect audio. Plug the desk feed into the laptop, select it as the input in the console, and have someone speak at the pulpit at preaching volume. On the desk, the send should sit steadily and well below the red.
  2. Minutes 5 to 15, run real speech. Play ten minutes of a recorded sermon through a desk channel that feeds the translation send, or have someone read one aloud at the pulpit. Follow along on two phones, ideally an iPhone and an Android, in two different languages.
  3. Minutes 15 to 20, check voice and screens. If you offer the AI voice, listen through earbuds. If you use the stage display, put it on the projector and read it from the back row.
  4. Minutes 20 to 25, practice the pauses. Pause, resume and pause again, just as you will for songs and the offering. Watch your test phone to see how quickly captions pick up again.
  5. Minutes 25 to 30, write it down. Record the input name, desk channel, send level and any glossary changes on a one-page runbook that stays with the laptop.

If a bilingual member can join, ask them to flag anything that changes the meaning. Fixing two or three names on Saturday saves a lot of confusion on Sunday.

Sunday: the 30-minute countdown

Same order every week, so nothing depends on memory
TimeTask
30 minutes beforeLaptop on power and online, sleep off. Open the console and the service room.
25 minutes beforeThe sound volunteer confirms the translation send is up. Speak into the pulpit microphone and check that text appears on your test phone.
20 minutes beforeConfirm the speaker's language and the listener languages. If a guest preacher is speaking, make sure the speaker language matches them.
15 minutes beforePut the stage display on screen so the welcome slide and large QR code greet people as they arrive.
10 minutes beforeGreeters hand out QR cards and carry a printed copy of the listener link for phones that won't scan.
5 minutes beforeJoin from your test phone as a guest and glance at the listener counts per language in the console.
First words spokenGo live.

Treat this like the band's line check: the same steps in the same order every week. On the first few Sundays, arrive 45 minutes early instead of 30.

During the service: what the operator does and when

Operator cues, start to finish
MomentActionReason
Welcome and announcementsLiveGuests settle in with captions already running
Worship setPauseSung lyrics translate poorly; show bilingual lyrics on slides instead
Scripture readingLiveIf you can, also show the passage on a slide in the guests' own Bible version
SermonLive; check the test phone every few minutesThe main event
Response, altar call or prayer ministryPause, and let a bilingual prayer team helpPersonal moments need people, not captions
OfferingPauseNothing to translate
Benediction and closing noticesLiveGuests learn how to connect next

Pausing is about clean, respectful captions rather than money. SermonLingo only meters time when someone is speaking, so songs and silence don't use hours either way.

Between cues, keep an eye on three things: the send meter on the desk, your test phone, and the greeters. If a guest's phone won't connect, the usual fix is to reload the page or switch from the building Wi-Fi to mobile data.

After the service: a 10-minute close-out

  • Pause translation as soon as the benediction ends, so nothing said afterwards is captioned.
  • Write the listener count for each language in the runbook. Over a few months, those numbers tell you which languages to keep.
  • Ask two or three guests, in their language if you can, what was hard to follow.
  • Collect the reviewer's notes and add new names or terms to the glossary.
  • If your plan includes transcripts (Advanced and Premium), export the sermon as TXT, CSV, SRT or WebVTT to check a passage or publish it. The sermon transcript SEO guide explains how to turn one into a useful web page.
  • Check the hours used. A 40-minute sermon plus 10 minutes of announcements in 3 languages comes to 50 × 3 = 150 minutes, or 2.5 translation hours.

What should you do when something goes wrong mid-service?

Symptom, likely cause, first fix
SymptomLikely causeTry first
No captions on any phoneSession paused or not live, or the wrong audio input selectedCheck the console status and input, then speak into the pulpit microphone
Captions full of nonsenseMusic or room noise in the feed, echo, or a distorted signalAsk for band channels to be removed from the send and the level lowered
Captions stop for everyoneLaptop asleep, network down or a cable unpluggedWake the laptop, check the network, and switch to the laptop microphone as a stopgap
One guest can't joinWi-Fi with a sign-in page, an outdated browser or a mistyped linkSwitch the phone to mobile data or scan the QR code again
Names come out wrongUnfamiliar proper nounsAdd them to the glossary for next week and show new names on a slide
A guest preacher speaking another language gets garbled captionsSpeaker language still set for the usual pastorMake the speaker language a fixed step in the countdown

For deeper audio problems such as hum, feedback or clipping, work through the church audio setup guide for live translation. To get printed codes right, see QR codes for church translation, and to prepare the people who run all this, use the volunteer training guide. When you are ready, start your free account and book the rehearsal.

Questions

How early should the translation operator arrive on Sunday?

Plan for the translation operator to arrive 30 minutes before the service, or 45 minutes for the first few Sundays. That covers power and network, the audio check with the sound desk, the stage display welcome slide and a test from a guest phone, with a few minutes spare for the problem nobody expected.

Can the sound volunteer also run sermon translation?

In a small church, yes. Once the audio send is set up, the translation operator mainly goes live, pauses for songs and the offering, and watches a test phone. In a larger service with a band, keep the jobs separate, because the sound volunteer's attention belongs on the mix when something goes wrong.

Should worship songs be translated in real time?

Usually not. Sung lyrics are hard for speech recognition, poetry loses its shape in machine translation, and SermonLingo does not count songs or music as translation time in any case. Pause during the worship set and show the lyrics on your slides in both languages, prepared ahead by a bilingual member of the team.

What happens if the internet drops during the sermon?

Real-time sermon translation needs a live connection for the operator and for every guest, so captions stop until the connection returns. Keep a phone hotspot ready as a backup for the operator laptop, brief greeters on helping guests reload the page, and try the backup once during rehearsal rather than discovering problems on Sunday.

All articles