For a simple Bible reading ticker in a continuous YouTube stream, put the current reading in a plain text file and add that file to an OBS Text source with Read from file enabled. A volunteer can update the file as the service moves on; OBS does not identify spoken verses or fetch them from a Bible database.
The useful distinction is between displaying text and deciding what text belongs on screen. OBS handles the first part. Someone on the team must supply and update the reading, unless you choose a separate overlay system with its own controls. This guide focuses on the plain-file method because it is easy to hand over and does not require rebuilding the scene each time.
Choose the ticker text and update method
Decide what the audience needs to read before you create a source. For some services, a short reference such as “Psalm 23:1–4” is enough. For others, the congregation benefits from seeing the full passage. A ticker can also show a brief label alongside the text, for example “Today’s reading — Psalm 23:1–4”. Keep the amount of text suited to the time people have to read it: a long passage moving quickly across the screen is not automatically more useful than a reference that stays visible.
A plain OBS Text source reading a file is the least complicated choice when a volunteer can update the text manually. It renders text in the scene, and the file is the update mechanism. This does not connect the ticker to the pastor’s speech. If the pastor changes passages, pauses, or moves to a different verse, the operator has to make the corresponding change in the file.
| Method | How the reading changes | Styling and behaviour | Useful when |
|---|---|---|---|
| OBS Text source reading a file | A volunteer edits the file as needed | Straightforward text; limited to the source’s text styling | The service needs a reference or simple passage that can be changed by hand |
| OBS Browser source | Update a local page, an overlay URL, or its controls | Web layout can support more structured designs and scrolling | You need a designed ticker or more layout flexibility |
| Bible overlay project | Use the project’s own control panel and setup | Bible-oriented controls may be available | Your team wants dedicated overlay functions and can check compatibility and maintenance |
An OBS Browser source can load a local page or a URL, and its viewport dimensions are configurable; see the OBS Browser Source guide. A browser overlay can be a better fit when you need motion, multiple fields, or controls beyond a single text string. It is also a more involved design and support choice. A project such as PrimeBible for OBS documents browser-source controls and ticker-related features, but it is software rather than a requirement. Before relying on it for a service, check the project’s present instructions, compatibility and upkeep.
For many churches, the decision comes down to who will update the reading and how much information should move across the frame. Ask whether the operator can see the reading plan, whether a second person can take over, and whether scrolling is genuinely needed. Consider how the text will appear on a phone, where much of the audience may watch. No implementation makes the wording correct on its own; someone still needs to check the reference and translation.
Create a plain text file for the reading
Create a small plain text file that a volunteer can locate without searching through project folders. Give it a descriptive name, such as current-reading.txt, and save it somewhere the OBS computer can access. The file can contain only a reference, or a reference followed by the passage. Keep the text free of formatting that a plain text source cannot reliably display, such as font styling or decorative layout characters.
A practical first line might be “Reading: Psalm 23:1–4”. If you plan to show the full passage, put the reference first and the passage after it, with sensible line breaks. This helps the operator confirm what is currently displayed and gives viewers context. Try a short version first, then check the line length and overall height in the actual scene. A verse that wraps into several narrow lines may take up more of the frame than expected.
Make the file easy to edit in the operating system’s basic text editor. Avoid a word processor document saved in a rich-text format; OBS needs the text content in a file format that its source can read. Keep a clean working copy or template with a placeholder, so a volunteer can replace the words without changing the file’s location or name. If the selected translation has punctuation or characters that look different on screen, include those in a test before the service.
Agree a simple naming and handoff rule. For example, keep one active file called current-reading.txt and have the service leader provide the next passage reference before the reading begins. Do not create a new file for every verse unless the OBS source will be pointed at that file; changing a source path adds another task and creates an easy handoff mistake. If the file is moved or renamed, OBS may no longer be able to read it from its configured location.
The file’s contents are not a substitute for checking translation permissions. If you display repeated scripture text publicly, identify the version and review its publisher’s current conditions for online display, attribution, geography and the scale or nature of use. Crossway’s permissions page sets out conditions for ESV quotations; Biblica’s terms cover its NIV text and related terms. Permission for a printed bulletin or in-person projection should not be assumed to cover an online stream. Check the applicable current terms and seek permission when your planned use falls outside them; this article is not a legal determination.
Add an OBS Text source and enable Read from file
Open the OBS scene that feeds the church’s programme output. In the Sources panel, add a Text source and choose the option to create a new source or reuse an existing one as appropriate for your scene. The OBS Text Sources documentation describes text rendering and the Read from file setting. Select that setting, browse to the text file, and confirm the source settings.
OBS can have multiple scenes and sources, so check that you have added the ticker to the scene actually used for the broadcast, not only to a rehearsal or holding scene. If your programme output switches between scenes, decide whether the reading should appear in all of them or only during the reading scene. Reusing a source or copying it between scenes can be useful, but first confirm that it points to the intended file and is visible in the correct order.
The source’s position in the Sources list affects what covers it. A ticker placed beneath a full-screen image or video may be hidden. A ticker placed above a lower-third graphic can cover the name or other information. Use the visibility control to check that the source is enabled, then inspect the preview rather than assuming that its presence in the list means it is on screen.
If the text does not appear, check the file path, that the file is readable, that Read from file is selected, and that the source is enabled in the active scene. Also check whether another source is covering it. Those checks are more useful than repeatedly adding duplicate text sources, which can leave a scene cluttered and make later edits harder.
Style and position the ticker in the scene
Place the ticker where it does not cover a face, the pulpit, a Bible, a hymn lyric, a sign-language interpreter, or information viewers need to follow the service. A bottom strip is familiar, but it is not automatically the right place: a church may already use captions, lyrics, or a lower third there. Look at the complete programme frame and choose an area that remains clear in the scenes where the ticker will be shown.
Set a readable type size and strong contrast between text and its background. White letters over a bright camera shot can disappear; a solid or lightly translucent panel can help separate the text from the image. Test against both a dark scene and a bright one if the stream alternates between them. Avoid relying on a thin outline or subtle shadow to rescue text that is too small or too close in colour to the background.
Keep the reading concise enough to scan. If the passage is longer, consider showing the reference and one manageable section at a time, with a volunteer replacing the text at an agreed point. Scrolling may fit more words into a narrow band, but viewers have to wait for each line and may miss the beginning. A static reference is easier to maintain and usually simpler to read at a glance. The choice should reflect what the congregation needs, not a preference for animation.
Use OBS’s transform handles or source properties to size and position the text, and inspect the edges of the output frame. The OBS Sources Guide explains adding, positioning and sizing sources. A ticker close to the frame edge can be cropped on some displays or feel cramped. Leave visual breathing room, and check whether the church’s usual layout has reserved a safe area for captions or platform controls.
If the stream includes several scenes, test the source on each relevant scene. A position that works over a wide camera shot may land over a speaker’s face on a close shot. You can hide the source in scenes where it is not useful, or create scene-specific placements. Keep the setup understandable to the next operator: clear source names such as “Bible reading ticker” are more useful than a string of default labels.
Update the text during the broadcast
Treat the file as a small part of the service’s operating plan. Before the stream, tell the volunteer who supplies the next reference, who edits the file, and what cue means the displayed reading should change. A reader at the pulpit may not be the person watching OBS. Agree a handoff signal, such as a spoken announcement or a message from the service leader, rather than expecting the operator to infer the next passage from the audio.
When it is time to change the reading, open the active file, replace the old content, save it, and check the OBS preview. Keep the file path and name unchanged. If the text source is set to read from the file, the source uses that file for its displayed text; check the result after saving rather than assuming the change is visible. If it does not update as expected, verify the file and source settings before making a second version or changing the scene.
A short control routine reduces avoidable errors: confirm the reference with the service leader, prepare the wording in the file, save it, check spelling and verse range, then verify the preview. For a full passage, a second person can compare the text against the chosen Bible version before it is shown. That matters especially when an operator is working quickly or transcribing from a printed service sheet.
During an unattended continuous broadcast, a manually updated ticker cannot continue to follow a service that has no operator. It will keep showing whatever text is in the file and scene until someone changes or hides it. Decide what should happen outside the live service: leave a neutral reference, remove the reading source, or switch to a holding scene according to your existing broadcast plan. Do not leave a dated or service-specific reading on screen for hours by accident.
The ticker is part of the picture composed by OBS. YouTube’s encoder guidance describes connecting with a stream URL and key and starting the stream from the encoder. That basic workflow is not a guarantee that every church’s continuous broadcast will remain connected indefinitely, and it does not replace your existing continuity plan. Confirm that the ticker is in the outgoing OBS scene and preserve the way your team already monitors the stream. If your channel uses an image or holding scene between programmes, this guide to setting up a 24/7 stream with a static image between videos may help you think through what viewers should see between services.
A continuous channel also benefits from a clear division between content operation and broadcast operation. One volunteer can be responsible for the passage, while another watches the programme scene and stream status. If one person does both jobs, keep the file easy to edit and avoid adding unnecessary animated controls. A ticker is useful only when it does not distract the operator from the broadcast itself.
Preview and test changes before going live
Test the ticker in OBS before the service, with the same scene and programme composition you intend to use. Read the text at the preview size and check whether it remains legible over the real camera background. Confirm that the reference is accurate, that line breaks look deliberate and that no word is cut off. If you use a full passage, verify the opening and closing lines as well as the reference.
Ask someone other than the operator to look at the preview if possible. An operator who has been focused on setting up the source may not notice that the text is too small, too low, or competing with lyrics. A second pair of eyes can also catch a wrong passage or an old reading that remains in the file. Treat this as a practical check, not a claim that a particular layout works on every screen.
Do a simple change test: replace the placeholder with a different short reference, save, and confirm that the preview changes. Then restore the intended reading and check it again. This verifies the path and the volunteer’s update routine without waiting until the service is underway. If you alter the source size, scene or file location later, repeat the check.
Preview the whole output, not only the text source’s own box. Look for collisions with captions, logos, lower thirds and faces. Check the scene transitions that matter: a source can be visible in one scene and absent in another, or hidden by a source that sits above it. The OBS Sources Guide’s positioning instructions are useful when moving a source; your own scene preview is what tells you whether the final composition is clear.
Keep a fallback that does not depend on fixing a design mid-service. If the text appears incorrectly, the operator should be able to hide the ticker source and continue the broadcast, then correct the file between readings. A modest reference that can be hidden is often easier to recover from than an elaborate animated overlay. Record the source name, file location and update steps where the next volunteer can find them.
The ticker does not change how the rest of your channel is run. If your team is comparing a computer-led workflow with a cloud playout approach for a lecture or continuous programme, the comparison of YouTube Live Control Room and cloud playout covers a broader operational decision. For churches that already use a laptop in the broadcast chain, the Gujarati podcast archive setup guide is a relevant example of planning a YouTube Live workflow around local operation. Neither replaces the need to test this ticker in your own OBS scene.
For a church that already has a continuous programme and wants the operator’s computer out of the overnight path, StreamNeo removes the need to keep that computer running for the uploaded video stream; the ticker itself still needs to be prepared and managed as part of the OBS output when that is the workflow in use. Keep the reading process separate from decisions about how the wider channel is broadcast.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
Does OBS automatically show the verse the pastor is reading?
No. A Text source with Read from file displays the contents of the file you select. A volunteer must update the file when the reading changes; OBS does not identify spoken verses or retrieve them from a Bible database.
Can the ticker show a whole Bible passage?
It can display text from the file, but a long passage may occupy much of the frame or be difficult to read in a moving ticker. Test the passage in your actual scene and consider showing a reference or a smaller section at a time. Check the selected translation’s current publisher terms before displaying scripture publicly.
What should I do if the text does not change after I save the file?
First confirm that you edited the file selected by the source and saved it in the same location. Check Read from file, the source’s visibility and whether another scene item covers it, then look at the OBS preview again. Avoid adding duplicate sources until you know which part of the setup failed.
Is a browser overlay necessary?
No. A plain Text source reading a file is suitable for a manually updated reference or simple passage. A Browser source or Bible overlay project may suit a team that needs more design or dedicated controls, but it brings a separate setup and maintenance choice.