MediaShout: a long-running Windows option for Sunday slides
MediaShout as churches actually meet it: Windows booth software for lyrics, scripture, and media, and when a newer or simpler tool is a better fit.
September 7, 2026
MediaShout is a long-running Windows option for church slides. Churches meet it on a booth PC that has been in the cabinet for years, not as the new name on a forum. The Sunday job is the usual one: lyrics, scripture, media, and someone clicking in real time. The product’s reputation is installed base, not novelty.
This page is a portrait, not a score. It does not pick a winner and it does not publish a switching funnel. For the rest of the field, use the church presentation software hub. If you are choosing without a media team, read church presentation software for small churches as the decision frame.
The vendor homepage is mediashout.com. Confirm current features, Windows requirements, and cost there. This magazine will not invent a price or a version number.
What it is (and who it is for)
MediaShout is church presentation software installed on a Windows machine that stays in the room — or at least should. Files live locally. The operator builds a Sunday from songs, verses, and media that are already on that computer. It is booth software in the older, familiar sense: you sit down, you open the service, you present to the projector.
Who it is for:
- Rooms that already know it. The volunteer who can find next slide without a map is a reason to stay
- Churches with a Windows booth PC and no plan to become Mac-only or Chromebook-only
- Teams that want lyrics and media on a local disk, not a cloud library as the default
- Mid-size or smaller Sundays that look like a familiar service order, not a multi-output production desk
Who it is not automatically for: a church starting from zero with no trainer, a building that only has Macs or Chromebooks, or a team whose weekday prep happens in five houses and needs the library to live in a browser.
If Sunday already works on MediaShout, the question is rarely “is there a newer logo.” The question is whether the computer, the files, and the next volunteer are church-owned. Switching because a larger church down the road uses something else is how you trade a known live view for a month of “where did the song go.”
If you do not have MediaShout yet, treat it as one Windows-shaped option among others. Read this page, then run the 30-minute test. Do not buy it because the name is old. Do not reject it because the name is old.
Features that matter on Sunday
These are Sunday jobs. They are not a feature matrix copied from a vendor page. Confirm ingest, scripture, and live-view details in a trial on the church computer.
Lyrics
The house needs the words the band will actually sing, in the order they will sing them. MediaShout is Sunday-shaped here: songs in a service, not a single office deck you hope nobody repeats.
Ask, during the trial, how a new song arrives and how you jump back to a chorus. Lyrics on the church screen is the arrangement piece. Display licensing is the church’s job.
Scripture
Put the translation the preacher uses on the projector in readable chunks. Do not screenshot a phone.
How MediaShout gets verses onto a slide in the current release is a trial question, not a claim this page will invent. Build one real passage. Practice a jump when the pastor skips a verse. Scripture slides for Sunday is the readability guide. If ingest is painful, you will skip it in a busy week.
Media
Announcement loops and short videos are normal. Local files are a MediaShout-shaped strength: the video is on the machine, not waiting on a tab. Test audio on the house system. Confirm you can leave a video without leaving a desktop on the wall. See church presentation hardware basics.
Live control
The operator needs current, next, and a way to jump. The house needs only the slide. That is the whole live job for most rooms that run MediaShout.
This is not the deep multi-output surface people associate with staffed booths. If you need stage layouts as the primary workflow, ProPresenter is the usual name. If you need a calmer Windows Sunday, EasyWorship is the other portrait. Neither sentence is a ranking. Confirm you can see the next lyric without putting the playlist on the house. Extended desktop, not mirror.
OS / where it runs
Windows booth PC. That is the durable fact.
Mac-only rooms and Chromebook rooms are a poor fit. There is no honest browser path for a Windows install. If the church laptop is a Chromebook cart, read church presentations on a Chromebook plus the hub. The computer should be church-owned and should stay.
Offline
Local files on a Windows machine should still present if you unplug the network — provided the service and the media are actually on that disk.
Unplug anyway. Advance a song. Jump a verse. Play the video. If something calls home and refuses to move, you have learned a Sunday fact. Guest wifi in a fellowship hall is not a reason to skip the test.
Strengths
Familiar in rooms that already know it. The strongest argument for MediaShout is often the volunteer who already clicks it. Training a substitute on a tool the church has run for years is cheaper than a new file format.
Local files. Songs, verses, and videos that live on the booth PC do not depend on sanctuary wifi to appear. Custody is still your job: church account, church folder, a second person who can open the service.
Sunday-shaped lyrics and media. It is church booth software, not a general slide deck with a cross on the title slide. Repeats, jumps, and a service order are the point.
An installed base that still has to get through Sunday. You are not inventing a workflow from a blank forum thread. That is not the same as a vendor on the phone at 8:40 a.m. Confirm what support you actually get before you need it.
Weaknesses / poor fit
Mac-only or Chromebook rooms. No Windows machine, no product. Do not plan around a borrowed PC that might not arrive.
Teams that need a modern cloud library as the default. If the weekday work is “five people add songs from home, and the booth only presents,” a local Windows library is the wrong center. Cloud-first tools exist for that shape; ask what happens when the network drops, and confirm the answer on the vendor site and in a trial.
People starting from zero with no trainer. Installed base helps churches that already have an operator. Without someone who knows the live view, you will spend the first month on settings. A newer or simpler tool can be a better fit when there is no institutional memory.
Expecting a deep production desk. If the room wants multi-screen looks as the main workflow, MediaShout is the wrong conversation.
One expert volunteer and no notes. Any booth tool dies when the only person who knows the output setup is on vacation. Write the input, the login the church owns, and where the service file lives.
How to evaluate it in 30 minutes
Use the church Windows computer and the real projector. A home machine with a different display path will lie to you.
- Open MediaShout the way Sunday will open it. Church profile. Church display settings. Sleep and notifications off.
- Build one song the band will sing, one scripture the preacher will read, and one video you already use. Put them in the service order you would actually run.
- Present to the house. Confirm the congregation sees only the slide. Confirm the operator sees current and next. Fix mirror mode before you blame the software.
- Unplug the network. Advance. Jump. Play the video. Write down what breaks.
- Hand Next to a second person who did not watch you build. Ask for the next slide, then a specific verse.
If you already run MediaShout, do the same test with a substitute, not as a reason to switch. If you are evaluating from scratch, compare the explanation time in step 5 with the hours you actually have. How church presentation software works is the category reminder: right words, right screen, on time.