Google Slides on Sunday: shared decks, and the wifi problem

Google Slides as a church slide stand-in: easy sharing and Chromebooks, versus live lyrics, operator preview, and what happens when the network drops.

September 7, 2026

Google Slides is a browser deck. Churches use it because a link is easy to share, a Chromebook can open it, and nobody has to install anything. That is a real convenience. It is not church presentation software.

Google’s Slides is a general slide tool. It assumes a finished sequence you click through. Church presentation software assumes a living service: a chorus repeat, a skipped verse, an operator preview the house must never see. Treat Slides as that category and you inherit PowerPoint’s live-worship gaps plus a network assumption.

This page is a portrait of that tradeoff. For the field, use church presentation software. For browsers that are actually built for Sunday, see web-based church presentation software.

What it is (and who it is for)

Google Slides is not church presentation software. It is a shared office deck that happens to run in a tab. Churches reach for it when the computers are Chromebooks, when install rights do not exist, or when three people need to edit the same file on Thursday night.

It is for rooms that already live in Google accounts, that need a link instead of a USB stick, and that can accept Next as live control. It is a reasonable path for announcement loops, a linear sermon outline, and a short lyric deck if the band will not wander.

It is a poor weekly plan for live worship if you need a jump list, a church scripture insert, or a Sunday that still works when guest wifi dies. Those limits are the same family as PowerPoint, with a stronger dependence on the network.

Who it is for:

Chromebook-only rooms that will not buy a Windows box this year
Teams that prep from several kitchens and need one shared file
Churches whose machines are locked down and will not run an installer
A backup link if the booth PC fails — if the network is up

Who it is not for: a sanctuary whose wifi is the weak point, or a volunteer who must jump to a verse while the preacher is already reading it. Sharing solved Thursday. It did not invent a live control surface.

A church-owned Google account is part of “who it is for.” A youth volunteer’s personal Gmail is not a church library. When that person moves, the deck moves unless you already copied it.

Features that matter on Sunday

Judge Slides on the same Sunday jobs as the rest of the field. Skip only what it truly does not have, and say so.

Lyrics

You type lyrics onto slides. Sharing is easy; live control is not. A repeat is still a hunt through a linear deck. Multiple editors can help on Thursday and overwrite the order on Saturday. Lock the file before Sunday, or appoint one owner.

Scripture

There is no church scripture insert. You paste a passage and format it. A second person can add verses from home — that is the sharing strength. The live weakness is the same as PowerPoint: no jump-to-verse object, no translation picker in the tool.

Media

Images and videos can sit on slides. Video in a browser depends on the machine, the tab, and sometimes the network. Test audio through the house path on the church Chromebook or laptop. USB-C adapters that do video and no audio are a common surprise.

Live control

Presenter view exists if you use it and if you can get an extended display. Many Chromebooks make that harder than a Windows laptop. Mirror mode still puts operator chrome on the house. There is no service playlist with named jump targets. Next and Back are the live surface.

The house must not see the filmstrip, the speaker notes, or a Chrome tab bar. Practice the drag on Saturday. If you cannot get a true extended desktop, write it down as a hardware limit.

OS / where it runs

A browser. Chromebooks, locked Windows images, a pastor’s home computer — anyone with the link and an account can open the deck. No install rights needed. Use a church-owned Google account.

Booth-class desktop apps will not install on ChromeOS. Slides exists in this conversation because those machines exist. That does not make Slides a church booth tool. It makes it a deck that will open.

Offline

This is the question that decides the room. Google Slides can work offline in some setups if the file was opened and cached in Chrome, with the right account, before you lost wifi. That is not the same as a local PowerPoint file on a USB stick. Unplug the network on the church computer and click through the actual deck. If the tab asks you to sign in, or the slides do not advance, you do not have an offline mode. You have a good weeknight editor.

Church guest networks that idle-kick devices are normal. A phone hotspot is a weak backup. Hardware details live in church presentations on a Chromebook.

Strengths

Shared links. The worship leader and the preacher can edit the same deck without emailing FINAL2. That is the job Google Slides is good at.

Chromebooks. If the only dependable computers are ChromeOS, a browser deck is a path that exists.

No install rights needed. A locked church laptop can still open a tab.

Familiar enough. Volunteers who have used Docs have used Slides. Training is: open the link, click Present, hit Next.

Prep from more than one place. The file is not trapped on a booth PC nobody can reach on Thursday.

A usable backup when the network is up. If the booth PC dies and a Chromebook can open the link, you have words on the wall. That is not a plan if the access point died too.

Weaknesses / poor fit

The same live-worship gaps as PowerPoint. Repeats, jump-to-verse, a linear pile of slides, no church song or scripture library. Presenter view is not a booth live surface.

A stronger network assumption. Even if offline cache can work, most churches treat the file as a cloud object. Sanctuary wifi on Sunday is not Thursday kitchen wifi. Phones join the guest network during announcements. That is when a tab that needs the server starts to stutter.

Operator preview. Getting a true house-only picture from a Chromebook is hardware as much as software. If you cannot extend the display, the room sees your tab bar.

Account custody. A personal Google login is not a church library. “Anyone with the link can edit” is how a helper duplicates the chorus and nobody knows which copy is live.

Video and audio. Browser playback plus a USB-C adapter is a stack of failure points. Test them together on the church machine.

Cost shape. Slides is free if you already have a Google account. A church Workspace account is a different shape than a personal Gmail. Confirm what you have. Do not invent a price.

If you want church slides in a browser — songs, scripture insert, a live present mode — you are looking at a different category. Start with web-based church presentation software, not with a shared office deck.

How to evaluate it in 30 minutes

On the church computer that will present — especially if it is a Chromebook:

Create a deck in the church Google account. Build one song in band order.
Paste and format one scripture passage. Feel the cost of no insert. Add a second passage so you can practice a hunt.
Add one Sunday video. Present it through the real projector and the house audio path.
Set the display so the house sees only the slide. If you are stuck in mirror mode, write that down. That is the weekly risk.
Unplug wifi. Advance the deck. Jump back to the chorus. If the tab dies, cache is not a plan for this room.
Hand the machine to a second person. Ask them to Present and hit Next with no speech from you.

If sharing was the only pain, and the network test passed, Slides can be a season. If the pain was a chorus repeat or a dead access point, you learned the category limit in half an hour. The hub’s evaluation frame is the same test for tools built as church software.

Do the network test on Saturday in the sanctuary. Home wifi will lie to you.