Sermon Slides Best Practices Every Church Tech Team Should Know

Good sermon slides best practices come down to this: show a short outline of main points and the key Scripture references, formatted in large, high-contrast text with one idea per slide — never a transcript of the sermon. Slides support what the pastor is saying; they don't replace listening, and they shouldn't compete with the pastor for the congregation's attention. Below is what sermon slides should actually contain, how to format them for readability, the weekly workflow that stops last-minute scrambles, why a searchable archive matters, and the mistakes that make slides a distraction instead of a help.

Sermon slides are a different job from song-lyric slides, even though they often live in the same presentation file. A worship set exists to put words in the congregation's mouths so they can sing along; sermon slides exist to reinforce a spoken message people are meant to be listening to, not reading. Mixing up those two jobs is where most sermon-slide problems start — a slide deck that tries to be a transcript ends up being neither useful notes nor a good visual aid. This guide treats sermon slides as their own category with their own rules, on the assumption that whoever's building them Sunday-to-Sunday wants something that works reliably, not a redesign project.

What sermon slides should actually contain

A sermon slide deck earns its place on screen by doing a small number of things well, not by trying to capture everything the pastor says. In practice that means:

• The sermon's key Scripture references, with the verse text itself on screen (not just "John 3:16" with nothing underneath) — see the formatting section below for how much text belongs on each slide.
• A handful of main points or an outline, usually three to five, matching however the pastor has structured the message — "Point One: Grace is a gift, not a wage" rather than a full paragraph explaining it.
• Key terms or a memory verse the pastor wants the congregation to hold onto after the service, sometimes repeated at the very end as a closing slide.
• A series title and week number if the sermon is part of a series, so newcomers and regulars alike know where they are in the bigger picture.

What it should not contain is a transcript of the sermon. If a slide has more than one or two short lines of the pastor's own words on it beyond a verse or an outline point, it has drifted from "aid" into "script," and the congregation starts reading the screen instead of listening to the person speaking. The test worth applying to every sermon slide before Sunday: could someone glance at this for three seconds and get the gist, or does it need to be actually read? If it needs to be read, cut it down.

Formatting for readability at a distance

The same physical-distance rules that apply to song lyrics apply even more strictly to sermon slides, because a congregation reads sermon text far less automatically than familiar song words. A few rules that consistently hold up:

• Short phrases, not full sentences. "Faith without works is dead" reads in an instant; a full grammatical sentence explaining that phrase takes real reading time away from listening to the pastor.
• Large, high-contrast text. The back row of the room is the test, not the laptop screen a volunteer is looking at while building the slide.
• One idea per slide. A three-point outline is three slides, not one crowded slide with all three points stacked on top of each other.
• A consistent template every week. The same font, the same color scheme, the same placement for a series title or reference — so the deck looks like it belongs to the church rather than looking thrown together an hour before the service. A recognizable template is also a quiet trust signal: it tells a visiting or new congregation member that this church runs things with some care.
• Restrained motion. A subtle background is fine; animated backgrounds, moving particles, or slide transitions that draw the eye away from the text pull attention from the message, not toward it.

Getting the pastor's outline to the slide-builder with real lead time

Almost every sermon-slide problem — typos, missing points, a deck that doesn't match what actually gets preached — traces back to the same root cause: the outline arrived too late. A workflow that consistently avoids the Saturday-night scramble looks like this:

• The pastor finalizes a working outline by midweek — Tuesday or Wednesday is realistic for most churches — even if a few details are still being refined. Main points and Scripture references are usually settled well before the exact wording of the sermon is.
• The outline goes to the slide-builder as a simple list, not a full manuscript: point one, point two, point three, key verses, closing thought. The person building slides doesn't need the sermon itself, just its skeleton.
• The tech volunteer builds the deck against the church's standard template, checks every reference for typos, and slots it into the week's service plan alongside the worship set and announcements — the same running order, not a separate file that has to be found and loaded on Sunday morning.
• The pastor reviews the finished deck before Sunday, even briefly, catching anything that's drifted from what they actually intend to say.
• Late changes get a clear channel — if the pastor tweaks a point Saturday night, there's one obvious way to get that change to the slide-builder rather than a last-minute phone call hoping someone's awake.

Churches that build this rhythm into their week — sermon outline early, slide build midweek, review before Sunday — rarely end up with sermon slides that don't match what's preached. Churches that leave it to Saturday night almost always do, at least occasionally, and it shows.

Keeping a searchable archive of past sermon decks

Once a sermon slide deck has done its job on Sunday, it still has value — but only if it's easy to find again later. A searchable archive of past decks pays off in a few recurring situations:

• Series recaps. A pastor closing out a six-week series often wants to reference a point made in week two; pulling up that week's actual outline slide is faster and more accurate than trying to remember it from memory.
• Repeated references. Pastors regularly circle back to a message preached months earlier — "as I said back in our series on grace" — and having that deck a quick search away (by series title, date, or keyword) saves rebuilding something that already exists.
• New tech volunteers. A new volunteer building their first sermon deck has an instant style guide in the archive: here's what the template looks like, here's how much text past decks actually used, here's how a series title was handled before.
• Pairing with the sermon-audio archive. A slide deck next to its matching audio recording is more useful than either on its own, particularly for anyone reviewing a message after the fact rather than sitting in the room for it.

The archive doesn't need to be complicated — a consistent naming pattern (date, series, week number) and a place everyone on the tech team knows to look is enough to turn "does anyone remember where that slide deck went?" into a thirty-second search.

Common sermon-slide mistakes to avoid

• Walls of text. A slide that needs to be read rather than glanced at has already lost the room's attention away from the pastor.
• A verse reference with no verse text. "Romans 8:28" on its own forces people to either flip through their own Bible mid-sermon or simply tune out; the actual verse text belongs on screen alongside the reference.
• Distracting backgrounds or animation. A busy image or moving background behind sermon text competes with the words for attention and makes short phrases harder to read at a glance, not easier.
• Inconsistent templates week to week. Slides that look different every Sunday — different fonts, different colors, no series branding — read as thrown together, even when the content itself is solid.
• No lead time. Building the whole deck Saturday night all but guarantees typos, missed references, and no chance for the pastor to review it before it's on screen in front of the congregation.

Frequently asked questions

What should sermon slides actually include?

A short outline of the sermon's main points (usually three to five), the key Scripture references with the verse text itself displayed, and sometimes a series title or a closing memory verse — not a transcript of what the pastor says.

How much text should be on a sermon slide?

As little as does the job: a short phrase for an outline point, a verse and its reference for Scripture, one idea per slide. If a slide needs more than three seconds to take in, it has too much text.

When should the pastor give the tech team the sermon outline?

By midweek — Tuesday or Wednesday works for most churches. Main points and Scripture references are usually settled well before the sermon's exact wording is finished, so there's no reason to wait until the weekend to send them over.

Should sermon slides use the same template every week?

Yes. A consistent font, color scheme, and layout across weeks makes the church's presentation look intentional rather than thrown together, and it speeds up the build for whoever's making the deck since the design decisions are already settled.

Why keep an archive of old sermon slide decks?

Pastors regularly reference past messages during a series recap or months later, and a searchable archive — by date, series, or keyword — makes finding that old deck a quick search instead of a rebuild from scratch.

Is there a free way to build and store sermon slides for a small church?

Yes. Ekkli's free trial includes the presentation tool for building sermon slides alongside a subdomain website, member database, rota and scheduling, push notifications, and a sermon-audio player with a rolling two-hour storage window, for up to 50 people with no card required.

This guide is maintained by the Ekkli team, who build the presentation tool described above. Have a sermon-slide or service-planning question we haven't covered? Reach out — we're happy to help, whether or not you end up using Ekkli.