How to start a church radio station

A church radio station is an internet station that carries your services, teaching, worship music and notices around the clock — it takes an afternoon to put on air and needs no transmitter and no studio. The hard parts are not technical: they are what you air the other 165 hours of the week, what you must not broadcast from a service, and which worship-music permissions you actually hold. This guide is about those.

1. The job the station is really doing

A congregation is together for two or three hours a week and apart for the rest. Everything a church does to close that gap — the newsletter nobody opens, the WhatsApp group that goes quiet, the sermon podcast with eleven downloads — is trying to solve the same problem. A station solves it differently: it is already playing. Nobody has to decide to engage with it. They turn on the kitchen speaker and the church is there.

Three groups get more from it than anyone, and they are the three most likely to drift away without it:

• The housebound. Illness, age, a new baby, no transport. For them a live-and-repeated service is not a nice extra — it is the only way to be in the room.
• The travelling. Long-haul drivers, offshore and rota workers, students in another city, anyone whose job eats Sundays. A repeat at 7pm catches people a 10am service never will.
• The diaspora. People who left the town but not the community. They will not join a video call at your local time. They will absolutely leave a station on in the background at theirs.

Notice that none of that is about reach in the marketing sense. Judge the station by whether the people who already belong to you stay connected, not by chasing strangers. That reframe changes almost every decision that follows — especially the programming.

2. What a church station actually airs across a week

The most common failure is a station that carries the Sunday service and then plays a shuffled folder of worship albums for six days. It sounds like a screensaver. A week that works looks more like this — and almost all of it runs unattended once it is built:

Repeating the service is correct, not lazy

New broadcasters feel embarrassed about repeats. Commercial radio does not — every talk network on earth reruns its best hour overnight, because the audience at 2am is a different audience. Your service is the single best hour of content your church produces all week, and it took a building full of people to make it. Airing it once is the waste.

A workable rule: the service airs live, then repeats twice on Sunday, then once mid-week, and the last four Sundays stay in rotation as a Sunday-night archive slot. Build that once in the schedule and shows grid and it repeats every week without anyone touching it. Between the scheduled blocks, Cloud AutoDJ fills with the right music category for the hour, so the station never falls silent when a volunteer is on holiday.

3. Streaming the Sunday service without it sounding like a phone in a pew

The audio path is short and there is one decision in it that matters more than everything else combined: take a feed from the mixing desk, not a microphone in the room.

A room mic picks up the air conditioning, the person unwrapping a sweet, the reverb of a hard-surfaced hall, and a preacher who is thirty feet away and off-axis. The desk already has a clean, close signal from every microphone and instrument that is plugged into it. On a stream, that difference is not subtle — it is the difference between people listening and people leaving.

The path, end to end

• A dedicated output on the desk — a post-fade aux send, a matrix out, or the record/monitor bus. Not the main output feeding the speakers, because you need to mix the broadcast independently.
• A line-level cable into a USB audio interface, or straight into the interface if your desk has USB out. Use a line input, not a mic input, or you will clip everything.
• A laptop or the desk’s USB connection, running either go-live from the browser or any Icecast-compatible encoder such as BUTT, OBS or Mixxx.
• Headphones on the operator, monitoring the broadcast feed — not the room. If nobody is listening to what goes out, nobody knows when it breaks.

The thing nobody warns you about: the room mix is the wrong mix. Anything loud in the air is turned down at the desk, because the room is already hearing it acoustically. So the drums, the acoustic guitar, the piano and — crucially — the congregation singing are all missing or tiny in the desk feed. A stream of the room mix sounds like a lead vocal in a vacuum.

Fix it with two additions. Push the acoustic sources up in your broadcast send until they sit naturally. Then hang a pair of ambience mics at the back of the room, mixed low — low enough that you would not say you can hear them, high enough that turning them off makes the stream feel empty. That pair is what makes a broadcast sound like a full church rather than a lecture.

The parts of a service you should not broadcast

This is where church broadcasting differs from every other kind, and where most of the real harm gets done. A service is a room where people say private things to people they trust. A stream turns that room into a public place, permanently and searchably.

Make the cut mechanical, not judgement-based. Agree one hand signal from the front that means *we are off air now*. The operator ends the live broadcast, the station falls back to the instrumental playlist already loaded in AutoDJ, and it comes back when the signal is given again. Practise it once in an empty building. Rehearsed, it takes four seconds; improvised, it takes forty and everyone hears the forty.

4. Worship music is copyrighted like any other music

The most expensive assumption in church broadcasting is that worship music is somehow exempt. It is not. A worship album is a commercial recording of a commercial composition, owned by a label and a publisher who license it exactly the way any other label and publisher do.

Two distinctions trip up nearly every church, and they are worth reading twice:

• A licence to sing a song in the building is not a licence to broadcast it. Many churches hold a copyright licence that covers reproducing lyrics and performing songs in worship. In several countries — the US religious-service provision is the well-known example — there is also a specific carve-out for performances during a service *at the place of worship*. Transmission to the public generally sits outside it. The moment you stream, you have left the room the exemption describes.
• Playing a recording and streaming your own congregation singing are two different permissions. Airing a commercial track engages the rights in the *recording* and in the *song*. Broadcasting your worship band playing that same song engages the rights in the song only — but it is still a public performance and often still a separate streaming licence. Holding one does not give you the other.

Where to go: your national collecting societies for performance and recording rights, plus the worship-specific licensing bodies that exist precisely for churches — organisations issuing church copyright and streaming licences, and the bodies that license liturgical and hymn repertoire. Ask them directly for a licence that names *webcasting* or *streaming*, not just congregational use. They deal with this question daily and will not be surprised by it.

One practical relief: a large share of a church station’s output is material you already own or hold the rights to — your own preaching, your own readings, your own recorded worship where the songs are covered, public-domain hymns, and anything a member of your congregation wrote and is happy to give you. Nobex keeps automated playout inside the statutory playout rules, but we do not supply licences and we do not give legal advice. The societies’ own answers are the ones that count.

5. Running it on volunteers without burning them out

Church stations do not fail from bad audio. They fail in month five, when the one person who knew how everything worked went on holiday. Design against that from day one.

• Two people per Sunday, always. One operator, one shadow. The shadow becomes an operator in about three weeks, and you get a rota that survives illness instead of a single point of failure with a hobby.
• Batch the midweek content. Do not record a devotional every morning — nobody sustains that past February. Book one two-hour session a month and record four or five segments back to back, then schedule them out. One session buys a month of weekday programming.
• A one-page runbook, printed and taped to the desk. Which input, which fader, how to go live, how to stop, who to call. Not a document in a folder someone has to be granted access to.
• Separate logins for every volunteer — never a shared password. When the rota changes, you remove one account instead of changing a password everyone has written down. See teams and DJ accounts.

That last one is not bureaucracy. A shared account means you cannot tell who took the station off air on Sunday, you cannot revoke access from a volunteer who has moved on, and the password ends up in a group chat. Individual accounts also mean each presenter can prepare their own show without being able to touch billing or the rest of the station.

6. Giving and support, handled with care

A station costs something to run: hosting, a licence, a microphone, occasionally a cable. Most churches want to cover that without turning the station into a fundraising channel, and that instinct is right — a station that asks constantly gets switched off.

Two restrained options. First, link the church’s existing giving page from the station’s public page and player, with no on-air appeal at all. People who want to give already know how; the link just removes a step. Second, Nobex includes tips and memberships on every plan, with Stripe and PayPal payouts, so listeners can support the station directly. Frame that as covering the media team’s costs — hosting, licensing, kit — rather than as giving to the church, and say it once a week at most, in one sentence, in the notices. The full picture is in the monetization overview.

Sponsor spots exist too and some churches use them for local businesses that already support the church. Be deliberate: a sponsor read is an endorsement from a pulpit, and your congregation will hear it that way whether you meant it or not.

7. Reaching the congregation where they actually are

The average church member will not visit a website to listen. They will use three things, and you should test all three before you announce the station:

• The smart speaker in the kitchen. For an older or housebound listener this is the single most important surface you have, because it needs no screen, no app and no password — just the station name said out loud. Getting listed is free and the walkthrough is in get your station on Alexa.
• The phone. Your public station page works in any mobile browser, and the embeddable player drops straight into the church website so the station lives where people already look for service times.
• The car. Phone plus Bluetooth or CarPlay covers it. This is where the 7pm repeat and the school-run children’s slot actually get heard.

Directory listings (Alexa, TuneIn and the rest) are also how the diaspora finds you without being told a URL. Getting your station on every device covers the whole set. When you announce the station from the front, give people one instruction — usually the smart-speaker phrase — not a list of six. Six options produce zero listeners.

8. Your first service on air

Concretely, from nothing to a live Sunday. Do steps 1 to 6 on a weekday and step 7 to 9 on the day.

1. 1Create the station. Every new Nobex account starts in free test mode with a real station on air and no card required — sign up at /register and name the station after the church, not after the technology.
2. 2Upload a starting library: your recorded worship, public-domain hymns, instrumental beds, and anything you hold the rights to. MP3, WAV, FLAC, M4A and OGG all work.
3. 3Build one instrumental playlist and set it as the fallback. This is what the station plays when nobody is live, and what you cut to when a service goes private.
4. 4Sort out the licensing question in parallel — email your national society and your worship licensing body and ask specifically about streaming. It takes days, not minutes, so start it before you need it.
5. 5Wire the desk: dedicated output, line-level into an interface, laptop on the sound desk. Test on a weekday evening with someone talking in the room, listening back on a phone somewhere else in the building.
6. 6Build the weekly grid from the table in section 2 — service, repeats, music blocks, prayer slot, overnight quiet. Do it once; it runs every week.
7. 7On the day, go live from the browser or your encoder ten minutes before the service starts, over the music bed. Confirm you can hear the broadcast in headphones before the first word.
8. 8Run the service. Watch for the hand signal, cut to the bed for anything private, come back after.
9. 9Stop the broadcast at the end and check the recording. Schedule the afternoon and evening repeats, then tell the church it exists — from the front, with one instruction.

Two more things worth doing in week one: tell the congregation the station is running so nobody is surprised to hear themselves, and ask one housebound member to listen and phone in what they thought. Their feedback is worth more than any analytics dashboard, though the listener stats will tell you which slots are working.

9. Church radio questions, answered