What “free” actually costs on Sunday

Free is a real way to run church slides. It is not the same as costless. A license you do not pay is often replaced by Saturday hours, a volunteer who becomes unofficial IT, and no one to call when the output is blank at 8:40 a.m.

This is a category look, not a ranking and not a “best free tools” list. For the wider field — including paid booth tools and cloud-first suites — use the church presentation software map. If you are choosing under one-volunteer constraints, the decision frame is church presentation software for small churches.

What “free” usually means

Churches say “free” to cover several different shapes:

• A dedicated church slide app with no license fee, supported by the community or by the people in your building
• Software you already pay for in another way — Office, a school Apple ID, a donated computer with a bundle
• Open source, where the code is free and the labor is yours
• A trial that is not a plan — ninety days of calm, then a Sunday that depends on a card

Those are not interchangeable. “We already have PowerPoint” is a different risk than “we installed a church-specific tool and will maintain it.”

Do not treat a missing price tag as a moral win. Treat it as a budget line that moved from the treasurer to the media volunteer.

WorshipDeck is not in this category. It is web-based church presentation software, and it has no free tier. If a page implies otherwise, that page is wrong.

FreeShow and tools like it

FreeShow is the name you will hear most often when a church wants church-shaped slides without a license: songs, scripture, media, a live control surface. It is capable. The honest cost is time and self-support, not a vendor invoice.

Good fit when:

• Someone will install it on a church-owned Windows or desktop-class machine and keep it updated
• You can accept forum posts and documentation instead of a support desk
• One volunteer is willing to own “why is the second output wrong” without burning out

Poor fit when:

• No one will touch settings after the first Sunday
• You need a named person to call during a failure
• The only computers are locked-down or browser-only and you cannot install anything

“And similar” here means other no-license church tools you evaluate the same way: do they ingest songs and scripture, can one person run them live, and what happens offline. Do not add names you cannot describe at that level. Confirm current platforms and limits on the project site. They change.

The evaluation is the same 30-minute test as any other tool: church computer, one song, one passage, one video, real projector, unplug the network, hand the clicker to someone untrained.

PowerPoint and Keynote: free if you already have them

PowerPoint and Keynote are general slide programs. Churches use them because the license is already sitting on the laptop. They can put words on a wall. They are a poor match for a living worship set.

Where they hurt on Sunday:

• Live repeats. Looping a chorus or jumping to a bridge is a scavenger hunt through a linear deck.
• Operator view. Mirror mode is the default instinct, which puts the slide sorter on the house. Presenter view helps and still is not a church jump list.
• Scripture and songs as data. You are pasting and formatting, not inserting a passage and keeping a library.
• Handoff. A 90-slide file with leftover drafts is how the next volunteer opens the wrong section.
• Videos and audio. Possible, and easy to send sound to the wrong place.

They are a reasonable emergency fallback: export a simple lyric-and-verse deck onto a USB if the main tool dies. They are a weak plan for weekly worship. If this is your only option this month, keep the deck short, use a holding logo, and do not build motion that you cannot control live.

Open source, if you can describe it fairly

OpenLP is a long-running open-source church presentation project (openlp.org). It runs on more than one desktop OS, and it is built around the same jobs as the rest of the category: songs, Bible texts, media, live display. Churches that like it usually have a volunteer who is comfortable installing software and reading project docs.

Good fit when you want a church-shaped tool, you can install on a machine you own, and you accept community support. Poor fit when you need a vendor, when no one will maintain plugins and outputs, or when your only devices cannot run a desktop app.

Open source is not “more honest” than a paid tool by default. It is honest about money and silent about labor. If your church has that labor, it can be a stable home. If it does not, you will quietly return to a phone screenshot.

Skip rumor lists of abandoned projects. If you cannot open the site and see an active project, do not put it on Sunday.

Hidden costs that show up in the booth

No vendor to call

At 8:40 a.m. you have the people in the room and whatever you wrote down last month. That can be enough if you already practice when Sunday slides fail: spare cable, logo, preach without slides. It is not enough if the only person who understands the install is out of town and the file will not open.

Paid support is not magic. It also will not reseat HDMI. The difference is whether anyone outside the building shares the problem.

One expert volunteer

Free tools often survive because one person enjoys them. That person becomes the media team. When they leave, the church discovers that the library, the outputs, and the “how we do communion slides” lived in one head.

Document the boring path: which computer, which output, where the service file lives, how to go to black. If you cannot write that on one page, the software is not simple yet — no matter the price.

CCLI and scripture workflow

Display licenses and Bible text rights are the church’s job, not a feature of a free download. Some free tools help you stamp a license number or insert a translation they ship. Some expect you to paste. Either way, someone still has to report songs if your license requires it, and someone still has to pick one translation for the room.

A free tool that makes messy lyric imports easy can create a copyright mess faster. Slow Saturday work is part of the cost. High-level note only: this is not legal advice; the church owns the license question.

Time you will not donate forever

Building a song library by hand, fixing line breaks, and re-creating last year’s announcement loop is real work. A paid library or insert feature can be cheaper than ten Saturday nights. It can also be wasted money if you will not use it. Count hours for your room, not a demo video.

Low-cost is not the same conversation

A one-time license or a modest subscription can be the right small-church spend if it removes the expert-volunteer trap or runs on the computers you have. “Low-cost” still needs the same tests: OS, one-person live view, offline, who owns the files. Do not invent a price from memory. Look at the vendor’s current page and ask what year two looks like.

Free trials belong in evaluation, not in the permanent plan. If you cannot say what you will run when the trial ends, you are not ready to put it on the house.

How to evaluate without a bake-off

Use the same questions as the main tools roundup, with one extra:

• Does it run on the church computer you already have?
• Can one volunteer operate it live — current, next, jump, black?
• How do songs and scripture get in, and can you keep them readable?
• What happens if the internet drops?
• What does support look like when the expert is sick?
• Who owns the files in year two?

Then run the 30-minute test on the real projector. If FreeShow (or OpenLP, or a careful PowerPoint fallback) passes, you have an answer. If it fails because no one will own updates, the license fee was never the problem.

For the category building blocks behind any of these tools, see how church presentation software works.

Free software can be the honest choice for a church that will support itself. Price it in volunteer hours, support, and file custody — not in the satisfaction of paying zero. Sunday does not care that the download was free. It cares that the next line is on the wall.