Setting up ProPresenter for church services

Most ProPresenter problems in churches are not technical. They are organisational: a library nobody can search, templates that only one person knows how to edit, and a rota of volunteers learning by watching. This guide covers the setup that makes a Sunday morning boring, in the best sense.

Structure your library before you fill it

Decide on a structure on day one and write it down. A structure that works for most churches:

• Songs — one library, alphabetical, one document per song.
• Scripture — generated live rather than stored, so you are never locked into a translation.
• Liturgy and responses — anything repeated weekly, built once.
• Announcements — rebuilt weekly and cleared out monthly.
• Seasonal — Christmas, Easter and anything you touch twice a year.

Name songs the way people search for them: the title everyone uses, not the copyright title. Consistency beats cleverness.

Build templates, not slides

Create a small set of themes: lyrics, scripture, sermon point, announcement, and lower third if you stream. Set the font, size, position and safe margins once, and build everything from those. When someone asks to make the lyrics bigger for the back row, you change one theme instead of two hundred slides.

Check every template on the actual screen in the actual room. Text that reads beautifully on a laptop can be unreadable from row fifteen, and the bottom of a projected image is often hidden behind heads.

The stage display earns its keep

A separate stage display is the feature that most changes how a service feels. Musicians see the current and next lyric, the speaker sees notes and a clock, and neither has to squint at the back wall. Keep it minimal: current slide, next slide, clock, and a message field for the person running sound to say "two minutes".

Train volunteers on the pattern, not the buttons

New operators do not need a tour of every menu. They need to know the five actions they will perform every week: advance a slide, jump to a song out of order, put up a scripture the speaker just called out, clear the screen, and start a video. Teach those five until they are automatic, then teach the rest as it comes up.

Run training on an unlicensed copy on their own laptop so they can practise at home. The watermark does not matter when nobody is watching.

Plan for the running order changing

It will. A song gets added, a passage gets skipped, an announcement gets cut for time. Two habits make this painless: keep the whole song library one search away rather than only what is in today's playlist, and agree a signal with the service leader so the operator is told rather than guessing.

Streaming considerations

If you stream, decide early whether the online audience sees the same output as the room. Many teams send a separate feed with lyrics keyed over camera rather than the raw projection output, which looks far better online. Our multi-screen guide covers how those outputs are configured.

Maintenance nobody enjoys but everyone needs

• Back up the support folder monthly to external storage, and check the backup opens.
• Clear out old announcement slides so search results stay useful.
• Install updates midweek, never on a Saturday, and read the release notes first.
• Keep a written note of screen resolutions, adapters and cable runs. The person covering next month will thank you.

Do these five things and the technology stops being a weekly source of stress. That is the whole goal: nobody in the congregation should ever think about the presentation software at all.