To show the current story title in an OBS scene, add a Text source and either enter the title directly or have the source read it from a text file. Keeping that title current is a separate job: a person or an external process must decide when the story changes and update the text.
That distinction matters on a 24/7 channel. OBS can display text, but a Text source does not know which story is playing and is not a story-feed connector. The practical setup is to make the display dependable first, then choose a manual or automated way to supply each new title.
Choose how the title will reach the screen
There are two straightforward ways to provide text to an OBS Text source. You can type a title into the source’s Text property, or you can enable its file-reading option and point it at a text file. The first is useful when the title rarely changes or you want to make a quick scene mock-up. A file is usually easier to operate when someone or something else must update the wording repeatedly.
With direct text, the wording lives in the OBS source properties. When a new story starts, an operator opens those properties, replaces the old title, and confirms the change. This is a simple arrangement for a short broadcast with an operator at the controls. Across an overnight schedule, it depends on someone being available at each transition, and edits made in the wrong scene or source can leave the old title on screen.
With a file-backed source, OBS reads the displayed text from a selected file rather than from the manually entered Text property. The file becomes a small hand-off point: the process that knows the current story writes a title there, and OBS displays what it reads. The process may be an operator, a scheduling application, or a script you have configured. Choosing file reading does not create that process for you.
| Method | Who supplies the new title | Useful when | Main operational risk |
|---|---|---|---|
| Text entered in OBS | An operator edits source properties | Titles change infrequently and someone is present | The old text remains if the operator misses a change |
| Text read from a file | A person or external process edits the file | You want a separate, repeatable update step | The file can be stale, misplaced, or updated at the wrong time |
| Script or WebSocket integration | An automation you configure updates a file or OBS source | A known schedule or application can reliably identify story changes | Setup and failure handling become part of the broadcast |
Start with the least complicated method that matches how your stories are selected. If your playlist simply repeats the same material and the title does not change, direct text may be enough. If a news loop rotates through separate items, a file-backed source gives an operator a clear place to update the label. If a scheduling system already tracks each item, you can assess whether it can write an update at the right time before adding a separate OBS integration.
For context on the wider playback arrangement, see how a playlist can run on YouTube Live around the clock. Playback order and title selection are related operational questions, but they are not the same thing: a playlist can run without sending its current item name to OBS.
Add and position a Text source
In OBS, select the scene that should carry the story label. If you do not yet have a suitable scene, create one in the Scenes dock. Scenes are compositions of sources, so the title is one layer in the scene rather than a separate YouTube setting. The OBS Studio overview explains the relationship between scenes and sources.
In the Sources dock, use the add control and choose the available Text source for your platform. OBS documents Text (GDI+) on Windows and Text (Freetype 2) on macOS and Linux; its documentation marks Freetype 2 as deprecated on Windows. Names and availability can depend on the installed OBS version, so use the source type offered by your current installation rather than following an old screenshot literally. The Text Sources guide describes the source properties.
Give the source a name you can recognise, such as “Current story title”. That small naming choice helps when a scene has several text labels, such as a station name, time, or presenter caption. If you have already created another text source, check carefully that you are editing the one intended for the story title, not a persistent label that should stay unchanged.
For a quick first pass, enter a sample title in the Text field and confirm that it appears in the preview. Make the lettering large enough to read at the intended viewing size, and choose a colour and outline or background treatment that remains visible over both bright and dark footage. A title over a devotional image, for example, may need a contrasting backing or edge treatment where pale lettering would disappear against a light background. Check the result over representative scenes rather than judging it against a blank canvas.
Position the source in the preview by dragging it, then resize it using its bounding box. OBS also offers Edit Transform for more precise placement. Keep the title inside the visible frame and leave room for other important content. A long story name can occupy more horizontal space than a short one, so test a realistic longest title before deciding that the box and font size are settled.
Source order matters. In the Sources dock, a source higher in the list appears above sources lower in the list. If the label is hidden behind a full-frame image or video source, move the title above the covering source; the OBS sources guide covers ordering, visibility, and transform controls. Do not solve a hidden label by making it larger until you have checked the layer order.
Connect the source to a title text file
Once the display works with sample text, connect the source to the file that will hold the current title. Open the Text source properties, enable Read from file, and select the intended text file. OBS describes this option as reading text from a file instead of the source’s Text property. From then on, the visible wording comes from that selected file, so typing a new title into the ordinary Text field is not the update path while file reading is enabled.
Put the file somewhere the operator or update process can find consistently. Avoid leaving it in a temporary folder or on a removable drive that might be disconnected. Use an informative name such as current-story.txt, and record its location in the channel’s operating notes. The file is not a YouTube upload or a stream key; it is a local input to the OBS scene. Do not put private credentials in it or display a stream key as part of an overlay.
Keep the contents simple. A single plain-text title line is generally easiest to maintain and troubleshoot. If the title includes punctuation or characters in a language used by your channel, test those exact characters in the selected Text source. The aim is not to build a data format inside a one-line label; it is to provide readable wording without extra markup, debug text, or blank lines appearing on screen.
Before relying on the file, confirm that OBS can read it under the account and machine used for the broadcast. If the text does not appear, check the selected path, whether the file exists, whether the source is visible, and whether another layer is covering it. Also check the source’s properties to ensure Read from file is enabled. Those checks separate a display problem from a failure to supply an updated title.
If the channel runs from a prepared sequence of videos, note that the list of files and the title file may need to be maintained separately. The guide to turning existing YouTube uploads into a 24/7 live channel can help frame the playback side, but it does not change OBS’s text-source behaviour. Decide which record is authoritative for the current item, then make the update process use it consistently.
Update the file when the story changes
For a manually operated stream, assign a person to replace the file’s contents whenever the story changes. The procedure should identify the exact file, the point at which the new title becomes current, and who checks the overlay. A short checklist can be enough: confirm the next item, replace the previous title, save, look at the OBS preview, and confirm the title corresponds to what viewers are seeing.
Avoid keeping several near-identical copies such as title-new.txt, title-final.txt, and title-final2.txt and then guessing which one OBS reads. A clear single path reduces wrong-file updates. If the title is prepared in another document or scheduling tool, make the hand-off explicit: someone must copy the approved title into the file OBS actually uses, unless you have configured an integration to do so.
A manual file update is not automatic merely because OBS reads the file. OBS handles the display end; your operating procedure handles the decision and update. That can be the right trade-off for a small local news loop where a person already supervises transitions. It is less suitable when the channel is unattended and titles change overnight, unless there is a dependable person or separate system that can make the update.
Write down what should happen if the title cannot be confirmed. For example, you might keep a neutral programme label visible rather than leave a specific but outdated story name on screen. The appropriate fallback depends on the channel and its editorial practice. What matters is that a missed update does not silently turn yesterday’s title into a claim about today’s content.
Also decide whether the title should update at the start of a new item or a little earlier. Updating too early can label the end of the previous story with the next one; updating too late can leave the new item without a label. The transition rule belongs to the person or system that understands the programme schedule, not to the visual Text source.
Automate only when the source of truth is clear
Automation is useful when another process already knows which story is current. That process might be a schedule you control or an application that advances items. Before connecting it to OBS, establish where the current item is recorded, how a change is detected, what title should be used, and how a failed update will be noticed. Without those answers, automating text changes can make an unreliable assumption happen faster rather than solve the underlying problem.
The simplest automated route may still be file-based: configure the process that selects or schedules the story to write the current title to the same text file OBS reads. This keeps the visual source uncomplicated. Test what happens at an item boundary, on a skipped or delayed item, and after the process restarts. Confirm whether the file is rewritten in a way OBS can read and that it does not briefly show an incomplete title during an update.
OBS also supports Python and Lua scripting, and an external application can interact with OBS through WebSocket. The OBS developer guide and remote control guide describe these interfaces. They are tools for building an integration, not a ready-made connection to a story feed. You still need a separate source of current-story information and logic that maps it to the title shown in your scene.
Choose a direct OBS update only if there is a reason to control the source itself rather than write a file. A script or WebSocket client can be useful when an existing workflow already talks to OBS or needs to change other scene properties at the same transition. It also adds configuration and another point to check when a title stops changing. If your only requirement is one line of text, a file-writing route may be easier for another operator to understand and recover.
Protect any remote-control connection. OBS’s remote control documentation recommends a password for WebSocket, and the guide notes that WebSocket is included by default in OBS Studio 28 and later. Keep credentials out of public overlays and notes, restrict access to the people or applications that need it, and consult the current OBS guide for the settings in your version. Do not expose a control endpoint casually to the wider network.
There is no need to add automation just because the channel runs all day. If a title changes only when an operator is present, a manual workflow may be more transparent. If the channel cannot be supervised at each transition, automation may be appropriate, but only after its input and recovery behaviour have been tested. For multi-channel scheduling considerations, see services for scheduling several 24/7 YouTube channels in India; scheduling a broadcast and supplying an accurate on-screen title remain distinct responsibilities.
Test the title change before going live
Test the full change, not just the appearance of the first title. Put a clearly different sample title in the file and observe whether the displayed text changes. Then test a title with the likely maximum length and the scripts or punctuation your channel uses. Confirm that it remains legible, fits the intended area, and does not cover important parts of the video.
Check more than one scene if the title source is used across multiple scenes. A source may be present in one scene but absent or hidden in another. Confirm visibility, ordering, position, and size in each scene where the title is expected. If you duplicate scenes or alter them later, repeat the check so that a layout change does not quietly remove the label.
Run a rehearsal through an actual story transition. Verify that the outgoing story remains labelled correctly until it ends, that the new title appears at the intended moment, and that the source process has not left stale text behind. If an operator performs the update, have them follow the written procedure without relying on memory. If a script or external app performs it, test the no-update case and decide how someone will notice that the expected change did not happen.
Inspect the programme preview and, when appropriate, a private or otherwise controlled test stream before the public broadcast. The complete scene should be checked at the size and quality viewers will encounter, not only in a close-up of the OBS canvas. OBS recommends testing scenes and settings before an initial stream in its Studio overview. For a live encoder workflow, YouTube’s streaming with an encoder instructions describe using the Live Control Room’s stream URL and stream key in encoder settings. Keep the key private.
Do not infer uninterrupted operation from a successful rehearsal. A text overlay can be correctly configured while the encoder, machine, or update process later stops. YouTube’s cited help page says streams under 12 hours are automatically archived; it does not settle archive behaviour for one uninterrupted 24/7 broadcast. Check YouTube’s current guidance for the workflow you use, and plan separately for stream continuity and title updates.
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 adding an OBS Text source make the story title update automatically?
No. The Text source displays text that you enter or that it reads from a file. A person or an external process must determine when the current story changes and supply the new title.
Should I use direct text or a text file?
Direct text is convenient when titles change rarely and an operator can edit the source at the right time. A file is useful when you want a separate, repeatable hand-off or another process can write the title, but someone still needs to maintain or configure that process.
Can OBS connect directly to my news or playlist feed?
The reviewed OBS documentation describes text sources, scripting, and WebSocket control; it does not document a turnkey story-feed connector. If you build an integration, identify a reliable source of current-item information and test how it handles transitions and missed updates.
Will the title overlay keep the stream running all night?
No. The title overlay affects what is displayed, not whether the broadcast or the process supplying titles remains active. Test the complete setup and monitor the relevant parts of your own workflow; no title-source configuration guarantees uninterrupted streaming.