Most church streams do not fail because of the camera. They fail somewhere between the camera and the viewer: a weak upload connection, a bitrate that is too high, a keyframe setting nobody changed or an audio feed that echoes through the sanctuary.
The good news is that the settings that matter are few, and the platforms publish them. This guide walks through the whole chain, from licensing to the encoder to the viewer's phone, and explains what to set in OBS or vMix to stream to YouTube and Facebook without stuttering.
Key takeaways
- Check your music licence before your first stream. A standard church copyright licence does not automatically cover streaming.
- Your upload speed sets the ceiling. OBS suggests starting with a video bitrate of about 75% of your stable upload speed.
- Use CBR, a keyframe every 2 seconds and the bitrate YouTube lists for your resolution. YouTube's table gives 14 Mbps for 1080p at 30 fps with H.264.
- Send the stream its own audio mix, and never send the stream's audio back into the sanctuary speakers.
The chain, in plain terms
A church live stream is a short chain. Each link can fail on its own.
- Sources: cameras, the slides computer and the audio from the mixer.
- Switcher or capture: the part that chooses what viewers see.
- Encoder: software such as OBS or vMix, or a hardware box, that compresses the picture and sound.
- Network: the upload connection that carries it out.
- Platform: YouTube, Facebook or your own page, which delivers it to viewers.
This article covers links two to five. If you are still choosing cameras, start with the guide to cameras for church livestreaming.
Step 0: Check the music licence
Before anything technical, check what you are allowed to stream.
In the United States, CCLI's base Church Copyright License covers things like projecting lyrics in a service. Streaming is covered by a separate CCLI Streaming License, which permits worship songs performed live by your own musicians in a streamed or uploaded service, as long as the stream is free to viewers. Playing artist recordings, backing tracks or multitracks in the stream needs the Streaming Plus License, and the licence does not cover other copyrighted material, such as video clips.
CCLI also notes that its licence does not override the rules of the platforms, so you may still receive a copyright notice on some of them. Licensing rules differ by country, so check the terms that apply to you.
Step 1: Test your upload speed
Streaming sends data out, so what counts is your upload speed, not your download speed.
- Run a speed test from the network and the location you will stream from.
- Prefer a wired connection. OBS's troubleshooting guide says Wi-Fi may be unstable for streaming and recommends a wired connection.
- Do not share the connection with other heavy traffic during the service.
OBS's guide suggests that a good starting point for your video bitrate is 75% of your total upload speed. That leaves room for audio and for the connection to fluctuate.
Step 2: Choose the resolution and bitrate
More is not better if your upload cannot carry it. YouTube publishes a table for H.264 streams, with a recommended bitrate and a minimum:
| Resolution and frame rate | H.264 recommended | H.264 minimum |
|---|---|---|
| 1080p at 60 fps | 17 Mbps | 6 Mbps |
| 1080p at 30 fps | 14 Mbps | 5 Mbps |
| 720p at 60 fps | 8 Mbps | 3 Mbps |
| 720p at 30 fps | 8 Mbps | 3 Mbps |
For AV1 and H.265, YouTube lists lower figures. For 1080p at 30 fps, it lists 10 Mbps as recommended and 4 Mbps as the minimum.
A simple calculation helps. If you want to send 14 Mbps and keep to the 75% guideline, you need a stable upload of around 19 Mbps. If your upload is lower, choose 720p or a lower bitrate in the range YouTube lists, instead of forcing a high bitrate that your connection cannot hold.
For Facebook, the published limits differ from YouTube's and have changed over the years, so check the requirements shown in Facebook's live tools before you start. The common ground across platforms is H.264 video, AAC audio, constant bitrate and a keyframe at least every two seconds.
Step 3: Set up the encoder
In OBS Studio
- Run the Auto-Configuration Wizard (Tools menu). OBS's quick-start guide describes it as testing your system and suggesting settings for resolution, bitrate and encoder.
- Output mode: Advanced gives you control over the settings below.
- Encoder: a hardware encoder such as NVIDIA's NVENC reduces the load on the processor, if your computer has one. Otherwise use x264 if your processor has capacity.
- Rate control: CBR. Both YouTube and NVIDIA's OBS guide recommend it for streaming.
- Bitrate: the value from your table, not above 75% of upload.
- Keyframe interval: set it to 2 seconds. In OBS the field is 0 (automatic) by default, so enter 2 yourself. YouTube recommends 2 seconds and says not to exceed 4.
- Audio: YouTube recommends AAC at 128 kbps for stereo.
If dropped frames appear in OBS, its troubleshooting guide explains that this indicates a network problem between your computer and the platform's server. Lowering the bitrate is the first fix it suggests.
In vMix
- Use the FFMPEG streaming application, which vMix's documentation calls the recommended option.
- Choose H.264 video and AAC audio.
- Keep the keyframe frequency at 2 seconds, which is the default in vMix.
- Leave the encoder preset on "veryfast", which vMix describes as the best balance between processor use and quality.
- Do not enable NAL CBR for normal RTMP streaming. vMix's documentation says it is not necessary and is mainly useful for diagnosing network problems.
Step 4: Give the stream its own audio mix
The sound in the sanctuary is mixed for a room. The sound online is heard on phones, laptops and headphones. They need different mixes.
- On most digital mixers you can create a separate stream mix on an auxiliary bus or a matrix, and send it to the computer through USB or an audio interface. The house mix stays on the main outputs.
- Keep these paths separate. If the stream's audio is played through the sanctuary speakers, the delay of a round trip over the internet creates an echo.
- Add what online viewers need: a little room or congregation sound, and a stronger lead voice.
- Use a limiter on the stream output so peaks do not clip. One church-production guide suggests keeping the master peak at or below -1 dBTP.
- Check the mix on a phone and on headphones, not only on monitors.
Step 5: Add lyrics and slides
Viewers at home need the words too. You can capture the slides computer as a source, or send them over the network. FreeShow, a free presentation program, can send its outputs to OBS over NDI, including a transparent version with only the text, so lyrics appear over the camera picture. Its documentation recommends an Ethernet connection for this, and NDI output is not supported on Linux.
Step 6: Choose the right latency on YouTube
In YouTube Studio's Live Control Room, under Stream Settings, you can choose the stream latency.
- Normal latency: the best quality, with the least viewer buffering. YouTube recommends it if you do not plan to interact with the audience.
- Low latency: most viewers see less than 10 seconds of delay. Suited to limited interaction.
- Ultra-low latency: most viewers see less than 5 seconds, with a higher chance of buffering.
For a service that people watch rather than join in, normal latency is usually the right choice.
Step 7: Test the way you will stream
YouTube advises testing before you go live, with audio and movement similar to the real event, and monitoring the stream health during the event. In practice, that means running a full rehearsal on the day before, with the worship band playing and the camera moving, and then watching it on a phone over mobile data.
Common problems
| Symptom | Likely cause |
|---|---|
| Frozen picture or disconnections | Network: bitrate too high, Wi-Fi, shared connection |
| Blocky picture during movement | Bitrate too low for the resolution, or a high-motion scene |
| Platform warns about keyframes | Interval not set to 2 seconds |
| Echo in the sanctuary | Stream audio is routed back to the house speakers |
| Muted or flagged audio | Music not covered by the licence or the platform's rules |
Who runs it
A stream is a team effort. It takes someone on camera, someone on audio, someone on slides and someone who starts and watches the stream. The settings above are set once. The harder part week after week is making sure each of those places is filled.
How Planify can help
Planify does not stream or encode anything. It helps you staff the people who do.
- Positions that match your crew. Create positions such as camera, sound, slides and stream operator, each in a department with its own coordinator.
- One-tap confirmation. Volunteers confirm or decline the day before with a tap on WhatsApp, so you know if the stream operator will be there.
- Replacement when someone drops. If a person declines, Planify can ask colleagues who cover the same position.
- Quick gaps. Open slots can go out as an open call to the people on a team or position, and only active members are invited.
- Time away. Unavailable periods are respected when assigning.
Which features you get depends on your plan.
Read next: media team scheduling: why sound, cameras and slides can't be swapped.
FAQ
What do you need to live stream a church service?
A camera or cameras, a computer or hardware encoder, a stable wired internet connection with enough upload speed, audio from your mixer and a platform account such as YouTube or Facebook. Check your music licence too.
What bitrate should a church use for YouTube?
YouTube lists 14 Mbps as the recommended H.264 bitrate for 1080p at 30 fps, with a minimum of 5 Mbps, and 8 Mbps for 720p. Choose a value your upload can hold, using about 75% of upload as a starting guide.
Is OBS or vMix better for church streaming?
Both work. OBS is free, and vMix is a paid product. The right choice depends on your team, budget and how many sources you switch between.
Why does our church stream keep buffering or dropping frames?
Dropped frames usually point to a network problem between your computer and the platform. Use a wired connection, lower the bitrate and avoid sharing the connection during the service.
Do we need a licence to stream worship music?
Usually yes. In the United States, the CCLI Streaming License covers worship songs played live by your musicians, and Streaming Plus covers recordings and multitracks. Rules differ by country, so check what applies to you.