Proclaim: cloud-first church slides, and what happens offline

How Proclaim fits church presentation software: cloud library and live slides, who it helps, and the questions to ask if the sanctuary wifi drops.

September 7, 2026

Proclaim is church presentation software that treats the library as a cloud object first. You build a service during the week from more than one kitchen table, then present it on Sunday from a church computer. The files are not supposed to live only on the laptop that went to the lake.

Many churches meet Proclaim because they already live in a wider church-software stack — the same family of products as Logos and Faithlife tools. That is the honest frame: cloud-first slides, often next to software you already pay for. Confirm the current bundle and cost shape on the vendor site. This page does not invent prices or a version number.

Who it is for: a team that preps from more than one place, a church that already has accounts in that stack, and a room that can explain what happens if the sanctuary wifi drops. If your only network is a guest SSID in a closet, or you want a deep booth-native production surface as the main workflow, keep reading before you add another login.

What it is (and who it is for)

The Sunday job is still lyrics, scripture, media, and a live control surface that does not show the congregation your playlist. What changes is where the library lives and what kind of failure you should plan for.

Local-install booth tools are often calm without wifi and fragile when the only licensed machine is missing. Proclaim inverts that: the machine in the room can be ordinary, and the service can be opened from more than one login. The weak point moves to the network, the account, and whatever the product does when it cannot reach a server.

A good fit looks like this:

Two or three people build the set during the week from home, and none of them is the only copy of the file
The church already pays for a wider Faithlife-shaped stack and does not want a second, disconnected library
Someone owns a church login, not a personal account that walks out with a volunteer
You have tested, on the church computer, what the operator sees if the network dies

A poor fit is a room that cannot answer the last point, or a team that wants ProPresenter-depth multi-output control as the primary Sunday surface. Proclaim is church slides with a shared library. It is not a production desk that happens to sync.

Read how church presentation software works if you still need operator view versus house view before you evaluate any cloud-first tool.

Features that matter on Sunday

Confirm each job on the current product, then prove it on your projector. Do not treat a homepage as a verified checklist.

Lyrics

A church tool should let you jump, go back, and keep the house on words while the operator sees current and next. Ask whether songs live in a shared library. Build one real song the band will sing this week, including a repeat. If that needs a settings panel in the moment, the cloud library will not save Sunday.

Scripture

Some churches buy into this stack because Bible text is already part of the wider product family. That can be useful: you insert a passage instead of screenshotting a phone. Confirm the translation you preach from, and whether the verse is stored in the service or fetched when you click. Build one passage, then jump ahead two verses. If insert needs a live connection at click time, write that down as a Sunday risk.

Media

Put one short video on the real projector. Confirm the sanctuary can hear it. Confirm you can leave it for a lyric without a black flash you did not choose. If media only plays while the tab can reach a server, that is a room problem, not a footnote.

Live control

The congregation must never see the playlist. Current slide on the house. Next slide on the operator view. A way to go to black or a logo. Have a second person sit down and hit Next with no training. If they cannot find current, next, jump, and black in a minute, the shared library is not the problem.

OS / where it runs

Proclaim is cloud-first. That often means a client or a browser plus a library that lives on someone else’s computer. Confirm current platforms on the vendor site. Do not assume a Chromebook path, and do not assume a locked-down church laptop will run an installer.

A church-owned machine that stays in the room is still the right default. A personal laptop that can “just log in” is how you discover that home wifi and sanctuary wifi are not the same network, and that the login expired overnight.

Offline

This is the question to ask out loud. We will not invent the current offline story. Products in this shape change how they cache, and a sentence on a magazine page would go stale.

Ask the vendor, 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?

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.

Strengths

Prep from more than one place. The worship leader can add songs on Thursday. The preacher can drop references on Friday. Sunday’s operator opens a service that already exists. That is the main reason churches accept cloud risk.

A shared library. Songs and services are not trapped in one user profile on one disk. A second volunteer is not starting from a USB stick labeled “DO NOT ERASE.” The church can own the login.

Less “laptop went to the lake.” If the library is not only on the machine that left town, you have a different backup problem than a local-only booth. You still need a machine, a cable, and a projector. You are no longer one forgotten bag away from a blank wall — unless the network is the bag.

Weaknesses / poor fit

Rooms whose wifi is the weak point. If you cannot present a cached service — or you do not know whether a cached service exists — the sanctuary network is part of the instrument. Do not buy a cloud-first workflow and hope the closet router grows up.

Ask what happens if the network drops. If the honest answer is “we are not sure,” stop. Run the unplug test before you move the whole church onto a login.

Teams that want a booth-native surface as the primary workflow. If Sunday is multiple outputs, a stage display you actually design, and a live desk a trained operator lives in, look at booth-class tools instead of stretching a cloud library into a production surface. That is a different job, not a higher score.

Cost as a shape, not a number. Expect a subscription, often next to that wider church-software stack. Confirm on the vendor site. It is a poor surprise when a volunteer cannot present without a personal login you cannot recover.

Poor fit is a room that cannot name its offline behavior, and a team that wanted a local booth desk.

How to evaluate it in 30 minutes

Do this on the church computer, not on a home laptop on fiber.

Sign in with a church-owned account. If you cannot, stop and fix that before you judge the software.
Build one song the band will actually sing, including a chorus you can jump back to.
Insert one verse the preacher will read. Jump ahead two verses.
Add one short video. Present to the real projector, not a window on the laptop.
Confirm operator view versus house view. The playlist must not hit the wall.
Unplug the network. Disable wifi. Finish the song, the verse, and the video. Write down exactly what happens.
Hand the clicker to a second person who has not been trained. Ask them to go Next, jump, and go to black.

If step 6 fails, you have your answer for this room. If step 7 fails, the shared library will not make Sunday safer. If both pass, Proclaim’s shape — cloud library, multi-place prep, less lake-house risk — is doing the job it is built for.