How to Translate a Church Service Live

Live translation begins with clean audio. Before anything else, make sure you can get a reliable audio feed from your sound system to the translation platform.

Audio Feed

You need a direct feed from your mixing console—not room audio captured by a microphone. Practical routing options include:

• USB audio interface — A simple audio interface connected to an aux or bus output on your mixer. Confirm that the feed contains spoken program audio and is not affected by the room's main-output level.
• Dante Virtual Soundcard — If your church uses a Dante audio network, expose the assigned channel to the operator computer through Dante Virtual Soundcard, then select it as an audio input.
• Other console or I/O feeds — Any route must arrive as an input device the operator computer can see. Confirm the channel assignment and level before opening the room.

Computer

Linguify's operator dashboard runs on a dedicated computer. A laptop or desktop at your tech booth is ideal. It should be connected to your audio source and have a stable network connection.

Internet Connection

A stable internet connection is needed for cloud-dependent functions and hosted attendee delivery. Local speech recognition can reduce one dependency, but it does not make the complete translation and translated-audio workflow offline. Use wired Ethernet for the operator machine where practical, and test the attendee path on both the church network and a typical mobile connection.

Start by understanding who is in your congregation. A brief survey, connection card, or conversations with community leaders can help you identify the languages spoken in your church.

• Start with the most-requested languages. You don't have to launch every language at once. Pick the top one or two and expand as your team gains confidence.
• Linguify supports 115+ translation languages and 75+ speech-input languages. Confirm the exact source and target languages your church needs on the supported languages page.
• You can configure up to five simultaneous translated-language streams for a service. Start with confirmed demand, assign an owner to each planned output, and rehearse every active language before launch.

The Linguify operator dashboard is the control center for your translation session. Here's what configuration looks like before your first service:

1. Select your audio input — Choose the USB device, Dante virtual soundcard, or other source you connected in the previous step.
2. Choose your transcription setup — Select the source language and the local or cloud-supported processing option that matches your deployment. Rehearse with the same microphones, mixer route, and network conditions you will use during the service.
3. Set your target languages — Select the languages you want to offer. You can add or change languages between services.
4. Configure AI voices — Linguify offers 250+ voice profiles. Select and audition a voice for each target language, then verify pronunciation, intelligibility, and output routing with a fluent reviewer whenever possible.
5. Add custom vocabulary — If your church uses theological terms, proper names, or phrases that speech recognition may mishandle, add them to your recognition terms and correction rules. These tools can reduce recurring transcription errors; they are not a translation-memory or terminology-lock system, so review important translated phrasing separately.

For a deeper look at the full workflow, see How It Works.

One of the biggest advantages of browser-based delivery is that attendees don't need to install an app. They simply open a link.

• Display a QR code on screens, in the bulletin, or at welcome stations. Scanning it opens the listener page in the phone's browser.
• Share a URL — for attendees who prefer typing, a short memorable link works just as well.
• Choose a language — the listener page is available in 30+ UI languages. Each attendee picks their preferred language and begins receiving captions, translated text, or spoken audio according to the outputs active for that service.
• Choose the access policy — a church can offer an open listener page or enable an optional contact-information gate. Test the exact policy you plan to use so greeters can explain what attendees will see.

Once the service begins, the operator dashboard shows the live status of each translation stream. Here's what to watch for:

• Audio level indicators — Confirm the audio feed is strong and consistent. If levels drop (e.g., the speaker steps away from the mic), transcription quality degrades.
• Stream health — The dashboard shows service and stream status. Define who will respond to a warning, which output they will check first, and when to restart a service rather than troubleshooting live.
• Quick controls — If your production team uses Stream Deck or Bitfocus Companion, you can map supported service start, stop, and restart actions, as well as supported NDI caption cues, to physical controls. Label each button clearly and test its status feedback before use.

For broadcast teams, Linguify can output translated captions via NDI as a production source for OBS, vMix, or Wirecast overlays and for ProPresenter workflows that receive NDI. Confirm source discovery, transparency, positioning, and safe-area placement in the actual production scene.

Translation doesn't have to end when the service does. The content captured during a live session has value throughout the week.

• Saved transcripts — When transcript capture is part of your workflow, staff can manage and export supported transcript formats for reference, editing, or approved publishing. Confirm which language outputs were actually saved before promising a translated archive.
• AI sermon summaries — Linguify can generate summaries of the message, which staff can use for social media, newsletters, or study guides.
• Guest engagement tracking — If attendees opted in through the listener page, your team can follow up with first-time guests and use the recorded language preference when planning outreach.