Online Worship — FAQs

Short answer: Yes — and which licence depends on the platform.

For YouTube and Facebook Live, you need a CCLI Streaming Licence (those platforms have a pre-existing agreement with PRS for Music, so a separate PRS licence is not required).

For Zoom, Microsoft Teams, your own church website, or any other platform that does not have a pre-agreed PRS arrangement, you need both a CCLI Streaming Licence and a PRS Digital Music Licence for Worship.

This is the single most misunderstood point in church streaming. Around 41% of Methodist churches surveyed in March 2026 use Zoom — many may be unaware that Zoom requires the additional PRS licence.

→ Full detail in the Copyright Guide, Part 2.

Short answer: Yes, with the right licences. Music does not need to be the first thing cut from your stream.

Most hymns sung in Methodist worship are covered by the CCLI Streaming Licence (and PRS Digital Music Licence for Worship where the platform requires it). The licences cover live performance of hymns by your congregation, music group or organist — i.e. people in your building singing and playing.

What the licences do not cover is using pre-recorded commercial recordings (a YouTube backing track, a Spotify playlist, a track from a worship CD) within a streamed service. That generally requires additional permissions or rights that most churches will not hold.

The practical upshot: live music is fine, recorded music is risky. If your congregation sings, your organist plays, or your worship band performs, you are almost certainly covered.

→ Full detail in the Copyright Guide, Part 3.

Short answer: YouTube uses an automated system called Content ID that does not see your CCLI licence. Even legitimately licensed streams can get flagged. There is a dispute process.

YouTube's Content ID compares the audio in your stream against a vast database of registered recordings. If it spots a match — and it will, even for hymns played by your local organist — it can flag, mute or pull down the stream automatically. CCLI does not currently have a way to register your licence with YouTube, so you have to dispute claims after the fact.

What to do:

1. Don't panic — a Content ID claim is not the same as a copyright strike, and does not affect your channel's standing.
2. Dispute the claim through YouTube's dispute interface, citing your CCLI Streaming Licence and the live performance.
3. Keep records — copies of your CCLI licence, the date the claim was made, the song flagged, and the outcome. A small log of repeat offenders is useful.
4. Consider streaming the same service to a second platform (a backup unlisted YouTube stream, your own website, or Facebook) so a Content ID hold on one platform does not lose the whole service.

This is a structural gap between licensing bodies and platform automation, not a problem with your licence. The Centralised Licensing Briefing (D3) explores whether the Connexion can negotiate a verification mechanism with CCLI and YouTube.

→ Full guidance and dispute templates in the Copyright Guide, Part 5.

Short answer: Usually not, unless you hold the additional permissions or a Church Video Licence.

The CCLI Streaming Licence covers live performance, not the use of commercial recordings within your stream. If you want to play a recorded track and stream the service, you generally need either explicit permission from the rights holders, or a different licence (such as the Church Video Licence for film clips, or specific permissions for the recording itself).

The simplest workaround: arrange a live performance, even if it is just one musician playing along to the words on screen.

→ See the Copyright Guide, Part 3 scenario "We play a worship CD during our streamed service".

Short answer: Mostly yes for Singing the Faith (under CCLI), all of Methodist Worship Book original Methodist content (under a TMCP waiver), and all of the Prayer Handbook. The detail matters.

• Singing the Faith (StF): Methodist-original hymns are covered for streaming under CCLI; some third-party hymns within StF have specific restrictions. The Hatfield Road list (lyrics-only) is the best current reference; D2 will extend this to tune copyright.
• Methodist Worship Book (MWB): Methodist original content is covered by a TMCP waiver and free to stream. Third-party MWB content (some readings, prayers, music) has specific permissions which are normally low risk but should be checked.
• Prayer Handbook: All TMCP-owned, free to stream.
• Bible translations: Depends on translation. NRSVA, NRSVue, NIV, CEB, GNT and others all have specific terms — generally fine for spoken reading in worship, but not always for on-screen display.

→ See the Copyright Guide, Part 4 for the full table.

Short answer: You probably need fewer than you think — and the Connexion is investigating bulk arrangements.

Most Methodist churches need only the CCLI Church Copyright Licence and the CCLI Streaming Licence to cover Sunday worship streamed to YouTube or Facebook. Combined cost is typically £100–£300 per year depending on church size — comparable to other annual operating costs.

If you stream to Zoom, Teams or your own website you will additionally need the PRS Digital Music Licence for Worship.

If cost is genuinely prohibitive:

• Consider whether YouTube or Facebook (CCLI Streaming only) is sufficient — it is for the majority of Methodist churches.
• Stream spoken-word services only as an interim step (no licences required for the spoken liturgy and Bible readings).

→ See the Copyright Guide, Part 3 scenario "We want to stream but we can't afford all these licences".

Short answer: YouTube for reach and discoverability; Zoom or Teams for two-way interaction; Facebook if your congregation already lives there.

There is no single right answer. Most Methodist churches start on YouTube or Facebook because they are free, familiar and need only one licence. Churches that want online viewers to be visible to one another — for example midweek prayer groups, bible studies, or an online congregation that gathers as well as watches — choose Zoom or Teams.

Many churches use more than one platform: YouTube for Sunday worship (public, archived), Zoom for midweek interactive groups, Teams for committee meetings. That is fine — just hold the right licence for each.

→ Full comparison in Platform Comparison.

No. A smartphone on a tripod with a clip-on microphone produces a perfectly serviceable stream.

The How-To Guides describe three tiers:

• Tier 1 (Simple, £45–£140 + an existing device): smartphone or tablet, tripod, clip-on lavalier microphone. Suitable for most churches as a starting point.
• Tier 2 (Intermediate, £200–£500 + an existing laptop): webcam, USB audio interface taking a feed from the church PA, OBS or StreamYard. The audio jump is the big win.
• Tier 3 (Advanced, £3,000–£10,000+): multi-camera, sound desk, dedicated streaming PC. Suitable for churches with a trained AV team.

Most churches stay at Tier 1 or Tier 2 indefinitely and serve their online congregation well. A steady, audible Tier 1 stream beats an ambitious Tier 3 setup that nobody can run.

Short answer: Stop using the room microphone. Take a feed from your church PA system into the streaming device.

The single biggest audio improvement is not buying a better microphone — it is plugging the streaming device directly into the existing PA mixer (the one your speaker microphones already feed into). The stream then hears exactly what the PA hears, properly balanced.

Practical route:

• Most church mixers have an unused output labelled AUX OUT, REC OUT or MAIN OUT.
• A simple USB audio interface (£80–£150) takes that signal into a laptop.
• If you are streaming from a phone at Tier 1, a clip-on lavalier microphone on the speaker is the next-best step.

→ See the audio walk-through in Tier 2.

Short answer: Wired ethernet beats Wi-Fi. Test your upload speed. Have a 4G/5G fallback.

Three checks, in order:

1. Test upload speed. Run speedtest.net from where the streaming device sits. Aim for 5 Mbps upload minimum for a standard stream, 10 Mbps for HD.
2. Switch to wired ethernet. Wi-Fi in church buildings (thick walls, distance from the router) is often the weak link. A £30 powerline adapter or a one-off cable run will solve most reliability problems.
3. Have a fallback. Use a phone as a 4G/5G hotspot. If the church broadband fails mid-service, you can switch over without rebuilding the stream.

If all three fail, your broadband itself may need upgrading — talk to your provider about business-grade or fibre-to-the-premises options.

Short answer: No. You need to be transparent about what is being recorded, provide a no-camera area, and obtain specific consent for identifiable individuals where appropriate.

Practical approach:

• Tell people clearly before the service that it is being streamed — verbal announcement plus visible signage at the entrance.
• Designate a no-camera zone (often the back rows or one side of the building) where people can sit if they do not want to be on the stream. Frame your camera so this zone is genuinely off-camera.
• Get specific written consent for people who will be visibly and identifiably on camera — preachers, worship leaders, soloists, children featured in a children's address.

You do not need a signed form from every person who walks in.

→ Full guidance and templates (privacy notice, consent form, verbal announcement script) in the Recording Consent and Accessibility Guide.

Short answer: Yes. Always, before the service. Sermons are protected by copyright and performers' rights, and many preachers have legitimate reasons not to be streamed.

This is a recurring concern in district listening — preachers feeling unable to decline mid-service because it would disrupt the atmosphere. The fix is procedural, not personal: ask in advance, every time, as part of the standing arrangement when booking a preacher. Make "happy to be streamed?" a tick-box on the service plan.

A preacher who says no is not being awkward — they may have safeguarding concerns, may not own the copyright in their material (a guest preacher using bought-in resources), or may simply want to think aloud in a sermon without it being permanently archived.

→ See Recording Consent and Accessibility Guide, local preachers and worship leaders.

Short answer: Higher bar. Children should generally not be identifiable on stream without explicit parental consent, and many churches choose not to film children at all.

Practical approach:

• Frame the camera to exclude pews where children sit (or designate a "children's area" out of frame).
• For children's addresses or activities you want to stream, get specific written parental consent — and if a child is visibly distressed or reluctant on the day, do not film them regardless.
• For streamed Sunday school or children's groups, default to audio-only or a fixed shot that excludes children's faces.

Methodist Safeguarding requirements apply to online activity as much as in-person activity. If children participate regularly in your streamed services, check with your circuit safeguarding officer that DBS arrangements are correct.

→ See Recording Consent and Accessibility Guide, children and vulnerable adults.

Short answer: Yes. They are an accessibility win for everyone and required by good practice for any public-facing service.

Options, easiest to most polished:

• YouTube auto-captions: turned on by default for live streams; not perfect but serviceable. Good enough as a starting point.
• YouTube edited captions: after the live stream ends, you can correct the auto-caption file — a 10-minute volunteer job for a 1-hour service.
• Live human captioner: for special services or where accuracy is critical (BSL services, deaf-led congregations), a paid professional captioner is the gold standard.

Facebook Live does not auto-caption live streams (only uploaded videos), which is one practical reason many Methodist churches default to YouTube for accessibility-conscious streaming.

→ See Recording Consent and Accessibility Guide, captions and subtitles.

Short answer: As long as is useful for your community, with a clear retention policy. Two to three years is a common default.

The legal position is that you can keep recordings indefinitely, provided your privacy notice and consent arrangements made that clear. The pastoral position is more nuanced — people in the recording may move on, change roles, or change their mind about being on a public archive.

A reasonable default policy:

• Sunday services: keep public on YouTube for 2–3 years, then unlist or delete.
• Special services (weddings, funerals, baptisms, anniversaries): keep available privately for the family and named participants; do not leave on a public archive.
• Mid-week study groups, prayer groups: delete shortly after, or do not record at all.

Document whatever policy you adopt and stick to it. Honour requests from individuals who ask to be removed from a recording, even if the request comes years later.

→ See Recording Consent and Accessibility Guide, how long to keep recordings.

Short answer: This is the single biggest risk in church streaming. Cross-train, document, and design for two operators wherever possible.

Around 29% of Methodist churches surveyed in March 2026 named volunteer recruitment and resilience as their biggest challenge — bigger than copyright, bigger than equipment. Several churches described single points of failure.

Practical steps:

1. Document the setup. Write down the boot-up steps, the camera positions, the streaming software settings. Photograph the cabling. A volunteer should be able to run a service from your notes alone, the first time.
2. Cross-train at least one second person. Even if they only run the stream for a fortnight a year while the lead is on holiday, they need to have done it.
3. Match your tier to your team. If you have one reliable volunteer, Tier 2 is your ceiling — Tier 3 needs three trained operators. Buying Tier 3 kit and running it like Tier 2 produces a worse stream than staying at Tier 2 deliberately.
4. Recruit before you upgrade. New equipment without new volunteers is a step backwards.

Short answer: Rotate roles, share the load, and treat the streaming team as ministry, not technical support.

Practical patterns from Methodist churches that have kept streaming sustainable:

• Two-person rota minimum: one operator, one online host (welcoming people in chat). Reduces the load on either role.
• Service of the month: rotate "complex" services (communion, baptism, festival) so one volunteer does not always carry the hardest weeks.
• Quarterly review: sit down with the streaming team, ask what is working and what is not. Often it is something small (the volunteer rota clashing with a school run) that nobody has flagged.
• Training as a gift, not an obligation: find or fund external training opportunities — the Church of England Digital Labs run free webinars, the URC's "Getting your church online" series is good.
• Recognise the role. Mention the streaming team alongside other servers, stewards, musicians and readers. Online ministry is ministry.

Short answer: Yes, this is a growing pattern — particularly where preachers are scarce — but it needs careful thought on licensing and consent.

The March 2026 survey surfaced several circuits already doing this:

• Nidd Valley Circuit runs daily morning prayer on Facebook live.
• Several circuits use streaming kit to feed into Zoom for circuit and district meetings as well as Sunday worship.
• Some circuits stream a single service across multiple chapels where preachers are unavailable.

Considerations:

• Licensing: the licences are held per-church (or per-organisation), not per-stream. Check that the church physically hosting the stream holds the right licences, and that any chapel receiving the stream has appropriate display rights if it is shown on a screen in another building.
• Consent: each chapel feeding into a circuit stream needs its own consent arrangements — privacy notices, no-camera zones, preacher consent.
• Pastoral care: a circuit-wide service is convenient but homogenises. Hold space for local distinctiveness — local notices, local prayers, local choir slots.

→ Add this to your circuit's mission planning conversations rather than treating it as a purely technical decision.

Short answer: Probably not. Look at who is watching before you look at how many.

Streaming view counts are usually low compared with in-person congregations and that is normal. Methodist churches surveyed in March 2026 commonly reported regular weekly figures of 20–80 viewers, with one church reporting a steady 40–50 viewers a week over five years of continuous streaming.

Before stopping, check:

• Who is watching? A stream watched by ten housebound members of your congregation, or three families exploring church for the first time, is not "no one".
• Are you inviting people? The first of the nine practical shifts in Part 1 of the How to guide is "invite people". More people watch online when you tell them about it.
• Are you welcoming them? A stream with no on-screen acknowledgement, no online steward in the chat, and no sense that anyone in the building knows the online viewers are there will not grow.

The mission opportunity is real, but it is not automatic. The missional half of the How to guide covers how to make a livestream work for the people watching.

Short answer: Make it easy to opt in to further contact, never required. Consider running explorers' courses or newcomer-friendly bible studies online.

Some practical patterns:

• A simple end-of-service slide with one URL or QR code: "If you'd like to know more, drop us a line at...". Not a sales pitch.
• A welcome email for first-time online viewers who get in touch — short, warm, signposting one or two upcoming events that might suit them.
• An online explorers' course, run on Zoom, for people who have been watching for a while and are starting to ask questions. Several Methodist churches run these and find the online format reaches people who would not yet step into a building.
• Pastoral contact for known online viewers — particularly those who cannot attend in person — that mirrors what the in-person congregation receives.

The GDPR consideration is straightforward: people opt in to further contact, you keep clear records of consent, and you make it easy to unsubscribe.

→ See charitable purposes soft opt-in for the route opened by the Data (Use and Access) Act 2025.