Streaming

How to live stream a church service, start to finish

By Mambo Mutinda · Founder & CEO, TajiCast

11 August 2026 · Updated 8 September 2026

Streaming a service is four decisions and one habit: what software, what scenes, which platform, and how it gets there — plus a midweek run-through that catches most of what would otherwise go wrong on Sunday.

Choosing the software

OBS Studio is free, open source, and what most churches use. It does everything a normal service needs, runs on modest hardware, and there is an enormous amount of help available when something breaks.

vMix is paid and Windows-only, and it earns its price when you run several cameras and want instant replay, proper transitions and a production-style interface. If one person is switching three or more cameras live, it is worth the money.

Both accept NDI, which is how scripture graphics and lyrics reach the stream from another computer — or the same one — without capture hardware. That matters more than the choice between them.

Setting up scenes that survive a service

A scene is a saved arrangement of sources. The temptation is to build many; the discipline is to build few.

Every scene is something to find under pressure. A volunteer hunting for the right one during the sermon is worse than a slightly imperfect shot held steady.

A workable set for most churches:

1. Pre-serviceA holding screen with the church name and a countdown, running before you go live.
2. MainThe camera on the platform. This is where most of the service lives.
3. WideA wider shot, for congregational moments and for cutting away from a problem.
4. ScreenWhatever is on the projector, for readings and songs, if you show it online.
5. SafetyA holding slide to cut to when something goes wrong.

That last one is worth building before you need it. Something will fail eventually, and a scene that says "we will be back shortly" is far better than a frozen shot of an empty platform.

Naming and ordering

Name scenes for what they show, not what they contain: "Wide", not "Cam2 + audio". Order them in the sequence you use them, so muscle memory does the work.

Scripture as a source

If you put verses online — and you should, since online viewers cannot see your projector — add it as an NDI source that sits above the camera in every scene where scripture might appear. A proper lower-third keys over the camera automatically. The full setup is in NDI for churches.

Getting it to a platform

YouTube

The most common destination, and the most forgiving. You need a channel with live streaming enabled — which takes 24 hours to activate the first time, so do not discover this on a Saturday.

1. Enable live streamingIn YouTube Studio, request access. Wait for it to activate.
2. Create the streamSet the title, description and privacy, and choose whether it is scheduled or immediate.
3. Copy the stream keyPaste it into OBS under Settings → Stream. Treat it as a password.
4. Go liveStart streaming in OBS; YouTube shows the incoming feed before it is public.

Facebook

Reaches people who will not go looking for a church website. The process is similar — create a live video, copy the stream key — with one difference worth knowing: Facebook's copyright matching is aggressive, and recorded music in the background of a service can get a stream muted or taken down mid-service. See copyright and streaming licences.

Several platforms at once

The instinct is to run two encoders on one laptop. Do not: encoding is the expensive part, and doing it twice on a machine already running the service is how streams start dropping frames.

Use a restream service instead. You send one stream to it; it forwards to YouTube, Facebook and anywhere else. Several offer free tiers adequate for a church, and the load on your machine is identical to streaming to one place.

Stream settings that matter

Three settings decide most of your quality, and they are covered properly in improving stream quality:

• Resolution — 1080p if your upload supports it, 720p if it does not. A clean 720p beats a stuttering 1080p every week.
• Bitrate — matched to your actual upload speed, with headroom.
• Encoder — hardware encoding if your machine has it, which frees the processor for everything else.

The run-through that prevents most problems

Do this midweek, not on Sunday morning.

• Stream privately or unlisted for ten minutes, with someone watching on a phone off the church wifi.
• Check the audio is coming from the sound desk, not the camera microphone.
• Check the scripture graphic appears and keys correctly.
• Check the stream survives a scene change.
• Watch the recording back afterwards, with sound.

That last step is the one people skip and the one that finds problems — an audio channel slightly distorted, a graphic sitting outside the safe area, a camera slowly drifting out of focus.

The takeaway

• OBS covers most churches; vMix earns its cost with several cameras.
• Build the fewest scenes you can operate without thinking, and build the safety scene first.
• Multi-platform means a restream service, not a second encoder on the same laptop.
• Do the run-through midweek and watch it back.

Related: Improving stream quality · NDI for churches · Scripture on your live stream