MINISTRY SYSTEMS CO. / ARTICLES

Best OBS Settings for Church Livestreaming

By Ministry Systems Co. ·

OBS Studio gives churches a lot of control.

That is useful.

It is also why churches sometimes end up with settings that are far more complicated than they need to be.

A small church livestream does not need to chase the highest resolution, highest frame rate, or most advanced encoder settings available.

It needs a configuration that works reliably every Sunday.

That should be the goal.

Not maximum quality.

Not maximum complexity.

Reliable quality.

Start With This Principle

The best OBS settings for your church are not the most aggressive settings your computer can run.

They are the settings your:

can handle consistently.

That means a church with a modest computer and stable 1080p30 stream may be in a better position than a church trying to force 4K60 through an unreliable system.

1080p30 Is a Strong Starting Point

For many churches, 1920×1080 at 30 frames per second is a very practical target.

Why?

Because most church services do not contain the kind of rapid motion that requires 60 frames per second.

A sermon, worship team, Scripture reading, prayer, or communion service usually looks perfectly good at 30 fps.

Going to 60 fps can increase:

without adding much value for the average church viewer.

For many small churches:

1080p30 is a strong balance between quality and reliability.

When 720p Still Makes Sense

Not every church needs to stream at 1080p.

A 720p stream can still be perfectly usable if:

A clean, stable 720p stream is better than an unstable 1080p stream.

The viewer usually notices buffering and dropouts much faster than they notice the difference between 720p and 1080p.

Do You Need 4K?

Probably not.

At least not for most small church livestreams.

4K requires more:

It also creates more opportunities for something to fail.

If your congregation is primarily watching on:

1080p is usually more than sufficient.

Do not build your system around 4K just because the cameras support it.

Ask whether it actually improves the ministry goal.

Canvas Resolution vs Output Resolution

OBS has two resolution settings that can confuse new users.

Base Canvas Resolution

This is the workspace OBS uses to build your scenes.

Output Resolution

This is the resolution OBS actually sends to the streaming platform.

For a simple church setup, keeping both at 1920×1080 is often the easiest option.

That avoids unnecessary scaling.

If the computer or internet connection struggles, you may keep the canvas at 1080p while sending a lower output resolution.

But unless there is a reason to do that, simpler is usually better.

Use 30 FPS Unless You Have a Reason for 60

Thirty frames per second is generally enough for:

Sixty frames per second may be useful if:

But 60 fps should not be the default simply because the option exists.

Every increase in frame rate creates more data to encode and send.

Use Hardware Encoding When Available

Modern computers often include dedicated hardware encoders.

Examples include:

OBS documentation describes hardware encoding options where available, which can reduce CPU load. See the OBS Studio overview.

For a church production computer, that can improve stability because OBS is not competing as heavily with other applications for processing resources.

If your computer offers a supported hardware encoder, that is usually a good place to start.

Do Not Change Encoder Settings Just Because You Can

OBS exposes many advanced options.

Most Sunday operators do not need to touch them.

Once your church has a tested encoder configuration, document it and leave it alone. Our OBS for Churches guide covers the volunteer workflow around that configuration.

The Sunday operator should not be experimenting with:

That belongs to the person responsible for configuring and maintaining the system.

Operation and configuration should be treated as two different responsibilities.

Use Constant Bitrate for Streaming

For normal livestreaming, CBR — Constant Bitrate is the standard choice.

YouTube currently lists CBR as its live-stream bitrate mode. See YouTube live encoder settings.

That keeps the outgoing stream predictable and makes it easier for the streaming platform to receive consistently.

What Bitrate Should a Church Use?

This is where churches sometimes get into trouble.

Bitrate determines how much video data OBS tries to send.

Higher bitrate can improve image quality.

But a higher bitrate also requires a stronger, more stable upload connection.

YouTube’s current H.264 live-stream guidance lists these recommended bitrates:

YouTube also recommends testing your actual upload performance and choosing a quality your connection can sustain reliably.

Those are platform recommendations, not commandments.

Your church should choose a bitrate based on:

Do not simply use the highest number available.

Leave Upload Headroom

If your internet connection can upload 12 Mbps under perfect conditions, trying to send a 12 Mbps stream is asking for trouble.

Other devices may also be using the connection.

Bandwidth fluctuates.

Sunday conditions change.

You want margin.

A livestream should not consume everything the church connection can theoretically provide.

That is one reason we recommend testing under real Sunday conditions rather than using a single weekday speed test. See our church livestream internet speed guide for more on upload capacity and headroom.

Keyframe Interval

YouTube currently recommends a 2-second keyframe interval and says not to exceed 4 seconds.

For churches, this is one of those settings that should generally be configured once and then left alone.

Most volunteers never need to think about it.

Audio Settings Matter Too

Video settings receive most of the attention.

But viewers are far more sensitive to bad audio than slightly softer video.

OBS lets you select audio sample rate and streaming bitrate.

The streaming platform ultimately determines what it accepts, but the bigger church-specific issue is simpler:

Make sure OBS is receiving clean soundboard audio.

Do not try to solve bad audio with higher audio bitrate.

If the source mix is poor, the encoding settings will not fix it.

Make sure the livestream has:

Keep Recording Separate From Streaming When Possible

Many churches record the service locally while also streaming.

That is useful.

If the internet fails, you still have a recording.

But recording can add load to the computer.

OBS allows you to configure recording separately from streaming.

If your system supports hardware encoding and has enough resources, this can work well.

But test it thoroughly.

Do not assume that because streaming works, streaming and high-quality local recording will work equally well together.

Watch Storage Space

Local recording can quietly fill a drive.

A church may stream perfectly for months and then discover that OBS cannot record because the SSD is full.

Create a simple routine:

Do not wait for Sunday morning to discover the drive has no space left.

Use OBS Auto-Configuration as a Starting Point

OBS includes an Auto-Configuration Wizard.

It considers your hardware and, for streaming, your network conditions. The OBS quick-start guide recommends it as a starting point for new setups.

That can be very useful when setting up a new church system.

But once you have tested settings that work well, stop changing them unnecessarily.

Stable systems come from repeatability.

A Practical Starting Configuration

For many small churches, a starting configuration might look like:

The bitrate should then be selected based on the streaming platform and the church's actual upload capacity.

This is not a universal prescription.

It is a sensible baseline to test.

Test Before Sunday

Never make major OBS configuration changes immediately before worship.

If you change:

test it during the week.

Run a private or unlisted test stream.

Include:

YouTube specifically recommends testing audio and movement that resemble the actual live event and monitoring stream health during the broadcast.

A five-minute test with an empty sanctuary is better than nothing.

A realistic rehearsal is better.

Do Not Optimize Yourself Into Instability

There is a point where better settings stop producing a better ministry result.

You may spend hours trying to improve:

while introducing more risk into the system.

The viewer usually cares about:

Those three questions should drive the configuration.

Create a Known-Good Configuration

Once your church finds settings that work, document them.

Record:

Then back up the OBS configuration.

The goal is to be able to say:

These are our normal Sunday settings.

That makes troubleshooting much easier.

Protect the Settings From Accidental Changes

Not every volunteer should have permission to redesign the system.

A Level 1 Sunday operator should primarily:

They should not be changing advanced output settings five minutes before worship.

A reliable system has boundaries.

If the Stream Is Unstable, Reduce Complexity

If your system struggles, simplify. If OBS reports network dropped frames, use our dropped frames troubleshooting guide to identify the cause.

Try reducing:

The goal is not to win a technical specification contest.

The goal is to get worship online reliably.

The Best OBS Settings Are the Ones You Can Trust

There is no single perfect OBS configuration for every church.

Different churches have different:

But the guiding principle is the same:

Choose the simplest settings that produce good quality and remain reliable under real Sunday conditions.

That is the philosophy behind Sunday-Proof Livestream from Ministry Systems Co.

Your OBS system should be:

Reliable. Repeatable. Volunteer-Friendly.

← All articles