Running church slides from a browser

Web-based church presentation software runs in a browser. You open a tab, load a service, and send HDMI to the projector the same way you would from any laptop. What changes is not the cable. What changes is where the library lives, who can prep during the week, and what kind of failure you should plan for.

This is a category page, not a versus page. Local-install tools are not worse. They carry a different risk: the booth PC is solid and the laptop with the only copy of the set is at a lake house. Browsers carry the opposite risk: the machine is in the room and the tab cannot reach the service. For the full field, start with church presentation software. For Chromebooks as hardware, see church presentations on a Chromebook.

Why churches ask for a browser

The request usually comes from the building, not from a trend.

Chromebooks. Many churches already have them for the office, the youth room, or a donated cart. Booth-class desktop apps will not install. A browser is the path that exists.

No install rights. The only Windows machine is locked by a volunteer’s workplace image, or the church laptop is so locked down that “run this installer” is a dead end. A browser sidesteps that, for better and worse.

Shared prep. The worship leader can build songs from home. A second person can add scripture without sitting at the booth PC. A team library means the service is not trapped in one user profile on one disk.

One machine that travels. A staff pastor preps on a kitchen table Thursday and presents from the same login Sunday. That is convenient. It is also how you discover that home wifi and sanctuary wifi are not the same network.

None of those reasons make a browser “modern” in a way you should brag about. They are constraints. Match the tool to the constraint.

What stays the same

The Sunday job does not change. You still need lyrics the band will actually sing, scripture the preacher will actually read, a live view with current and next, and a house picture that is not the operator desktop. HDMI still matters. Sleep settings still matter. A clicker still has to talk to the machine that is presenting.

If you skip those, a web app will fail in the same ways a desktop app fails, plus one: the tab. Read how church presentation software works if you need the building blocks before you pick a delivery method.

Offline and degraded mode

Ask every web-based or cloud-first tool a set of boring questions, then test the answers on the church computer:

• After the service is built, can you present with wifi off?
• If the answer is “it caches,” how do you know the cache is current? Who opens the service once on Saturday so Sunday is local?
• What does the operator see if the network dies during song two — last slide frozen, a login wall, or a usable next button?
• Does scripture insert need the network at click time, or only when you built the passage?
• Do logins expire overnight?

“Works in a browser” is not the same as “works in this sanctuary.” Guest networks that idle-kick devices, captive portals, and consumer routers in closets are normal church infrastructure. A phone hotspot is a weak plan: it fails when the room is full of other phones, and it does not help if you never cached the service.

If you cannot unplug the network and finish a simple set, you do not have a Sunday mode. You have a good weeknight editor.

Degraded mode is also about people. If only one login can present, and that person is sick, the browser did not make you more resilient. Use a church-owned account.

Cloud-first tools at category level

Some products are cloud-first even when they have an install: the library, the billing, and sometimes the Bible text live on someone else’s computer. Proclaim is the name many churches meet in that shape, often because they already live in a wider church-software stack.

Good fit when the church wants prep from multiple places and is already paying for that stack. Poor fit when you cannot explain the room’s behavior if the network drops, or when the operator still needs a dedicated machine the church does not own.

Do not treat “cloud” as a single feature. Ask where the live click happens. A service you fully downloaded is a different object than a stream of slides that need a server for each advance.

Local-install tools (Windows-centered suites, booth-class production software, many free desktop apps) invert the risk. They are often calm without wifi and fragile when the only licensed machine is missing. That is not worse. It is a custody problem instead of a network problem. Pick the failure you can actually back up: a second machine with the file, or a cached service plus a spare cable.

A web-based example

WorshipDeck is web-based church presentation software. It runs in a browser, including on Chromebooks, and is aimed at smaller teams: decks and services, songs, scripture insert, a live present mode, a shared library. HDMI from a laptop is the normal path; wireless display is optional later.

WorshipDeck has no free tier. It is a poor fit for churches that want a deep, booth-native production surface as their primary Sunday workflow.

Use it as an example of the shape — browser, shared prep, church-owned login — not as a default winner. Run the same tests you would run on anything else.

Chromebooks and other locked-down machines

A Chromebook can present if three things are true: the tool actually runs in that browser, the machine can output to the projector (USB-C adapter, HDMI, the right input), and someone has tested sleep, audio, and the clicker on that device. Some rooms open Google Slides on those machines because sharing is easy. It is a general slide tool, not church presentation software.

A Chromebook cannot present if you were counting on a Windows-only installer. Do not fight that for six months. Either pick a browser tool or buy a cheap church-owned Windows mini-PC and keep it in the room. Honesty here saves money.

Details — adapters, performance, when to stop trying — belong on the Chromebook guide. The category point is simple: web-based tools exist because those machines exist.

Shared libraries without losing the files

A team library is the main reason to accept browser risk. The worship leader adds songs on Thursday. The preacher drops references on Friday. Sunday’s operator opens a service that already exists.

Set rules so the library stays a church asset:

• Church-owned login, not a personal Gmail that walks out with a volunteer
• A naming habit for services (“2026-09-07 Sunday”) so last week is findable
• One person still checks the live view on Saturday — shared prep is not shared responsibility unless you say so
• A duplicate: export, USB, or a second device that has opened the service

Shared and unowned is how you get three versions of the chorus and no one sure which is presenting.

A 30-minute evaluation in a browser

Do this on the sanctuary network, not only at home.

1. Sign in with the church account on the church computer.
2. Build one song, one scripture passage, one short video.
3. Present to the real projector with the desktop extended, not mirrored.
4. Hand “next slide” to a second person with no tour.
5. Disable wifi and try the next two advances.
6. Walk the laptop to sleep and back. See what the house showed.

If step 5 fails, you have a weekday tool. If step 3 puts the browser chrome on the wall, you have an output problem to solve before you adopt anything. If step 1 is impossible because no one knows the password, you have a custody problem.

When a local install is the calmer choice

Stay local when you already have a dedicated booth machine, a trained operator, and a library on disk you can copy. Move toward a browser when the computers you have are Chromebooks or locked laptops, when prep must happen off-site, or when the last crisis was “the laptop never arrived.”

You can also mix: build where it is convenient, present from a machine that has already opened the service, and keep a USB fallback. The method is allowed to be dull.

Web-based church presentation software changes the custody of the library and the type of Sunday failure you should rehearse. It does not change the job: right words, right screen, on time, with a plan if the tab or the cable gives up.