What OBS plugins does a church actually need?

Usually one: the NDI plugin, which lets graphics and video arrive from another application or computer over the network. Beyond that, add a plugin only when you have a specific problem it solves — audio monitoring, scene automation or captions being the common ones.

Do OBS plugins break when OBS updates?

Frequently, yes. Plugins are built against a particular OBS version and an update can stop them loading, usually silently. This is the main argument for installing as few as possible and for not updating OBS the week before a big service.

Is the NDI plugin safe to install?

The community NDI plugin, currently maintained by DistroAV, is widely used and actively maintained. Install it from its official releases rather than a mirror, match the build to your OBS version, and close OBS before installing.

How do I know a plugin loaded correctly?

Its feature appears where it should — an NDI Source in the source list, for example. If the option is missing, the plugin did not load, whatever the installer said. That is almost always a version mismatch.

Streaming

Free OBS plugins worth installing for church streaming

By Mambo Mutinda · Founder & CEO, TajiCast

2 September 2026 · Updated 8 September 2026

OBS does most of what a church service needs on its own. The plugin ecosystem is large, most of it is built for gaming, and each addition is one more thing that can quietly stop working after an update. This is the short list that earns its place, and the reasoning for keeping it short.

The rule before the list

Install a plugin to solve a problem you actually have.

Every plugin is compiled against a particular OBS version. When OBS updates, a plugin can stop loading — usually with no error, just a missing feature discovered on a Sunday morning. A church with two plugins has a far more predictable setup than one with nine.

Do not update OBS in the week before Christmas, Easter, or any service you cannot afford to have go wrong. Update afterwards, and test the plugins before the next Sunday.

NDI — the one most churches need

What it solves: getting video and graphics into OBS from another application or another computer, over the network, with no capture card.

For a church that means scripture graphics, lyrics, or a second machine's output arriving as a selectable source. It is the difference between buying capture hardware and plugging in a network cable.

Notes on installing it: close OBS first, match the build to your OBS version exactly, and expect "NDI Source" to appear in the source list afterwards. If it does not, the plugin did not load.

Full setup, for OBS and vMix, is in NDI for churches.

ImageScreenshot: the OBS source menu open with 'NDI Source' visible in the list, confirming the plugin loaded

The confirmation that a plugin actually loaded: its feature is there.

Audio monitoring and routing

What it solves: hearing exactly what the stream hears, and sending different audio to the stream than to the room.

OBS's built-in monitoring is adequate for most churches. Where a plugin helps is when you need independent control of several audio destinations — for example a stream mix separate from what is being recorded.

Worth it if: your audio setup is genuinely complex. Skip if: you take a single feed from the desk, which is most churches and is the arrangement recommended in connecting a mixer.

Automatic scene switching

What it solves: changing scene without a person clicking, based on a trigger — a window opening, a timer, an external signal.

Where it genuinely helps a church: switching to a holding scene automatically at the end of a stream, or bringing up a countdown before a service begins without someone watching the clock.

Where it hurts: anything reacting to what happens in the room. A scene that changes on its own during a sermon is unnerving for the operator and worse for the viewer. Automation is right for predictable transitions, not for live judgement.

Captions

What it solves: live text for deaf and hard-of-hearing viewers.

Several plugins produce automatic captions from the audio. They work, with the usual caveats: errors, a short delay, and a public failure mode.

Most churches are better served by captioning the recording, where mistakes can be corrected before anyone sees them — see accessibility. Live captions are worth the trouble when you have members who need them in the room, in which case the imperfection is a small price.

Stability and monitoring

What it solves: knowing the stream is healthy without watching it constantly.

Plugins exist that watch for dropped frames, disconnections and encoder overload, and can reconnect or alert you. Worth considering if your connection is unreliable and one person is running everything.

OBS's own statistics panel — dropped frames, bitrate, encoding load — already tells you most of it, and checking it at the end of every service is a better habit than any plugin.

ImageScreenshot: the OBS statistics dock showing dropped frames, bitrate and CPU during a service

Built in, and enough for most churches.

What to skip

Anything for gaming. A large share of the ecosystem exists for streamers with alerts, overlays and chat integrations. None of it serves a church service.
Chat and alert overlays. On-screen notifications during a sermon are the opposite of what you want.
Filters you will not tune. Video filters that need adjustment per lighting condition become one more thing to get wrong.
Anything unmaintained. Check the last release date. An abandoned plugin will break at the next OBS update and stay broken.

Installing safely

Close OBSPlugins register at start-up; installing while OBS runs is the most common reason one fails to load.
Match the versionDownload the build for your exact OBS version and operating system.
Get it from the sourceThe project's own releases page, not a mirror or a video description link.
Verify it loadedLook for the feature it adds. Missing means it did not load, whatever the installer reported.
Test before SundayMidweek, with a short private stream.

The takeaway

NDI is the plugin most churches genuinely need; it removes capture hardware from the setup.
Everything else should answer a problem you already have.
Plugins break on OBS updates, quietly. Fewer plugins means more predictable Sundays.

Send scripture into OBS over NDI, with no capture card. Free.

Download TajiCast, free

Frequently asked questions

What OBS plugins does a church actually need?: Usually one: the NDI plugin, which lets graphics and video arrive from another application or computer over the network. Beyond that, add a plugin only when you have a specific problem it solves — audio monitoring, scene automation or captions being the common ones.
Do OBS plugins break when OBS updates?: Frequently, yes. Plugins are built against a particular OBS version and an update can stop them loading, usually silently. This is the main argument for installing as few as possible and for not updating OBS the week before a big service.
Is the NDI plugin safe to install?: The community NDI plugin, currently maintained by DistroAV, is widely used and actively maintained. Install it from its official releases rather than a mirror, match the build to your OBS version, and close OBS before installing.
How do I know a plugin loaded correctly?: Its feature appears where it should — an NDI Source in the source list, for example. If the option is missing, the plugin did not load, whatever the installer said. That is almost always a version mismatch.

Keep reading