Choosing presentation software when you do not have a media team

“Small church” here is not a spiritual category. It is a process: one person clicking slides, a computer that might go home in someone’s bag, no weekday IT, and a room that still has to sing if the wifi blinks. An 80-seat sanctuary and a 250-seat room with the same volunteer pattern have the same software problem.

This page is a decision frame, not a scorecard. The names and tradeoffs live on the church presentation software map. Read that when you want portraits. Use this when you are trying to avoid buying a booth for a room that does not have a booth.

If you are that one volunteer, the Saturday-to-Sunday habits in running Sunday slides with one volunteer matter more than the logo on the splash screen. If the cable is the weak point, start with church presentation hardware basics before you switch tools.

What “small” means on Sunday

A small team usually has some mix of these:

• One operator, sometimes also running audio or unlocking the building
• Little rehearsal with the actual projector
• A shared or borrowed computer, or a church laptop that lives in a closet and is also used for announcements
• No dedicated media hour on Wednesday
• High cost of a miss — there is no second person to jump to the chorus while you fix a window

Those constraints decide the software. A tool that shines with a trained operator, a locked booth Mac, and a stage display is not “better.” It is built for a different week.

Do not optimize for a future media team you do not have. Optimize for the person who will arrive 45 minutes early this Sunday.

Four criteria that actually matter

The OS you already have

If the church owns a Windows laptop, a Windows-centered tool is not a compromise. It is using the machine you can leave in the room. If the only dependable computers are Chromebooks, a booth-class desktop app will not install, and wishing will not change that. If someone insists on a personal Mac that also goes to work on Monday, you have a custody problem, not a brand problem.

Write down the computer that will stay. Choose software that runs there without a new purchase. Buying a machine later is fine. Pretending you have a booth PC this week is how Sunday starts with “I have to download it again.”

Learning time for one volunteer

The right tool is the one a second person can advance after ten minutes of “current, next, jump, black.” If Sunday depends on the one member who enjoys settings panels, you do not have a system. You have a single point of failure with a vacation calendar.

Count the weekday hours it takes to build one song, one scripture passage, and one announcement loop. If that work requires a course, you will skip it in busy seasons and fall back to a phone screenshot.

What happens when the network drops

Guest wifi in a fellowship hall is not a data center. Phones on the same router will saturate it during announcements. A tool that must reach a server to show the next lyric is a different risk than a tool that opens a local file.

Ask a blunt question: if you unplug the ethernet and disable wifi, can you still run the set you built? “It usually works” is not an answer. Test it on the church computer. Some web-based tools cache a service. Some cloud-first tools assume the network is there. Some local installs are fine until the library lives on a drive that did not come to church.

Offline is not a feature checkbox. It is whether the third song still has words.

Who owns the files

Songs, scripture decks, and last month’s announcement loop should live on a church-owned account or a church-owned folder — not only in one volunteer’s personal login. When that person moves, the library should not move with them.

Ask where a service file lives, how a second person opens it, and what happens if the laptop is replaced. USB copies, shared logins the church controls, or a team library can all work. A personal iCloud of “my church slides” does not.

When a booth-class tool is too much

Production-heavy software earns its keep in rooms with staff, multiple outputs, and a reason to build looks. In a one-volunteer church it often costs you in:

• Setup time (outputs, themes, layers) that no one will maintain
• A learning curve that keeps substitutes from helping
• A dedicated machine you do not have yet
• Features you will not use: live switching across several decks, lyric motion, complex stage layouts

If your actual Sunday is lyrics, a few verses, a welcome loop, and maybe one video, you do not need a console. You need a live view that stays boring and a service you can save.

ProPresenter-shaped tools are a poor fit when the pain is “we have one person and a tired laptop,” not “we need a deeper production surface.” EasyWorship can be a good fit when you already live on Windows and want something familiar; it is a poor fit if you do not have a Windows box and will not buy one. Proclaim-shaped, cloud-first tools can be a good fit when the church already lives in that wider software stack; they are a poor fit if you cannot explain what the room does when the network drops.

Those are shapes, not rankings. Confirm details on the vendor sites. Do not switch because a larger church down the road uses a different logo.

When free software is more expensive

A free license can be the right call. It can also hide the bill in volunteer hours.

FreeShow is a real option for churches that will install it, learn it, and support themselves. The cost is time: updates, “why is this output blank,” and no vendor to call at 8:40 a.m. If one person enjoys that work and documents it, free can be cheap. If no one will own it, you will pay in stalled Sundays.

PowerPoint or Keynote can look free because the church already has them. They are weak at live worship: no service-shaped jump list, easy to mirror the operator view, painful repeats, and a workflow that wants a finished deck instead of a living set. See what “free” actually costs if that is the fork you are on.

Open-source tools exist. They are honest about price and honest about support: you are the support. That is fine when you have a patient volunteer. It is not “free” if that volunteer is also the preacher.

A web-based option

WorshipDeck is web-based church presentation software aimed at smaller teams and browsers, including Chromebooks. It has no free tier. It is a poor fit if what you actually want is a deep, booth-native production surface as the main way you run Sunday.

Treat it as one shape among others: browser, shared library, HDMI still from a laptop. Compare it with the same questions — OS on hand, one-volunteer live view, offline behavior, who owns the files — not as a default winner. The tools roundup is the map.

A short decision path

Work this in order. Stop when the answer is clear.

1. Which computer stays in the building? Write the OS. Cross off anything that will not run there.
2. Who clicks next Sunday, and who might click the Sunday after? If the answer is “only Jordan,” prioritize a live view a substitute can learn.
3. Unplug the network and run last week’s service. If you cannot, you do not have a Sunday plan.
4. Where do the files live if Jordan is out of town? If you cannot open the set, the software is incidental.
5. What do you actually put on screen? Lyrics, scripture, a loop, one video. If that is the list, ignore feature tours for LED walls you do not own.
6. What is the year-two cost shape? Subscription, one-time license, or free with self-support. Confirm on the vendor site. Do not pick from a remembered sale price.

Then run a 30-minute test on the church computer: one song, one passage, one video, real projector, a second person hitting next. That test beats a week of tab-comparing.

When not to switch

If the words already arrive on time and the pain is training or a loose HDMI cable, new software will not help. Switching has a cost: rebuilt songs, new habits, a Sunday where muscle memory is wrong.

Stay if the room is calm and the complaints are taste (theme, motion, “it looks dated”). Change if you cannot run the computer you have, cannot survive a network drop, or cannot hand the service to anyone else. The software should match one volunteer, the machines already in the closet, and a room that still works when the internet does not.