How do you show a long Bible passage on screen?

Page it rather than shrinking it. Break the passage into screens of a few lines each at full size, and turn the page as the reading moves. Shrinking text to make a long passage fit means the people furthest away cannot read any of it.

Should we show the full verse or just the reference?

It depends what you want people to do. The full verse suits a passage you want the congregation reading along with. The reference alone suits a sermon where you want people finding it in their own Bibles, and it works better for long readings.

What should I do when the wrong verse is on screen?

Correct it and move on, without drawing attention. It takes about ten seconds and most of the congregation will not have registered it. Clearing the screen entirely is usually worse than a quick correction, because a blank screen is more noticeable than a changed one.

How do you follow a preacher who jumps between cross-references?

Manually, you mostly cannot — by the time each reference is found the preacher has moved to the next. Pre-building slides does not help either, because the chain is rarely planned. This is the case automatic detection is genuinely built for.

Presentation

What goes on the screen: full verse or reference, long passages, and fixing mistakes

By Mambo Mutinda · Founder & CEO, TajiCast

7 August 2026 · Updated 8 September 2026

Once scripture is reliably reaching the screen, the questions change. How much of it should be up there? What do you do with a passage too long to fit? What happens when the preacher chains five references together, or asks the congregation to look back at something from ten minutes ago — or when the verse on the wall is simply wrong?

Full verse, or just the reference?

Both are right, for different moments.

Show the full verse when you want people reading along. A verse the sermon is about to unpack, one worth sitting with, or a passage that lands better read than heard. The screen carries it, and nobody is hunting through pages while the preacher talks.

Show the reference alone when you want people in their own Bibles. Some churches teach this deliberately, and the screen supports it by naming the passage clearly and getting out of the way. It also suits long readings, where the full text would need several screens anyway.

A rule of thumb: if the preacher says "look at this with me", show the text. If they say "turn with me", show the reference.

Either way, keep the reference visible. Someone arriving late, or looking up mid-sermon, needs to know what they are reading without being told.

Long passages: page, do not shrink

The instinct with a long reading is to reduce the font until it fits. It is the wrong instinct.

Shrinking works on the operator's monitor, which is a metre away. On a wall seen from thirty metres, it fails the people furthest from the screen — the ones who most needed the screen in the first place.

Page it instead. Break the passage into screens of a few lines at full size, and move through them as the reading goes. Nothing is smaller than it should be; there is simply more than one screen of it.

ImagePhotograph: the same long passage twice — once shrunk to fit one screen, once paged at full size — shot from the back of the room

Both fit. Only one can be read from the back.

Turning the page while it is being read

The timing is the skill. Turn too early and you take words away from someone still reading them; turn too late and the room is waiting.

Watch the reader rather than the clock. Most people read aloud at a fairly steady pace, and the turn wants to land as the last line is being spoken, not after it. If you are operating and cannot hear well, that is a reason to fix the booth audio — timing a page turn by guesswork is unpleasant.

Following cross-references

The hardest thing a screen operator faces: a preacher chains four or five references together, each one a sentence apart.

Manually, you cannot keep up. By the time the first is found and sent, the second has been spoken. Most operators learn to give up and wait for the chain to end, which means the screen is blank through the densest part of the teaching.

Pre-building does not rescue it. Cross-reference chains are rarely planned in detail; they emerge from the preaching. A deck built on Saturday covers the passages that were known on Saturday.

This is the case automatic detection is genuinely built for: each reference is recognised as it is spoken, so the chain appears at the pace it is preached. Nothing to search, nothing to anticipate.

If you take one thing from this: the moments a screen fails are almost never the planned ones. They are the unplanned chain, the passage added on the way to the pulpit, the verse quoted from memory.

Going back to a verse already shown

"Look again at what we read earlier."

Circling back is not an edge case; it is how most sermons are structured. And it is where manual operation goes wrong most often, because the operator is now searching from memory — reconstructing a reference they typed twenty minutes ago, while the preacher waits.

The fix is not a better memory. It is that the service should keep its own record of what has been shown, so going back is a matter of choosing from a list rather than remembering. Any tool that keeps a history of the verses displayed turns this from a scramble into a click.

Worth preparing for, too: if a preacher tells you beforehand they will return to a passage, note it. Ten seconds on Sunday morning saves an awkward thirty later.

ImageScreenshot: a history panel listing the verses already shown in this service, with one selected to re-display

The service keeps its own record, so going back is a choice, not a memory test.

When the wrong verse is on screen

It will happen. Here is the proportionate response.

First, the ten seconds. Correct it. Send the right verse. Do not clear the screen to a blank first — a blank screen is far more conspicuous than a changed one, and it announces that something went wrong.

The mistake is smaller than it feels. From the booth it is enormous. In the room, most people are listening rather than reading, and a verse that changes has an obvious explanation. Nobody is keeping score.

Make the mistake cheaper. The real fix is structural, not personal:

A preview you can check before anything is public turns a public error into a private one.
Fast correction — a search box already focused, a history to click back to — means a wrong verse costs seconds rather than a scramble.
Detection that shows its working, so a low-confidence match can be spotted before it is sent.

Preview, if the moment allows

Broadcast galleries have run preview and program monitors for seventy years, for exactly this reason: every switch is public and irreversible, so nothing untested reaches the audience.

The same split works for scripture. Stage the verse where only you can see it, read it properly — the real theme, the real line breaks, the right translation — and send it deliberately.

It is not free: it adds an action, and an action is a thing to forget. During a straight reading through a chapter it is friction with no benefit. Use it for the deliberate verses, where being right matters more than being fast, and switch it off when a reading needs pace.

The takeaway

Page long passages at full size. Shrinking fails precisely the people who needed the screen.
Full text for reading along, reference for looking up — and keep the reference visible either way.
The unplanned moments are what break a screen: chains, callbacks, and mistakes. Make each of them cheap rather than trying to prevent them.

Keep up with the sermon, including the parts nobody planned. Free for Windows.

Download TajiCast, free

Frequently asked questions

How do you show a long Bible passage on screen?: Page it rather than shrinking it. Break the passage into screens of a few lines each at full size, and turn the page as the reading moves. Shrinking text to make a long passage fit means the people furthest away cannot read any of it.
Should we show the full verse or just the reference?: It depends what you want people to do. The full verse suits a passage you want the congregation reading along with. The reference alone suits a sermon where you want people finding it in their own Bibles, and it works better for long readings.
What should I do when the wrong verse is on screen?: Correct it and move on, without drawing attention. It takes about ten seconds and most of the congregation will not have registered it. Clearing the screen entirely is usually worse than a quick correction, because a blank screen is more noticeable than a changed one.
How do you follow a preacher who jumps between cross-references?: Manually, you mostly cannot — by the time each reference is found the preacher has moved to the next. Pre-building slides does not help either, because the chain is rarely planned. This is the case automatic detection is genuinely built for.

Keep reading