Church Live Captioning Guide

Captioning isn't just a nice-to-have—it's a meaningful act of inclusion. Consider who benefits:

• Deaf and hard-of-hearing attendees — Captions provide direct access to sermon content without relying on sign language interpreters (though both can coexist).
• Non-native English speakers — Reading text in a familiar language while hearing the original audio gives attendees another way to follow the message.
• Noisy environments — Cry rooms, lobbies, and overflow areas where audio quality is poor are easier to follow when captions are available on screen or phone.
• Livestream and remote viewers — Online audiences benefit from captions, especially in contexts where they can't control their listening environment.

Captioning can remove practical barriers, but the display still needs to fit the people and the room. Ask the people you intend to serve what presentation, placement, and support they need, then include those needs in rehearsal and operator training.

There's an important distinction between these two use cases, and your church may need one or both.

Single-Language Captioning

This is transcription: converting the speaker's words to text in the same language. It serves deaf and hard-of-hearing attendees, people in noisy environments, and anyone who prefers reading along.

Multilingual Captioning

This adds a translation step: the speech is transcribed, then translated, and each attendee reads captions in their chosen language. Linguify supports 115+ translation languages. Churches should still confirm the exact source and target languages they need and arrange fluent review for ministry-critical terminology.

The simplest way to deliver captions is directly to each attendee's phone. With Linguify, this is browser-based—no app installation required.

• QR code or short URL — Display it on screens, in bulletins, or at welcome stations. Attendees scan or type the address and open the listener page in a browser.
• Language selection — The listener page supports 30+ UI languages. Each person picks their preferred language and begins reading.
• Text and audio options — Attendees can read captions, listen to AI-translated audio, or both—whatever works for them.
• Configurable access — The listener page can be open, or the church can enable an optional contact-information gate. Train greeters on the policy actually in use rather than promising the same flow at every event.

Phone-based delivery works well for multilingual captioning because each device shows only the language its user selected. There's no visual clutter and no need for multiple displays.

Some churches prefer or additionally use large displays or projection for captions. This is especially useful for:

• Broader in-room access — A visible caption display helps people read along without relying on a personal smartphone.
• Overflow rooms — Rooms with video feeds of the main service benefit from caption overlays.
• Lobby and welcome areas — Captions on a hallway screen let latecomers or parents in the foyer follow along.

When using on-screen captions, consider font size (large enough to read from the back row), positioning (lower third of screen to avoid blocking visuals), and contrast (light text on a dark background or using a text shadow/box for readability).

For churches with broadcast or livestream operations, Linguify can deliver a styled caption-video source over NDI. Production teams can receive that source in familiar tools:

• OBS, vMix, and Wirecast — Add the NDI caption feed as a source and composite it over your camera feeds, sermon graphics, or announcement layouts.
• ProPresenter — Display translated captions alongside teaching slides, Scripture references, or announcements using an NDI input layer.
• Alpha channel support — The NDI output supports transparency, so captions overlay cleanly without a background box unless you want one.
• Resi — Include caption visibility and attendee-language checks in the production runbook used for your Resi events.

NDI output means your existing production team can incorporate captions into their workflow using the tools they already know.

A captioning workflow can also create a transcript that staff retain after the event. Decide before the service whether recording and transcript storage are appropriate, who may access the files, and how long they should be kept. Useful follow-on workflows include:

• Searchable archives — Staff can organize saved sermon transcripts and search them with the available archive tools.
• AI-generated summaries — Linguify can produce sermon summaries for newsletters, social media, or study guides.
• Planned language exports — Verify which source or translated text was actually saved, review it, and export only the files your publishing workflow requires.
• Internal reference — A church may retain reviewed sermon records for staff research or its own denominational documentation process.

Before your first captioned service, work through these practical details:

Audio Quality

Caption accuracy starts with clean audio. Use a direct feed from your mixing console—not a room microphone. The quality of your speech-to-text output depends directly on the quality of the audio input. Test the selected transcription setup with the actual speaker, microphone technique, and console processing used in the room.

Internet Bandwidth

The operator machine needs a stable connection for cloud-dependent functions and hosted caption delivery. Listener traffic adds aggregate demand to the attendee network. Use a wired operator connection where practical, then test the listener page from seating, lobby, and overflow areas.

Font Size and Readability

If displaying captions on screens, test readability from the farthest seat. Use high-contrast text (white or light text on dark backgrounds) and avoid fonts that are too thin or decorative.

Theological Vocabulary

General AI models sometimes struggle with terms like "justification," "eschatology," or Scripture proper names. Add these to your custom recognition terms or correction rules in Linguify, then review important passages with a fluent person. These controls can reduce recurring recognition errors but do not guarantee translation choices.

Operator Workflow

Designate someone on your production team to manage the captioning session from the operator dashboard. This can often be the same person running slides or managing the livestream. Use Stream Deck or Bitfocus Companion to simplify start/stop controls during the service.