A house of worship needs very little internet most of the week and a lot of upload for a few hours at a time. Size the plan around the livestream: a steady upload with plenty of room to spare, the streaming encoder on a wired connection, and nothing else competing for that upload during services. Then give guests their own Wi-Fi, separate from the office, giving systems and cameras.
Churches, synagogues, mosques and temples have a usage pattern unlike most organisations. The office runs on a handful of computers on weekdays. Then the building fills, hundreds of phones look for Wi-Fi, and the service goes out live to members at home. When the stream stutters, everyone notices, and the volunteer running it is the one who hears about it. This guide explains how to set things up so that does not happen.
How usage looks across the week
| When | What is happening | What it needs |
|---|---|---|
| Weekdays | Office work, email, accounting, phones, small meetings | Modest bandwidth, reliable phones |
| Main services | Livestream, guest Wi-Fi for a full house, children's check-in, giving | A large, steady upload and Wi-Fi built for crowds |
| Weddings, funerals, special events | Extra streams, visitors who have never been to the building | The same as services, sometimes on a weekday |
| Overnight | Backups, software updates, cameras | Little, unless cameras record to the cloud |
The livestream sets the requirement
Upload, not download
A livestream goes out of the building. A plan that advertises a large download figure with a small upload, as many cable plans do, can look generous and still struggle on a Sunday morning. Read the upload figure on any quote before anything else, and see symmetrical vs asymmetrical internet for why the two numbers differ.
How much upload
Start from your stream settings. A 1080p stream commonly runs somewhere between the mid single digits and around 10 Mbps, depending on frame rate, motion and the encoder; your streaming platform publishes recommended settings for each resolution. A common rule of thumb is to have at least one and a half to two times the stream's bitrate available as steady upload, because internet speeds wobble and a stream that uses every last megabit will buffer for viewers. If you send the same service to several platforms at once directly from the encoder, each one needs its own upload; a relay service that receives one stream and redistributes it avoids that.
Make the stream the priority
- Wire the encoder. Put the streaming computer or hardware encoder on a cable, never on Wi-Fi.
- Give the stream priority. Quality of service on the router, or a separate network for production equipment, keeps guest phones from eating its upload.
- Pause the competition. Schedule office backups, cloud photo syncing and software updates away from service times.
- Record locally as well. If the stream fails, a local recording can be posted afterwards.
- Have a backup path for the stream: a second internet line, or a cellular or bonded cellular device that the encoder can switch to.
- Test before each service, with a private stream a few minutes ahead of time.
Music licensing is separate
One non-technical point. Streaming worship music generally needs its own streaming licence, separate from the licence that covers congregational singing and printed lyrics. Check with your music licensing provider before you go live. This is general information, not legal advice.
Guest Wi-Fi for a full house
The challenge in a sanctuary or hall is capacity, not coverage. A single access point can reach every seat and still fail when several hundred phones try to join at once. A design built for crowds:
- Enough access points for the density, placed for the seating, not just for the walls. Our guide to access points vs mesh explains why mesh kits struggle in large rooms.
- A limit per guest device, so a few people streaming video or updating phones cannot take the upload the livestream needs.
- Content filtering on guest networks, and especially on any network used in children's and youth areas.
- A simple way to join, with a short acceptable-use page and a password that is easy to display on screens or in the bulletin.
Our managed network and Wi-Fi service handles the survey, the access point design, the separation between networks and ongoing monitoring, which suits congregations where the network is otherwise run by whichever volunteer knows the most about computers.
Separate the office, giving and check-in
Guests should never share a network with the systems that hold donor records or take payments. A typical layout:
- Office: staff computers, accounting, donor and membership databases.
- Giving: card readers and giving kiosks, on their own network, using devices approved by your payment provider.
- Children's check-in: check-in stations and label printers, which handle information about minors.
- Production: encoders, cameras, sound and lighting control.
- Building systems: security cameras and door access.
- Guests: internet only.
A business-grade firewall that enforces this separation, with current firmware and two-step sign-in on the office's email and donor systems, covers most of the risk. Our cybersecurity page covers managed firewalls if nobody on staff wants that job.
Phones for the office and pastoral calls
A congregation office needs a main number that reaches the right person, voicemail that goes to email, and a way for urgent pastoral calls to reach whoever is on call after hours. A hosted phone system handles this with schedules and call forwarding to mobile apps, and it keeps working from anywhere if the office is closed.
Volunteers and the handover problem
In many congregations the network was set up by a volunteer, and the knowledge of how it works left when that volunteer moved away. Write it down while it is fresh:
- A one-page diagram of the internet line, the router or firewall, the switches, the access points and the streaming equipment.
- Account details in a shared password manager controlled by the organisation, not a personal phone: the internet provider's account, the firewall, the Wi-Fi system, the streaming platform and the phone system.
- A Sunday checklist for the streaming team: power on, wired connection checked, test stream, backup path ready, recording started.
- Who to call, and the account number to quote, when the line is down on a Saturday night.
This costs nothing but an afternoon, and it turns a crisis into a phone call.
Budget and plan choices
Many congregations do well with shared fiber or a cable plan with a strong upload, plus a modest backup. Shared fiber is often symmetrical, which suits livestreaming, and costs far less than a dedicated circuit. Dedicated internet access makes sense when streaming is central to the ministry, the building is already lit by a carrier, or the facility runs a school or offices with stricter needs. If your building also houses a school, our guide to internet for schools covers the extra requirements.
Two practical points for boards and finance committees. First, quotes usually have an expiry date, so time the request so that a decision can be made within it. Second, check the contract term and what happens at renewal; a plan that rolls onto a higher rate after the first term is common.
A worked example
Hypothetical: the congregation, stream settings and usage are invented to show the sizing method. Use your own encoder settings and attendance.
A congregation of about 400 on a typical weekend streams its main service at 1080p and 6 Mbps to one platform and at 720p and 3 Mbps to a second, directly from the encoder. It has a cable plan with a large download and a 20 Mbps upload.
- Streams: 6 + 3 = 9 Mbps of upload. Applying the rule of thumb of about twice the bitrate, the streams want roughly 18 Mbps of steady upload kept clear.
- Guest Wi-Fi: perhaps 120 phones connect. Most are idle, but photo uploads and video calls in the lobby can easily use several megabits of upload in bursts.
- Office and check-in: light, but a cloud backup set to run at 10am Sunday would collide directly with the service.
A 20 Mbps upload leaves almost no margin, which matches the buffering viewers have been reporting. The options, in order of cost: move the backup to overnight, cap guest devices and use a relay service so only one stream leaves the building; then move to a symmetrical shared fiber plan if one is available at the address, keeping the cable line as a backup, or to a cable tier with a much larger upload. A cellular backup device for the encoder covers the stream if the main line fails mid-service.
Questions to ask your provider
- What is the upload speed, in writing, and is it consistent at weekend peak times?
- Is shared fiber or a symmetrical service available at our address?
- Can a backup line come from a different network?
- Can the Wi-Fi handle several hundred devices in one room, and how would it be laid out?
- Can guests, the office, giving, check-in and production be on separate networks?
- How long is the contract, and what happens to the price at renewal?
- How long is this quote valid, so our board can approve it in time?
Get your building priced
We qualify your address across several Tier 1 carriers, including shared fiber and cable options, and bring back the best offer with the alternatives so your committee can see the market. Carriers pay FiberX, so there is no markup, our lowest-price promise applies, and if your current plan is already the best deal we will say so. Quotes are free with no obligation, Phil Morales is your one point of contact, and you usually hear back the same day. Send us the address, call 478-758-8091 or text (347) 870-0965.
