YouTube Live captions for churches

Choose the caption path

• YouTube automatic live captions: viewer-switchable platform captions, currently English-only, subject to channel eligibility and normal-latency requirements
• Voco through an OBS Browser Source: translated text becomes part of the video picture and is visible to every viewer
• Professional captions: embedded CEA-608/708 or supported caption software can send a caption stream to YouTube; this is a specialised broadcast workflow

Path 1 — YouTube automatic live captions

YouTube's current help states that automatic captions for live streams are available in English only, are enabled per stream, require normal latency, and may not be available to every channel. They are machine-generated and can misrepresent accents, names, dialects, overlapping speakers, or poor audio. After the live stream ends, the live captions do not remain; YouTube generates a separate caption track for the archived video.

1. 1Set the correct video languageIn YouTube Studio, create the stream and confirm the spoken language rather than leaving an inherited default.
2. 2Use normal latencyYouTube says live automatic captions are not available for low or ultra-low latency streams.
3. 3Enable closed captions for that streamChoose automatic captions as the source when the option is available to the channel.
4. 4Review the archive separatelyDo not assume the live text becomes the final VOD captions. Review and edit the newly generated archive track after processing.

Path 2 — burn translated captions into OBS

When the church needs Spanish, Portuguese, Arabic, or another translated language live, add the Voco display URL as an OBS Browser Source above the programme video. The text is composited before the stream reaches YouTube, so every viewer sees it and no YouTube caption control is required. The trade-off is equally important: viewers cannot hide it or select another language, and it remains visible in the archived video unless you record a separate clean feed.

1. 1Build one translated sceneStart with one language and one readable lower-third region. Avoid stacking several small translations on a phone-sized video.
2. 2Keep a clean recording if neededIf the archive will receive edited subtitles later, record a version without the burned-in overlay or preserve an isolated programme feed.
3. 3Test on a television and phoneA caption that looks large in the OBS preview can be unreadable on a mobile YouTube player or obscured by player controls.
4. 4Review meaning with a fluent viewerA technically successful overlay is not proof that the translated sermon is clear or pastorally appropriate.

Path 3 — professional live-caption ingestion

YouTube documents two professional routes: embedded CEA-608/708 captions in the encoder output, or supported captioning software sending text to the stream's caption ingestion URL. YouTube currently supports one live caption track even though the broadcast standard can carry more. This route can preserve viewer controls, but it needs compatible encoding/caption software and a complete rehearsal; it is not the same thing as pasting a browser overlay URL.

A church-ready rehearsal

• Use the real pulpit and handheld microphones with music, prayer, names, and scripture references
• Open the public watch page on a signed-out phone rather than trusting only YouTube Studio
• Measure readability on a phone, laptop, and television with player controls visible
• Check the stream latency setting and confirm the intended caption path still appears
• Record five minutes, end the stream, and inspect what survives into the archive
• Document who corrects or replaces the VOD captions after Sunday

Primary YouTube and OBS references checked